OpenStack

Field	F/LOSS, technology
Scope	online, offline
Source	https://www.openstack.org/legal/community-code-of-conduct/
Related	Django

THE OPENSTACK FOUNDATION COMMUNITY CODE OF CONDUCT

The OpenStack community is made up of a mixture of professionals and volunteers from all over the world, working on every aspect of the OpenStack mission. We strongly believe diversity is our strength and want to promote an inclusive and safe environment.

To that end, we have a few ground rules for engaging in the community. The OpenStack Foundation (“Foundation”) has adopted the following code of conduct (“OpenStack Code of Conduct”) which applies equally to all community participants, including board members, committee members, project team leads, core contributors, mentors, user group leaders and participants, and those seeking help and guidance. Because of the laws governing employees which would supersede any contract, in some circumstances, the Foundation staff may be subject to a separate procedure.

This OpenStack Code of Conduct also applies to all spaces managed by the Foundation or authorized by the Foundation, including IRC channels, the mailing lists, issue trackers, Foundation sponsored events and any other forums the OpenStack community uses which are managed by the Foundation (“OpenStack Venues”), including without limitation the Open Infrastructure Projects. In addition, violations of this OpenStack Code of Conduct outside of OpenStack Venues may affect a person's ability to participate within them after appropriate investigation. For the twice-annual OpenStack Summit, please also see the event-specific code of conduct on the Summit website with additional details for speakers, sponsors and attendees.

We do not tolerate harassment in any form. If you believe someone is violating the OpenStack Code of Conduct, please see our Reporting Guidelines below.

OpenStack community members strive to

• Be friendly, patient and welcoming. We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to, members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion and mental and physical ability.

• 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. Remember that we're a world-wide community and we have a global base of users and of contributors. Even if it's not obvious at the time, our contributions to projects managed by the OpenStack Foundation will impact the work of others.

• Be respectful. Not all of us will agree all the time, 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. Members of the community should be respectful when dealing with other contributors as well as with people outside of the community and with users of the projects managed by the OpenStack Foundation.

• Collaborate openly. Collaboration is central to projects managed by the OpenStack Foundation and to the larger free software community. This collaboration involves individuals working within teams, cross-project collaboration within the OpenStack Foundation and working with other projects outside of the OpenStack community. 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. We do not create private forms of communication that take away transparency or exclude other contributors and collaborators.

• When we disagree, try to understand why. 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. Remember that we’re different. The strength of the OpenStack community comes from its varied community, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Focus on helping to resolve issues and learning from mistakes. It is important that we resolve disagreements and differing views constructively and with the help of the community and community processes. We have a series of governance bodies which help to guide the right course for projects managed by the OpenStack Foundation. 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.

We take the following very seriously, and any violations may impact your ability to participate in the OpenStack community

• Be careful with your words and actions. We are a community of professionals, and we conduct ourselves professionally. Do not insult or put down other participants. Harassment and other exclusionary behavior is not acceptable and should be reported. This includes but is not limited to:
  • Violent threats or language directed against another person.
  • Discriminatory jokes and language.
  • Posting sexually suggestive, explicit or violent material.
  • Posting (or threatening to post) other people's personally identifying information ("doxing").
  • Personal insults, especially those using racist or sexist terms.
  • Unwelcome sexual attention.
  • Advocating for, or encouraging, any of the above behavior.
  • Repeated harassment of others. In general, if someone asks you to stop, then stop.

• Respect the election process. Members of the OpenStack community should not attempt to manipulate election results. Open debate is welcome, but vote trading, ballot stuffing and other forms of abuse are not acceptable.

Reporting Guidelines

If you believe that the OpenStack Code of Conduct is being violated, you are being harassed, or have any other concerns, please contact a member of the Foundation staff immediately via phone or email.

The Foundation staff (“Staff”) who manage these issues have the following contact information:

Jonathan Bryce, jonathan@openstack.org, cell # +1-210-317-2438 Allison Price, allison@openstack.org, cell # +1-214-686-6821

Process to file complaint

• Please report violations of the OpenStack Code of Conduct at the OpenStack Venues immediately to Staff.

• Please be prepared to provide as much of the following information as possible about the alleged violation:
  • Identifying/contact information of the person you believe is violating the OpenStack Code of Conduct
  • Contact information of the complainant or the person who was the target of the violation
  • The behavior that was in violation, approximate time and circumstances
  • Other people involved in the incident
  • Whether or not you would prefer to have your complaint be kept anonymous in the situation

• Staff will be responsible for notifying the alleged offender of complaint, investigating the complaint, determining the violation, if any, determining the appropriate penalty and communicating the resolution to the alleged offender and the target of the violation of the OpenStack Code of Conduct.

• Best Practices for participants:
  • You should not feel the need to engage directly or further with the alleged offender, the Staff is there to support you or bring in additional resources.
  • If you feel your safety is in jeopardy please do not hesitate to contact law enforcement.
  • When reporting the incident to Staff, try to gather as much information as available, but do not interview people about the incident.
  • Staff will assist you in writing the report/collecting information.

Staff response procedure

• Staff are well-informed of OpenStack Code of Conduct and response procedures.

• Staff will gather details of the complaint to make an initial report, including:
  • Whether or not there is immediate or physical danger, in which case Staff should contact local authorities
  • Identifying information of the person accused of violation of the OpenStack Code of Conduct.
  • The behavior at issue, approximate time and circumstances
  • Other people involved in the incident
  • Whether or not the reporting party prefers to remain anonymous

• Staff will try to get as much information on the incident in written form by the reporter, or will otherwise record the information about the incident as it was told to them.

• Staff will make an initial response to the complainant which will include:
  • Do they need help?
  • Do they need to be connected with a safe person, friend or family member?
  • Do they need a safe space?

• Staff will make the complainant aware of the response procedure and next steps to feel confident action is being taken, but avoid the following:
  • Do not overtly invite them to withdraw the complaint or mention that withdrawal is OK. This suggests that you want them to do so, and is therefore coercive. "If you're OK with it [pursuing the complaint]" suggests that you are by default pursuing it and is not coercive.
  • Do not ask for their advice on how to deal with the complaint. This is a Staff responsibility
  • Do not offer them input into penalties. In certain cases, it may be appropriate to ask complainant what it would take for the alleged offender to “make it right” such as an apology. However, the determination of any penalties, including restrictions on future participation in the OpenStack Venues is at the sole discretion of the Staff.

• After taking any initial action required to care for the complainant, Staff will notify Foundation Executive Director, who will determine:
  • If there is a need to bring in legal counsel, authorities or additional resources
  • If public communications are required in the case of a public incident
  • If additional information gathering is required from witnesses, Staff or other parties

• Staff or Executive Director will notify the alleged offender of the complaint and allow for response as part of the investigation and before reaching conclusion or applying any penalty. In the meantime, the alleged offender and complainant (or target of the violation) should not have any contact.

• Following the conversation, Staff will convene to review the available information and consider appropriate action, which may include:

• • Reaching a conclusion about a violation of the OpenStack Code of Conduct occurred
  • Determining whether it is appropriate to ask/suggest that the complainant and alleged offender consider a joint meeting in the presence of a neutral third party to address their perspectives

• Where violation of the OpenStack Code of Conduct is found, the Staff may take any one or more of the following actions:

• • Direct the offender to cease the behavior and warn that any further violations will result in sanctions
  • Requiring the offender to avoid any interaction with, and physical proximity to, the complainant anywhere in the OpenStack Venues
  • Banning the offender from IRC channels or mailing lists or other communications channels controlled by the Foundation
  • Ending any volunteer responsibilities or privileges that the offender holds from the Foundation (either indefinitely or for a certain time period)
  • Requiring that the offender immediately leave a Foundation sponsored event and not return
  • Banning the offender from future Foundation sponsored events (either indefinitely or for a certain time period)
  • Removing the offender from membership of the Foundation and OpenStack community roles and responsibilities

• Staff will then inform the offender of what action, if any, will be taken against them.

• Staff will then inform complainant (and other involved persons, to the extent appropriate) of the resolution, and record the outcome.

Portions of the OpenStack Code of Conduct are derived from the PyCon Conference Code of Conduct, licensed under Creative Commons Attribution 3.0 Unported License, and the Django Project Code of Conduct.