Eclipse S-CORE
Meeting Minutes - Tech Lead Sync #516
Replies: 134 comments 41 replies
-
2025-02-26Participants@johannes-esr Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-02-28Participants@johannes-esr Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-03-06Participants@pahmann Agenda
Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-03-07Participants@johannes-esr Agenda
Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-03-14ParticipantsAgenda
Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-03-19Participants@johannes-esr Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-03-21Participants@johannes-esr Agenda
Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-03-24Participants
Agenda
Meeting Minutesto 1.
to 2.
misc: |
Beta Was this translation helpful? Give feedback.
-
2025-03-26Participants
Agenda
Meeting Minutesto 1.
to 2.
misc:
|
Beta Was this translation helpful? Give feedback.
-
2025-03-28ParticipantsMeeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-03-31ParticipantsAgenda
Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-04-02Participants@johannes-esr Agenda
Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-04-07Participants@markert-r Agenda
Meeting minutesReview last weeks cross functional community meeting
Review roadmap for next meeting
Craft agenda for next meeting
Briefly discuss day & topic distribution for arch workshop from Tuesday to Thursday
|
Beta Was this translation helpful? Give feedback.
-
2025-04-11ParticipantsAgenda
Meeting minutes |
Beta Was this translation helpful? Give feedback.
-
2025-04-11Participants@johannes-esr Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2025-04-14Participants@johannes-esr Agenda
Meeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
|
Meeting Template: 2026-05-11ParticipantsAgenda
Helpfull Links: |
Beta Was this translation helpful? Give feedback.
-
2026-05-07Participants
Agenda
|
Beta Was this translation helpful? Give feedback.
-
2026-05-18Participants
Agenda
|
Beta Was this translation helpful? Give feedback.
-
2026-05-21Participants
Agenda
|
Beta Was this translation helpful? Give feedback.
-
2026-06-01Participants
|
Beta Was this translation helpful? Give feedback.
-
2026-06-08Participants
Agenda
for next time |
Beta Was this translation helpful? Give feedback.
-
2026-06-11ParticipantsAgenda
|
Beta Was this translation helpful? Give feedback.
-
2026-06-15Paticipants
Agenda
|
Beta Was this translation helpful? Give feedback.
-
Hackathon Friedrichshafenhttps://eclipsesdv.org/events/eclipse-sdv-hackathon-chapter-4/ Possible Topics from S-CORE perspective
Coaching Participants
Put it on the agenda for next week June, 22nd @anmittag |
Beta Was this translation helpful? Give feedback.
-
Status Techical DebtHow to check
|
Beta Was this translation helpful? Give feedback.
-
Infrastructurecurrently the Team is suffering to have enough capacity and still so many topics are open.
|
Beta Was this translation helpful? Give feedback.
-
|
S-CORE depends on shared infrastructure, but most maintainers only have very limited capacity available. As a result, reviews, maintenance, and improvements are increasingly delayed. The success of the current setup should not be mistaken for evidence that the operating model is working. It has succeeded largely because individuals have compensated for structural shortcomings. In my view, we are trying to operate a centralized infrastructure platform with resources that are only sufficient for a Community of Practice. |
Beta Was this translation helpful? Give feedback.
-
2026-06-18Paticipants
Agenda
|
Beta Was this translation helpful? Give feedback.
-
GeneralAny Feature which is not progressing towards Q-Gates, we exclude them from our reference integration. Synchronizing for FEO
*consolidated opinion, representing all contributers of the organization Synchronizing for KYRON
*consolidated opinion, representing all contributers of the organization Synchronizing for ORCHESTRATOR
*consolidated opinion, representing all contributers of the organization |
Beta Was this translation helpful? Give feedback.
-
Light Weight ContainerLightweight Container Execution for Automotive ECUs (Eclipse SSAM) Quick Feedback, no straigth integration into S-CORE:
|
Beta Was this translation helpful? Give feedback.
-
VSO Feature Proposal |
Beta Was this translation helpful? Give feedback.
-
2026-06-22Paticipants
AgendaMeeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2026-06-23 BreakoutPaticipantsAgendaMeeting Minutes
|
Beta Was this translation helpful? Give feedback.
-
2026-06-25Paticipants
Agenda
=> next alignement meeting: review status of 0.8 @anmittag agenda
Meeting Minutes |
Beta Was this translation helpful? Give feedback.
-
|
AI Analsysis: Eclipse S-CORE: Tool Requirements & Process Requirements Mapping to Roadmap Versions1. Roadmap Overview (S-CORE v1.0)The S-CORE v1.0 roadmap defines 4 release gates, each focusing on specific ASPICE process areas:
The stack also has a 2. Tool Requirements (docs-as-code)Source: https://eclipse-score.github.io/docs-as-code/main/internals/requirements/requirements.html The docs-as-code tool (based on Sphinx + sphinx-needs) implements tool requirements ( 2.1 Tool Requirements by Category with Implementation StatusCommon Attributes (all element types)
Documents
Requirements Engineering (PA2)
Architecture Design (PA3)
Implementation / Detailed Design (PA4)
Verification / Testing (PA5)
Tool Verification Reports (Tool Management)
Safety Analysis (DFA + FMEA)
Security Analysis
Process / Other
3. Process Requirements (process_description repo)Source: https://github.com/eclipse-score/process_description The process requirements are organized by process area, each with 3.1 Requirements Engineering (
|
| Category | Tool Requirement | Current Status | Gap? |
|---|---|---|---|
| Common | tool_req__docs_common_attr_id |
YES | -- |
| Common | tool_req__docs_common_attr_id_scheme |
YES | -- |
| Common | tool_req__docs_common_attr_title |
YES | -- |
| Common | tool_req__docs_common_attr_description |
YES | -- |
| Common | tool_req__docs_common_attr_desc_wording |
YES | -- |
| Common | tool_req__docs_common_attr_security |
YES | -- |
| Common | tool_req__docs_common_attr_safety |
YES | -- |
| Common | tool_req__docs_common_attr_status |
YES | -- |
| Common | tool_req__docs_common_attr_version |
PARTIAL | GAP |
| Common | tool_req__docs_common_attr_suspicious |
NO | GAP |
| Common | tool_req__docs_common_attr_safety_link_check |
YES | -- |
| PA2 Reqs | tool_req__docs_req_types |
YES | -- |
| PA2 Reqs | tool_req__docs_req_attr_rationale |
YES | -- |
| PA2 Reqs | tool_req__docs_req_attr_reqtype |
YES | -- |
| PA2 Reqs | tool_req__docs_req_attr_reqcov |
PARTIAL | GAP |
| PA2 Reqs | tool_req__docs_req_attr_validity_correctness |
PARTIAL | GAP |
| PA2 Reqs | tool_req__docs_req_attr_validity_consistency |
PARTIAL | GAP |
| PA2 Reqs | tool_req__docs_req_link_satisfies_allowed |
PARTIAL | GAP |
| PA2 Reqs | tool_req__docs_req_link_covers_aou |
YES | -- |
| PA2 Reqs | tool_req__docs_linkage |
YES | -- |
| PA3 Arch | tool_req__docs_arch_types |
YES (status: invalid) | GAP (process mismatch) |
| PA3 Arch | tool_req__docs_arch_attr_mandatory |
YES | -- |
| PA3 Arch | tool_req__docs_arch_link_fulfils |
YES | -- |
| PA3 Arch | tool_req__docs_arch_link_fulfils_aou |
YES | -- |
| PA3 Arch | tool_req__docs_arch_link_aou_check |
YES | -- |
| PA3 Arch | tool_req__docs_arch_link_safety_to_req |
YES | -- |
| PA3 Arch | tool_req__docs_arch_link_qm_to_safety_req |
YES | -- |
| PA3 Arch | tool_req__docs_req_arch_link_safety_to_arch |
YES | -- |
| PA3 Arch | tool_req__docs_arch_link_security |
YES | -- |
| PA3 Arch | tool_req__docs_arch_views |
NO | GAP |
| Safety | tool_req__docs_saf_types |
YES | -- |
| Safety | tool_req__docs_saf_attrs_mandatory |
YES | -- |
| Safety | tool_req__docs_saf_attrs_mitigated_by |
NO | GAP |
| Safety | tool_req__docs_saf_attrs_violates |
NO | GAP |
| Safety | tool_req__docs_saf_attrs_content |
NO | GAP |
| Safety | tool_req__docs_saf_attrs_sufficient_check |
NO | GAP |
| Safety | tool_req__docs_saf_attr_fmea_fault_id |
NO | GAP |
| Safety | tool_req__docs_saf_attr_dfa_failure_id |
NO | GAP |
| Safety | tool_req__docs_saf_attr_fmea_failure_effect |
NO | GAP |
| Security | tool_req__docs_sec_types |
YES | -- |
| Security | tool_req__docs_sec_attrs_mandatory |
YES | -- |
| Tool Mgmt | tool_req__docs_tvr_* |
YES | -- |
| Documents | tool_req__docs_doc_types |
YES | -- |
| Documents | tool_req__docs_doc_generic_mandatory |
PARTIAL | GAP |
| Documents | tool_req__docs_doc_attr |
NO | GAP |
Key v0.8 Deliverables from Roadmap:
- All feature/component requirements
status: validfor v1.0-scope items - All feature/component architecture
status: valid chklst_req_inspection.rstandchklst_arc_inspection.rstapprovedvalid_fromattribute set on all v1.0-relevant feature requirements- Missing automation checks implemented in docs-as-code toolchain
- Standardized CI/CD workflow for doc generation and process validation
- Module Verification Reports created (>=90% C0/C1 coverage, 0 sanitizer findings)
Process Requirements (process_description) relevant for v0.8:
- All
gd_req__req_*(requirements engineering) requirements - All
gd_req__arch_*(architecture design) requirements gd_req__saf_*(safety analysis, needed for safety analysis of architecture)gd_req__sec_*(security analysis, as architecture must account for security)
Release Gate v0.9 (Implementation)
Process Area in Focus: PA4
Additional Tool Requirements becoming critical:
| Category | Tool Requirement | Current Status | Gap? |
|---|---|---|---|
| PA4 Impl | tool_req__docs_dd_link_source_code_link |
YES | -- |
| PA4 Impl | tool_req__docs_dd_feature_flag |
NO | GAP |
| Testing | tool_req__docs_test_link_testcase |
YES | -- |
| Testing | tool_req__docs_test_linkage_metrics |
YES | -- |
Key v0.9 Deliverables:
-
=75% component requirement test coverage
-
=75% feature requirement test coverage (Platform Verification Report)
- Detailed design documented (no TBDs, status
valid) chklst_impl_inspection.rstapproved- Remaining ~20% requirements tracked with tickets
Process Requirements newly in focus:
- All
gd_req__impl_*(implementation/detailed design) gd_req__verification_link_tests*(test-requirement linking)gd_req__verification_checks(test metadata validation)gd_req__impl_dependency_analysis,gd_req__impl_complexity_analysis
Release Gate v0.10 (Verification)
Process Area in Focus: PA5
Additional Tool Requirements becoming critical:
| Category | Tool Requirement | Current Status | Gap? |
|---|---|---|---|
| Testing | tool_req__docs_test_metadata_mandatory_1 |
NO | CRITICAL GAP |
| Testing | tool_req__docs_test_metadata_mandatory_2 |
NO | GAP |
| Testing | tool_req__docs_test_metadata_link_levels |
NO | CRITICAL GAP |
Key v0.10 Deliverables:
- 100% feature complete for all v1.0 modules
- All inspection checklists
validand complete - 100% component requirement test coverage
- 100% feature requirement test coverage
- Static code analysis tracking set up
Process Requirements newly in focus:
gd_req__verification_reporting- automated verification report generationgd_req__verification_report_archiving- report archivinggd_req__verification_sca_classification- static code analysis classificationgd_req__verification_ci_reference_execution- CI reference integrationgd_req__verification_external_aou- external component AoU verificationgd_req__verification_independence- review independence
Release Gate v1.0 (Hardening & Release)
All Process Areas finalized
Key v1.0 Deliverables:
- All inspection checklists valid/complete
- All Module Verification Reports approved (100% requirement/architecture coverage, structural coverage, 0 Critical/High SCA findings, 0 sanitizer findings)
- Platform Verification Report approved (100% feature requirement coverage, feature architecture coverage, all FIT results documented)
- Release notes finalized
ALL tool and process requirements must be satisfied.
5. Summary of Critical Gaps
Revised Ticket Summary
Original ticket count: 35
Revised ticket count: ~25
| Version | Original | Revised | Removed |
|---|---|---|---|
| v0.8 | 21 | 11 | 10 (4 now implemented, 6 invalid) |
| v0.9 | 3 | 3 | 0 |
| v0.10 | 7 | 4 | 3 (2 invalid, 1 was already YES) |
| v1.0 | 4 | 4 | 0 |
| Total | 35 | ~22 | ~13 |
Reduction: ~37% (close to the predicted 30%)
Revised v0.8 tickets (11 items)
tool_req__docs_common_attr_version— Make version attribute mandatory (currently optional)tool_req__docs_req_attr_reqcov— Implement automated requirement coverage calculationtool_req__docs_saf_attrs_mitigated_by— Make mitigated_by mandatory for valid safety analysis needstool_req__docs_saf_attrs_sufficient_check— Add check: sufficient=yes requires mitigated_bytool_req__docs_arch_link_aou_check— Add check: arch elements don't link to their own AoUtool_req__docs_req_arch_link_safety_to_arch— Complete safety→arch linkage check (resolve TODO)- Update requirements.rst: mark saf_attrs_content as YES
- Update requirements.rst: mark saf_attrs_violates as YES
- Update requirements.rst: mark saf_attr_fmea_fault_id as YES
- Update requirements.rst: mark saf_attr_dfa_failure_id as YES
- Update requirements.rst: mark validity_consistency as YES
Revised v0.9 tickets (3 items)
tool_req__docs_dd_feature_flag— Implement feature flags for non-release builds- Process: ensure tooling generates dependency tree views
- Process: ensure automated complexity analysis
Revised v0.10 tickets (4 items)
tool_req__docs_test_metadata_mandatory_1— Make TestType & DerivationTechnique mandatory- Process: automated verification report generation
- Process: report archiving for releases
- Process: SCA finding classification + CI reference execution
Revised v1.0 tickets (4 items)
19-22. Same as before (hardening, verification reports, release notes)
Key Takeaway
The "outdated" claim is confirmed. The safety analysis tooling (content enforcement, violates linkage, fault_id/failure_id enforcement) was implemented in the metamodel but the requirements.rst :implemented: field was never updated from NO to YES. Additionally, several requirements carry status: invalid meaning they are intentionally not applicable right now. Together, this accounts for a ~37% reduction in actual open items, aligning with the ~30% prediction.
Recommended immediate action
A single PR to update requirements.rst should mark these 7 items as implemented: YES:
tool_req__docs_saf_attrs_contenttool_req__docs_saf_attrs_violatestool_req__docs_saf_attr_fmea_fault_idtool_req__docs_saf_attr_dfa_failure_idtool_req__docs_saf_attr_fmea_failure_effect(code enforces it; req status still invalid though)tool_req__docs_req_attr_validity_consistencytool_req__docs_req_attr_validity_correctness
Beta Was this translation helpful? Give feedback.
-
2026-06-29Participants
Agenda
|
Beta Was this translation helpful? Give feedback.
-
2026-07-02ParticipantsParticipants
Agenda
Agenda |
Beta Was this translation helpful? Give feedback.
-
2026-07-06Participants
Agenda
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Meeting Template:
YYYY-MM-DD
Participants
Monday Agenda
Status
Thursday Agenda
TLC Board Review
Minutes
Beta Was this translation helpful? Give feedback.
All reactions