On Tue, Oct 9,= 2018 at 11:53 PM Jeff Osier-Mixon <jefro.net@gmail.com> wrote:

You are absolutely right to ask these questions, and I&= #39;m sure each community will want to fine-tune it, although as a communit= y manager I actually prefer some of the vagueness in it. It is normal to ad= d to a CoC to try to cover all the bases, but people will always think up w= ays 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, r= ather than legislation for behavior, as it should be.

As long as we're aware that there's a line to trea= d with the vagueness, I don't mind. IMO one of the points is to highlig= ht to community members what is and isn't abusive language, so having a= code that's too vague opens the door for a victim to be gaslit out of = realizing there is a problem going on.=C2=A0 I don't feel that's an= issue with this Contributor Covenant.

=C2=A0

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. Ide= ally it would never be used - it never has been needed in almost 8 yrs of t= he Yocto Project, as the leaders simply set a tone of respect.=C2=A0
<= /div>

+1000. Like I said at the outset, I d= on't think this is to address a problem happening now, so much as it is= to codify our current positive culture and cover ourselves for later.
<= /div>

=C2=A0

=
That's a really good question of harassment outside. Tec= hnically it is private conversation, or outside the project's boundarie= s. 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 escalatio= n 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 han= ds-on doesn't scale up to thousands of participants.

One more tidbit - this is the same CoC adopted by the kernel communi= ty 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 submi= t a pull request to the CoC itself.

I hope thi= s is helpful to the process and not disruptive=C2=A0 :)

I've got a copy of the Contributor Covenan= t up for review in docs/ now:

https://gerrit.openbmc-proje= ct.xyz/#/c/openbmc/docs/+/13920/

Happy to cont= inue discussion in both places.
<= div class=3D"gmail_quote">