Missing license for file Modules/ossaudiodev.c
Hello, Could you please let me know what is the license for the file Modules/ossaudiodev.c ?Inside the description there is a statement :"XXX need a license statement" which creates some confusion.Can we simply disregard that statement as for the other .c files which do not have such statements?Please note that we need this information for our OSS clearance report. Thank you, Mihaela
The LICENSE file at the top level of the repo covers everything. On Mon, Aug 19, 2019 at 7:33 AM mihaela olteanu via Python-Dev < python-dev@python.org> wrote:
Hello,
Could you please let me know what is the license for the file Modules/ossaudiodev.c ? Inside the description there is a statement :"XXX need a license statement" which creates some confusion. Can we simply disregard that statement as for the other .c files which do not have such statements? Please note that we need this information for our OSS clearance report.
Thank you, Mihaela _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@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/BOG2EPE7...
-- --Guido van Rossum (python.org/~guido) *Pronouns: he/him/his **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
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. You cannot find many instances of those words in CPython (and Jython is worse). Many of the files pre-date the fomula, most contributions are a change to existing code, and adding it later to someone else's work doesn't feel right. (The situation is clear for pristene code.) I have wondered if it's an issue. Jeff Jeff Allen On 19/08/2019 15:35, Guido van Rossum wrote:
The LICENSE file at the top level of the repo covers everything.
On Mon, Aug 19, 2019 at 7:33 AM mihaela olteanu via Python-Dev <python-dev@python.org <mailto:python-dev@python.org>> wrote:
Hello,
Could you please let me know what is the license for the file Modules/ossaudiodev.c ? Inside the description there is a statement :"XXX need a license statement" which creates some confusion. Can we simply disregard that statement as for the other .c files which do not have such statements? Please note that we need this information for our OSS clearance report.
Thank you, Mihaela _______________________________________________ Python-Dev mailing list -- python-dev@python.org <mailto:python-dev@python.org> To unsubscribe send an email to python-dev-leave@python.org <mailto:python-dev-leave@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/BOG2EPE7...
-- --Guido van Rossum (python.org/~guido <http://python.org/~guido>) /Pronouns: he/him/his //(why is my pronoun here?)/ <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@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/O2VUG4CF...
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. -- Terry Jan Reedy
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
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-leave@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/NX2IJXGR...
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-leave@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/NX2IJXGR...
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@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/WL4LKYTC...
-- --Guido van Rossum (python.org/~guido) *Pronouns: he/him/his **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
I've opened https://github.com/python/cpython/pull/15346 to remove the dead comment.
That's perfect! Thank you for clarifying this. On Tuesday, August 20, 2019, 5:09:43 PM GMT+2, Guido van Rossum <guido@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-leave@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/NX2IJXGR... _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@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/WL4LKYTC... -- --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-leave@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/VWJBFGF6...
On 19/08/2019 21:30, Terry Reedy wrote:
On 8/19/2019 3:19 PM, Jeff Allen wrote:
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. Ah, ok. I hadn't read it that way: rather a request to add both. That is useful, thanks: occasionally, I have to guide contributors to Jython, who sign the same form.
Jeff
participants (6)
-
Brett Cannon
-
Guido van Rossum
-
Ivan Pozdeev
-
Jeff Allen
-
mihaela olteanu
-
Terry Reedy