Re: [Python-Dev] About multiprocessing maintainership

2019-02-04 Thread Antoine Pitrou
On Mon, 4 Feb 2019 09:45:39 -0600 Zachary Ware wrote: > On Mon, Feb 4, 2019 at 4:39 AM Antoine Pitrou wrote: > > What I did (*) is different: I asked to mark Davin inactive and to stop > > auto-assigning him on bug tracker issues. Davin was /still/ listed in > > the experts list, along with me a

Re: [Python-Dev] About multiprocessing maintainership

2019-02-04 Thread Antoine Pitrou
Hello Davin, I would like this discussion to be constructive and not vindicative. So I would ask that we leave personal attacks out of this. > I have been part of several group discussions (among core developers) > now regarding how to balance the efforts of contributors with copious > time to

Re: [Python-Dev] About multiprocessing maintainership

2019-02-04 Thread Zachary Ware
On Mon, Feb 4, 2019 at 4:39 AM Antoine Pitrou wrote: > What I did (*) is different: I asked to mark Davin inactive and to stop > auto-assigning him on bug tracker issues. Davin was /still/ listed in > the experts list, along with me and others. IOW, there was no "editing > out". Auto-assignment

Re: [Python-Dev] About multiprocessing maintainership

2019-02-04 Thread Davin Potts
Antoine's change to the devguide was made on the basis that "he doesn't contribute anymore" which, going by Antoine's own description in this thread, he contradicts. My current effort, mentioned in Antoine's other thread, is not my single largest contribution. I have been impressed by the volume

[Python-Dev] About multiprocessing maintainership

2019-02-04 Thread Antoine Pitrou
Hello, In a recent message, Raymond dramatically pretends that I would have "edited out" Davin of the maintainers list for the multiprocessing module. What I did (*) is different: I asked to mark Davin inactive and to stop auto-assigning him on bug tracker issues. Davin was /still/ listed in t