Heather VanCura, Vice President of Oracle, responsible for community engagement, introduced the second phase of the initiative aimed at bridging the gap with the community and accelerating the development of MySQL. While the first phase focused on enhancing process transparency and engaging the community in defining MySQL's development path, the second phase will concentrate on involving community representatives in development. Among the goals mentioned are accelerating innovation, providing clear pathways for implementing changes, and expanding the MySQL ecosystem.
To implement this intention, a Steering Committee has been established, which will include representatives from the community, define the strategy for the development of MySQL, and serve as a liaison with the MySQL ecosystem. The initial composition of the committee will include representatives from Amazon Web Services (AWS) and Google Cloud, in addition to Oracle employees.
The committee will address issues related to long-term development priorities, expanding the ecosystem, modernizing project management, involving the community in development, and gathering feedback from the community. The committee will not replace technical leadership and will not interfere with day-to-day development processes.
To engage community representatives in the work, a new management model has been proposed, which defines the following roles:
- Contributors write code, test, review, document, and participate in technical discussions. A contributor can be a community representative, not just an Oracle employee.
- Committers review changes and ensure code quality. Initially, the team of committers will be formed from Oracle employees, but in the future, committer rights may be granted to well-established community contributors.
- Project leads are responsible for making technical decisions and planning development in specific areas such as toolsets, optimizers, runtime, InnoDB, and so on.
- The Core Project lead is responsible for the MySQL Community Edition product.
- The Vulnerability Group is responsible for handling vulnerability reports, coordinating the fixing of vulnerabilities, and disclosing information about security issues.
The management model was developed based on discussions at the MySQL Contributor Summit, which included organizations such as Amazon Web Services (AWS), Google Cloud, Percona, ProxySQL, Readyset, VillageSQL, and the MariaDB Foundation.
Source: opennet.ru
