[core-workflow] PEP 481 repo URL branding

[Nick Coghlan]

On 16 December 2015 at 04:03, Barry Warsaw <barry at python.org> 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.

>From an organisational branding perspective, the GitHub model tends to
be more focused around GitHub Pages, as in sites like
https://microsoft.github.io/ and simple redirects like
https://google.github.io.

Site markup for the latter arrangement:
https://github.com/google/google.github.io/blob/master/index.mkd

The major advantage of doing that (rather than just linking directly
to the project landing page URL) is that if an organisation's hosting
situation changes in the future, it's a lot easier to appropriately
update a GitHub Pages based microsite than it is direct links to the
project repository on github.com.

It's also possible to use the CNAME support in GitHub Pages to move
the landing page out to a subdomain of another site.

Cheers,
Nick.

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