Skip to main content

Community Office Hour 2026-10-30

Stephan Bauer
Stephan Bauer
Eclipse Tractus-X Project Lead

Community Office Hour Meeting Minutes​

Status updates discussed in meeting:

Executive Summary​

  • The meeting clarified that the proposed Toolbox and wizard/starter-kit concepts still need alignment before definitive next steps and milestones are set.
  • The group agreed on tractusx-starter-kit as the working repository/project name.
  • The repository will support a static webpage and a dynamic wizard-like tool for generating configured Docker Compose files, initially for two or three components.
  • Release-process improvements are planned, focusing on better documentation, broader participation from initiatives and industries beyond Catena-X, and more accessible planning meetings.
  • Several tracked items remain blocked or awaiting review, including Gateway API updates, committers information, security follow-up, and the AI-related TRG discussion.

Topics Discussed​

Toolbox and Starter Kit​

  • The relationship between the Eclipse Tractus-X Developer Toolbox and the existing wizard remains unclear; intended integration and the next steps should be confirmed with him.
  • The planned repository will contain a static webpage and functionality to generate an easy-to-run, fully configured Docker Compose file with documentation, without requiring Kubernetes.
  • The initial scope is two or three components, with the possibility of adding more later.
  • The working name agreed in the discussion was tractusx-starter-kit.

Portal Hackathon​

  • The hackathon remains planned for Friday, with a large attendee list for the onsite meeting at the Arena.
  • Differences in the new architecture were not reviewed because they are expected to be discussed again immediately before development begins.

Eclipse Tractus-X Community Days​

  • Registration is still open; participants were encouraged to seek approval to attend and book hotels early.

Product Page and Repository Status​

  • The new product page was described as an improvement, but the displayed people may incorrectly mix committers and contributors.
  • The repositories and people shown on the page still need validation before the information can be considered accurate.
  • Work on the related item was deferred because other work is currently taking priority.

Release Management​

  • The release timeline is approaching the testing phase.
  • Initial pull requests for kits should be created soon so reviewers have enough time before the release.
  • A brainstorming effort planned for next week will examine the current release and planning processes, including how to document them better and make them more open to other initiatives and industries.
  • The current planning meetings were described as having approximately 100–120 participants in the past (two years ago) and approximately 10–20 currently -> this is the place where we can discuss and plan YOUR features -> don`t be shy, join the meeting and create your issues/requirements

Security​

  • The Eclipse Foundation is expected to offer a meeting next year to present security options.
  • The team discussed whether the existing security issue is still needed after changes for five individual users.

Gateway API and Other Issues​

  • The Gateway API work remains blocked until the active repositories are identified, after which a major issue can list the repositories requiring updates.
  • A pull request concerning the committers project description was created, but it still needs review by someone other than its creator.
  • The AI-related pull request remains unresolved after an earlier discussion about whether the topic needs its own TRG.

Decisions​

  • Decision: Use tractusx-starter-kit as the working name for the repository/project.

Action Items​

  • @stephanbcbauer: Create the tractusx-starter-kit repository and submit a pull request to the Eclipse Foundation repository.
  • @stephanbcbauer: Create the open meeting and kickoff issues on the Tractus X webpage.
  • @stephanbcbauer: Add screenshots to the security-related issue and move it to done if complete.
  • @stephanbcbauer: Check whether the committers pull request matches the issue requirements.
  • Unassigned: Review and merge the committers pull request; the creator cannot approve it.
  • @stephanbcbauer: Create a 15-minute meeting with the participants of the AI-related pull request discussion.
  • Unassigned: Decide whether the AI topic should have a separate TRG or be handled within another TRG.