I’m fairly new to the community: I have contributed some documentation and issues. I hope to participate more in the community in the future. So far, my experience with the community was quite positive, which is a welcome change from other places on the internet, so already: thank you for that, you’re awesome.
One thing I look at when I get involved with a new community, is the way the community is managed. So far, I am happy to see a forum and various accessible tools for newcomers: that is a good sign. Now one thing I feel is missing from the community is a code of conduct. I don’t think there has been any harassment or related problems yet in the Restic community. But it’s exactly at about that time that it is good to set preemptive code of conduct policies, before problems happen. It shows a clear stance against abusive or discriminatory behaviour, and makes people feel more welcome.
A code of conduct is not about establishing an absolutist set of moral guidelines over right and wrong: it’s more about establishing a process for when people feel flawed in their interactions in the community. It’s about setting expectations of behavior with each other. It’s also not a manual on how to make releases or decisions in the community: that belongs elsewhere. @fd0 found, for example, this governance guide from the
A code of conduct is different. A commonly used code of conduct is the Covenant:
There is a markdown version that could be adopted with only minor changes. What such an adoption would mean is simply that:
- a set of contact points would be established in case of problems
- an enforcement policy would be established (i often refer to the spirit of the django enforcement policies here)
- the document would be added to the source tree, with modification (specifically: the “enforcement” section needs to be modified)
- the above would be added to the project’s documentation
Note that this forum already has some set of guidelines:
Those affect only the forum however: a code of conduct would cover all areas of operations of the Restic project: the GitHub issue queues, the forum, the IRC channel, the blog and so on.
More references regarding code enforcement:
Again: this is not because there is any trouble in the community (hopefully!). This is to help preventing (or having ways of managing) any future problems. It also serves as a standard landmark, like a
LICENSE file, that provides expectations about how the community is managed.
There has been some discussions about this on IRC, where there was some interest in discussing this more broadly. I’m hoping this proposal will be welcome as a positive addition to the community: a code of conduct is not designed to change practices, but like any “standardization” attempt, it is aimed at consolidating what are already existing processes.
Thank you for your time!