Community Code of Conduct

[Emily Shaffer]

Reading through this, I've got a couple concerns:

- There's a clause for enforcement. How do we want to assign ownership when
enforcement is needed? We probably want to lay it out, I'm not sure that it
should come through the TSC. Maybe Kurt would be a good start as the
community manager? No offense to Kurt but I'd also like an escalation path
or alternative path - with these kinds of things it's important to be able
to bypass an individual if necessary.

- The clause on scope seems to me like it may leave a gap surrounding
harassment of community members outside of the official OpenBMC setting -
ie, Foo posts to their Twitter account, "I'm having a lot of trouble with
Bar's code reviews. What an idiot! Tell them so - their email is bar at baz.org!"
I'm not sure I'm seeing how the contributor covenant protects against this
kind of behavior. Maybe I'm just misreading and this counts as "prviate
communication"?

On Tue, Oct 9, 2018 at 11:31 AM Jeff Osier-Mixon <jefro.net at gmail.com>
wrote:

> Hi folks
>
> We strongly recommend the contributor covenant coc. Being adopted by many
> projects.
>
> https://www.contributor-covenant.org/version/1/4/code-of-conduct
>
> Glad to discuss more
>
> On Tue, Oct 9, 2018, 11:28 AM Emily Shaffer <emilyshaffer at google.com>
> wrote:
>
>> Hi all,
>>
>> As I briefly mentioned at the end of Brad's presentation today, I'd like
>> to propose adding and enforcing a code of conduct for us to follow.
>>
>> For now, I am planning to grab a copy of the Linux CoC and put it up for
>> review in /docs. If anybody has a different CoC source to suggest, I'd be
>> happy to discuss.
>>
>> Brad asked me whether I had seen an issue so far and I had not, so please
>> don't take this email as some kind of retaliation - it's not. I think we've
>> got a great, positive community and as we grow I'd like to preserve that
>> culture, and the code of conduct is a great way to do so.
>>
>> - Emily
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20181009/03b5ae7b/attachment.html>