On Thu, Jun 12, 2008 at 2:29 PM, Mark Reinhold <<a href="mailto:mr@sun.com" target="_blank">mr@sun.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The issue here is not one of copyright.<br>
<br>
The problem is, as I explained back in April, that you based the Closures<br>
prototype on the JRL source distribution, and under the terms of the JRL<br>
you don't have the right to publish your modified version under the GPL,<br>
or to forward-port your changes to a GPL'd OpenJDK source tree and<br>
publish that. (IANAL, but that's my best understanding of the story.)</blockquote><div><br>Your understanding of my development processes is incorrect. In any case, my development processes are irrelevant. I own my changes until I license or contribute them to another party. Sun has granted me a license to the openjdk code under GPLv2. Under section 2 of that license I have been granted the right to distribute my modified version - that is, a version that contains only Sun's GPLv2 code with my own changes. <b>Sun is attempting to repudiate its license to me under the GPL by adding additional restrictions to my ability to distribute my modified version - specifically, the requirement that I contribute my changes to Sun Microsystems before publishing them under GPL. That is a violation of section 6 of the GPL.</b> Presuming you want downstream receivers of openjdk code to be bound by GPLv2 section 6, Sun Microsystems must honor its license.<br>
<br>You have my changes. Please describe precisely what intellectual property I have misused and in what way. Otherwise I plan to publish my changes on or after June 21.</div></div>