CODE OF CONDUCT

SPECIFIC GUIDELINES

We strive to:

• Be open. We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages regarding help or project-related support, too. Not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.
• Be empathetic, welcoming, friendly, and patient. We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we can not allow frustration to turn into any sort of personal attack. After all, a community where people feel uncomfortable or threatened is not a productive one. It's imperative for all to remain respectful when dealing with other community members as well as those outside of our community.
• Be collaborative. Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of the project, we must be willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.
• Be inquisitive. Nobody knows everything! Asking questions early on avoids many problems later. Thus, questions are encouraged, although they ought to be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving the Evil Bees codebase.
• Be careful in with words you choose to use. Whether you are are participating as a professional or a volunteer, we value professionalism in all interactions, and take responsibility for our own words. Be kind to others. Never insult or put down other participants. Harassment and other exclusionary behavior are not acceptable nor will they be tolerated. This includes, but is not limited to:
  • Violent threats or language directed against another person.
  • Sexist, racist, or otherwise discriminatory jokes and language.
  • Posting sexually explicit or violent material.
  • Posting (or threatening to post) other people's personally identifying information ("aka doxing").
  • Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
  • Personal insults, especially those with racist or sexist undertones.
  • Unwelcome sexual attention.
  • Excessive or unnecessary use of profanities.
  • Repeated harassment of others. In general, if someone asks you to stop, then stop.
  • Advocating for, or encouraging, any of the aforementioned behavior or language.
• Be concise. Keep in mind that what you write once will be read by hundreds of people. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should also strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary. Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made. Try to stay on topic, especially in discussions that are already fairly large.
• Step down considerately. Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.