3 ms·
Hello, I am the author of VkFFT. When I made VkFFT I wanted license to be like this: your project doesn't have to be open-source, but please share your modifica
by DTolm 6y ago
Hello, I am the author of VkFFT. When I made VkFFT I wanted license to be like this: your project doesn't have to be open-source, but please share your modifications to VkFFT. I think about switching it to MPL 2.0, is this one better for everybody?
- cycloptic 6y agoThat would probably do what you want because it applies on a per-file basis and not to the entire program, but make sure you read the MPL FAQ and the fine print before making such a change: https://www.mozilla.org/en-US/MPL/2.0/FAQ/ https://www.mozilla.org/en-US/MPL/2.0/FAQ/
- snovv_crash 6y agoYes, MPLv2 does what you want. Consider that it's also used by Eigen. I strongly advocate for MPLv2 for math style libraries.
- drran 6y agoGoal of LGPL is to protect freedom of developers to modify code of a library (e.g. to improve it, fix bugs, fix incompatibilities, port to new hardware, etc.) shipped as part of proprietary application. This freedom is important for developers of niche OS'es. This protection works, because of hard consequences for proprietary code in case of license violation: proprietary code must be released under GPL then. MPL doesn't protect such developers, but it "forces" contribution of changes back to original code. In reality, it's ignored. Header-only library cannot be compiled as separate library, so requirements of LGPL cannot be met by proprietary code.
- Seirdy 6y agoIt might be better to simply switch to the LGPL v3 or later, since that explicitly addresses header libs.