Alyssa Coghlan

Heh, "look for the commits from the last time an extension module was added" is *exactly* how I've handled our current lack of docs myself :)

Even if the details are delegated to the devinabox documentation, it would still make sense to have section about it in the developer guide. However, that section could be smaller,...

Software Carpentry also use that "Copy-and-customise" model for their bootcamps, so setting up something similar for CPython sprints sounds sensible to me. It also provides a separate issue tracker for...

https://docs.python.org/devguide/committing.html#what-s-new-and-news-entries has the details on when "skip news" is appropriate. "skip issue" is similar but isn't currently documented anywhere: if it's a follow-up to an unreleased change, re-use the existing...

Adding new C files can also be trickier than it seems at first glance, as even though forgetting that will give you immediate build failures, you still need to know...

I'm not sure where you'd put this info in the current dev guide though - we don't really cover the build process right now beyond what's in https://devguide.python.org/setup/#compiling-for-debugging It may...

All of @rhettinger's steps were right, it's just that in the final PR creation step in the web UI it's necessary to know that there are some dropdowns in the...

Deciding how to add this is actually a bit tricky, since we don't currently discuss `git revert` at all, not even in the simpler case of reverting a commit to...

I agree with the conclusion, but not entirely with the rationale. As per https://www.python.org/dev/peps/pep-0394/ an unqualified "python" still refers to the system Python 2 installation in most Linux installations. What's...

https://docs.python.org/3/installing/#installing-into-the-system-python-on-linux should continue to use `python3` in the appropriate location, but other than that I'd expected us to be using the generic `python`.