Project Lead Circle [2025-01-24] · eclipse-score · Discussion #214

Agenda for last meeting

Approval last meeting minutes (BMW (@antonkri ) pushes forward to accept meeting minutes, Qorix (@HartmannNico) seconds the motion)

Vorstellung Capgemini in the next PL-Sync

Invite Capgemini to the next PL-Sync, 31.01.2025
@antonkri to forward the meeting invitation and agree with Capgemini the content of their presentation and reserve the slot in the PL-Sync

Onboarding of new contributors in CFTs, Communities and upcoming workshops

Invite Lutz to sw architecture community (@qor-lb) and later to corresponding CFTs
Add Lutz to contributor group in S-CORE (@antonkri)

Feature request process

Improve Feature Request process and define whether Feature Request should be documented in GitHub Issue or GitHub PR (Improve documentation of Feature Request process #261)

We need to present our 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)
@antonkri will create a ticket (Create slides to present S-CORE development process in Process SIG #165)
@markert-r will take over the lead
Due date for the first version to be presented in the PL-Sync is 31.01.2025
Proposal for presenters: Alexander Schemmel, Markus Schu, Philipp Ahmann. @markert-r will confirm with them.
@antonkri agenda point for next week due to absence of responsible persons

S-CORE Logo & Name

Confirmed by PLs, that the name should be changed from SCORE to S-CORE
Technical Circle should document where it should be changed and where not (@antonkri to create a ticket: Change project name from SCORE to S-CORE #166)
@FScholPer will start a request by Eclipse SDV to check the name (S-CORE) trademark topic (Check the copyright for the logo & name #106)
To propose a new S-CORE logo based on SCORE logo (see, here bottom left) -> @qor-lb
We plan to write the project name as "S-CORE", for the logo we take the image with the dot in the middle (logo trademark should be checked by Eclipse SDV as well)

Initial set-up of the S-CORE project

Feature Requests overview

Kick-off 15.01.2025 for all architectural communities

Kick-off has taken place, following Feature Requests were presented: IPC, Logging, FEO, Persistency
Next step is to work on the definition of requirements and architecture in the Cross Functional Teams. Meetings for Cross Functional Teams will be set-up by the Feature Requests owners.
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: 27.01.2025
@qor-lb will discuss in sw architecture community how the contributions to incubation repository should be done, e.g. on separate branch.
@qor-lb will discuss in sw architecture community when is the deadline till when we need to decide which solution we take.

Escalation path for technical decisions

Proposal: technical lead circle should make proposal till 31.01.2025, @antonkri will create a ticket.
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

See init version of Communication Channels document in File Exchange
Townhall
- Due Date for the first Townhall meeting "s-core for all": end of Februar.
- First proposal of agenda: end of January, @b-rei
One Pager for Contribution #141 (Due date for initial version: 31.01.2025)
Incorporation of the Communication Plan & Strategy in Platform Management Plan
Sara asked for Update on S-CORE. Should we do in TAC or should we wait for "s-core for all" meeting?
- @b-rei will talk to Sara regarding what is exactly needed
Define how to structure file uploads.
We found a communication community, Discussions and GitHub project should be created, tasks should be planned in the GitHub project and Project Management Plan should be extended with information about new community. Invite someone from Eclipse SDV to the community on regular basis for consulting regarding legal aspects.

Provide feedback