Technical group

1. Within Gaia-X, the "Legal Committee" deals with internal issues around compliance and licensing for the Federated Services Code. All questions related to more or less automatic contracting around data is not dealt with within Gaia X. Athos Legal Department works on these subjects (which are not yet taken into account by Gaia-X).

2. We should not welcome only free, if not too restrictive. And for companies to want to hang on to it, there needs to be a guarantee of transparency. Companies that want to provide a service are exposing themselves by going free.

3. Most open source licenses do not have a law, so there is a problem with litigation because the applicable law / jurisdiction is not specified.

4. If the contributors to the software are identified and few in number, the license can easily be changed (negotiation). If too many, it's too complicated.
You have to know exactly what you want to do behind it (what are the objectives of reusing the material protected by the license).The most reasonable is to use the same license as the federated systems of Gaia X.
5. CeCILL B (BERKELEY / APPACHE / W3C): very light version, minimum constraints for people who use these licenses => for Gaia X federated services? For example useful for libraries (bookstores) which will be reused by all
CeCILL C (LGPL): interesting in the way in which the components are articulated between them, problem of jurisdiction and law
CeCILL / GNU GPL (linux) = the most restrictive, more suited to the services provided by the participants (protects the community)

6. Eclipse is American, but also AISVL under Belgian law. Very American according to him, Stéphane does not recommend these licenses, especially for National Education, peri and extracurricular
7. CeCILL licenses have not really been maintained for 2 years, they would have to be recognized by GNU and OSI (Open Source Initiative), little used except for French research. They may be a drag compared to the Apache 2.0 or GPL 3 licenses known to all
To choose a license, you would need:
- Check user license choices (EdTech)
- Know what companies want to do and what they are willing to share and what needs to be protected
- Do we want others to reuse in a wider way or to stay in the community?
For a specific data service it is not necessary to have something too broad.