Project Lead Circle [2025-05-23] #1095

antonkri · 2025-05-16T05:40:55Z

antonkri
May 16, 2025
Collaborator

Agenda

Approval of Meeting minutes for last meeting
Status of milestones

"Modules Buildable" and "QNX Toolchain" milestones are reached
To achieve further milestones, we need a detailed planning -> task for TL round
Focus today: Process & Tools
- We need to staff tooling team much better for achieving process&tools milestones -> we need urgent support from PLs
- Proposal: split critical topics and assign every topic to a PL, TL pair
- Proposal for topics split:
  - "Requirements & Architecture" Workstream → Stakeholder/Feature/Component requirements, Feature/Component architecture, Detailed Desing. Main focus: enablement of sphinx and sphinx-needs toolchain
  - "Compiler Toolchain & Code quality" Workstream → Coding Guidelines/Misra warnings and corresponding tools for both C++ & Rust.
  - "Testing" Workstream → Platform/Feature/Componet testing and tooling.

Jira integration into S-Core project
- GitHub Project is not really usable for big projects as S-CORE
- GitLab instance was provided, @antonkri and @johannes-esr will evaluate it
- Ideally, we would like to use open source instance of Jira. Eclipse EMO team rejects this idea -> we need assistance.
- @thilo-schmitt any update?
Follow-up: Security/Safety/Quality manager roles
- We need to define such roles
- Proposal:
  - every project lead can name for every role 0 ... 1 person, e.g. we can have 5 Security Managers.
  - One person can be assigned to multiple roles
  - if project lead doesn't name anyone, he automatically agrees with decisions, taken by other managers.
  - Definition of Quality, Security and Safety Management Roles #1050

Meeting minutes

to 1
- Approval last meeting minutes (BMW (@antonkri) pushes forward to accept meeting minutes, @b-rei, @HartmannNico second the motion)
to 2
- Agreed, that every PL will check it on his side and will communicate his feedback till Wednesday to his TL, so that this can discussed in TL circle on Wednesday
- The main idea is not to find "someone", we need real experts, who knows what they are doing
- In case there will be no progress till Wednesday, we will organize additional PL Sync on 02.06.2025
- Goal is to stuff Tooling team and have a clear detailed roadmap till holiday in June ("Pfingsferien")
- ETAS & Mercedes will focus on workstream 1 and 2 , BMW on workstream 2 and 3.
to 3
- There was a misunderstanding, that @thilo-schmitt will push Jira topic, @thilo-schmitt was pushing GitLab topic, that's why we got a GitLab instance
- @antonkri and @johannes-esr will check GitLab first, only if it is not suitable, we will think about how to process with Jira.
to 4
- Proposal from PLs who should act as security/safety/quality manager should come till 06.06.2025.
- Ideally, that should be already discussed in TL round before and in PL only final proposal should be approved

Misc:

Next week no PL Circle
Capgemini will have a meeting with @qor-lb to check, which technical topics they could take over.

AlexanderLanin · 2025-05-23T15:55:36Z

AlexanderLanin
May 23, 2025
Collaborator

🧩 Clarification Request: New Infrastructure Workstreams (S-CORE)

This is the infrastructure team's current understanding of the workstream split. Please confirm or suggest adjustments.

🚧 Requirements & Architecture Workstream

Pre-Defined Scope: Stakeholder, Feature & Component requirements, Architecture, Detailed Design. Enablement of the sphinx and sphinx-needs toolchain.
Additional Scope: All existing "infrastructure" topics remain here – including basic tooling, reference integration, traceability to code, test report integration, etc.
Team: Alex, Max, Aymen, Dan??, Nicolae??, Michael, Sameer
Note: for faster results we need more full-time senior contributors

🛠️ Compiler Toolchain & Code Quality Workstream

Pre-Defined Scope: Toolchains, Coding Guidelines, MISRA rules, Static Analysis tools for C++ & Rust
Additional Scope: Includes QNX-related topics
Team: Nikola??, Lukasz??, Mark??, Frank??, Dan??, Nicolae??

🧪 Testing Workstream

Scope: Platform, Feature & Component testing and related tooling
Team: Testing community

1 reply

AlexanderLanin May 26, 2025
Collaborator

Reviewed in TL circle

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Eclipse S-CORE

Project Lead Circle [2025-05-23] #1095

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Eclipse S-CORE

Project Lead Circle [2025-05-23] #1095

Uh oh!

Uh oh!

antonkri May 16, 2025 Collaborator

Agenda

Meeting minutes

Replies: 1 comment · 1 reply

Uh oh!

AlexanderLanin May 23, 2025 Collaborator

🧩 Clarification Request: New Infrastructure Workstreams (S-CORE)

🚧 Requirements & Architecture Workstream

🛠️ Compiler Toolchain & Code Quality Workstream

🧪 Testing Workstream

Uh oh!

AlexanderLanin May 26, 2025 Collaborator

antonkri
May 16, 2025
Collaborator

Replies: 1 comment 1 reply

AlexanderLanin
May 23, 2025
Collaborator

AlexanderLanin May 26, 2025
Collaborator