[python-committers] Proposal for procedures regarding CoC actions
Guido van Rossum
guido at python.org
Fri May 5 14:51:15 EDT 2017
More information about the python-committers mailing list
Fri May 5 14:51:15 EDT 2017
- Previous message (by thread): [python-committers] Proposal for procedures regarding CoC actions
- Next message (by thread): [python-committers] Coverage build broken?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Maybe there should be a published list of moderators (not a mailing list, just a list of people to mail!) where you can send such reports. If a moderator is being rude it's probably time to escalate to the PSF. Thanks for pushing for a definite process on this issue! On Fri, May 5, 2017 at 11:44 AM, Mariatta Wijaya <mariatta.wijaya at gmail.com> wrote: > Thanks everyone for the input. > > > It is still unclear to me how one can report when someone is being rude on > GitHub. > In the mailing lists we can email the administrators. But what about on > GitHub? > Do I write to python-committers? > What if it was a core developer who was being rude, where can a non > core-dev contributor report such behavior? > > > > Mariatta Wijaya > > On Thu, May 4, 2017 at 6:53 AM, Nick Coghlan <ncoghlan at gmail.com> wrote: > >> On 4 May 2017 at 06:10, Guido van Rossum <guido at python.org> wrote: >> > Two ex-board members disagree. I have to side with Brian; the PSF board >> > should have minimal say in how the developers develop. >> > >> > Note, I'm fine with the board being the arbiter when someone disagrees >> with >> > their ban though -- there's got to be a "higher authority" for appeals. >> But >> > I don't agree that the board should be the decider on the initial ban. >> >> I think initial temporary suspensions should definitely be handled >> without involving the Board (just as they are for any other PSF >> provided channel). >> >> I also think there are two cases that can definitely only be handled >> at the board level: >> >> - folks that feel they've been treated unfairly by the core >> development team appealing to the Board for reconsideration >> - the core development team recommending that a ban from our channels >> (python-dev, python-ideas, core-workflow, bugs.python.org, GitHub >> python org) be extended to other PSF provided channels >> >> I'd previously said that I thought conversion of temporary suspensions >> to permanent bans should also go to the Board, but I now think it >> makes more sense to handle that as: >> >> - the Board gets notified if a temporary suspension is now considered >> a permanent ban >> - they only need to get further involved if the ban is appealed >> >> Cheers, >> Nick. >> >> P.S. Don't forget that the specific context here is *public* behaviour >> that is the domain of channel moderators, rather than confidentially >> reported Code of Conduct concerns. Handling of the latter will remain >> with the PSF Board or their appointed representatives, independently >> of how we handle moderation of the development channels. >> >> -- >> Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia >> > > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20170505/4f626c7b/attachment.html>
- Previous message (by thread): [python-committers] Proposal for procedures regarding CoC actions
- Next message (by thread): [python-committers] Coverage build broken?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list