Add advice on copyright notices and PRs

[hugovk]

Closes python/cpython#126133.

Re: python/cpython#126133 (comment), this is so we can link to this section if we get PRs attempting to update copyright years each year.

Feedback welcome on wording and where to put this in the devguide.

---

📚 Documentation preview 📚: https://cpython-devguide--1470.org.readthedocs.build/

[malemburg]

You should also add a note that for most code in the PSF CPython distribution, the PSF does not own the copyright, but only has redistribution rights to that code, so randomly applying the PSF copyright notice is often plain wrong.

There were a few copyright assignments in the past, but I'm not sure whether we really have a complete list of those. Only code which falls under one of these assignments is legally copyrighted by the PSF.

Note that the PSF does own the copyright on the CPython distributions, i.e. the compilation of the files which make up CPython, which is why there is a copyright statement in the README and the LICENSE.

[hugovk]

Thanks for the info.

I'd prefer to keep this particular change scoped only about the existing notices, not about adding any new notices, or how copyright applies. It's primarily so we have something to point at if we get PRs adding new years to the list.

Please could you open a new issue or PR if you'd like to extend it? Thank you!