Drupal Governance

The TWG coding standards committee is announcing two coding standards changes for final discussion. These appear to have reached a point close enough to consensus for final completion. The new process for proposing and ratifying changes is documented on the coding standards project page.

The two issues being proposed are:

The security working group is proposing this policy around disclosure of private information. We are seeking community feedback.

In the past our policy has been a tad thin.

“State that you are willing to keep the confidential issues of the team confidential”

This document aims to add clarity to that sentence and some example scenarios to guide team members decision making.

We are seeking public feedback before making this a policy.

The policy is attached as a PDF.

Please provide feedback by commenting on the post

The Drupal project just turned 14 years old. There are now over 1 million known installations of Drupal, and Drupal.org has over 1 million users. Drupal 8 has over 2,700 contributors (almost three times that of Drupal 7) and over 13,000 commits so far (50% more commits per day on average than Drupal 7). I wanted to take an opportunity to reflect on our current governance structure and try to evolve the Drupal leadership team and decision-making, enable better scaling, and document both the formal and informal processes we have currently in place.

In previous posts, we’ve talked about who the Community Working Group (CWG) is and why we’re here, as well some of the work we’ve done around establishing a process for conflict resolution in the Drupal community.

In this post, I’d like to go into more detail about what happens when folks file incident reports with the Community Working Group, and open up the conversation on how we can more effectively address issues that have a larger impact on the Drupal community as a whole.

Greetings from your friendly neighbourhood Drupal.org Software Working Group!

https://drupal.org/node/2261945 has a proposal + mockups on a new way to handle feature requests for Drupal.org in order to help both the Drupal.org Software Working Group and other working groups prioritize the feature roadmap for Drupal.org. Since this tool will become the method through which the Drupal community (in the widest sense of the word) makes known their Drupal.org needs/wants/desires, we'd love to hear your comments and feedback on the proposal.

Michael Hess, Greg Knaddison, Mori Sugimoto, Ben Jeavons, Matt Chapman, Angie Byron and myself have been working on the charter for the Security Working Group (DocWG). The mission of the SecWG is to ensure that Drupal core and Drupal's contributed project ecosystem provide world-class security, and to provide security best practices for site builders and module developers. The work is part of our work on evolving and streamlining the Drupal project's governance.

The Drupal.org Software Working Group is looking for volunteers to take on leadership roles and help guide development of the Drupal.org Community Tools, which include Forums, Drupal Planet, User Groups (groups.drupal.org), User Profiles, User Dashboard.