On Wed, 2008-01-16 at 16:43 -0800, Jody Garnett wrote:
> Adrian Custer wrote:
> > We can't start this step until we have all signed the copyright
> > assignment document. Then the question arises how we want to go about
> > automating this as much as possible.
> >   
> I think we can start this step; and I don't think we can automate it - 
> as updating these headers
> is our providence review.
> > The situation today is that the headers are WRONG. The line that says
> > (c) PMC is incorrect since that entity does not exist, it cannot hold
> > copyright. The legal situation today, DESPITE what the headers may say,
> > is that each contributor of non-trivial changes to any file holds a
> > joint copyright to that file. The best assumption is that all the
> > usernames in the svn log are those who have copyright on the file.
> > Essentially,
> >   svn log FILE | grep '^r[0-9]'
> > gives the full list of copyright holders, except that for some of those
> > the copyright will rest with their employers. 
> >   
> Okay if that is what we need to do then that is what we need to do. 
> Perhaps we can sort this out a head of time
> using a batch process that genrates a file; with the filename followed 
> by each person in the log history?
> - org.geotools.GeoTools jive, acuster, .....

But if jive, acuster, ... have signed the letters, then we can
automatically strip their names. We only need the list of names of
non-signees (those who retain (c) and license OSGeo the use of their
code under the LGPL). Hence, it makes more sense to proceed in order.

That's why we need to (1) pick a course of action (2) sign, seal, and
deliver (3) go after the headers. 

So we need to frame up a 'proposal' asking the community:
  who is willing to sign (c) to OSGeo, if the most pick to go that route
  who is willing to sign (c) to FSFeu, "
  if they prefer [] the OSGeo route or [] the FSF route
I would rather that a core contributor (PMC/module maintainer) do this.

Then
  we have an irc where we formally decide on a route
then
  we sign and sign and sign
then
  we clean the headers out.

The headers and clean up rules are the only thing we can be working on
concurrently and I'd just assume stay focused.

--adrian


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to