Cray pointer paperwork is done.

David Edelsohn dje@watson.ibm.com
Sat Oct 22 23:13:00 GMT 2005


>>>>> Asher Langton writes: 

> The FSF has had that paperwork for nearly three months.  The last email
> I received from Ted Teah (on Thursday) indicated that the matter was at
> last resolved.

	The FSF has received incorrect paperwork from you and Mike and
LLNL at the beginning of the summer.  The FSF sent email last week that
the disclaimer was received and properly executed, not that the matter was
resolved.

> The paperwork sent to the FSF months ago seems to do this.  From my copy
> (dated 7/11/05):
> 
> "EMPLOYER LICENSE OF RIGHTS

	That is a license, not a copyright assignment.  This is where the
problem began: LLNL did not send the appropriate legal documentation that
the FSF requires from all developers and used their own boilerplate form
without discussing it with the FSF first.  A license does not transfer
copyright.

> I don't have any copyright on the code!  I never did.  The work was done
> entirely on the behalf of LLNL, so I have no legal claim to the code.

	That is exactly what LLNL now has changed.  LLNL has disclaimed
ownership of the code, so it reverts to you and Mike for you and Mike to
assign to the FSF.

> I signed one copy, but it was sent through LLNL's legal department, who
> modified it.  Again, to the best of my knowledge, I have no legal
> standing here.  I have no problem signing an unmodified Copyright
> Assignment, but whether I can do so is up to the LLNL legal department.

	Not only did LLNL modify the earlier assignment form, but they
signed it on behalf of you, which is not allowed.  If LLNL owns the code,
LLNL signs the document assigning *their* code.  If you own the code, you
sign the document assigning *your* code.

	I do not know if the most recent copyright assignment forms were
sent to you directly or through Mike Kumbera, but my current understanding
is that you need to sign the unaltered copyright assignment form assigning
*your* code to the FSF.

David



More information about the Gcc-patches mailing list