[core-workflow] PEP 481 repo URL branding

Nick Coghlan ncoghlan at gmail.com
Wed Dec 16 05:39:18 EST 2015


On 16 December 2015 at 18:56, M.-A. Lemburg <mal at egenix.com> wrote:
> On 15.12.2015 19:03, Barry Warsaw wrote:
>> On Dec 15, 2015, at 09:15 AM, Guido van Rossum wrote:
>>
>>> I would hope it would be hosted on GitHub. Getting out of the sysadmin
>>> business is one of my goals here.
>>
>> The two aren't mutually exclusive.  For PEP 507, I propose a donated and
>> managed GitLab instance answering to git{,lab}.python.org.
>
> Is it possible to setup a CNAME git.python.org which then maps
> to the Python github account page ? (*)
>
> I'm not worried much about the github.com in the URLs, but if
> we move there with the intent of moving somewhere else in a
> few years, then it may be good to avoid breaking links by
> using such a more generic URL which is under our control.

While it would be possible to set something up using redirects, if
this is aimed at having a canonical *.python.org URL for code
references, that's the best argument I've heard in favour of the
GitHub-with-a-read-only-GitLab-mirror setup - keeping a mirror at a
stable URL regularly updated is straightforward to do indefinitely,
regardless of what else happens with the development workflow.

The idea also raises the question of how long we preserve
hg.python.org/cpython as a read-only Mercurial mirror of the new git
repo.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia


More information about the core-workflow mailing list