> [...] The devguide is *already* too big. [...]
> The devguide was supposed to be something that you read quickly and easily, not an exhaustive
> reference of how development works. Or at least there should be a clear separation between the
> two (the guide part, and the reference part). [...]
> The devguide is *not* primarily for core developers. It's for new contributors who want to get
> set up, so that they don't give up in the absence of clear indications. [...]

Thanks Antoine, I was not aware of that or I had forgotten it.  The old python.org/dev pages contained information for new and experienced core devs too, so I thought the devguide was intended to contain the same info.  I’ll support a clearer separation between the guide and the reference, to make the devguide less overwhelming for new contributors but still complete for core devs.