Technical Lead Circle [2025-02-18]

[johannes-esr]

Participants

@qor-lb
@FScholPer
@markert-r
@antonkri
@johannes-esr

Agenda

1. Discussion regarding website (https://github.com/orgs/eclipse-score/discussions/387)
2. GitHub Teams
3. Working Model with Communities & CFTs
4. Roadmap Planning

Meeting Minutes

1. Proposal accepted
2. • adding people to GitHub teams is no longer working (needed for codeowner) -> @antonkri to raise ticket at Eclipse
   • adding of contributors in Eclipse not functional & sync to GitHub -> @FScholPer to contact Eclipse regarding process
   • two approvals should be needed for merging -> @FScholPer to raise ticket to Operational Community
3. • Proposal:
     • Monday, 9 - 11 am, Technical Lead Circle + CFT Leads + Community Leads -> @FScholPer to update current meeting; @johannes-esr to create meeting structure
     • Technical Lead Circle tbd

Milestones	Date	Description
Modules Buildable	15.04.2025	All MVP defined features (FEO, IPC, Logging, Common Libraries, Persistency) can be built in software module repositiories. Until then, the modules are handled within the incubation repositories. Acceptance Criteria: - All modules use a common repository template (build, CI, gitlint, README, ...); to be checked by operational whether Git submodule/bazel module can be used to avoid code duplication. - All modules are built with bazel, (C++17: clang for x86 Linux with -Wall, -Wextra, -pedantic; Rust: tbd). - Unit tests are built and run, also via GitHub Actions. - No strict adherence to coding guidelines, but coding guidelines are available. - How to guide for reference build & test environment. - Result: every software module can be built inside of its repository. No common integration so far, no running image.
Process & Tools enable Development	31.03.2025	Left side of V-Model done. Acceptance Criteria: - Process & Tooling for requirements & architecture is available (sphinx-needs incl. additional checks for verifying traceability/consistency). - Process & Tooling for Detailed design, implementation & unit verification defined and implemented (e.g. spinx-test-reports). - CI/CD is capable to automatically verify the consistency & traceability. - Tooling for test coverage & static code analysis.
GAP Analysis finished	01.06.2025	- For all existing solutions for Release v0.5 analysis of missing features (GAP analysis) is finished, POCs has confirmed possible implementation solutions and everything is documented in Feature Requests. - Feature Requests are confirmed in the TL round and Software Architecture community, tickets are created and prioritized for implementation accrodingly
QNX Support	01.06.2025	The project supports the QNX toolchain. Acceptance Criteria: - The modules can be built with qcc.
Reference Integration Linux	15.04.2025	- A reference integration repository is available which depends on all feature/module repositories and the score main repository. - reference Linux image (Docker) is available - There are integration tests available which run on Linux image. - Usecases for the integration tests are defined.
Reference Integration QNX	01.06.2024	- reference QNX image (Qemu) is available - There are integration tests available which run on QNX images.
Process & Tools enable Testing	31.05.2025	Testing strategy is defined and corresponding tooling is implemented. Acceptance Criteria: - Process and Tooling for Testing (e.g. component or integration tests) are available.
Features follow S-CORE Process	01.06.2025	The features of the 0.5 MVP are according to the S-CORE processes and all artefacts are created initially. Acceptance Criteria: - All already existing artifacts (requirements, tests, architecture) are transferred to S-CORE formats and are generated/executed in CI pipeline for the Release v0.5 components
Release v0.5 feature complete	01.10.2025	- All Feature requests that are relevant for Release v0.5, including the ones resulting from the GAP analysis, are implemented according to the S-CORE software development process (requirements, architecture, dd, implementation and unit verification, integration tests)
Release v0.5 Certified	01.12.2025	The features of the 0.5 MVP are in a state to be safety certifiable. Acceptance Criteria: - Release v0.5 components have all necessary working products (also release and config mgmt documents) according to the S-CORE software development process - All corresponding tools are certified
Blueprint definition for Release v0.5	01.06.2025	- Define demo use-cases (aka. Eclipse SDV Blueprints) in which we plan to use our Release v0.5 modules (e.g. a real vehicle) to prove its usability (performance, scaling, ...). -
Reference Hardware for Release v0.5	01.10.2025	- Reference hardware and reference OS are defined. - Reference hardware farm is connected to S-CORE CI. - Integration tests on hardware are running periodically (e.g. nightly). - Define hardware relevant integration tests, e.g. performance, and corresponding KPIs
S-CORE v1.0 specification	01.08.2025	- scope for Release v1.0 is defined in Software Architecture community and agreed with TL/PL-circle. - Feature requests for missing Release v1.0 modules are created and agreed. - POCs are done to show possible implementation approach

gantt
   dateFormat YYYY-MM-DD
   title S-CORE Roadmap
   excludes weekends
   tickInterval 1month


  section Project Milestones
      Software Architecture Workshop: milestone, m0, 2025-02-11, 0D
      Blueprint definition for Release v0.5: milestone, m1, 2025-06-01, 0D
      Release v0.5 feature complete: milestone, m2, 2025-10-01, 0D
      Release v0.5 Certified: milestone, m3, 2025-12-01, 0D
   
  section Initial take-over
      Modules Buildable: milestone, m4, 2025-04-15, 0D
      Features follow S-CORE Process: milestone, m5, 2025-06-01, 0D
      GAP Analysis finished: milestone, m6, 2025-06-01, 0D

   section Process & Tools
      Process & Tools enable Development: milestone, m7, 2025-03-31, 0D
      Process & Tools enable Testing: milestone, m8, 2025-05-31, 0D

   section Reference Environment
      Reference Integration Linux: milestone, m9, 2025-04-15, 0D     
      Reference Integration QNX: milestone, m10, 2025-06-01, 0D      
      QNX Support : milestone, m11, 2025-06-01, 0D
      Reference Hardware for Release v0.5: milestone, m12, 2025-10-01, 0D

   section S-CORE v1.0
      S-CORE v1.0 specification: milestone, m13, 2025-08-01, 0D
 

Loading

timeline

• Q1 Concepts agreed & implemented
• Q2 Feature complete
• Q4 Certifiable

Features

Q1 Concepts agreed & implemented:
x Code builds in inc repo

• Plan for reaching feautre complete exists
• Implementation concepts are agreed
• No restriction on coding rules or style guide

Q2 Feature complete:
x Requirements, architecture, dd, implementation & unit verification available in s-core repo

• Plan for reaching safety certifiability exists
• Integration repo concept implemented

Q4 Certifiable:

• safety manual & verification artifacts available
• user documentation available
• consistent release notes for Q4 release

Process

Q1 Concepts agreed & implemented:

• process for requirements, architecture, dd, implementation & unit verification defined
• process for configuration management defined

Q2 Feature complete:

• process for verification & validation defined
• process for management & supporting parts defined

Q4 Certifiable:

• Certifiability demonstrated (via audits or assessments)

Operational

Q1 Concepts agreed & implemented:
x Tooling for requirements, architecture, dd, implementation & unit verification available

• Configuration management defined
• CICD is capable to automatically verify the consistency

Q2 Feature complete:

• Release pipelines defined
• Tooling for verification & validation available

Q4 Certifiable:

Testing

Q2 Feature complete:

• Testing strategy defined
• Test framework implemented & automated through pipeline
• Test framework demonstrated with one feature

Q4 Certifiable:

• Verification & validation completed