I suppose it gets to the point of what python.org is intended for – if the website is primarily an advert for the project as a whole and the charity, then it may make sense (and I would argue that it does) to put PEPs on a subdomain also, similar to docs.python.org.
It seems at the monement that there seems to be a good precendent for hosting things on subdomains as opposed to the main site, but I guess PEPs might be “sufficiently different”, and warrant staying on the main website.
list of subdomain things:
- issue tracker (
bugs.python.org) - automatic builds (
buildbot.python.org) - developer’s guide (
devguide.python.org) - documentation (
docs.python.org) - email list archives (
mail.python.org) - packaging guide (
packaging.python.org) - performance statistics (
speed.python.org) - status (
status.python.org) - wiki (
wiki.python.org)
I’d agree with this – there’s no point doing both, there should be one canonical source – for the reasons in my original paper I would favour peps.python.org, but we shouldn’t create that if we continue integrating into the main python.org website.
A