PEP 481 repo URL branding
This isn't described in PEP 481. I think this was briefly mentioned in a previous message, but I can't find it so I'm starting a new thread. If PEP 481 is accepted, will we be getting a GitHub enterprise instance that we can run on git{,hub}.python.org, or will we just use github.com/python/cpython? (FTR, the intent of PEP 507 is that we would be getting a GitLab EE or CE instance running on git{,lab}.python.org). Cheers, -Barry
It's just github.com. We can do a read only mirror to git.python.org if we would like. Sent from my iPhone
On Dec 15, 2015, at 10:02 AM, Barry Warsaw <barry@python.org> wrote:
This isn't described in PEP 481. I think this was briefly mentioned in a previous message, but I can't find it so I'm starting a new thread.
If PEP 481 is accepted, will we be getting a GitHub enterprise instance that we can run on git{,hub}.python.org, or will we just use github.com/python/cpython?
(FTR, the intent of PEP 507 is that we would be getting a GitLab EE or CE instance running on git{,lab}.python.org).
Cheers, -Barry _______________________________________________ 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
I would hope it would be hosted on GitHub. Getting out of the sysadmin business is one of my goals here. On Tue, Dec 15, 2015 at 7:31 AM, Donald Stufft <donald@stufft.io> wrote:
It's just github.com. We can do a read only mirror to git.python.org if we would like.
Sent from my iPhone
On Dec 15, 2015, at 10:02 AM, Barry Warsaw <barry@python.org> wrote:
This isn't described in PEP 481. I think this was briefly mentioned in a previous message, but I can't find it so I'm starting a new thread.
If PEP 481 is accepted, will we be getting a GitHub enterprise instance that we can run on git{,hub}.python.org, or will we just use github.com/python/cpython?
(FTR, the intent of PEP 507 is that we would be getting a GitLab EE or CE instance running on git{,lab}.python.org).
Cheers, -Barry _______________________________________________ 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
-- --Guido van Rossum (python.org/~guido)
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. Cheers, -Barry
On 16 December 2015 at 04:03, Barry Warsaw <barry@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@gmail.com | Brisbane, Australia
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. (*) FWIW: I've never heard of such a feature, but it would be a great thing to have :-) -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, Dec 16 2015)
Python Projects, Coaching and Consulting ... http://www.egenix.com/ Python Database Interfaces ... http://products.egenix.com/ Plone/Zope Database Interfaces ... http://zope.egenix.com/
::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ http://www.malemburg.com/
On 16 December 2015 at 18:56, M.-A. Lemburg <mal@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@gmail.com | Brisbane, Australia
участники (5)
-
Barry Warsaw -
Donald Stufft -
Guido van Rossum -
M.-A. Lemburg -
Nick Coghlan