Project Lead Circle [2025-02-07] · eclipse-score · Discussion #288

Meeting minutes for last meeting

Approval last meeting minutes (BMW (@antonkri ) pushes forward to accept meeting minutes, @b-rei seconds the motion)

S-CORE Safety Audit

Review of Safety Audit report and decision whether to put it to the S-CORE web page.
@antonkri clarify whether we can put it online and share with PLs and TLs of S-CORE project.

Presentation of SW Dev Process in Eclipse Process SIG mid of February next year

@grandyholger will take care of organizing the meeting/slot in Process SIG (proposal 17.02.2025)
@markert-r will take over the lead
@markert-r to share working document with Projects & Technical Leads.
@markert-r to make sure that it's clear that Eclipse S-CORE takes over no responsibility/liability for the platform.
Due date for the final version to be presented in the PL-Sync is 14.02.2025
Proposal for presenters: Alexander Schemmel, Philipp Ahmann.

Architectural communities & Architecture Workshop

Contributions from multiple companies as open source (branches of incubation repos) will be reviewed on 11.02.2025-13.02.2025. Goal is to look into the solutions and to choose the best possible solution as basis for the S-CORE project.
Location for the follow-up workshop (11.02.2025-13.02.2025) should be chosen. ESRLabs will provide rooms and will send invitation to the participants. Details to be discussed in Technical Lead Circle. Due Date: 03.02.2025
@qor-lb will discuss in sw architecture community how the contributions to incubation repository should be done, e.g. on separate branch. Conclusion: Hosting in own organization or in brach of incubation repository.
@qor-lb will discuss in sw architecture community when is the deadline till when we need to decide which solution we take. -> https://github.com/orgs/eclipse-score/discussions/234

Escalation path for technical decisions

Proposal: technical lead circle should make proposal till 14.02.2025 (Escalation path for technical decisions #262)
The overall goal: in S-CORE we should have for every problem only one solution. Distributors could still replace some S-CORE modules with their own ones.
We should enforce, that all our solutions look the same and fit each other ("wie aus einem Guss").

Project Communication

Provide feedback