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).
On Sat, 2 Jan 2016, 21:40 Nick Coghlan <ncogh...@gmail.com> wrote: > On 3 January 2016 at 13:50, Barry Warsaw <ba...@python.org> wrote: > > On Jan 02, 2016, at 06:45 PM, Brett Cannon wrote: > > > >>> Some of these things might already be covered by existing PEPs, but I > >>> don't see them in PEP 507[0] and 481[1] (and I'm getting a bit lost > >>> among all the competing PEPs and multiple threads across at least a > >>> couple different MLs :). > >> > >>It will be either be a new PEP or the GitHub PEP will simply be > rewritten. > > > > Please either write a new PEP, or just write some draft new chapters for > the > > developer's guide. Ultimately, anything that a developer has to care > about > > really needs to be described in the devguide. > > For the last hosting transition, PEP 374 covered the process of > choosing a distributed VCS, while PEP 385 covered the actual > Subversion -> Mercurial transition, and I think that's a good way to > go. > > In particular, a separate "Migrating from hg.python.org to GitHub" PEP > provides a place to document the TODO list for the transition, and the > outcomes of any smaller decisions that will need to be made as an > incidental part of the migration (like handling Author/Committer data > for old commits), which aren't generally relevant to future > contributors (so don't belong in the developer guide), but also > weren't part of the repository hosting decision making process (so > don't really belong in PEP 507). > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > _______________________________________________ > core-workflow mailing list > core-workflow@python.org > https://mail.python.org/mailman/listinfo/core-workflow > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct >
_______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
