From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Joe Buck <jbuck@synopsys.COM>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Copyright forms for new contributor?
Date: Tue, 16 Oct 2001 13:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0110162146001.6927-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <200110161945.MAA06074@atrus.synopsys.com>
On Tue, 16 Oct 2001, Joe Buck wrote:
> The reason for not giving out the forms directly was that people were
> sending the wrong forms, making small (but legally significant) changes
> to them, etc. Since the contract has to be on paper, it works best if
> the FSF sends out the actual paper; before they switched to this approach,
> RMS had to personally check every word of every form, which doesn't work
> too well.
Are there any plans to allow digitally signed forms? I think Ulrich
Drepper wanted to do this for glibc.
> Just the same, we need a better procedure. Perhaps we SC members will
> need to take turns being the copyright form liason. We could set up
> a mailing list for the purpose of handling requests from contributors
> for the legal documents.
We also need a better procedure for maintainers to have access to the GNU
copyright.list listing assignments.
How do the assignments to the FSF interact with the presence of
non-FSF-copyright files in the tree? For example, some of the files in
the gcc/ada directory are copyright FSF, some are copyright Ada Core
Technologies, some are copyright Florida State University. If people with
FSF assignments contribute to these files, do their contributions become
copyright FSF (rather than any other copyright holder of the files)?
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2001-10-16 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011012115247.B25697@tornado.cygnus.com>
[not found] ` <20011012174437.B10341@linux11.lxfarm.csc.liv.ac.uk>
[not found] ` <20011012125150.C25999@tornado.cygnus.com>
[not found] ` <20011012190633.C10341@linux11.lxfarm.csc.liv.ac.uk>
[not found] ` <20011012142725.A26727@tornado.cygnus.com>
[not found] ` <20011015112854.A8793@linux11.lxfarm.csc.liv.ac.uk>
[not found] ` <20011015095852.D22414@tornado.cygnus.com>
[not found] ` <20011015162207.A17825@linux11.lxfarm.csc.liv.ac.uk>
[not found] ` <20011015114013.A23365@tornado.cygnus.com>
[not found] ` <20011015173305.B17825@linux11.lxfarm.csc.liv.ac.uk>
2001-10-15 9:39 ` Diego Novillo
2001-10-16 1:38 ` Gerald Pfeifer
2001-10-16 12:47 ` Joe Buck
2001-10-16 13:33 ` Florian Weimer
2001-10-16 13:43 ` Diego Novillo
2001-10-16 14:03 ` Joe Buck
2001-10-16 13:54 ` Joseph S. Myers [this message]
2001-10-16 14:08 ` Joe Buck
2001-10-17 12:21 ` Gerald Pfeifer
2001-10-17 17:42 ` Carlo Wood
2001-10-16 15:09 ` Craig Rodrigues
2001-10-16 19:38 ` Joe Buck
2001-10-16 8:46 mike stump
2001-10-16 17:53 mike stump
2001-10-21 19:35 dewar
2001-10-22 2:09 ` Richard Earnshaw
2001-10-22 4:13 Richard Kenner
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.LNX.4.33.0110162146001.6927-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.COM \
/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).