On 2 November 2010 04:31, Thomas Broyer <[email protected]> wrote: > On 2 nov, 03:42, Hilco Wijbenga <[email protected]> wrote: >> On 1 November 2010 17:48, Thomas Broyer <[email protected]> wrote: >> >> > On 2 nov, 00:43, nino ekambi <[email protected]> wrote: >> >> If i put the library under gpl is because a friend told me that the best >> >> way >> >> the keep improvment in the community. >> >> > I don't think it's compatible with Apache-licensed code however (as >> > soon as you start copying/adapting it; only using it isn't a problem, >> > it's a "bind by name" in Java, so it's not considered a "Derivative >> > Work" (otherwise GXT wouldn't be GPL'd)). >> > That's why I don't think too much about licensing and just pick the >> > one of the project I'm basing my work on (Apache 2.0, the same as GWT, >> > in this case). >> > And given that you don't intend to make money out of it (contrary to, >> > say, GXT), I'd recommend using Apache rather than GPL so anyone can >> > use it any way they want (provided they following the licensing terms; >> > item #4 of the Apache 2.0 license distributed in the COPYING file for >> > instance ;-) ) >> >> FYI, the BSD licence is GPL-compatible. So taking BSD (specifically >> "Apache License version 2.0") licenced code and relicencing it as GPL >> is perfectly legal. (Don't take my word for it, of course, do your own >> research.) It's called "commercial-friendly" for a reason: it >> explicitly allows *anyone* to "steal" your code and do with it pretty >> much as they see fit (with some very minor caveats). So if you don't >> want that then don't use a BSD licence. :-) > > Yes, you're right (my understanding, IANAL), except for one thing: the > modified version must include the original copyright and attribution > notices.
Yes, those are the very minor caveats I mentioned. :-) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
