This project was formed to work together on the Drupal community's governance process and structure and policies. If you're interested in specific issues regarding governance, take a look in the issue queue and add more if you'd like.
The repository holds a collection of charters relating to Drupal community governance working groups, as well as a place to hold discussion about said policies. These charters are currently solely maintained by Dries Buytaert. Other governance policy documentation can be found at About Drupal: Governance.
For the Drupal project, we are working towards developing a number of working groups related to various aspects of the community (security, documentation, conflict resolution, Drupal core, etc.), with Dries Buytaert as the final decision-maker:
In the case of the Drupal.org websites, however, it makes sense for this final decision-maker to be the Drupal Association, since they are ultimately responsible for the website, purchasing hardware, etc.
- Community Working Group (Background discussion: )
- Technical Working Group (Background discussion: )
- Drupal.org Infrastructure Working Group (Background discussion: )
- Drupal.org Software Working Group (Background discussion: )
- Drupal.org Content Working Group (Background discussion: )
Coming soon: Security Team, Documentation Team, Drupal Core N Working Groups.
Original community governance proposal as a result of sprint in Portland: http://buytaert.net/drupal-governance-sprint
Revised proposal for Drupal community vs. Drupal.org governance: http://buytaert.net/creating-a-structure-for-drupal-governance
This project was originally created as a response to the Drupalcon Denver Core Conversations on Governance and Painting the Bikeshed. For background the blog series at randyfay.com/topics/governance may be useful.
Needing more governance is a good problem to have. It means we're collaborating, growing, and building things!