The Drupal Code of Conduct, heavily borrowed from our friends at Ubuntu, does an excellent job enshrining the characteristics we aim to foster, in order to ensure people "Come for the software, stay for the community". However, there are still some gaps. For example, how to deal with conflict resolution, and how an individual best goes about proposing new governance policies.
Key Drupal contributor Randy Fay has done a tremendous amount of research into governance models of other open source projects, which you can read more about on his blog. For those who have not been following Randy's posts, he and I are holding a sprint about Drupal Governance on July 16 and 17 in Portland, Oregon just after the Community Leadership Summit. Randy, Angela Byron, Greg Dunlap, David Strauss, and myself will be in attendance.
This sprint is a first for Drupal. The goal of this sprint is to come up with a proposal for subsequent community discussion with recommendations around some of the following topics:
- Processes to create and maintain policies, as a general concept
- A process for resolving technical conflicts
- A process for resolving community/interpersonal conflicts
- A process and team for resolving "nuclear" issues that need extremely delicate handling.
If you have other topics you'd like to propose, or would like to provide feedback on these items in advance of the sprint, please chime in in the Governance project issue queue. It is important work to streamline and evolve the governance of our project, so thanks in advance for your contributions.
— Dries Buytaert
Dries Buytaert is an Open Source advocate and technology executive. More than 10,000 people are subscribed to his blog. Sign up to have new posts emailed to you or subscribe using RSS. Write to Dries Buytaert at firstname.lastname@example.org.