From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: gcc@gcc.gnu.org
Cc: Richard Stallman <rms@gnu.org>
Subject: Manual contributions and copyright assignments
Date: Wed, 21 May 2003 12:02:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.55.0305211340130.24110@naos.dbai.tuwien.ac.at> (raw)
RMS asked us to implement the following policy:
[P]lease don't install changes in the manual on the strength
of copyright assignments signed before Jan 2002. If a person signed
before that, assign@gnu.org can look at the papers and tell you if
they explicitly cover documentation. If not, we should get new papers
from that contributor.
As far as I understand, obvious fixes and minor changes (where we didn't
need a copyright assignment before) are not affected.
RMS, how do you suggest to proceed practically? This seems to affect more
than 100 developers with CVS write access, any of which can commit patches
of her/his own or others, and about 700 contributors overall (according to
/gd/gnuorg/copyright.list).
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
next reply other threads:[~2003-05-21 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 12:02 Gerald Pfeifer [this message]
2003-05-22 11:44 ` Richard Stallman
2003-05-23 17:42 ` Joe Buck
2003-05-23 18:22 Nathanael Nerode
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=Pine.BSF.4.55.0305211340130.24110@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=rms@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.
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).