unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Carsten Mattner <carstenmattner@googlemail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Updating copyright years
Date: Thu, 12 Jan 2012 01:22:30 +0900	[thread overview]
Message-ID: <87y5te8b09.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <CACY+Hvpf5LUmbK11Xye1ZfQK8CbQ02k+=veOyTFseiLRx258_A@mail.gmail.com>

Carsten Mattner writes:
 > Ted Zlatanov writes:

 > > Doesn't the act of modifying the file to insert the new year make
 > > the file modified and thus require the new year?  Heh heh.

No.  Dates are not expressive works.  Q.E.D.

 > Does anyone know why it's required to include a date (year) in
 > copyright headers.

I don't know what the current situation is exactly, but the basic
thing is that in the U.S., the automatic Berne Convention copyright
doesn't require any notice at all (of course that's true of all Berne
Convention signatories).  If you receive a work with no notice, you
must assume that all (copy) rights are reserved to the owner, even if
you don't know who that is.  However, the owner's powers of
enforcement are basically limited to a cease-and-desist order on
copying, and destruction of existing unlicensed copies.

If you want to press criminal charges, and IIRC also to sue for
damages (at least for statutory damages), you need to register your
copyright, and in turn you are obliged to provide a notice of
copyright, including when copyrights in the work were established.
The reason for that requirement today is mostly moot: copyrights do
expire (although we'll probably not see that day), and the copyright
notice tells the user when.

 > In the same context, do all licenses lend themselve to just be
 > referred in the file
 > header (foobar $LICENSE_NAME .... found in LICENSE), or is this dangerous?
 > Is a complete verbatim copy of the license a requirement? Maybe if
 > the file is distributed separately?

The problem with a permission-by-reference is that the user doesn't
know what her rights are, not that the owner of the copyright can't
enforce any restrictions that they choose to maintain (if they're
enforceable at all, of course).  With a well-known license such as the
GPL, it's really not necessary to provide a copy of the license from a
legal point of view (except in cases where it's an invariant section
in an FDL document or the like).  However, the GPL is also an advocacy
document, so providing it in every distribution is a GoodThang.



  reply	other threads:[~2012-01-11 16:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1RilkG-0001VX-GA@quimby.gnus.org>
     [not found] ` <m3fwfufjjl.fsf@stories.gnus.org>
2012-01-05 23:05   ` Updating copyright years (was Re: [gnus git] branch master updated: n0-17-447-g55c26cf =1= Add 2012 to FSF copyright years for Emacs files.) Katsumi Yamaoka
2012-01-05 23:14     ` Updating copyright years Glenn Morris
2012-01-05 23:54       ` Katsumi Yamaoka
2012-01-07  0:13       ` Richard Stallman
2012-01-10 23:35       ` Randal L. Schwartz
2012-01-11 13:43         ` Ted Zlatanov
2012-01-11 14:21           ` Carsten Mattner
2012-01-11 16:22             ` Stephen J. Turnbull [this message]
2012-01-11 16:36               ` Carsten Mattner
2012-01-12  4:13                 ` Richard Stallman
2012-01-12  6:52                   ` Stephen J. Turnbull
2012-01-11 19:39         ` Richard Stallman
2012-01-07  1:45     ` Updating copyright years (was Re: [gnus git] branch master updated: n0-17-447-g55c26cf =1= Add 2012 to FSF copyright years for Emacs files.) Stephen J. Turnbull
2012-01-07  4:16     ` Jason Rumney
2005-05-17 21:48 Updating copyright years Kim F. Storm
2005-05-18 13:20 ` Thien-Thi Nguyen
2005-05-18 22:44 ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y5te8b09.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=carstenmattner@googlemail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).