[Buildbot-devel] Code of Conduct

[Dustin J. Mitchell]

Good points (Bill made a similar point on the pull req) -- I'll add
some more moderator-oriented content based on the links you've
provided (we need to account for lists, trac, and github as well as
irc).

Dustin

On Mon, Oct 6, 2014 at 1:12 PM, Tim Flink <tflink at redhat.com> wrote:
> 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 [1], and
>> Quentin pointed to Rust's code of conduct [2].
>>
>> 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 [1] which was adapted from
> Node.js [2]. As another point of potential inspiration, Fedora's IRC
> channel operator code of conduct [3] also has a list of consequences and
> has a method for appeal [4].
>
> [1]https://github.com/rust-lang/rust/wiki/Note-development-policy#moderation
> [2]http://blog.izs.me/post/30036893703/policy-on-trolling
> [3]https://fedoraproject.org/wiki/IRC_operators_code_of_conduct
> [4]http://fedoraproject.org/wiki/Fedora_Social_Channel_FAQ#Ban_Removal_or_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".
>
> Tim
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.  Videos for Nerds.  Stuff that Matters.
> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>