How can an open source license be compatible with a multi-licensing scheme?
According to a similar question, the author of a library could potentially change its license. But problems arise when the project as already received contributions from the community, because the contributors kind of 'own' the software it self.
Is this right?
I don't understand how such reasonable restriction, apply when a double license is applied to a product. E.g. I release a software with a double license:
- GPLv2|v3 for open source projects (users must release their code if using the given library publicly distributing the software using it)
- Commercial license that under certain conditions (e.g. payment), allows the user to not distribute their application's source code (e.g. they can pay the author and release a commercial closed source application)
I have several questions on this topic:
How this could be possible? Does the changes/contributions provided by the community itself be used under the commercial license once received? Isn't this something similar to change the license (see the linked question): you accept changes by the community and release them under another license? If this is legal, are there any difference/compatibility between major open source license such as GPLv2|3, lGPL, Mit, Bsd?