[python-committers] I have blocked Wes Turner from the Python org on GitHub
Paul Moore
p.f.moore at gmail.com
Sat Apr 1 14:55:05 EDT 2017
More information about the python-committers mailing list
Sat Apr 1 14:55:05 EDT 2017
- Previous message (by thread): [python-committers] I have blocked Wes Turner from the Python org on GitHub
- Next message (by thread): [python-committers] I have blocked Wes Turner from the Python org on GitHub
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1 April 2017 at 18:59, Nick Coghlan <ncoghlan at gmail.com> wrote: > In this particular case, we're only at step 2 - self-moderation based > on previously provided guidance has proven inadequate, so an enforced > break specifically from the Python org on GitHub makes sense (mainly > because the tools for dealing with non-productive noise on GitHub > issues aren't anywhere near as well developed as those for email). If > there was finer granularity available on GitHub, the suspension would > presumably have only been from the core-workflow repo specifically, > but that's not currently an available option. That seems entirely sensible. As does the entire process you describe. Paul
- Previous message (by thread): [python-committers] I have blocked Wes Turner from the Python org on GitHub
- Next message (by thread): [python-committers] I have blocked Wes Turner from the Python org on GitHub
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list