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
https://mail.python.org/archives/list/python-dev@python.org/message/NX2IJXGR4S6N6X6EW2J2Z3U3XGOYBKVY/