Jump to: navigation, search

Difference between revisions of "Governance/Foundation/CommunityCodeOfConduct"

m (Protected "Governance/Foundation/CommunityCodeOfConduct": Reference page ([Edit=Administrators only] (indefinite) [Move=Administrators only] (indefinite)))
(No difference)

Revision as of 21:06, 16 February 2013

Appendix 6


This Community Code of Conduct covers our behavior as members of the OpenStack Community, in any forum, mailing list, wiki, web site, IRC channel, public meeting or private correspondence. OpenStack members and governance bodies are ultimately accountable to the OpenStack Board of Directors.

  • Be considerate. 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. OpenStack has a global base of users and of contributors. Even if it's not obvious at the time, our contributions to OpenStack will impact the work of others. For example, changes to code, infrastructure, policy, documentation, and translations during a release may negatively impact others' work.
  • Be respectful. The OpenStack community and its members treat one another with respect. Everyone can make a valuable contribution to OpenStack. 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 OpenStack community to be respectful when dealing with other contributors as well as with people outside the OpenStack project and with users of OpenStack.
  • Be collaborative. Collaboration is central to OpenStack and to the larger free software community. This collaboration involves individuals working with others in teams within OpenStack, teams working with each other within OpenStack, and individuals and teams within OpenStack 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 and downstream 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.
  • When we disagree, we consult others. Disagreements, both social and technical, happen all the time and the OpenStack community is no exception. It is important that we resolve disagreements and differing views constructively and with the help of the community and community processes. We have the Technical Board, the User Committee, and a series of other governance bodies which help to decide the right course for OpenStack. There are also Project Core Teams and Project Technical Leads, who may be able to help us figure out the best direction for OpenStack. When our goals differ dramatically, we encourage the creation of alternative implementations, so that the community can test new ideas and contribute to the discussion.
  • When we are unsure, we ask for help. Nobody knows everything, and nobody is expected to be perfect in the OpenStack 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 forum.
  • Step down considerately. Members of every project come and go, and OpenStack 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.
  • Respect the election process. Members should not attempt to manipulate election results. Open debate is welcome, but vote trading, ballot stuffing and other forms of abuse are not acceptable.

We pride ourselves on building a productive, happy and agile community that can welcome new ideas in a complex field, and foster collaboration between groups with very different needs, interests and goals.

Mailing lists and web forums

Mailing lists and web forums are an important part of the OpenStack community platform. This code of conduct applies to your behavior in those forums too. Please follow these guidelines in addition to the general code of conduct:

  1. Please use a valid email address to which direct responses can be made.
  2. Please avoid flamewars, trolling, personal attacks, and repetitive arguments. On technical matters, the Technical Review Board can make a final decision. On matters of community governance, the Community Council can make a final decision.