[jgroups-dev] JGroups license change ?

Hi all,

over the years I've had quite a few projects, either commercial or open 
source, turn down JGroups because of the (LGPL 2.1) license.

I've never been 100% happy with the LGPL myself because (1) it is long 
and complicated, and (2) because it is (and I'm not a lawyer) ambiguous. 
Even the creators of the LGPL spurn it...

So I'm thinking about changing the license for JGroups 3.0.

This is a request for comments/feedback. I'd like to get as much 
feedback as possible on whether we should do this and - if yes - to 
which license we should switch ?

I understand that most open source Java projects use ASL 2.0, so this is 
a likely candidate, however, there are others such as BSD, MPL, EPL and 
so on.

Unlike other projects, I wrote most of the current JGroups code, so a 
license change should be easy. The procedure would be to track down all 
contributors in the 3.0 code base and ask for their permission to change 
the license. If someone objects, I'd have to pull his/her code or 
rewrite it.

Should we embark on this ?

Counting on your feedback ...
Cheers,

-- 
Bela Ban
Lead JGroups / Clustering Team
JBoss

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Javagroups-development mailing list