- Issue created by @quietone
- Status changed to Needs work
3 months ago 12:42pm 17 September 2024 - 🇭🇺Hungary Gábor Hojtsy Hungary
Thanks for starting on this! "Within the core committer team", "while core committers", etc. still has the old terminology.
- Status changed to Needs review
3 months ago 4:17am 18 September 2024 - 🇳🇿New Zealand quietone
1) And the way it is written the Project lead is not a core committer and thus not part of the Leadership team.
2) The changes so far disagree with this existing statement
### Core initiative facilitator ([\#](#core-initiative-facilitator)) Initiative facilitators are members of the committer team who help with multiple initiatives and assist individual [initiative coordinators](#initiative) to work effectively with the core team and other initiatives.
It may be better to rework this to remove all changes and replace with a single new section that only define membership in the Core Leadership Team.
- 🇳🇿New Zealand quietone
So, at the top add
## The Drupal Core Leadership team The Drupal Core Leadership team is the team responsible for all aspects of Drupal core. The team members are - **Project Lead** - **Core Committers** - **Initiative Coordinator** These roles are defined later in this document.
- 🇭🇺Hungary Gábor Hojtsy Hungary
There seem to be contradictions in the current proposed text, where the leadership team is defined as people with commit access, while also defined separately as being wider than the people who are the core committers. I'll try to propose something.
- 🇭🇺Hungary Gábor Hojtsy Hungary
I think the leadership team was meant to be the "extended core committer team", so this structure. Started updating the text to this, but it definitely needs more work.
- **Project Lead**: The chief decision-maker for the project. - **Leadership Team**: A team, including the Project Lead with varied skills who make decisions about the general direction of the project. Roles within the leadership team are: - **Product Managers**: Focus on user-facing features and Drupal's user experience. - **Framework Managers**: Focus on cohesiveness of Drupal's architecture, APIs, and developer experience. - **Backend Framework Managers**: are collectively responsible for PHP, bash, and database APIs. - **Frontend Framework Managers**: are collectively responsible for Twig, HTML, CSS, and JavaScript APIs. - **Release Managers**: Focus on processes to increase release stability, and on facilitating effective collaboration among contributors. - **Team Facilitator**: responsible for meetings within the core leadership team, with the Drupal Association, and with the community. - **Initiative Facilitator**: helps with multiple initiatives and assist individual initiative coordinators to work effectively with the core team and other initiatives. - **Committers**: A subset of the Leadership Team. People who can commit changes to Drupal core itself. - **Subsystem Maintainers**: Maintainers of one particular part of Drupal core, such as the Entity system or Comment module. - **Topic Maintainer**: Subject-matter experts in a topic that spans multiple subsystems—Accessibility, Documentation, Performance, Testing, and Usability. These correspond to the [core gates](https://www.drupal.org/core-gates) which all proposed changes must pass. - **Initiative Coordinator**: Community members appointed by the Project Lead to coordinate strategically important work. Initiatives are typically cross-functional in that they span different subsystems and different topics, and can affect both Drupal the product and Drupal the framework.
- 🇳🇿New Zealand quietone
@gábor hojtsy, thanks those changes made a lot of sense.
I made a few grammar and spelling changes. I did find it a bit odd that the Project Lead was not listed within the team in the list of roles. So, I moved things around a bit so that all the roles in the leadership team are before other roles, and in the same order as the list of roles.