Why would a file ever be seen out of context? Surely to make my source
available without the LICENSE file is breaking the terms of my license,
so I'm not sure why I ought to jump through hoops just to cater for such
people. Am I wrong?
Jonathan
On 09/09/13 14:30, Martin P. Hellwig wrote:
I concur, you do not have to put the full license text in it, a
reference to it is fine.
The logic behind that request is that some files may be seen out of
context of the project (as there is no reference), without having a
license attached the file can be legally misrepresented as being
public domain.
So yes a one liner as Andy has given is all you need, by having your
name and year, any reference can be then looked up by anybody who is
interested.
On 9 September 2013 14:24, Andy Robinson <a...@reportlab.com
<mailto:a...@reportlab.com>> wrote:
On 9 September 2013 14:18, Jonathan Hartley <tart...@tartley.com
<mailto:tart...@tartley.com>> wrote:
> They'd like me to include a license and copyright info in every
source file
> (including empty __init__.py files).
I have had this with big companies before, long ago. It may actually
be sufficient to have one line saying something like...
"Copyright Jonathan Hartley 2013. MIT-style license; see
mypackage/LICENSE.TXT for details"
- Andy
_______________________________________________
python-uk mailing list
python-uk@python.org <mailto:python-uk@python.org>
https://mail.python.org/mailman/listinfo/python-uk
_______________________________________________
python-uk mailing list
python-uk@python.org
https://mail.python.org/mailman/listinfo/python-uk
--
Jonathan Hartley tart...@tartley.com http://tartley.com
Made of meat. +44 7737 062 225 twitter/skype: tartley
_______________________________________________
python-uk mailing list
python-uk@python.org
https://mail.python.org/mailman/listinfo/python-uk
