You make some good points. “Developer’s Guide” is ambiguous for a programming language. Would “Contributor’s Guide” be better? The first sentence of the guide is “This guide is a comprehensive resource for contributing to Python,” so perhaps.
But: we are looking at splitting the documentation contribution sections out of the Developer’s Guide, so that doc contributors don’t have to wade through core-dev esoterica. So we might need a more specific title.
Changing “Developer’s guide” to “Contributors’ guide” and then having subsections for “Contributing to code” and “Contributing to docs” seems reasonable.
Great question! I don’t think there was a specific reason not to include “contribute to CPython” in the python.org website, perhaps more of they just didn’t think of including it there at that time.
The pages and content on python.org are maintained by PSF staff, different group of people from Python contributors/core developers, and there is also a different issue tracker for the website vs for CPython itself. So perhaps at the time of writing that page, they were focused on ways to contribute to the PSF/Python community in general.
On CPython’s Readme file, the devguide is linked under the “Contributing Guide” heading:
I agree that on python.org website menu, it could be clearer if it was called “Contributing Guide” instead of “Developer Guide”.
Perhaps long term solution is to actually rename the DevGuide to Contributing Guide. It seems like “Contributing Guide” is a well-known terminology nowadays to the general open source contributors.