unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: Copyright notices
Date: Sun, 31 Jul 2005 12:36:42 +1200	[thread overview]
Message-ID: <17132.7450.945474.746680@farnswood.snap.net.nz> (raw)
In-Reply-To: <E1Dyt59-0004B0-Tr@fencepost.gnu.org>

 >     I will do the lisp/progmodes directory (probably sometime next week).
 > 
 > Thanks.
 > 
 > I think we should redo every file according to the new legal advice.

It occurs to me that if there isn't a release until 2006 (or later!) then all
the files will need to be changed again.  Now that the legal advice suggests a
straightforward solution perhaps this process could (ultimately) be scripted.

Given that the copyright seems to apply to Emacs as a whole:

"Our lawyer says it is ok if we add, to each file that has been in Emacs
 since Emacs 21 came out in 2001, all the subsequent years.  We don't
 need to check whether *that file* was changed in those years.
 It's sufficient that *Emacs* was changed in those years (and it was!).

perhaps all files could display the _same_ copyright notice (apart from
comment delimiters) for the period from the start of Emacs (1985?) to the
present?

Currently emacs/admin/notes/years has the above paragraph and notes from our
earlier uninformed discussions.  I think the latter should be removed and
(some of it contradicts the paragraph) and some statement about partial dates
e.g 1994,95,96,97 and periods e.g 2001-2004 could be added.  Ideally the file
should really be written by a lawyer if thats possible.

I am somewhat surprised that the FSF doesn't aleady have clear guidelines
about copyright notices for GNU projects and Free Software in general.
Currently, if I start GDB from CVS, I get:

> nickrob/39 src/gdb/gdb
> GNU gdb 6.3.50.20050729-cvs
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i586-pc-linux-gnu".
> (gdb) 

Not only is the year wrong but it seems to suggest that everything before 2004
is not copyrighted.  I don't pretend to understand these issues but it seems
like we could be giving away the family silver.

Nick

  reply	other threads:[~2005-07-31  0:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 13:54 Copyright notices Richard M. Stallman
2005-07-29 18:10 ` Thien-Thi Nguyen
2005-07-29 21:43 ` Nick Roberts
2005-07-30 15:16   ` Richard M. Stallman
2005-07-31  0:36     ` Nick Roberts [this message]
2005-07-31 15:20       ` Stefan Monnier
2005-08-01 14:19         ` Richard M. Stallman
2005-08-01  0:45       ` Richard M. Stallman
     [not found]         ` <17134.56687.951950.51407@farnswood.snap.net.nz>
2005-08-02 17:45           ` Richard M. Stallman
2005-08-04 17:06           ` Juri Linkov
2005-08-04 19:59             ` dired-do-query-replace-regexp (was: Copyright notices) Juri Linkov
  -- strict thread matches above, loose matches on Subject: below --
2005-07-13  5:16 Copyright notices Richard M. 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=17132.7450.945474.746680@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --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).