On 1 April 2017 at 18:59, Nick Coghlan <ncogh...@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 _______________________________________________ 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/
