Here's another idea. Ban him temporarily from the tracker and the lists(*) and tell him that to be unbanned he has to talk to me, and to me only. I will then negotiate a cool-off period and posting guidelines with him. If he violate those he will automatically be banned permanently (or at least for a year).

(*) Which lists? I'd say python-dev and python-idea -- are there any other lists where he hangs out? Or perhaps all lists on mail python.org just so he won't take his complaints to other lists.

On Fri, Nov 29, 2013 at 11:59 AM, Antoine Pitrou <antoine@python.org> wrote:

On ven., 2013-11-29 at 11:40 -0800, Guido van Rossum wrote:
>
> If you can get a majority of the committers to vote to ban him we
> should do it -- but that's a high bar (many committers probably don't
> care enough to vote).

Well, many are probably inactive enough to not even notice this
discussion :-) I'm not sure about the authoritative source, but the SSH
keys repository shows 178 people with access rights. The majority of
them isn't probably active nowadays.

Then I don't know where his behaviour is most problematic: on the
tracker or the MLs?
If we only ban him from the tracker, I'm afraid he'll start making
"here's an issue I can't post on the tracker because I'm banned" posts
on the mailing-list...

Perhaps a temporary ban? There does need to be a signal sent to him.
(apparently, he stopped reopening the issue when Georg told him
reopening the issue would lead to loss of posting rights, which implies
he is sensitive to this kind of signals)

Regards

Antoine.


_______________________________________________
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers

--
--Guido van Rossum (python.org/~guido)

_______________________________________________
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers