Last updated August 29, 2010.
As our community grows, it is imperative that we preserve the things that got us here; namely, keeping Drupal a fun, welcoming, challenging, and fair place to play. The Drupal Code of Conduct (DCOC) states our shared ideals with respect to conduct. Think of this as coding standards for people. It is an expression of our ideals, not a rulebook. It is a way to communicate our existing values to the entire community.
Our friends at Ubuntu have blazed a brilliant trail in this area. They use Drupal as their CMS, and in turn we have embraced their Code of Conduct.
This code of conduct is essentially identical to that used by Ubuntu, except that the name of the project has been changed, and the conflict resolution process has been removed since we don't have one.
Discussion about this policy belongs in the Drupal.org Policies group
Our work will be used by other people, and we in turn will depend on the work of others. Any decision we take will affect users and colleagues, and we should take those consequences into account when making decisions. Drupal has millions of users and thousands of contributors. Even if it's not obvious at the time, our contributions to Drupal will impact the work of others. For example, changes to code, infrastructure, policy, documentation, and translations during a release may negatively impact others' work.
The Drupal community and its members treat one another with respect. Everyone can make a valuable contribution to Drupal. We may not always agree, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the Drupal community to be respectful when dealing with other contributors as well as with people outside the Drupal project and with users of Drupal.
Collaboration is central to Drupal and to the larger free software community. This collaboration involves individuals working with others in teams within Drupal, teams working with each other within Drupal, and individuals and teams within Drupal working with other projects outside. This collaboration reduces redundancy, and improves the quality of our work. Internally and externally, we should always be open to collaboration. Wherever possible, we should work closely with upstream projects and others in the free software community to coordinate our technical, advocacy, documentation, and other work. Our work should be done transparently and we should involve as many interested parties as early as possible. If we decide to take a different approach than others, we will let them know early, document our work and inform others regularly of our progress.
If and when we choose to adopt a more extensive or formal conflict resolution process, we will add to this section. But for now, the title says it all.
Nobody knows everything, and nobody is expected to be perfect in the Drupal community. Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked questions should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate place.
Members of every project come and go and Drupal is no different. When somebody leaves or disengages from the project, in whole or in part, we ask that they do so in a way that minimizes disruption to the project. This means they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off.