|
|
[[_TOC_]]
|
|
|
|
|
|
# Basic facts
|
|
|
# Basic Facts
|
|
|
|
|
|
* The Hackathon <span dir="">#</span>3 will take place on the **20th and 21st of June 2022**
|
|
|
* Organized as **online event**
|
|
|
* Two main goals have been identified for the Hackathon format:
|
|
|
* Increase Gaia-X knowledge in the community
|
|
|
* Check/validate Gaia-X state (in regards to technology, processes and general terms & conditions) via bootstrapping a Gaia-X compliant provider and via deploying applications leveraging Gaia-X technology
|
|
|
* The Hackathon <span dir="">#</span>4 will take place on the **June 20-21, 2022**, * organized as **online event**
|
|
|
|
|
|
* **The coordination is done by the Gaia-X AISBL & MVG group with support from eco.**
|
|
|
|
|
|
* Four goals have been identified for the Hackathon format:
|
|
|
|
|
|
a. Increase Gaia-X knowledge in the community, encourage collaboration and enable participants to make use of current open-source implementations and codebase
|
|
|
|
|
|
b. Develop tools for creating / validating Self-Descriptions
|
|
|
|
|
|
c. Usage and further development of the Gaia-X Compliance Service and Trust Framework
|
|
|
|
|
|
d. Check & validate Gaia-X state (in regards to architecture, specifications, technology, processes and general terms & conditions) via creation of Gaia-X compliant federation services and service offerings leveraging Gaia-X architecture and projects
|
|
|
* Apart from a general track, two dedicated tracks focusing **on the provider/federator** and **on the user perspective** will be scheduled, one for each of the two Hackathon days
|
|
|
|
|
|
* The Hackathon #4 will center around the Gaia-X Scenarios, outlined by the CTO, the Gaia-X Trust Framework and Gaia-X Compliance.
|
|
|
|
|
|
1. Cross organisation identity and management access
|
|
|
- as a user/employee, Bob, part of organisation/federation A, I want to get from A’s federator, credentials which describe my access rights that I can use in another organisation/federation B
|
|
|
|
|
|
2. Registering Service Offering in a catalogue
|
|
|
- As a service provider, I want to create a Gaia-X Compliant self-description and find federation’s catalogues where to register them (ID/Link to the hosted SD)
|
|
|
|
|
|
3. Querying Service Offering in a catalogue
|
|
|
- As a service consumer, I want to find federation’s catalogues and filter Gaia-X Compliant services.
|
|
|
- Get detailed and protected information that is not ut of the service self-description
|
|
|
|
|
|
4. Data exchange
|
|
|
- As a data producer, I want to express policies and enforce access control (!= usage control) on my data, based on Gaia-X self-descriptions, using existing data pipeline toolset (no demo from scratch)
|
|
|
|
|
|
# Deliverables of the Hackathon
|
|
|
|
|
|
* Demonstrate usage of the Gaia-X Compliance Service and Trust Framework
|
|
|
* Contribute to and implement the Gaia-X Scenarios
|
|
|
* Contribute to the open source projects
|
|
|
* ... tbd
|
|
|
|
|
|
# From Proposal to Session
|
|
|
|
|
|
1. To propose for a presentation / hack for Hackathon #4 you can reach out to the track organisers or directly create a merge request / add your proposal to the proposal page (include link)
|
|
|
2. Please make sure to include all information related to the minimum requirements and to provide a clear link to the hackathon goals, Gaia-X scenarios and deliverables of the hackathon.
|
|
|
3. The organizers will discuss and evaluate the proposals and decide on the placement in the agenda.
|
|
|
4. Feedback will be given in a transparent way and documented on the proposal page.
|
|
|
5. The proposal deadline is May 26, 2022.
|
|
|
|
|
|
# Hackathon Registration
|
|
|
|
|
|
TODO
|
... | ... | @@ -26,7 +64,7 @@ Apart from the room for general discussions on the Hackathon, a room for all org |
|
|
# Overview of Hackathon Tracks
|
|
|
|
|
|
**1. General Track**:
|
|
|
- In this Track the Hackathon Introduction will take place. Additionally, the intermediate and finale results of the Hackathon will be presented within this Track.
|
|
|
- In this track the hackathon introduction will take place. Additionally, the intermediate and final results of the hackathon will be presented within this Track.
|
|
|
- **Coordinator**: Marius Feldmann
|
|
|
|
|
|
**2. Provider / Federator Track (1st day)**:
|
... | ... | |