After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 634550 - Fix up copyright and license notices for St
Fix up copyright and license notices for St
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2010-11-10 22:25 UTC by Owen Taylor
Modified: 2010-12-06 17:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fix up copyright and license notices for St (55.36 KB, patch)
2010-11-10 22:25 UTC, Owen Taylor
reviewed Details | Review

Description Owen Taylor 2010-11-10 22:25:28 UTC
* Make sure all source files have a LGPL copyright header, and standardize
  non-standard variations of the header to a common form.

* Check and update all copyright notices.

* Remove 'Written By:' lines. They are universally incomplete and
  typically indicate only who started a particular file.
Comment 1 Owen Taylor 2010-11-10 22:25:30 UTC
Created attachment 174217 [details] [review]
Fix up copyright and license notices for St
Comment 2 Dan Winship 2010-11-11 13:11:31 UTC
Comment on attachment 174217 [details] [review]
Fix up copyright and license notices for St

>* Make sure all source files have a LGPL copyright header, and standardize
>  non-standard variations of the header to a common form.

The standard form recommended by the FSF now
(http://www.gnu.org/licenses/gpl-howto.html) ends with:

    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.

rather than giving their mailing address, so that everyone doesn't have
to update all their copyright headers again next time the FSF moves.

>* Check and update all copyright notices.

There are inconsistencies between "Copyright 2009, 2010" and "Copyright
2009-2010". I don't know if this matters at all. Also, it might be nice
to get rid of the "(C)"s everywhere, since they're legally meaningless.

>+ * st-overflow-box.c: A vertical box which paints as many actors as it can fit
>+ *
>+ * Copyright 2009, 2010 Red Hat, Inc.
>+ *
>  * Portions derived from st-box-layout.c, which is
>  *   Copyright 2009 Intel Corporation.

I don't think there's any need to keep the "portions derived from" line, and it's
inconsistent with the changes elsewhere.
Comment 3 Giovanni Campagna 2010-11-12 16:35:46 UTC
What about JS code?
Most of it does not have a copyright declaration at all, but of course that does not mean the authors are assigning copyright (to whom, anyway? GNOME Foundation?).
On the other hand, does writing copyright in JS increase memory / disk usage for user (and thus is bad)?
Comment 4 Owen Taylor 2010-11-12 19:52:55 UTC
According to "best practices" we should have copyright and license headers on all our source files. It feels ugly to have read and discard the headers for all the JS source files, but I doubt it's really a concern in practice.

In this commit I stuck to St since that was enough work to deal with and I had a particular request to do it from the MX maintainer (so patches could be folded back).

Copyright notices have almost nothing to do with actual copyright - whether I put in no copyright notice, or "Copyright 2010, The King of Siam", my code contributions are still copyright to me (or to my employer, if I'm doing them on company time). The main legal point of a Copyright notice, in my non-lawyer knowledge, is that you can prove that someone was *knowingly* violating your copyright.
Comment 5 Owen Taylor 2010-11-12 20:30:33 UTC
(In reply to comment #2)
> (From update of attachment 174217 [details] [review])
> >* Make sure all source files have a LGPL copyright header, and standardize
> >  non-standard variations of the header to a common form.
> 
> The standard form recommended by the FSF now
> (http://www.gnu.org/licenses/gpl-howto.html) ends with:
> 
>     You should have received a copy of the GNU General Public License
>     along with this program.  If not, see <http://www.gnu.org/licenses/>.
> 
> rather than giving their mailing address, so that everyone doesn't have
> to update all their copyright headers again next time the FSF moves.

All updated.

> >* Check and update all copyright notices.
> 
> There are inconsistencies between "Copyright 2009, 2010" and "Copyright
> 2009-2010". I don't know if this matters at all. Also, it might be nice
> to get rid of the "(C)"s everywhere, since they're legally meaningless.

The FSF recommendation is a list of all years. 2001, 2002, 2003, 2004, 2007, 2009, or whatever. It's there would ever be a legal situation on this code when a notice of 2006-2009 left up in the air whether there was code in their copyright 2007 or not and we cared. (It's not like copyrights _expire_ these days after all...) So I went with a policy of , for two years and a range for more than two years.

> >+ * st-overflow-box.c: A vertical box which paints as many actors as it can fit
> >+ *
> >+ * Copyright 2009, 2010 Red Hat, Inc.
> >+ *
> >  * Portions derived from st-box-layout.c, which is
> >  *   Copyright 2009 Intel Corporation.
> 
> I don't think there's any need to keep the "portions derived from" line, and
> it's
> inconsistent with the changes elsewhere.

That one cleaned up. Left a few other places where the history was more intricate and potentially more interesting.