in reply to Copyright issues: year range, module vs distribution, rename/reorganization

First off: IANAL, so any reader is advised to keep a bucket of salt at their reach.

So, putting things together. Each significant portion of your distribution has a publication year to it. Keep individual notices in the header of each source content file. List all applicable licenses, (c) notices, years in the distro license text. The purpose of the latter is to inform, and clarity does no harm.

Whether you can use just a range instead of a list, is up to your discretion. In a series of version releases, it is usually pretty simple to show where and when does a particular portion appear.

#1. One good reason to be clear about copyright is to let your users actually make use of your work, i.e. exercise the rights your license grants.

  • Comment on Re: Copyright issues: year range, module vs distribution, rename/reorganization