Re: Run grand-replace to update copyright

[Werner LEMBERG]

>> AFAIK, this is not correct.  We have to make a distinction between
>> singular files and files that a part of a package.  What matters
>> for us is the *package* copyright.
> 
> I do not believe that there is a notion of "package" copyright in
> most countries' laws.

On page

  http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html

I see this:

  To update the list of year numbers, add each year in which you have
  made nontrivial changes to the package.  (Here we assume you’re
  using a publicly accessible revision control server, so that every
  revision installed is also immediately and automatically published.)
  When you add the new year, it is not required to keep track of which
  files have seen significant changes in the new year and which have
  not.  It is recommended and simpler to add the new year to all files
  in the package, and be done with it for the rest of the year.

This answers it, doesn't it?

> - does the GNU maintainers' guide make suggestions that are founded
>   in good legal understanding?

Definitely yes!  The FSF Europe is also working on this.  For example,
the GPL has successfully defended in German courts.

> - does lilypond follow the GNU maintainers' guide?

I hope so.  If we don't, we should access our working routines.


    Werner