Copyright assignments and the MAINTAINERS file

[Geoff Keating]

> X-Original-To: geoffk@foam.wonderslug.com
> Cc: Phil Edwards <phil@jaj.com>, Geoff Keating <geoffk@geoffk.org>,
>         "Joseph S. Myers" <jsm@polyomino.org.uk>,
>         Mark Mitchell <mark@codesourcery.com>, gcc@gcc.gnu.org
> Reply-To: law@redhat.com
> From: law@redhat.com
> Date: Mon, 16 Feb 2004 02:01:44 -0700
> X-OriginalArrivalTime: 16 Feb 2004 09:02:11.0390 (UTC) FILETIME=[902AADE0:01C3F46B]
> 
> In message <402D448D.8060607@apple.com>, Stan Shebs writes:
>  >This would be easier to track if MAINTAINERS mentioned the nature of the
>  >copyright assignment; for instance, assume it's personal by default, but
>  >if it's corporate, add the name of the assigning company in parentheses
>  >after the person's name or some such. We ought to be able to trust
>  >everybody to seed the file correctly, if the call goes out.
> And you'd really also need to know if it was a past/future assignment, 
> if it covered specific areas of the compiler or if it was for the entirety
> of GCC and so on.
> 
> At which point you've basically reinvented the copyright list maintained
> by the FSF.  Sigh.....

Yes.  Every person with commit access needs basically every piece of
information in the copyright list mantained by the FSF.  At the moment
this works by asking people whether they've made a copyright
assignment (or just assuming that they have), which has several
obvious problems.  Why can't the GCC part of that list be made public?

-- 
- Geoffrey Keating <geoffk@geoffk.org>