Joomla Framework and the LGPL - Say No!
This is in response to a potential license change to lgpl for joomla! framework
Joomla was founded on the principle of Open Source Matters and a change to using the LGPL licence for the framework is completely against that. For those of you that don't know the LGPL allows the code to be included in proprietary, closed source software.
How does allowing people to produce closed source software with the Joomla Framework support the principle of Open Source Matters?
Just another rant?
Before you think this is Brian just going off on a rant of his own I'm not alone with this view. The Free Software Foundation, the people behind both the GPL and LGPL licences, agree.
But we should not listen to these temptations, because we can achieve much more if we stand together. We free software developers should support one another. By releasing libraries that are limited to free software only, we can help each other's free software packages outdo the proprietary alternatives. The whole free software movement will have more popularity, because free software as a whole will stack up better against the competition.
Source https://www.gnu.org/philosophy/why-not-lgpl.html available in multiple languages.
It doesn't effect Joomla?
The proposal states that this change is only for the Framework and it has no effect on the CMS but once again that is not 100% true.
Joomla is licenced GPLv2 or later but, and this is very important, the GPLv2 licence is NOT compatible with the LGPL v3 licence. Source: The perils of LGPLv3. Now to be fair the proposal statement does not mention which version of the LGPL would be chosen but if we assume it is the latest version then that would mean a change in the licence for Joomla would be required as well.
So a statement that says "This potential license change would only apply to the Joomla Framework, but not to the Joomla Content Management System (CMS)." is, potentially, not true. IF the Framework uses LGPLv3 then Joomla would need to change its own licence to GPLv3 in order to use its own framework.
UPDATE: The original post at joomla.org has now been updated to clarify that it is referring to LGPLv2.1 but this still effects Joomla!
Joomla only allows extensions to be created under the open source GPLv2 or later licences but with this proposal the Joomla Framework would allow "applications" written with the Joomla Framework to be under a closed source proprietary licence. So now we have to try and explain to "users" that no the Joomla Framework is NOT the software that Joomla is written with and is at the moment, and for the foreseeable future unrelated, so you have to use GPL for Joomla but you don't for the Framework but don't think you can use the Framework with Joomla because it's not the same thing. Yes that's right the Joomla Framework is not Joomla - it is something completely different which may or may not be used by Joomla at some time in the future. Confusing? Yes it sure is. Two unrelated products sharing the same name but with different code and importantly different rules. IF the Joomla Framework had a different name then that confusion would go away and one objection to the LGPL licence change would be removed.
But our competitors use LGPLv3?
While some use a more permissive licence than the GPL others do not. Drupal for example uses GPLv3.
The only people that really benefit are those people who want to take the Framework and use it in a proprietary piece of software. Are those same people likely to contribute to the Framework itself and help to develop it?
Open Source Matters
This is our founding principle. If someone won't use the Joomla framework because they want to use it to produce closed source, proprietary software then tough luck go and find another php framework to use.
- This is against the principle of Open Source Matters
- This would, probably, mean changing the licence of Joomla to GPLv3
- Confusion abounds - two products with the same name with different rules
- The argument about competition is irrelevant.
- This only benefits those who wish to take open source software and use it in proprietary closed source software.
- And once againt this is against the principle of Open Source Matters
Comments are welcome here but perhaps you should be commenting on the official thread in the forum