Nelson B Bolyard wrote:
> Today, I see the FSF web site talks about "copyright assignment". I don't
> know all the implications of that, but I presume that it is essentially
> a relinquishment, except that you keep your own name on the copyrighted
> work.
>
> http://www.gnu.org/licenses/why-assign.html says:
>
>   
>> Why the FSF gets copyright assignments from contributors
>> by Professor Eben Moglen, Columbia University Law School
>> [...]
>> In order to make sure that all of our copyrights can meet the
>> recordkeeping and other requirements of registration, and in order to be
>> able to enforce the GPL most effectively, FSF requires that each author
>> of code incorporated in FSF projects provide a copyright assignment, and,
>> where appropriate, a disclaimer of any work-for-hire ownership claims by
>> the programmer's employer.
>>     
>
> I would imagine that any piece of work whose copyright has been assigned
> to FSF is no longer free to be relicensed by its original author.
Copyright assignment is, and always has been, orthogonal to GPL licensing. The 
FSF
requires that you assign copyright to them for any non-trivial contributions to
their projects (Presumably so they have the ability to handle legal actions, 
such
as infringement lawsuits, for the entirety of the code base)


Attachment: signature.asc
Description: OpenPGP digital signature

-- 
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to