<p dir="ltr">I'm planning to write a separate PEP. I'll start outlining what I think we need to accomplish and in what order on Monday and that will be the kick-off for the outline of the PEP so we can get a good feel for the work to be done (roughly).</p>
<br><div class="gmail_quote"><div dir="ltr">On Sat, 2 Jan 2016, 21:40 Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 3 January 2016 at 13:50, Barry Warsaw <<a href="mailto:barry@python.org" target="_blank">barry@python.org</a>> wrote:<br>
> On Jan 02, 2016, at 06:45 PM, Brett Cannon wrote:<br>
><br>
>>> Some of these things might already be covered by existing PEPs, but I<br>
>>> don't see them in PEP 507[0] and 481[1] (and I'm getting a bit lost<br>
>>> among all the competing PEPs and multiple threads across at least a<br>
>>> couple different MLs :).<br>
>><br>
>>It will be either be a new PEP or the GitHub PEP will simply be rewritten.<br>
><br>
> Please either write a new PEP, or just write some draft new chapters for the<br>
> developer's guide. Ultimately, anything that a developer has to care about<br>
> really needs to be described in the devguide.<br>
<br>
For the last hosting transition, PEP 374 covered the process of<br>
choosing a distributed VCS, while PEP 385 covered the actual<br>
Subversion -> Mercurial transition, and I think that's a good way to<br>
go.<br>
<br>
In particular, a separate "Migrating from <a href="http://hg.python.org" rel="noreferrer" target="_blank">hg.python.org</a> to GitHub" PEP<br>
provides a place to document the TODO list for the transition, and the<br>
outcomes of any smaller decisions that will need to be made as an<br>
incidental part of the migration (like handling Author/Committer data<br>
for old commits), which aren't generally relevant to future<br>
contributors (so don't belong in the developer guide), but also<br>
weren't part of the repository hosting decision making process (so<br>
don't really belong in PEP 507).<br>
<br>
Cheers,<br>
Nick.<br>
<br>
--<br>
Nick Coghlan | <a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a> | Brisbane, Australia<br>
_______________________________________________<br>
core-workflow mailing list<br>
<a href="mailto:core-workflow@python.org" target="_blank">core-workflow@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/core-workflow" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/core-workflow</a><br>
This list is governed by the PSF Code of Conduct: <a href="https://www.python.org/psf/codeofconduct" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct</a><br>
</blockquote></div>