[Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.

[Tim.Bird at sony.com]

> -----Original Message-----
> From: Shuah Khan
> 
> On 09/25/2018 07:38 AM, Jonathan Corbet wrote:
> > On Tue, 25 Sep 2018 13:56:04 +0300
> > Jani Nikula <jani.nikula at intel.com> wrote:
> >
> >> Is the implication that further discussion on this is futile?
> >>
> >> Fire-and-forget is not exactly the best approach for rolling out a code
> >> of conduct.
> >
> > I doubt anybody is going to forget! :)
> 
> It is disappointing that it had to be committed without following the usual
> process. That said, I do support the direction and stating the expectations.
> 
> >
> > This is only my opinion, but I don't believe that the current CoC is set
> > in stone and immune to further changes.  It is something to start with.
> > I expect we will end up evolving it, like we evolve our other code.  We
> > will need to figure out how to do that, though; that discussion has not
> > yet even begun.
> >
> 
> One of the reasons for starting this thread is to get a clear understanding
> of the intent for next steps and the next steps for involving the community
> and evolving  the CoC. I hope a concrete plan or some plan emerges out of
> this
> discussion.
> 
> Since the way it currently reads, it adds to maintainer responsibilities,
> it is important to open it up for review by all maintainers as opposed to
> participants of just the Maintainer Summit which is a very small group.

I am speaking only for myself, but I couldn't agree more, on all points. 

I think Mauro raised some very good points about aspects of the CoC
being a better fit for a github-style project as opposed to a widely
distributed e-mail based project.  And certainly the ambiguity regarding the
treatment of published e-mails as private information needs to be
resolved.  So I think it's unquestionable that the CoC will need to change.

But I still don't know what the process for that is, and I hope that
we'll see some suggestions at Maintainers Summit, that can be discussed
as a wider community.  I agree that the Maintainer Summit and Plumbers
doesn't represent all affected community members, and that should
definitely be taken into account.
 -- Tim