The Age of Peers Community Code Of Conduct

Age of Peers is made up of a mixture of professionals from all over the world, working on every aspect of the Age of Peers platform. We strongly believe diversity is our strength and want to promote it.

This CoC does not include any measures in case of violations, but is primarily meant to endorse our sense of community made up of all Age of Peers team members, clients, partners and projects AoP guides on a pro-bono basis.

To that end, we have a few ground rules for engaging in the community. Age of Peers has adopted the following code of conduct (“OpenStack Code of Conduct”) which applies equally to all Age of Peers team members, our clients, partners and projects we guide on a pro-bono basis.

This Age of Peers Code of Conduct also applies to all communication spaces used by Age of Peers, including IRC channels, the mailing lists, issue trackers, Age of Peers sponsored events and any other forums Age of Peers uses.

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 the OpenStack project 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 OpenStack community should be respectful when dealing with other contributors as well as with people outside of the OpenStack project and with users of the OpenStack project.
  • Collaborate openly. Collaboration is central to the OpenStack project and to the larger free software community. This collaboration involves individuals working within teams, cross-project collaboration within the OpenStack project 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 the OpenStack project. 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.