... | ... | @@ -13,11 +13,13 @@ |
|
|
## Goal
|
|
|
|
|
|
This hackathon edition is different because we have for the first time a proper, approved, measurable set of rules to fullfil in order to be Gaia-X compliant.
|
|
|
Thoe rules are available in the **[Gaia-X Trust Framework document](https://gaia-x.gitlab.io/policy-rules-committee/trust-framework/)**.
|
|
|
Those rules are available in the **[Gaia-X Trust Framework document](https://gaia-x.gitlab.io/policy-rules-committee/trust-framework/)**.
|
|
|
|
|
|
With this regards, the CTO office would like to stress the important of using and contributing to the Gaia-X Registry and Gaia-X Compliance APIs.
|
|
|
|
|
|
In order to streamline our effort to deliver Gaia-X, **only** scenario and projects committed to contribute or use the [Gaia-X Registry](https://gitlab.com/gaia-x/lab/compliance/gx-registry) and [Gaia-X Compliance](https://gitlab.com/gaia-x/lab/compliance/gx-compliance) API will be accepted.
|
|
|
In order to streamline our effort to deliver Gaia-X, projects committed to contribute or use the [Gaia-X Registry](https://gitlab.com/gaia-x/lab/compliance/gx-registry) and [Gaia-X Compliance](https://gitlab.com/gaia-x/lab/compliance/gx-compliance) API will be prioritized.
|
|
|
The CTO office reserves its right to not accept project unrelated to the Gaia-X compliance.
|
|
|
|
|
|
|
|
|
A. Increase Gaia-X knowledge in the community, encourage collaboration and enable participants to make use of current open-source implementations and codebase
|
|
|
|
... | ... | |