Update license from GPL-3.0 to LGPL-3.0 #69
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello everyone,
We're moving from GPLv3 to LGPLv3 to offer greater flexibility for both developers and businesses. This change allows our library to be linked with proprietary software, while still requiring any changes made to the library itself to be open-source under LGPLv3.
Key Changes:
License Update: The main library is now licensed under LGPLv3, allowing developers to integrate it into closed-source applications.
Open-source Core, Business Modules: Modifications to the core library must remain open-source under LGPLv3, ensuring that improvements to the core stay accessible to the community.
Improved Adoption: This update is designed to promote wider adoption, especially in enterprise settings, by reducing licensing obstacles.
We acknowledge that a more flexible license could result in less open-source code. However, in the context of administrative privilege management, many scenarios require specialized modules to handle industry-specific access control policies. These specialized requirements often fall outside the scope of the open-source mindset.
By adopting LGPLv3, our goal is to make it easier for the software to be adopted in specific use cases without forcing proprietary implementations to revert to GPLv3 just because of the original license. Our commitment is to keep the core open-source, while encouraging collaboration within the industry and the broader community.
Finally, I wanted to mention that this project was initiated by IRIT in 2018 and sponsored by IRIT and Airbus PROTECT through an industrial thesis from 2022 to 2025.
Thank you for your understanding
Eddie BILLOIR
PhD Student at IRIT and Airbus PROTECT