[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCHES] 21.3.50 for Cygwin: patch 7
From: |
Kim F. Storm |
Subject: |
Re: [PATCHES] 21.3.50 for Cygwin: patch 7 |
Date: |
11 Dec 2002 11:23:09 +0100 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 |
Eli Zaretskii <address@hidden> writes:
> On 11 Dec 2002, Kim F. Storm wrote:
>
> > Joe Buehler <address@hidden> writes:
> >
> > > Kim F. Storm wrote:
> > >
> > > > We usually cannot copy (or adapt) stuff from XEmacs, as we require
> > > > papers from the original author, as well as anyone who has contributed
> > > > with anything but tiny changes to the code.
> > >
> > > The files I copied already had copyright notices that say that the FSF
> > > owns the files. Is that adequate?
> >
> > We require papers for all "non-tiny" changes that are installed in CVS.
>
> It might be useful to check the list of existing assignments on gnu.org.
> It could happen that Andy already has an assignment for Emacs-related
> work, in which case the problem is solved.
Sure, but I cannot access gnu.org to check the list. I *did* ask if
someone would do that.
In any case, I believe it is important that all emacs developers
cleary understand that we cannot just pick any piece of software and
include it in emacs just because a comment in the file says it is
GPL and copyright FSF.
AFAICS, the only mentioning of this principle is in the TODO file:
> Since Emacs is an FSF-copyrighted packages, please be prepared to sign
> legal papers to transfer the copyright on your work to the FSF.
Maybe we can make this clearer by adding more sections to the admin/README
file (or a different file in the CVS tree) which give a brief list of
"principles and practices", and then point any new emacs developer to
that file when they join the team.
It could include stuff like:
* legal issues (and how to check papers)
* coding style
* tips for using CVS
* active development / release branches
* "links" to other important documents
--
Kim F. Storm <address@hidden> http://www.cua.dk
- [PATCHES] 21.3.50 for Cygwin: patch 7, Joe Buehler, 2002/12/10
- Re: [PATCHES] 21.3.50 for Cygwin: patch 7, Paul Eggert, 2002/12/12
- Re: [PATCHES] 21.3.50 for Cygwin: patch 7, Joe Buehler, 2002/12/13
- Re: [PATCHES] 21.3.50 for Cygwin: patch 7, Richard Stallman, 2002/12/14
- Re: [PATCHES] 21.3.50 for Cygwin: patch 7, Joe Buehler, 2002/12/16