gpl
Contribution terms for an LGPL Licensed Project
<p>Background: I am making contributions to a certain project which is released under <a href="http://www.gnu.org/licenses/lgpl-3.0.en.html" rel="nofollow">LGPL</a> and also under a commercial license. </p>

<p>According to the terms of contribution in the project by doing so I am transferring all my rights and ownership of the code to the company which owns said project. </p>

<p>My question is whether this stipulation has any effect on the license-terms of the code I contribute? That is as far as I understand that once a code is released as <a href="http://www.gnu.org/licenses/gpl-3.0.en.html" rel="nofollow">GPLv3</a> (and LGPL seems to contain mostly permissions for use additions to GPL) that this license cannot be rescinded. </p>

<p>Is my contribution (independent of ownership) thus also LGPL in a way which cannot be rescinded? </p>

<p>Are their terms of contribution than just a way of saying that they can dual-license your code (if they so choose) for a Proprietary version of the product? </p>

<p>Do I lose the ability to do the later myself? </p>

<p>If you sign over the copyright of a piece of code, then under US copyright law you have essentially lost any authority over the code and any inherent right to use it. It is exactly as if a company employee had written it; for at least 35 years, you lose any and all rights of authorship. You may <em>not</em> use the code except under license from the assignee; in particular, you may <em>not</em> modify it and use it in your own proprietary program, unless you have permission from the company.</p>

<p>The default for a simple copyright assignment is that the assignee gains the right to do whatever they want with the code. If they own the copyright, nothing they do could conceivably be copyright infringement. Likewise, the original author often loses any right to do anything whatsoever with their code without explicitly gaining permission. Note, though, that the GPL is not revocable except under certain conditions; the company could at most make <em>future</em> versions proprietary. </p>

<p>That said, these agreements can be more complicated. The FSF copyright assignment licenses the code back to the author for use as the author sees fit; it also imposes conditions on how the FSF may use the code. Copyright assignments are generally standard contracts, and can have all sorts of terms. I'm not sure what the effect is if the FSF violates its transfer, but the specific legal document you have been asked to sign is very important. The details of understanding it are a matter for a licensed lawyer, not a Stack Exchange site. </p>
