Everyone is welcome to the table. Here are our guidelines for participation, conduct, and enforcement. We’re also aware that by saying „everyone“ we’ll have a lot of people from many different backgrounds. And that’s a good thing. It’s impossible to embark on the kind of journey we envision without making this community large, inclusive, and occasionally a little spirited. No one is perfect, certainly not us. But we strive to have open and honest conversations, behave well, and do something good for humanity.

Code of Conduct

This code of conduct aspires to support a community where all people should feel safe to participate, introduce new ideas and inspire others. It applies to all spaces managed by Both/And gUG (hereafter Both/And), including all communication channels used by our communities such as public and private mailing lists, issues trackers, wikis, blogs, social media and messaging services. We expect this code of conduct to be honoured by everyone who participates in the Both/And community formally or informally, or claims any affiliation with Both/And. This code further serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so it can enrich everyone who participates.


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 sensitive or private topics. This applies to messages for 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 empathic, 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 do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not productive. We should be respectful when dealing with other community members as well as with people 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 are 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 avoids many problems later, so questions are encouraged though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goals.

Be careful in the words that we choose. Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behaviour are not acceptable.
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 („doxing“).
  • Sharing private content, such as emails or messages sent privately or non-publicly.
  • Personal insults, especially those using racist or sexist terms.
  • Unwelcome sexual attention.
  • Excessive or unnecessary profanity.
  • Repeated harassment of others. In general, if someone asks you to stop, then stop.
  • Advocating for, or encouraging, any of the above behaviour.

Be concise. Keep in mind that what you write once will be read by hundreds of people. Writing a short email or message means people can understand the conversation as efficiently as possible. Short emails or messages should always 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 message 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 and contributors 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.

Diversity Statement

Both/And welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining. Although we may not be able to satisfy everyone, we will always strive to treat everyone well.
No matter how you identify yourself or how others perceive you: we welcome you. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability. And if there’s something we missed let us know.
Though we welcome people fluent in all languages, Both/And development and communication is mainly conducted in English. Standards for behaviour in the Both/And community are detailed in the Code of Conduct above. We expect participants in our community to meet these standards in all their interactions and to help others to do so as well.

Reporting Guidelines

While this Code of Conduct should be adhered to by participants, we recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. When that happens, you may reply to them and point out this code of conduct. Such messages may be in public or in private, whatever is most appropriate. However, regardless of whether the message is public or not, it should still adhere to the relevant parts of this Code of Conduct; in particular, it should not be abusive or disrespectful.
If you believe someone is violating this Code of Conduct, you may reply to them and point out this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your compliance issues in confidence to:


This Code of Conduct is a modified version of The Apache Software Foundation’s Code of Conduct licensed under the Apache License, Version 2.0 with additional text and inspiration from the Mozilla Foundation’s Community Guidelines. We’re very grateful for their work and support them in their efforts.