[JXTA discuss] Re: [JXTA dev] Any plans for JXTA License to replicate Java License?
[email protected] Mon, 11 Dec 2006 12:18:44 +0800
| Newsgroups | gmane.comp.java.jxta.devel,gmane.comp.java.jxta.general |
|---|---|
| Message-ID | <20061211121844.q1onlrsqo4c0sksg__48430.1571654671$1165810836$gmane$org@202.157.161.163> |
Apologies for cross posting. But this is something that needs to go to =20 Dev and Discuss lists for consideration and understanding. > > On the one hand, switching jxta license to LGPL would allow (L)GPL > projects to make use of jxta right now (which is currently literally > illegal, as jxta/apache licenses are GPL imcompatible). Alexander, sorry! I am unable to catch up with the above illegality. I =20 am keen to know if it is illegal for JXTA if an LGPL application =20 develops over JXTA or is it illegal for an LGPL application to use a =20 non-LGPL licenced Open Source technology like JXTA? As long as both, the application and the dependent technologies are =20 Open Source despite using different licensing recognized by the OSI I =20 do not see any illegality. It may have limitations in adoption but not =20 illegal as long as the terms specified in the respective licenses are =20 adhered to. Someone correct me if this is wrong. I am curious to learn how to make JXTA a popular option for those who =20 want to develop peer-to-peer or distributed applications. Appropriate or more open licensing that could bring more developers =20 into the JXTA fold is one move I believe would make it more =20 accessible. The most effective way to make JXTA well known is to see =20 if there was really a successful application that is catering to a few =20 thousand users in the enterprise or consumer market :-) Because P2P is =20 all about numbers!!! Cheers, Rajesh http://samooha.sourceforge.net Quoting Alexander Sack <[email protected]>: > On Fri, Dec 08, 2006 at 03:20:57PM +0800, [email protected] wrote: >> >> Wondering if there are any plans to make JXTA (or JXTA-J2SE) available >> under GPL or LGPL to keep the reference implementation inline with a >> single license? >> >> What are the pros and cons of doing so for projects that have already >> taken off based on the present License? > > On the one hand, switching jxta license to LGPL would allow (L)GPL > projects to make use of jxta right now (which is currently literally > illegal, as jxta/apache licenses are GPL imcompatible). OTOH, this > obstacle will be gone for projects that adapt (L)GPLv3, so the most > pressing need to do something about jxta licensing is about to be void > soon. > > Though, my personal believe is that LGPL is a more appropriate license > for jxta, I see that not all major contributors would be happy with > such a move. So IMO, a licensing switch is unlikely. > > > - Alexander > > -- > GPG messages preferred. | .''`. ** Debian GNU/Linux ** > Alexander Sack | : :' : The universal > [email protected] | `. `' Operating System > http://www.asoftsite.org | `- http://www.debian.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >