Re: setup.py and licensing questions
Ben Finney wrote: > songbird writes: > >> can i put multiple License lines in setup.py >> classifiers like: ? >> >> "License :: OSI Approved :: ???", >> "License :: OSI Approved :: ???", > > Yes. > > The semantics of that are not formalised, to my knowledge. You would be > signaling that the specified licenses are involved somehow, but not how > they combine for this specific work. ok, thanks, that's good to know. i will have a list of each file i've used from elsewhere, where it came from and as best as i can figure it out the licenses/copyright holders and/or permissions. i'm not using anyone else's code but i am using some artwork and a man page that i've adapted. > For this reason (and others) you should always put an explicit, > unambiguous *grant of license* in the work, preferably in the README > document or somewhere prominent like that. > > The grant of license is a statement, preferably brief, that says exactly > what the work is, who holds copyright, who receives a grant of license, > and what that grants the recipient to do, under what explicit conditions. > > For example: > > Copyright © 2018 Ben Finney > Purple Drachma is free software: you are free to copy, modify, > and/or distribute this work under the conditions of the GNU Affero > General Public License, version 3 or later as published by the Free > Software Foundation. See the file LICENSE.AGPL-3.0 for details. yes, i'll be putting a license on the code and any of the artwork i've made. thank you, songbird -- https://mail.python.org/mailman/listinfo/python-list
Re: setup.py and licensing questions
songbird writes: > can i put multiple License lines in setup.py > classifiers like: ? > > "License :: OSI Approved :: ???", > "License :: OSI Approved :: ???", Yes. The semantics of that are not formalised, to my knowledge. You would be signaling that the specified licenses are involved somehow, but not how they combine for this specific work. For this reason (and others) you should always put an explicit, unambiguous *grant of license* in the work, preferably in the README document or somewhere prominent like that. The grant of license is a statement, preferably brief, that says exactly what the work is, who holds copyright, who receives a grant of license, and what that grants the recipient to do, under what explicit conditions. For example: Copyright © 2018 Ben Finney Purple Drachma is free software: you are free to copy, modify, and/or distribute this work under the conditions of the GNU Affero General Public License, version 3 or later as published by the Free Software Foundation. See the file LICENSE.AGPL-3.0 for details. -- \ “You don't need a book of any description to help you have some | `\kind of moral awareness.” —Dr. Francesca Stavrakoloulou, bible | _o__) scholar, 2011-05-08 | Ben Finney -- https://mail.python.org/mailman/listinfo/python-list
setup.py and licensing questions
hi, i'm currently working through all the packaging and licensing stuff for my project and want to put the license in the setup.py file, but there may actually be more than one license (GPL ones for the artwork i've borrowed from another project and whatever license i choose to put on my own code and the artwork i've done). can i put multiple License lines in setup.py classifiers like: ? "License :: OSI Approved :: ???", "License :: OSI Approved :: ???", thanks, songbird -- https://mail.python.org/mailman/listinfo/python-list
