[python-committers] Commit rights to Ethan Furman

[Brett Cannon]

Ethan should now have commit rights and be subscribed to this list.

On Fri, May 10, 2013 at 9:08 AM, Eli Bendersky <eliben at gmail.com> wrote:
> Thanks!
>
> I'll go ahead and point Ethan to the dev guide, so he'll send his SSH keys
> to the appropriate place. Naturally I'm volunteering to mentor him in the
> initial work he'll be doing as a Python core developer. We'll start with
> getting an enum implementation committed (issue 17947). Since the
> implementation will almost certainly be based in large parts on Ethan's
> ref435 code, I think it's fair to let him commit that once it goes through a
> review.
>
> P.S. code review of on issue 17947 will be very much appreciated!
>
> Eli
>
>
>
> On Wed, May 8, 2013 at 4:07 PM, Terry Reedy <tjreedy at udel.edu> wrote:
>>
>> On 5/8/2013 4:44 PM, Eli Bendersky wrote:
>>
>> So I guess I can move forward with this unless there are objections in the
>> next day or two,
>>
>>
>> I have not responded before since Guido's approval seems sufficient ;-).
>> The main concrete step is that one of the repository supervisors add his
>> access key.
>>
>> On Mon, May 6, 2013 at 7:46 AM, Barry Warsaw <barry at python.org> wrote:
>>>
>>> On May 03, 2013, at 08:59 PM, Eli Bendersky wrote:
>>>
>>> >I'd like to propose to grant Ethan Furman commit rights. He's authored
>>> > PEP
>>> >309,
>>
>>
>> 409, not 309: http://www.python.org/dev/peps/pep-0409/
>>
>>
>>> has been very helpful in the Enum saga (and is the de-facto author of
>>> >the current reference implementation),
>>
>>
>> You, Barry, and Guido, who have also worked on enum, know him best and are
>> the principle supporters of this proposal. I gather that you all agree that
>> he has shown the 'cooperativeness' necessary to a collective project.
>>
>>
>>> and has also been active on the tracker for a couple of years (username
>>> stoneleaf).
>>
>>
>> As 'stoneleaf', he has been active on 12  issues since June 2010 (nosy on
>> 2 more). One patch is open and 5 have been applied (3 by Nick, 1 each by
>> Antoine and R. David),  I would say that the enum code, which appears to be
>> on the way to acceptance,  is equivalent to a few more typical issue
>> patches.
>>
>> FWIW, This is enough for a +1 from me.
>>
>>
>>> I think he has already
>>> >signed the contributor agreement, and explicitly expressed interest to
>>> >contribute directly to PEP 435.
>>
>>
>> That is the enum PEP.  http://www.python.org/dev/peps/pep-0435/
>> I consider a (nontrivial) reference implementation to be a direct
>> contribution even if he has not yet been pushing text changes.
>>
>>
>>> >Any objections?
>>>
>>> +1 for Ethan.
>>
>>
>> --
>> Terry Jan Reedy
>>
>>
>> _______________________________________________
>> python-committers mailing list
>> python-committers at python.org
>> http://mail.python.org/mailman/listinfo/python-committers
>>
>
>
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> http://mail.python.org/mailman/listinfo/python-committers
>