On Mon, 23 Sep 2002, Joerg Schilling wrote:

>>You can put code that you have written under whatever license(s) 
>>you like.  However, when you accept code contributions from other 
>>people into your source code, they are the copyright owner of 
>>that code.  In order to _change_ the license of the software, you 
>>must get all of the people who have ever contributed code to the 
>>software to agree to the license change, or to assign the 
>>copyright of the code they've contributed to you.  Only once all 
>>parties have agreed to the license change and/or reassigned their 
>>copyright to you, can you change the license of the code, or 
>>release it under a multiple license which they've agreed to.
>
>>I can't speak for every software author or contributor out there,
>>but I know if anyone ever changed the license on a GPL'd piece of
>>software and that I had contributed to under the terms of the GPL
>>license, and I had not explicitly handed them my copyright and
>>did not agree to the license change, I would be calling a lawyer
>>instantly.
>
>AFAIK, I am the only author who did major contributions and I _do_
>already allow this kind of usage with cdrecord....
>
>Minor contributors have no own rights on the work.

Joerg, cdrecord isn't the topic of discussion here right now.  
cdrdao is.  If someone who had contributed to cdrecord decided 
they thought their rights were abused and wanted to pursue action 
against you for it, then that would be between you, them, and 
some court of law in some jurisdiction somewhere.

But it isn't the case right now, and nobody is talking about 
cdrecord and the GPL.


>>If in doubt however, one should contact a copyright/patent
>>lawyer.
>
>You definitely should...

I don't need to do that.  I do not have source code of my 
authorship right now which is in violation of the GPL, or being 
used in a piece of software which GPL violation is taking place.  
If some of my own code does end up in such a situation, I would 
indeed do so.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to