Preferable in practical terms, as "more professional developers around VLC" sound a bit vague and, if that is really the stated goal, will you follow up on this with statistics to show if the license is drawing more professional developers to the project?
Competition.
AppStores and other crap of the post-PC era. :)
I would be very interested to see some data on that, say gathered over a year or two. Licenses decision really need more scientific approach, and if the main desire from choosing a license is to attract more third-party contributions, GPL vs LGPL is an interesting situation.
Have you seen a change in third-party contributions from companies for the libVLCcore after the license change? Its not the same type of software as the mods, but would still be interesting in this context.
Unlike other OSS licenses like BSD, Apache, LGPL, etc, GPL makes it impossible to utilize the library in any way in a commercial product. My current company works on some video related stuff, and we use OpenCV, ffmpeg etc but we completely steered clear of libVLC due to the GPL licensing (even though we think it's a fantastic piece of software). We will however be revisiting this now due to this excellent work by jbk.
That's not strictly true. You could license your commercial product as GPL, or (more likely) contact the library's authors and negotiate usage of the code under another license.
However, whatever your views on closed source products, they are still quite prevalent. IMO LGPL is a great license to get support from companies that sell these products, while ensuring that your software fundamentally remains free.
It remind me a few months ago the launch of meteor.js. I heard so much people saying that it was "not usable commercially"...
And the worse is that the same people have MongoDB in production with it's AGPL license.
If you are not intending to modify Mongo then AGPL is not restrictive, which may be OK. The database API is not usually considered as "linking" as it is a wire protocol.
So yeah, "contact the authors" can be hard, but an up-front agreement and price can make it pretty easy.
Yes
> Have you seen a change in third-party contributions from companies for the libVLCcore after the license change?
Yes, but most of them asked for more.
Those details can be very useful for the community of free and open source software, and when deciding licensing for oneself.
Why not?
What prevented you from asking someone like the Software Freedom Law Centre or Software Conservacy to help you enforce it? Do you actually need lawyers to enforce the license?
And SFLC and SC care about "more important projects" as we were told.
I usually shut down 2 violations per week and it is not decreasing...
The one that a VLC contributor working for Nokia (Rémi Denis-Courmont) managed to take down, for not being in compliance with GPL?
A cynic would ask if it has anything to do with not working for Nokia anymore...
The LGPL move started some time ago and Rémi was still at Nokia and he was pushing for it.
My understanding of LGPL is that it requires that users be able to switch out the LGPL-licensed code. This implies dynamic linking, not a difficult proposition, but more fundamentally it requires that users are able to access the LGPL code portion, delete it, and replace it with something else. I don't see how any old iOS user can do this without paying a dev fee.
There is no requirement that end users be able to do any of this on a platform without becoming licensed developers for that platform. (At the time LGPL was written, many platform vendors charged hundreds or even thousands of dollars for their developer tools.)
I think not. The issues were mainly 2:
- The Apple EULA was applied ON TOP of the GPL, whatever happened. This was clearly incompatible. And this is not resolved with Apple updates on the iTunes ToS.
- The Apple ToS did not allowed you to use the App for every use, which is a violation of the GPL §0. This is still an issue today.
Anyway, the title is, of course, misleading. VLC core, named libVLCcore is LGPL since last year (I did it too in december) and the wrapper for 3rd party applications libVLC was relicensed too at the same time.
This is different, since most modules of VLC are now LGPL. We speak about codecs, demuxers, format parsers, protocol accesses, filter and outputs. And those modules are way more important in terms of contributors and lines of code than the VLC core. In fact, we speak here of 230 people with around 300,000 lines of code, compared to 80 people and 80,000 lines of code for the VLC core.
Of course, from a higher-level point of view, all those playback modules are part of the "core of VLC" :)