[core-workflow] Migration PEP started

Brett Cannon brett at python.org
Sun Jan 10 12:29:45 EST 2016


Sure, I can drop a note.

As for python-dev not being involved, that was somewhat on purpose. I said
at the beginning of this process, the switch is geared towards making
things easier for core developers while not making things worse for
external contributors, and so I focused on python-committers as the most
affected group (bringing the whole community in would have just made the
process too draining for me). And with Ezio and others planning to put the
work in to make sure that non-GitHub contributions are still serviceable I
think that goal has been met.

On Sun, 10 Jan 2016 at 01:56 Victor Stinner <victor.stinner at gmail.com>
wrote:

> Hi,
>
> It looks like there no email to python-dev. Can you please sometimes
> communicate status on python-dev (and maybe other python mailing list) to
> keep people aware of what is happening?
>
> For example, I don't think that python-dev was involved in the final
> choice of github.
>
> Victor
>
>
> Le dimanche 10 janvier 2016, Brett Cannon <brett at python.org> a écrit :
>
>> I'm developing it at
>> https://github.com/brettcannon/github-transition-pep/blob/master/pep-NNNN.rst .
>> I'm not posting it here as I'm still actively writing it. The only reason
>> I'm mentioning it now is because the migration plan has been very roughly
>> outlined, so if it  looks like I'm missing something, please let me know.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160110/53e225e0/attachment.html>


More information about the core-workflow mailing list