Change licence to something more liberating

[eimantas]

This licence does not allow of inclusion of this library into iOS applications. Any chance you can fork the project with MIT, BSD or some similar licence?

[penduin]

iOS apps can't use LGPL code? searches and reads Huh. That surprises me a bit. Yet another case of Apple having backwards policies. Guess I shouldn't be that surprised. ;^)

Sounds like there's a common maneuver here, the addition of a "static library exception" clause to the license. Would that be sufficient in your case? It's always a bit painful to take freedom away from users, but anybody on iOS gave that up anyway, and it's not likely that end users are going to want custom versions of a JSON parser. :^)

In any case I'm always interested to hear about this running on other platforms, be sure to post any patches needed for clean building etc!

[minego]

I'm sure we can make the change to allow static library exception.

[penduin]

No answer for two weeks, here or by email...

Adding a static library exception to our licensing isn't objectionable, but until I hear that doing so will actually be helpful to somebody, I'll leave the license as it is. If that exception wouldn't help but an alternate license would, we'll need to chat with management. My hunch is they'd probably be OK with MIT/BSD/etc, but it might take a little while to get a decision.

To eimantas or anyone else looking to use WJElement on iOS: feel free to re-open this, let me know whether the static lib exception will do the trick for you, and I'll go ahead with either adding that clause or reopening talks with management about alternate licenses.

[penduin]

Worth mentioning here:
WJElement is licensed as LGPL. Since we do not specify a version, according to the LGPL text itself, that means you are free to use it under the terms of any version of the LGPL. Current (version 3) copies of the GPL and LGPL are included in WJElement, but as they state, any previous version may be used as well.

For clarification, I've added "(any version)" to the documentation where the LGPL is mentioned.