I have forked a project with LGPLv3 license and I did there a lot of changes. Can I distribute a new version under the MIT license?

Or only the possibility is to write the code from "scratch"?

Alternatively: To which license is it possible to migrate, from LGPLv3?



You will have to do a clean-room implementation of the substitute MIT-licensed library. That means to not look at all on the existing library except the public interface defintion. You might have made this approach already impossible by looking at the existing code. If you look at the existing code, it usually can be considered already a derivative.

See also this related question https://softwareengineering.stackexchange.com/questions/151515/rewrote-gnu-gpl-v2-code-in-another-language-can-i-change-a-license

  • 2
    To answer the last part of the question, LGPLv3 does permit relicensing to straight GPLv3.
    – MadHatter
    May 11 '20 at 11:34
  • Seems like something is wrong in the system or some software. For example, github.com/ethereum/trinity (MIT) came from Ethereum - LGPLv3 (compared dates and code) and github.com/hyperledger/besu (Apache License 2.0) came from the same. From this discussion, it looks like they broke the LGPLv3 license.
    – Maximi
    May 12 '20 at 15:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.