[python-committers] Davin Potts as a new committer
brett at python.org
Sat Mar 5 11:51:11 EST 2016
Who wants to be Davin's mentor and tell him to do the steps outlined in
On Sat, 5 Mar 2016 at 01:04 Serhiy Storchaka <storchaka at gmail.com> wrote:
> On 05.03.16 09:21, Berker Peksağ wrote:
> > On Sat, Mar 5, 2016 at 8:44 AM, Gregory P. Smith <greg at krypto.org>
> >> On Fri, Mar 4, 2016 at 10:07 PM Raymond Hettinger
> >> <raymond.hettinger at gmail.com> wrote:
> >>>> On Mar 4, 2016, at 4:07 PM, Brett Cannon <brett at python.org> wrote:
> >>>> I guess I'm just worried about the health of this project. I'm doing
> >>>> what I can through the migration to GitHub to make it easier for
> others to
> >>>> get involved while making it easier for us to accept the work of
> others, but
> >>>> the maintenance and health of this team worries me. For instance, if
> >>>> look at the developer's log you will notice we only gained 2 core
> devs for
> >>>> all of 2015 and the last one was August 2015:
> >>> Last year on this list, I recommended that Davin Potts be granted core
> >>> developer status for his on-going work on the multiprocessing module.
> >>> group collectively said no, leaving Davin in an odd and uncomfortable
> >> Huh? Searching for Davin Potts in my mail, I see a ~27 message long
> >> from January 2015 about that. Many of us were +1 to give him commit
> >> I personally assumed it had happened, but the only objections seemed to
> >> "lets see some patches first"... That part has happened:
> >> Among the other things in my mail with Davin's name mentioned are
> >> streams of committed patches over the past year or so on multiprocessing
> >> related issues (as expected), including recently.
> >> berker.peksag, martin.panter and serhiy.storchaka have been the primary
> >> committers of said Davin patches.
> > +1!
> > I was going to send an email to python-committers about this a couple
> > weeks ago, but I couldn't find enough time (or I was just lazy :)) to
> > collect issue numbers (he did a great job on triaging old
> > multiprocessing issues) and commits.
> +1 from me. I have committed not too much Davin's patches (they were not
> easy), but confirm his proficiency. We need an expert in this domain.
> python-committers mailing list
> python-committers at python.org
> Code of Conduct: https://www.python.org/psf/codeofconduct/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the python-committers