Community Code of Conduct

[Jeff Osier-Mixon]

You are absolutely right to ask these questions, and I'm sure each
community will want to fine-tune it, although as a community manager I
actually prefer some of the vagueness in it. It is normal to add to a CoC
to try to cover all the bases, but people will always think up ways to
violate the spirit of the rule while staying within the letter. For a
positive community (like openbmc) the CoC is a guideline for new users,
rather than legislation for behavior, as it should be.

The best offense is a good community manager who can set the tone, with an
escalation path to a TSC or governing board, whichever is appropriate for a
given community. Ideally it would never be used - it never has been needed
in almost 8 yrs of the Yocto Project, as the leaders simply set a tone of
respect.

That's a really good question of harassment outside. Technically it is
private conversation, or outside the project's boundaries. If I were
community mgr in that case, I would have a frank conversation with the
harasser and let them know that simply isn't the way escalation is done in
this project, then provide the proper way and make sure their concern is
answered while respecting both sides. That being said, being hands-on
doesn't scale up to thousands of participants.

One more tidbit - this is the same CoC adopted by the kernel community and
several other high profile communities, so there is precedent within the
wider open source community for it. One thing I like quite a lot about it
is that it is itself open source - if I find a bug with it, I can submit a
pull request to the CoC itself.

I hope this is helpful to the process and not disruptive  :)

On Tue, Oct 9, 2018 at 11:53 AM Emily Shaffer <emilyshaffer at google.com>
wrote:

> 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/1aeadd05/attachment.html>