Brian DeSpain <[EMAIL PROTECTED]> > > Yes - but the previous versions licensed under the GPL remain GPLd and > development can continue on the code. Can you explain why this is the case? > > In reality, the code would most likely *fork,* leaving one strand open > > and the other proprietary. > > That's exactly what would happen and that's why the GPL is there in the > first place. The copyright owner retains copyright, therefore can make > changes. You cannot retroactively change licenses under the GPL. People > retain their original rights under the GPL. How can licensees retain their rights against the copyright owner's will? Is there something in the GPL that requires this? --
- Converting/Splitting Code - Open to Closed Ralph Bloemers
- Re: Converting/Splitting Code - Open to Closed Brian DeSpain
- Re: Converting/Splitting Code - Open to Closed Samuel Reynolds
- Re: Converting/Splitting Code - Open to Closed Matthew C. Weigel
- Re: Converting/Splitting Code - Open to Close... David Johnson
- Re: Converting/Splitting Code - Open to Closed Eric Jacobs
- Re: Converting/Splitting Code - Open to Close... Matthew C. Weigel
- Re: Converting/Splitting Code - Open to Closed Ben Tilly
- Re: Converting/Splitting Code - Open to Closed Ryan S. Dancey
- RE: Converting/Splitting Code - Open to Closed Dave J Woolley
- Re: Converting/Splitting Code - Open to Closed Chris Sloan
- RE: Converting/Splitting Code - Open to Close... Lawrence E. Rosen
- RE: Converting/Splitting Code - Open to Closed Dave J Woolley
- RE: Converting/Splitting Code - Open to Close... Lawrence E. Rosen
- RE: Converting/Splitting Code - Open to Closed Ravicher, Daniel B.

