Architecture Community [2025-02-17]

[qor-lb]

Participants

• Markus Bechter @ramceb
• Arvid Sievert @arsibo
• Anton Kiroborodov @antonkri
• Johannes Glamsch @johannes-esr
• Frank Scholter Peres @FScholPer
• Lars Bauhofer @qor-lb
• Nico Hartmann @HartmannNico
• Ulrich Freund
• Lutz Niebergall @LuNieb

Agenda

1. Approval of Architecture Community F2F Workshop [2025-02-11 - 2025-02-13] #375
2. Formal criteria for contribution selection
3. Repository structure for contributions
4. Next steps

   • Vote in CFTs for leads.
   • Current FR owner invite for the next session and subsequently invites by new owners.
   • CFTs perform a gap analysis and create a plan to achieve version 0.5 by the end of February.

Formal definitions of criteria for contribution selection

1. Functional adherence to feature request.
2. Availability of source code.
3. Implementation language: Support for C++17 and Rust.
4. Maturity (technical debt of code base):
   1. Is the implementation already safety certifiable?
   2. Non-Functional adherence to feature request (e.g. resource consumption)
5. Adherence of available artifacts to score process expectations.
   1. Are all artifacts for a certification available in public?
   2. Are all artifacts created with and according to the S-CORE process?

Repository structure for ipc, logging, baselibs

Assumption is that we will have one bazel module for ipc, logging and baselibs
Option 1: Own eclipse project per module
Option 2: Own repository within score project (e.g.https://github.com/eclipse-score/ipc)
Option 3: Develop within incubation repo until maturity is reached e.g. in https://github.com/eclipse-score/inc_mw_com/
Option 4: Develop in .score repository https://github.com/eclipse-score/score/ipc

Meeting Minutes

to 1.

• Include formal selection criteria from 2. to reflect the decisions made
• AI & D accepted in the meeting minutes
• @cft owners to transfer action items into issues
• consolidated review on 24th

to 2.

• @qor-lb to approach process team for checklist regarding contribution selection (till 19th)
• @ramceb / @qor-lb proposal of all contributions for by cfts until 24th

to 3.

• Option 2 preferred, check with the process community if we can directly use "standard" repos
• @ramceb / @qor-lb proposal for repositories & repository structure for s-core 0.5

to 4.

• agreed and accepted