3 ms·
Yes. I release software X under license that turns to Y license after z years. I am free to take exactly the same code and do the same at a later date. Or ar
by benj111 3y ago
Yes.
I release software X under license that turns to Y license after z years.
I am free to take exactly the same code and do the same at a later date.
Or are you referring to code by a second submitter where their code goes gpl, but then you need to re get their permission to restart the clock.
I still think you could work around that if the license is structured correctly.
Treat the source tree as it stands at a point in time as a release that becomes open source 2 years later, but keep the core project closed.
So all code in the project is always available to be in the project.
- the_mitsuhiko 3y agoAt FSL-GPL artifact would raise very interesting legal questions I don’t want to explore :)
- benj111 3y agoI don't think it's that complicated. If I release software under the gpl and to someone to integrate in a closed source application. You don't have gpl code in a closed source application. You have code with 2 licenses. This is perfectly ok, the two pieces of software can coexist. This would be the same, if correctly structured. The only nit would be that code would be forever dual licenced. Some evil company could buy up the code base and do whatever they want and not release code back for 2 years.
- the_mitsuhiko 3y agoA today FSL artifact is an amalgamation of Apache/MIT licensed stuff and FSL licensed stuff. This amalgamation would not be possible with GPL per the GPLs license terms.