CTO Update
- The participants are informed about the termination of the Sub-WG Self-Description Lifecycle. No one objects and the dissolution of the group is ratified.
- Report on follow-up meetings with iSHARE https://ishare.eu/ and X-Road https://x-road.global/.
iSHARE:
– summarised objectives and provided updates
– work to have iSHARE network participants Gaia-X compliant
X-Road:
– started in 2001, and involved Finnish and Estonian Governments
– public-private partnerships
– exchange of citizens’ data – federation of ecosystems
– the specifications will be approved by the Governments
– input in terms of functional specifications will be provided to the Data Exchange Services Sub-WG
– input expected also on compliance specifications (e.g. with regard to trust anchors, time stamp issuers, list of subjects who maintain revoked certificates)
Vote to establish authoritative representation of Gaia-X deliverables from the TC working groups and their relationship to the Gaia-X Framework and other relevant external components
References to the preliminary work:
Discussion:
- Ongoing activity to represent identified deliverables, tasks, timelines, dependencies in Jira
- Goal to agree upon this representation, starting from the TC, in order to structure better the work and communicate better about deliverables
- The role of the OSS Community is also highlighted
- The representation clarifies what is in/out of scope for the Gaia-X (for example, Connectors are not covered)
- To be highlighted that these documents (e.g. IAM Federated Catalogue) should be defined through a discussion and alignment between groups (Michael)
- The Lighthouse projects should be involved in an early phase (Klaus)
- The fastest way for the Lighthouses to ensure that their requirements are addressed is to attend to participate in working groups and write Merge Requests (Pierre)
- The representation needs to be integrated and enriched with reference to versions of the documents
- Distinction between functional and technical specifications
- Information to be linked with Gitlab and Jira
- This work follows the TC reorganisation approved in December 2021
- Also breaking changes between versions can be highlighted (e.g removal of DIDComm)
- The representation is an authoritative reference to see and manage changes
- Content in the excel to be moved into html
- Overarching picture provided in the .ppt file – this is an important way to communicate with Lighthouses (no static view)
- Transparent view to be provided on the process to address requirements – alignment on the process to assign components to releases
- Goal to define tasks against deliverables
Decision:
The participants agree to use this representation of Gaia-X Framework and deliverables as a basis for internal alignment and communication to the outside.
Follow-up discussion on code contribution/FOSS Policy
(see https://community.gaia-x.eu/f/15767798 )
- Possible unclarities on the scope of the FOSS Policy are discussed/possible need to ask for clarification to the BoD (reference to the Lab or more general purpose) – consequent risk to slow down activities
- The intent of the Association is to create an OSS Community – governance is needed and the FOSS Policy Document says who is entitled to take decisions
Starting from the analysis document prepared by Cristina (see https://community.gaia-x.eu/f/15650841 ), a sub-group of TC participants (some expressions of interest have already been collected) will work on the clarification of all the TBDs. Until a different solution is identified and proposed, the FOSS Policy rules are applied.
WGs updates and sync
WG Service Characteristics
- Mission document ready for approval
- Infrastructure attributes should be ready after the workshop planned on 25 August by the Sub-WG
OSS Community
- A MR for the Mission Document has been prepared by Cristina. The participants are invited to review it.
|
