This repository was archived by the owner on Dec 18, 2022. It is now read-only.
Could Muse retroactively copyright already forked code? #712
SumianVoice
started this conversation in
General
Replies: 1 comment
-
|
Copyright holders can license their works how they please - so not so much retroactively, as offering it under a different license. But what is released GPL stays GPL (too), can't retroactively retract it, only potentially stop licensing new work under GPL, at which point forks could have a problem merging in changes into a GPL fork. Same kind of problem between different versions of GPL if there is no "or later" clause, etc. IANAL. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I just read an article about the nightmare of changing licensing retrospectively, by getting past contributors to comply with the new agreement. It seems highly illegal, but I had to ask myself the question, is it theoretically possible that Muse might try to muscle out forks of Audacity through legal threats?
I'm wondering if anyone else has a better understanding of how licensing works. I was under the impression that although original creators of material fundamentally own the copyright to that material, if it is ever licensed under GPL for instance, that it could not be re-licensed retrospectively and terminate already licensed copies of the material.
Beta Was this translation helpful? Give feedback.
All reactions