Hello, I'd like to inform you that I've requested a restructuring review of the Keyple project to the EMO team (https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/908
).
All elements of the Keyple project are currently published under the EPLv2 license: this license is ideally suited to the protection of library-type project components.
- Keyple also offers 7 API components that enable the community to develop extensions to interface with the Keyple framework.
To enable these extensions to be designed without license conditions, → we would like to switch these 7 APIs to the more permissive MIT license.
- The project also illustrates the best practices for using Keyple libraries with 2 repositories of usage examples: the aim
is for users to adopt the best ways of integrating the Keyple framework into their projects. There is no issue of restitution on modifications that would be applied to these examples: → in the same way we would like to switch the 2 example repositories to
the MIT license.
For this change, I have the agreement of the 3 developers who made all the contributions to the concerned APIs and examples (https://accounts.eclipse.org/users/jfortune
/ https://accounts.eclipse.org/users/acristeatwy /
https://accounts.eclipse.org/users/amunsch ).
Discussion regarding Eclipse Keyple®
https://projects.eclipse.org/projects/iot.keyple
