[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] [Xen-devel] [RFC] Code of Conduct

Lars Kurth writes ("Re: [Xen-devel] [RFC] Code of Conduct"):
> I attached a redline version of both the original (based on the LF events 
> CoC) and a redline version based on the covenant given the constraints we 
> agreed. Aka
> [1] Xen CoC Contributor Covenant baseline (redline).pdf 
> [2] Xen CoC LF events baseline (redline).pdf
> I minimized changes to [2]. 

I like both of these.  I would be happy to adopt either.  I prefer the
Contributor Covenant based version.

I have two comments.  The first is very minor:

The LF Events one has one different section title.  Instead of
it has
        What To Do If You Witness Or Are Subject To Unacceptable
which is unwieldy but better in other ways - more positive and
constructive.  I'm not sure if there is a happy middle ground.
I am happy to adopt either version with either title.  I mention it in
case anyone has better ideas etc.

My second comment is more substantial.  It should not be regarded as a
blocker, but I would like to see it addressed either now or after CoC

The root issue is the difficult one of what to do about possible
involvement in abuse by members of the conduct@ address.

I would like to see two changes: firstly, we should publish the list
of people that the conduct alias goes to.  The CoC should contain a
reference to the place where this can be found.  "The membership of
the conduct@ alias is publicly documented in [location]".

Secondly, we should explicitly provide a route for someone who
distrusts member(s) of conduct@.  How about:

  If you have concerns about any of the members of the conduct@ alias,
  you are welcome to contact precisely the Conduct Team member(s) of
  your choice.

The team should be large and diverse enough that this is a practically
useful recommendation, but it should not be unwieldy.

Thanks for driving this.


MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.