These steps sound right to me. Make the notification a private email, not a public one -- this doesn't have to be a big deal. It's not a warning shot to other people, this is one isolated individual, and we should treat it as such.

Alex


On Sat, Nov 30, 2013 at 1:44 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 30 November 2013 15:23, Guido van Rossum <guido@python.org> wrote:
> Nick,
>
> I think we've seen the issue from every possible side now. I trust your
> judgment that he has pulled this trick once too many times. So please
> implement the ban. Or wait until the next infraction -- that's up to you.
> Either way, since the archives of this list are public, our deliberations
> will stand up to scrutiny.
>
> My offer to mediate (*after* he's been banned) stands, but it's up to you if
> and how you want to mention that to Anatoly.

OK, moving on to mechanics, here's what I would like to propose:

- flip his moderation bit on the mailing lists, at least for
python-dev, python-ideas and distutils-sig (are there any other lists
where his presence is considered disruptive?).

- revoke his tracker privileges. If he would like something done on
the tracker, he can ask Guido or Ezio to make the change on his
behalf.

I'm willing to be the bearer of bad news, and let Anatoly know this is
being done, and cc' Guido and Ezio (as I'll also pass along their
offers of assistance).

Regards,
Nick.

--
Nick Coghlan   |   ncoghlan@gmail.com   |   Brisbane, Australia
_______________________________________________
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers



--
"I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: 125F 5C67 DFE9 4084