That's perfect! Thank you for clarifying this. On Tuesday, August 20, 2019, 5:09:43 PM GMT+2, Guido van Rossum <gu...@python.org> wrote: The LICENSE file at the top is all you need. There is no need to contact inidividual contributors. That's the whole point of how Python licensing is set up.
On Tue, Aug 20, 2019 at 7:48 AM mihaela olteanu via Python-Dev <python-dev@python.org> wrote: Is it possible to contact the contributors and have their explicit agreement or is the LICENSE file at the top level of the repo already covering this scenario? Thank you,Mihaela On Tuesday, August 20, 2019, 12:22:04 AM GMT+3, Ivan Pozdeev via Python-Dev <python-dev@python.org> wrote: On 19.08.2019 23:30, Terry Reedy wrote: > On 8/19/2019 3:19 PM, Jeff Allen wrote: >> This is undoubtedly the right answer for someone wanting to *use* code >> *from* CPython. >> >> When one signs up to contribute code to the PSF, one is asked to write on >> contributed software that it has been "Licensed to the PSF >> under a Contributor Agreement" (see >> https://www.python.org/psf/contrib/contrib-form/). The XXX comment may >> signal an intention to return >> and insert such words. > > The form says specifically "adjacent to Contributor's valid copyright > notice". *If* the contribution comes with a separate explicit > copyright notice (most do not), then it should be followed by the > contribution notice. > > ossaudiodev.c has 3 copyright notices, the last being by PSF in 2002, long > before he current Contributor Agreement, and apparently never > challenged. Hence Guido's claim that the module is covered by the general > PSF license. > The text has "All rights reserved" in all three lines which is _not_ a copyright notice but a license grant. It's those license grants, including PSF's, that are untrue. Compare with e.g. Tools/msi/bundle/bootstrap/pch.h and Modules/_hashopenssl.c in which a copyright notice correctly comes bare and is followed by a license grant compatible with PSFLA. -- Regards, Ivan _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/NX2IJXGR4S6N6X6EW2J2Z3U3XGOYBKVY/ _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/WL4LKYTCEABYNRXN3VQV2NHFD4EMGRN5/ -- --Guido van Rossum (python.org/~guido)Pronouns: he/him/his (why is my pronoun here?)_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/VWJBFGF6WG4H4P3ETTG4DY2NTOJGDO7H/
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/37ISB5PI7EM6JKAO7B4TYMQ7DEWMPDQ5/