By using the software and services we provide, you agree to our Terms of Service, including our Privacy Policy and the following Code of Conduct. It explains the "dos and don’ts" when interacting with our team and other community members.
Last Updated: May 13, 2023
Because we want our Code of Conduct to be easy to understand and implement, we have only three basic rules, numbered in order of importance:
(1) Be respectful, be responsible, be kind.
(2) Don’t panic.
(3) Don’t feed the trolls.
Not everyone has experience with Open Source communities and intuitively knows what is acceptable. In that case, the following guidelines and examples are meant to provide a quick overview and help you avoid the most common pitfalls:
(a) Do not feel entitled to free software, support, or advice, especially if you are not a contributor, member, or paying customer. Don't expect contributors to report to you and meet deadlines as if they work for you or owe you something, even if you donated a small amount. We also ask that you do not use GitHub Issues or other development tools to start general discussions, get technical support, or express personal opinions.
(b) Honor Rule #2, read the docs and determine the cause of your problem before opening invalid bug reports, starting a public "shitstorm", or insulting other community members in our chat rooms. Aside from being annoying for everyone, it also keeps our team from working on features and enhancements that users like you are waiting for.
(c) Reckless, surprisingly harsh or ignorant communication that disregards Rule #1 is unacceptable, whether public or private. If you are having a bad day and want to offend someone, please go somewhere else.
We have found that many of the issues that new users get upset about when they read about them in community forums or old issue comments have been resolved in the meantime. If not, you can be sure that we are working to improve our software and services to the best of our ability.
Thanks to our amazing community, problems are rare in practice. Common sense and staying away from the computer when you are tired or hungry should usually be enough to get along with others.
We encourage all community members to resolve problems on their own whenever possible. Serious and persistent violations, such as disrespectful, abusive, harassing, or otherwise unacceptable behavior, may be reported to us.
Our community standards will be enforced as necessary to protect everyone's well-being and to ensure that our discussion forums, chat rooms, and other infrastructure can be used as intended.
Initial warnings may be issued in the form of a snarky comment, especially if your tone is harsh to begin with. In serious cases, we will provide a link to this Code of Conduct to avoid misunderstandings. We also reserve the right to delete rants, personal attacks, spam, and unsolicited advertising from our community forums.
Getting a simple *plonk*1 in response finally signals that we have lost hope and you're being ignored according to Rule #3. This old tradition from Usenet days is as time-saving as it is clear. It is not meant in a disrespectful way.
In addition, we may use technical measures to temporarily or permanently restrict your access to our infrastructure, including forums and chats.
Footnotes
-
*plonk* including variants such as "Plonk." stands for the metaphorical sound of a user hitting the bottom of the kill file. It was first used in Usenet forums, a worldwide distributed discussion system and precursor to the Web. ↩