all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
Date: Thu, 06 Nov 2008 20:57:32 -0500	[thread overview]
Message-ID: <E1KyGbM-0000WR-DF@fencepost.gnu.org> (raw)

That is a free software license.  "Without fee or royalty" means you
don't have to pay to redistribute it.  So we can use those files,
but we have to maintain the copyright notices and license notices.

How did they get lost?

We must NEVER install code in Emacs without proper copyright notices
and license notices in each file.  Whoever installed these should have
checked them and noticed the lack of these notices.

When the file lacks a notice, it needs to be changed.  If the FSF has
copyright, then it needs an FSF copyright notice and a GPL license
notice.  Otherwise it needs the _right_ notices whatever they are.
Also, any non-FSF-copyrighted material must be checked by the FSF!

Also, we have to distribute the source code.  Someone said these files
are the result of "transforming" some other files.  What kind of
"transforming" was it?  If it is automated, then maybe these files
are the real source code.




             reply	other threads:[~2008-11-07  1:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  1:57 Richard M. Stallman [this message]
2008-11-07  5:37 ` http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 Chong Yidong
2008-11-07 17:05   ` http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 Richard M. Stallman
2008-11-07  9:47 ` http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 Sean Sieger

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

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

  git send-email \
    --in-reply-to=E1KyGbM-0000WR-DF@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.