Code of Conduct
We want to turn Quanta into a lovely, friendly, fun community.
That's why we have put together some small Code of Conduct guidelines, based on the ones suggested by the Ubuntu community.
You are going to contribute into a project used - potentially - by thousands of people. Applying wrong changes to code, documentation, translations, etc. - may negatively impact others' work. And it's really not fun!
Because even if sometimes we disagree, and that's causing us frustration, that doesn't ever justify poor manners, threatening, personal attacks and so on.
We are open source, we are a community, and we should always be open to collaboration, working closely with each other to make Quanta great.
When we disagree, we consult others.
Conflicts in our community can take many forms. Disagreements, social and technical, are normal, but we do not allow them to persist and fester leaving others uncertain of the agreed direction.
We expect individuals to first try to resolve conflicts between themselves in a constructive manner, asking for help when needed. This approach gives people more control over the outcome of their dispute.
If that fails, we escalate the matter to structures with designated leaders to step in and provide clarity and direction. When conflicts do arise there is a thought-out and agreed process for resolving them: Conflict Resolution Policy.
We will not tolerate bullying or harassment of any member of the Quanta community.
If you feel threatened or violated as a result of intimidating, bullying, harassing, abusive, discriminatory, derogatory, or demeaning conduct, please speak up and ask it to stop. If you do not feel that you can speak up, contact the Community Working Group immediately with evidence of the incident. Incidents of bullying and harassment can be reported privately and will be treated seriously and discreetly.
Please speak up if you notice someone else being subjected to such behavior. Refer people to our Code of Conduct and point out such behavior is unwelcome.
When we are unsure, we ask for help.
Asking questions - when needing answers - is the most natural, therefore encouraged - activity in an open source project. On the other hand, replies to questions should always be responsive and helpful.