Change licenses on code

The question was asked: 6 years 9 months ago   views: 5
0

Good day, ladies and gentlemen!

Have a fork of the project, whose code is released under GPLv3. Modules written by me, I released under MPL1.1. Do I have the right to change the license for other modules with the GPL for MPL if I made them a significant part of the changes (of course referring to the first author)?

I don't know exactly, but most likely would require the consent of all authors. Google the transition of the Linux kernel from GPL2 to GPL3 - Vladimir Gordeev Vladimir Gordeev 21-06-2012 в 09:46:30

Answers   2

0

Copyright holder (copyright holder), in this case the author has the right to change the licensing terms for new releases. However, since we are talking about derivative work, the copyright are all authors, regardless of contribution, so the General consent is necessary.

In any case, you cannot change the licensing rules for the already released under the GPL releases, they are still required to provide the source code, and, accordingly, anyone can make fork.

Answered: northerner northerner 21-06-2012 в 11:51:12
And if the project is included in parts under the GPL, and the project itself must be distributed under the GPL - alexlz alexlz 21-06-2012 в 20:10:53
As I understand it, if all the authors participating in the project will agree to change the license from GPL to MPL, we can safely change it in the whole project? - Валерий Валерий 01-07-2012 в 19:43:15
Safely - it will be pirates :-) - karmadro4 karmadro4 01-07-2012 в 21:56:32
Why "pirates" if all agree to change the license? - Валерий Валерий 03-07-2012 в 11:27:39
> all agree to change the license right now? The holder of each patch and of each copy-paste? > from the GPL code remains Well themselves acknowledge that the derived work... - karmadro4 karmadro4 03-07-2012 в 20:26:20
0

When switching from GPL2 to GPL3 consent is not usually required, as at the end usually says: "... or a newer version of the GPL".

If you release the modules under a different license (not gpl3), then You must distribute separately. The project with your modules or without you may redistribute only under the GPL3.

An exception is possible if the source project is released under multiple licenses.

Answered: Deleted Deleted 21-06-2012 в 11:03:05
@drdaeman, read vnimatelno SMU license. GPL-compatibility means that any piece of code you are permitted to distribute under the GPL, i.e. you described variant corresponds to a project under several licenses: GPL for the whole project + other compatible licenses on some of its parts, but these parts are licensed under GPL because of compatibility. - sercxjo sercxjo 21-07-2012 в 14:05:45
@drdaeman,read on your link: "... you can combine text, released under this license, issued under the GNU GPL in one larger program. All GNU GPL versions permit such combinations, without publishing them; they are also allowed to distribute such a combination if the combination is available for the same version of the GNU GPL. The other license is compatible with the GPL if it permits this too." So the whole project is released under the GPL. And this means that any part of it, including the fact that is licensed under another license, also licensed under the GPL. - sercxjo sercxjo 21-07-2012 в 22:26:07
@sercxjo: Yes, You are right, I was wrong. Sorry. - drdaeman drdaeman 23-07-2012 в 00:44:06