Thanks, Raymond, this reads like a good proposal, but I'd like to
suggest that the three people in question are only intended to
discuss whether a CoC event has taken place or not and what the
person has to say about this.

They should then write up a summary to present to the PSF Board
which then decides. We have already had precedents for this and
it worked well.

No single moderator of a PSF resource should be allowed to impose
a ban on anyone. I also don't think that what Wes has done is
serious enough to be considered a CoC violation or that a ban
was the right action to take.

What I miss in the proposal is more emphasis on getting
feedback from the person in question (I often see CoC rule
sets miss out on this - even though it's one of the most basic
human rights principles: the right to a fair trial) and trying
to change behavior before CoC actions such as bans have to be
triggered.

In most cases, it's possible to find a way forward without
any actions and that's what we should strive for as a community.

Thanks,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Mar 31 2017)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/
________________________________________________________________________

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/
                      http://www.malemburg.com/



On 02.04.2017 01:07, Raymond Hettinger wrote:
> I would like to make a procedural proposal based on the ideas emerging from 
> the other python-committers discussion regarding the two month suspension of 
> Github project access for a developer who was posting non-productively.
> 
> It seems that there is general agreement to differentiate commonplace list 
> moderation actions from CoC actions which are more of a nuclear option to be 
> reserved for egregious cases of harassment and abuse.
> 
> Also, there is general agreement not to concentrate that power in the hands 
> of a single person and that we should have some principles and procedures in 
> place.
> 
> I propose that when someone thinks there is a problem serious enough to 
> warrant a Code-of-Conduct action, that it get referred to a group of three 
> people to make the decision.  Two of those three people should be long-term, 
> senior, and respected core devs who have good knowledge of the community 
> (Brett Cannon, Nick Coghlan, Antoine Pitrou, et al).  The third person should 
> be someone who is also well-respected but more independent and who has more 
> experience in sociology and community management issues (Alex Gaynor or Carol 
> Willing come to mind). 
> 
> To prevent endless bickering and sharing of sensitive details, the group's 
> decision should be considered settled business which can only be overridden 
> either by an appeal to the PSF board or by the BDFL.  When possible, the 
> affected person should be contacted and given an opportunity to defend 
> themselves.  The decision shall be announced on python-committers with an 
> overall rationale but without personal details.
> 
> The group shall consider the needs of the community first and foremost, and 
> secondarily shall prioritize being as respectful as possible to all parties, 
> and thirdly shall do whatever they can to mitigate the harm to the violator.  
> The actions shall be taken with an intent to protect the vibrancy of the 
> Python community rather than with an intent to punish, humiliate, or 
> discredit the affected person.  When possible, some path to redemption or 
> forgiveness shall be offered.
> 
> Respectfully submitted,
> 
> 
> Raymond Hettinger
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 

_______________________________________________
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Reply via email to