Skip to main content

Office Hour meeting minutes​

Infrastructure​

Release Management​

  • The first activities for the next release are coming up as per the timeline.
  • docusaurus of the website will finally be updated to 3.x 😍 Everyone who is responsible for a kit should join the kick-off as announced per the open meetings page.

FOSS​

Community/Open Planning​

  • Everyone is invited to join the community days in May 2025.

Feedback/Questions/Requests​

  • There's a new architecture whitepaper on integrating the identity hub with other TX components in the concept of a BYO-wallet concept.
  • The release timeline of TX, CX and the ecosystem are aligned here.

Tom Meyer

Office Hour meeting minutes​

Infrastructure​

  • Test Environments:
    • STABLE environment24.12 installations in early december
    • Test Management: Reference Quality Gate Checks and walkthrough them in "Test Management"
    • Resolved Issue with SAP DIV -> Onboarding should work now

Release Management​

  • Reminders
    • use TX EDC 0.8.0 RC5 -> RC6 is on its way -> Rediscuss in testmanagement daily during next week
      • we should improve test automation -> the umbrella helm chart targets to support that
    • reminder for open planning

Security​

  • GitGuardian will be removed soon.

FOSS​

  • TRG 7.09
  • discuss how to document releases between ecosystem releases and deployment experiences -> ongoing / announcement
  • TRG about testing will come up
  • Mano's election ended. Reminders
    • small amount of participations
    • points that would have been great: participation in community & handling of TRGs etc.
  • ClearlyDefined is down: revisit on next week and then ask via IP matrix check
  • MDX files in KITs: only if needed, is CC-BY-4.0

Community/Open Planning​

  • remove the .cal file and just state the time (in an international time format)

Lars Geyer-Blaumeiser

Office Hour meeting minutes​

Infrastructure​

  • Test Environments:
    • Currently a blocking issue is with SAP. They want to do a change in the DIF deployment and we are blocked by that. Target for the change is early next week. This involves both STABLE and INT environment.
    • It is important that we can start with the deployment for the e2e test of 24/12 on INT, there are school holidays in southern Germany between Oct., 28th and Nov., 1st, so deployment is constrained in time.
    • The INT environment has to be wiped to start from scratch with the deployment for 24/12.
    • Doubleslash will provide information on how to proceed next week.

Release Management​

  • EDC 0.8.0 to be used during e2e testing. There will be a RC5 early next week, that should be used as a start for e2e testing
  • Release check issues are due on Oct. 18th for release 24/12

FOSS​

  • Sources of pictures: Do we need to regulate the availability of sources for binary pictures, as there are pictures in the website repo without editable sources.
    • There is already a TRG that specifies the handling of pictures. It should be controlled better by committers.
  • Concerning intermediate releases, especially bugfix releases that need to be done in Tractus-X during a operating cycle. There is a task to make a proposal on how to handle the situation from Eclipse Tractus-X perspective.
  • Deprecation of Repos. The regulation in TRG 7.09 is currently reworked to be more precise.
  • Discussion on a TRG about testing.
    • Doubleslash prepares a TRG concerning automated testing
    • Some repositories use SonarCloud and code coverage measurements there
    • General openness towards a new trial on some specs concering testing

Community/Open Planning​

  • Files like presentations done during Open Planning are currently not provided in Open Source. The proposal is to store such files in the already existing large files repository attached to the webpage repo.
  • Open Meetings page has been enhanced, there are now relevant links like to the task board that is relevant and related release timelines
  • Regular New Joiner meeting was canceled. If a session is needed, it needs to be requested

Theresa Hilger

Office Hour meeting minutes​

Infrastructure​

  • eclipse-tractusx/eclipse-tractusx.github.io requires just One Committer Review now
    • Committers that approve: Please double-check the content, remember you have also responsibility when approving non TRG compliant content
    • Expectation for KITs: It should be less stressful to find a committer
  • Setup Catena-X STABLE Environment
    • Organizational issue that’s why the stable is not there right now but they are working on it
    • Questions: Will the STABLE environment stick to the released version or will it evolve with the development of the components?
  • Planned general infrastructure maintenance INT environment 2024-09-29
    • 24.12 e2e test phase on INT environment still planned to start 25.10. as communicated in adapted timeline

Release Management​

  • EDC 0.8.0 to be used during e2e testing.
    • The upcoming Eclipse Tractus-X 24.12 release will include EDC version 0.8.0.
    • If your component relies on the Eclipse DataspaceConnector (EDC), we highly encourage you to align your development and testing efforts with this version to ensure compatibility.
  • Reminder for Refinement Day 1: 16.10
    • Each group will focus on the first steps of skeleton-building for their features, based on the feature template, mapping them to the related roadmap items
      • For more information please read the news blog
  • Reminder for Refinement Day 2: 06.11
    • Build on the work from Refinement Day 1 and focus primarily on the identified dependencies
      • For more information, please read the news blog

Security​

  • [Trufflehog Update] Deprecation of GitGuardian and mandatory update to Trufflehog
    • Please update your repositories
    • There are still many issues opened and waiting to be resolved by their responsible committer
    • The Trufflehog Workflow is a active TRG since March 26,2024

FOSS​

  • TRG proposal for product deprecation including a process and criteria to close Issue #1037
  • Please review and provide some input

Feedback / Question / Request​

  • Add Testmanagement timeline into timeline of the overall release

Mathias Brunkow Moser

Office Hour meeting minutes​

Infrastructure​

  • @SebastianBezold -> Wednesday (31.07.2024) the Catena-NG will be deleted! No more access to the consortia environment will be allowed!
    • Friendly reminder from @matbmoser: copy the configuration from the consortia environment argo, so you dont loose it, for the association env;)
  • @hzierer -> Most of E2E Tests are already passed! Great job everyone!
  • @matbmoser -> Don't forget to document the Quality Gate tickets!
  • System team is leaving in wednesday! The participants that will not act as committers please or remove yourself from the list, or contact a project lead. Thank you for you wonderful hard work!

Security team​

FOSS​

Open planning / community​

Tom Meyer

Office Hour meeting minutes​

Infrastructure​

  • Discussion on catenax-ng
    • @matbmoser: please cross-check your own repository, if you reference it!
    • @lgblaumeiser: we noticed that the R24.03 MIW needs catenax-ng resources. It temporarily stays up. (see issue)
  • Consortia teams are gone. Thanks, it was a pleasure!

Security team​

  • @matbmoser: Please do check for your security issues on the tab. High and critical issues need to be fixed. We should check this on high level / project level regularly in this meeting
  • @tom-rm-meyer-ISST: For Truffle Hog, make sure that the workflow runs before merging. (see e.g.)

FOSS​

  • @AngelikaWittek is gone. Thanks for your work!

Open planning / community​

  • @stephanbcbauer:
    • Refinement Phase went well overall. Committers please join the planning meetings.
    • Some QGates are still open, please check.
    • Review together the release preparation

Mathias Brunkow Moser

Office Hour meeting minutes​

Infrastructure​

  • @SebastianBezold -> Wednesday (31.07.2024) the Catena-NG will be deleted! No more access to the consortia environment will be allowed!
    • Friendly reminder from @matbmoser: copy the configuration from the consortia environment argo, so you dont loose it, for the association env;)
  • @hzierer -> Most of E2E Tests are already passed! Great job everyone!
  • @matbmoser -> Don't forget to document the Quality Gate tickets!
  • System team is leaving in wednesday! The participants that will not act as committers please or remove yourself from the list, or contact a project lead. Thank you for you wonderful hard work!

Security team​

FOSS​

Open planning / community​

Office Hour meeting minutes​

Infrastructure​

  • Info from Test / Infrastructure Management CX Association by Harald:
    • SAP DIM follow up meeting with on 8.7.2024 together with Christian Lahmer (SAP) and Evelyn Gurschler and DoubleSlash Net-Business GmbH
    • Work-in-progress with SDE team and importing of test cases
    • Access is currently limited –> would be great to make it accessible and available within Tractus-X
  • Tomasz - Presented about how do you need to publish your API using .tractusx metafile and publish via GitHub pages - API Hub.

Security team​

  • Info from security team by Rohan:
    • Reminder about replacement of GitGuardian with TruffleHog, see according pull request to update TX release guideline: #950
    • Reminder about updates to Trivy workflow , see according pull request to update TX release guideline: #949
    • Reminder about about absence of security team members from August 2024
    • Security tools walkthrough in the Committers Meeting of July 5, 2024 (about 20 minutes) - Rohan will announce the walkthrough next week on the TX mailing list while sending out a reminder for the meeting

FOSS​

Open planning / community​

  • Info by community manager Stephan about the Tractus-X/Catena-X working model and the refinement phase for the 24.12 release
  • Registration is open for the Third Eclipse Tractus-X Community Days on December 05 and 06, 2024, ARENA2036 in Stuttgart!

Security Office Hour meeting minutes​

Announcements​

  • Gitguardian tool for secret scanning will be replaced by TruffleHog. This will be used in parallel with Github's native secret scanning tool.
  • Trivy workflow has been updated to address the failure of workflows
  • Announcement of Security handover during the committer round

Office Hour meeting minutes​

Infrastructure​

  • Info from Test / Infrastructure Management CX Association by Harald:
    • status of product onboarding and deployment progression to new environment
    • clarifying dependencies, resolving blockers is ongoing
    • handover of test cases to new CX Association Xray
    • Invitation to E2E Test Management Daily beginning Monday (July 1, 2024): frequency determined determined to half an hour every 2nd day
  • Status about current works on API publishing by Tomasz currently in progress: a separate repository to store API docs and publish via GitHub pages - API Hub - was created. He will present the topic a bit more hands on in one of the upcoming office hours

Security team​

  • Info from security team by Rohan:
    • Replacement of GitGuardian with TruffleHog, see according pull request to update TX release guideline: #950
    • Updates to Trivy workflow , see according pull request to update TX release guideline: #949
    • Security tools walkthrough in the Committers Meeting of July 5, 2024 (about 20 minutes) - Rohan will announce the walkthrough next week on the TX mailing list while sending out a reminder for the meeting

FOSS​

  • Committer Election for Lucas concluded successfully, congratulations and welcome!
  • Don't forget to update the legal docs!! Close the tickets in your repositories if its done: eclipse-tractusx/sig-infra#477

Open planning / community​

Discussions​

  • Evelyn suggested a consistent storing for environment specific deployment configuration (helm values files) in TX repositories:
    • IF products teams store deployment configuration in TX, it should be stored in a separate directory at root level (/environments) and the notice file should explain it is need for the end-to-end testing of TX releases
    • no deployment configuration other than the one used for the official E2E Testing of TX releases should be kept in TX
    • suggestion is not intended to promote the storing of this configuration in TX but if you do it, do it as proper as possible
    • a benefit from (properly) storing the configuration in TX is the versioning with the TX GitHub releases, allowing to easily trace back the exact configuration used for testing
    • other options for handling environment specific deployment configuration outside of TX were discussed as well as the option of multiple sources for Argo CD was mentioned by Carsten
  • Stephan was wondering about how to handle outdated information on the TX Product Page:
    • product teams should check if the information on the page is still up to date, Stephan will write send a reminder on the TX mailing list
    • Arno mentioned that he would update the products which are still outdated in a couple of weeks, thanks for volunteering!