[Buildbot-devel] Code of Conduct
tflink at redhat.com
Mon Oct 6 17:12:11 UTC 2014
On Mon, 6 Oct 2014 09:53:11 -0400
"Dustin J. Mitchell" <dustin at buildbot.net> wrote:
> The topic of a code of conduct came up today in #buildbot , and
> Quentin pointed to Rust's code of conduct .
> I'd like to add this to the list of Buildbot policies. Not in
> response to any problem we've had, but because it's simple and to the
> point, and it's better to write these things down *before* you need
> them. I don't intend for this to represent any change -- just a
> codification of something already in place.
That sounds like a good plan to me, I think that a code of conduct
is kind of like insurance - you hope you never need it but if the worst
happens, it's there and you have one less thing to worry about.
> The pull request is at https://github.com/buildbot/botherders/pull/3
> and I'd welcome any feedback here or there.
Overall, it looks good but I wonder if it would be wise to add a
section on moderator actions - what warnings will happen, the usage of
silence/kick/ban, how long consequences last and a process for appeal
(even if that's just "contact the botherders"). Keeping with the spirit
of borrowing from Rust, their section is  which was adapted from
Node.js . As another point of potential inspiration, Fedora's IRC
channel operator code of conduct  also has a list of consequences and
has a method for appeal .
I figure that if someone ever violates the code of conduct, having a
set of pre-defined actions would reduce confusion over how to respond at
that time and start defusing any potential "you're not being fair" with
"the consequences are written out already, follow the process outlined".
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 473 bytes
Desc: not available
More information about the devel