Skip to main content
Open Source

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    The trouble with that is the "GPL condom" problem: I create a MIT library which does nothing other than proxy calls through to your library. I release the (minimal) code to my library. I can now use my MIT licensed library in any code I feel like without ever releasing the code to your library. Commented Jan 2, 2021 at 21:04
  • Quite similar (duplicate?) I'm developing a library. Is there a license similar to GPL3 that doesn't force a license change for the project? Commented Jan 2, 2021 at 21:32
  • 6
    You want your code to be usable in projects under permissive licenses like Apache 2 and MIT. Those projects want to be usable in proprietary projects. Do you want your project to exist within an MIT-licensed project without stopping that MIT project from being included in a proprietary project? If you do not object to that, you want a permissive license. If you do object, you want your license to impose requirements on downstream projects that force source disclosure (i.e., you want a copyleft license like the GPL). Commented Jan 2, 2021 at 21:38