I understand your concern since it doesn't look very DRY to put the license
in all the source files but I believe
that putting at least a header in each of the files as well as a full
License file in the root of your project is the
best way to do it.

Check this:
http://www.oss-watch.ac.uk/resources/opensourceyourcode#applying-the-licence

Cheers,
Gil


On Mon, Sep 9, 2013 at 2:18 PM, Jonathan Hartley <tart...@tartley.com>wrote:

> A small Python project of mine is apparently being included in Chromium,
> because I've had a bug report from them that my source files (plural) fail
> their build-time license checker.
>
> They'd like me to include a license and copyright info in every source
> file (including empty __init__.py files).
>
> I've responded that I don't want to be unhelpful, but I don't believe in
> putting duplicate license and copyright info in every source code file. To
> my mind, it belongs in a single central place, i.e. the project LICENSE
> file.
>
> Am I being unreasonable and/or daft?
>
>     Jonathan
>
> --
> 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<https://mail.python.org/mailman/listinfo/python-uk>
>
_______________________________________________
python-uk mailing list
python-uk@python.org
https://mail.python.org/mailman/listinfo/python-uk

Reply via email to