Architecture Community [2025-01-09]

[qor-lb]

Participants

• Fabian Frie
• Alexander Warg
• Lars Bauhofer @qor-lb
• Nico Hartmann @HartmannNico
• Arvid Sievert @arsibo
• Johannes Glamsch @johannes-esr
• Marthin Thiede @mthiede-acn2
• Gerd Schäfer
• Felix Obenhuber @flxo
• Markus Bechter @ramceb

Agenda

1. 14th Jan: Kick-off Architecture Community + Teams (online): welcome, recap architecture workshop [120 min]

   1. Organizational [30 min]
      • Roadmap & Timeline
      • Target 11th - 13th Feb: F2F Munich: Review of existing contributions
      • Team Setup & Work Mode
      • Explanation Incubation Repos
   2. Recap Architecture Workshop/Initial Contribution Requests [80 min]
      • 20 min per Feature Request
   3. Q&A [10 min]

2. Work Mode Cross Functional Teams

   • CFT meetings starting CW 4 (20th Jan)
   • Review & Detailing Feature Requests
   • Preparation Code Contributions for F2F in Feb

3. Current Status v0.5 Feature Request Preparation Feature Requests / Modification

4. Recap Planned Contributions Architecture Community [2024-12-16] #93

   • FEO:
     • Flux: Gerd Schäfer
     • Nautilus: Holger Grandy
     • Runtime: Nico Hartmann
   • IPC
     • LoLa: Holger Grandy
     • (IceOryx 2 - inclusion of ekxide discussion with Nico Hartmann)
   • Logging
     • Guidelines: Gerd Schäfer
     • (MP/DLT Log: Sven Kappel)
   • Persistency
     • no existing contributions - green field approach

5. CFT Participant naming (along with other communities) in PL Circle on Jan 10th

   • Differentiation Orchestration & FEO?

Meeting Minutes

to 1.

• 15th Jan 14 - 16 CET
• Presenters as per Feature Request Assignments

to 2.

• workmode agreed
• @qor-lb to send blockers for all F2F meetings + kick-off

to 3.

• Preparation of feature description in Issue -> approval of features in PL Circle
• After approval, work results (requirements) within repository

to 5.

• If additional/separate Orchestration Feature required, first create Feature Request, afterwards discussion in Architecture Community