ARENA2036 Stuttgart · Friday, 6 November 2026

From one portal to data space management, built by the community.

–days

–hours

–minutes

–seconds

until doors open

Storyline

Why we are here

Today we start the successor of the Tractus-X portal: the Data Space Management Service and UI, directly in Eclipse Tractus-X.

01 · Problem

One central portal

Onboarding a company runs through one application for the whole data space. That does not scale to many data spaces and many onboarding service providers.

02 · Target (OSP 2.0)

Every OSP runs its own portal

One core service provider (CSP) provides the trust: admitted OSPs and issuers, the BPN, the directory BPN → DID and discovery. No passwords: the person signs in with the EUDI Wallet, the company proves itself with its Business Wallet.

03 · Today

Go-live at 15:15

One CSP and two OSPs run together. A company signs in, applies, gets approved and becomes an active member of the data space, end to end. Your first commit lands in Eclipse Tractus-X.

Tutorial

Your path through the day

Tick the steps off as you go. Your progress stays in this browser only.

Repository and commit path

Where you commit

One fork per team and repository: one team member forks the Eclipse Tractus-X repository into their GitHub account and adds the teammates as collaborators, so everyone in the team can push and merge in the team fork. The team works on the branch team/<n>. In the merge window at 14:45 the team opens one pull request upstream. The ECA check runs on every commit author and a Tractus-X committer merges. No ECA, no merge.

Your laptop

clone of the team fork, branch team/<n>

git push origin team/<n>

→git push

Your team's fork of Eclipse Tractus-X

owned by one team member, teammates as collaborators · fork of dataspace-mgm-services · dataspace-mgm-ui

team/1 … team/6

→pull request
14:45

Eclipse Tractus-X

eclipse-tractusx/dataspace-mgm-services · dataspace-mgm-ui

maincommitters mergeECA check

gh pr create --repo eclipse-tractusx/dataspace-mgm-services --base main --head <fork-owner>:team/<n>

main of the fork stays equal to upstream, nobody pushes to it. Same path for the UI with dataspace-mgm-ui. No code goes to tx-arena-events: only the spec is cloned from there (read-only, portal-backend-spec, for the UI portal-frontend-spec).

Work packages

Six teams, one data space

Six teams, every module once. Only Team 1 builds the onboarding: C1-M2 Registration and C1-M3 Application review with the EBW-Connector. The scaffold mounts a stand-in for every module, so the go-live runs even if a team is not done. Provided, not built: C12-M1 Process Orchestration, C5-M1 EBW-Connector, Keycloak (C2-M5). Not part of the day: C8-M1 Offers, C10-M1 Subscriptions.

Pick a module to see which teams work on it.

Without subscriptions, C6-M1 covers company connectors only, no connector as a service. The go-live shows onboarding and connector, not offers.

Friday, 6 November

The day

On the day this list follows the clock and marks what is happening now.

Roadmap

From the hackathon to the Community Days

The milestones update with the date. Select one for details.

Live from GitHub

Status right now

Read from the public GitHub API when the page opens and every five minutes.

Scaffold · service

…

Scaffold · UI

…

Team pull requests

…