epdiy
epdiy copied to clipboard
vroland
Will LGPL license be changed to MIT?
Thank @martinberlin for developed driver of lvgl, connected epdiy with the nearly best embeded GUI library. But the code cannot be merged because of LGPL license of epdiy: https://github.com/lvgl/lvgl_esp32_drivers/pull/75#issuecomment-1112135305
So will the license be changed to MIT? I know the license had changed from GPL, but this still doesn't look friendly enough for open source contributions.
Hi Lanistor, in #138 @vroland mentioned about the License being GPL:
The main reason is that I wanted derivative works to stay open-source.
I guess would be his ultimate decision what kind of License to use for his repository.
By the way I would like that my proposal is merged one day and even take the time to explore how to make it work in future LVGL versions. But all this is pointless if it will never be merged because there is a License conflict, something that is really not under my control as a developer. Everyone has his reasons to choose the right License for a project and a decision we should respect. Let's wait some weeks to know what are @vroland thoughts on this topic.
For now I'm still leading towards LGPL. IMO, it is permissive enough to allow linking to other code bases, which I see is a requirement for many people. For epdiy itself however, I was glad to have copyleft when lilygo forked the driver. That way, they had to publish all changes and we could easily make epdiy compatible. With LVGL, I don't see a problem with LGPL, even with static linkage: https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic Since they provide the source code, it is easy to re-link different another version of epdiy or vice-versa. So I don't see any conflict here, even with static linking.
Thanks. Will try to see if I can achieve somehow adding epdiy as a component with static linkage as you describe, Lanistor I’m closing here since your question was answered.