JOHN J. BARTON wrote:
Another goal you might consider is maximizing contributions to your project.
Absolutely. That's what we're trying to achieve by moving to a plug-in oriented architecture.
True, but GPL would prevent even internal use.
Not true. As Zsombor already pointed out neither GPL nor LGPL specify any limitations on internal usage.
You might have a look at "Toward true open source" By: Tom Walker
The author makes some good points but I find the article a bit too generalizing. Open source is written by many different people for many different reasons. It is somewhat utopic to believe that all of them would feel fine with a public domain license (or lack there of).
You also might take a look at the Eclipse Public License. It removes one sentence from the Common Public License. CPL was defined by the company I work for; nevertheless it offers a useful balance.
Hm ... As much as I'd like it - we don't really have the community eclipse has neither its industrial support. We thought that LGPL would be good for us as it would allow commercial entities to use the software and write commercial/closed plugins (I was not aware that companies tend to put it in the same category as GPL) and yet not allow someone else to make a closed fork of the communicator, and compete with us. We need all the feedback we can get in order to provide a decent peice of software.
I am not against unrestrictive licenses at all but I believe that in this particual case, a small project as the sip-communicator would do better with a more restrictive one. I believe this could help us avoid having public attention split over the SC and the commercial clones it might have.
It is of course very probable that I may have it all wrong. Could you please give us some examples of a case where a CPL, EPL or any other BSD like license would do good to the project whereas LGPL would have made that impossible?
Comments from anyone else are moste welcome (come on guys - speak up. i don't want to find myself a couple of years from now cursing myself for chosing sth when everyone else seemed to prefer sth else).
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org