Meeting Minutes - Tech Lead Sync

[johannes-esr]

Meeting Template:

YYYY-MM-DD

Participants

• @anmittag
• @antonkri
• @FScholPer
• @johannes-esr
• @mlangerwisch
• @qor-lb

Monday Agenda

Status

• S-CORE Milestones
• S-CORE Bugs
• [Feature Requests-Open] (Feature Requests / Modification & FEPs (view))
• [Feature Requests V1.0] (Feature Requests / Modification & FEPs (view))
• Progress Review

Thursday Agenda

TLC Board Review

• Product Increments
• Epics
• Tasks
• Bugs

Minutes

[johannes-esr]

2025-09-14

Participants

@antonkri
@FScholPer
@opajonk
@marcolan
@PhilippM-qorix

Agenda

• Lessons Learned Release V0.9
• PR Decision Record for name collision in include paths & file names #3234 (https://eclipse-score.github.io/score/pr-3196/design_decisions/DR-003-arch.html) needs feedback
• Feedback AI Rules

Meeting Minutes

• Feedback AI Rules (Wait until @antonkri feedback arrived -> open PR)
• Lessons Learned Release Process
• Proposal: Higher interval of integration and module releases to fail fast
• Tracability Report job should contain every artifact of the release validation
• Patches should be not usual case -> Analyse reasons(public/private apis, breaking changes workflows)
• Release notes should be automated. Should be integrated in the new release workflows -> @FScholPer
• Tagging of epics which are relevant for the next release (autotag?!)
• Every module should provide a verification report inside reference integration like in https://eclipse-score.github.io/reference_integration/main/verification_report/modules/baselibs/baselibs_verification_report.html
• DR-08 DR-008 Option 4: two-stage test-execution workflow (PR 2 of 2) reference_integration#280 -> TL needs deep dive session -> invite @PiotrKorkus
• @FScholPer will open pr to demonstrate module_template needs of verification report, tracability report
• ML3 should be checked against SBOM.
• Alignment Meeting Agenda:
  • Code Coverage tooling implementation
  • Please link code to requirements and unit -test to requirements and component requirements to feature_features. And please check if you fulfill aous.
  • Fill out inspection checklist

[johannes-esr]

2025-02-28

Participants

@johannes-esr
@markert-r
@vinodreddy-g
@antonkri
@FScholPer

Meeting Minutes

• Additional weekly slot: Friday, 1:30 - 2:30pm -> @FScholPer to invite
• @markert-r to schedule meeting for March 20 for new interested companies
• New agenda points for PL Circle:
  • Date of Townhall
  • Combination of https://eclipse-score.github.io/ & https://eclipse-score.github.io/score/main/ to allow next step of Contribution One Pager

[johannes-esr]

2025-03-06

Participants

@pahmann
@antonkri
@FScholPer
@johannes-esr

Agenda

• Breakdown of first to Milestones in Epics

Meeting Minutes

• Milestone: Process & Tools Enable Development
  • Epic: (Initial) Processes Requirements #581
  • Epic: (Initial) Tooling Requirements & Architecture #582
  • Epic: (Initial) Processes Detailed Design, Implementation #583
  • Epic: (Initial) Tooling Detailed Design, Implementation, Unit Verification #584
• Milestone: S-CORE v0.5 Modules Buildable
  • Epic: (Initial) Set-up basic repository & build infrastructure #585
  • Epic: LoLa buildable & existing tests runnable #586
  • Epic: Logging buildable & existing tests runnable #587
  • Epic: Persistency buildable & existing tests runnable #588
  • Epic: FEO buildable & existing tests runnable #589
  • Epic: ITF buildable & existing tests runnable #590
  • Epic: (Initial) Coding Guidelines C++ #591
  • Coding Guidelines Rust #592
  • Epic: (Initial) Coding Guidelines Python #593
• Tasks for Communities / CFTs:
  • All existing issues which are matching to the Epics of the Milestone shall be attached
  • Add Milestone to all linked Issues

[antonkri]

2025-03-07

Participants

@johannes-esr
@antonkri
@vinodreddy-g
@FScholPer

Agenda

• Breakdown further Milestones

Meeting Minutes

• Milestone: Reference Integration Linux

  • Epic: Linux container x86_64 is up and running
    Acceptance criterias: Linux container (x86_64) is prepared, configured properly (ethernet/ssh access) and uploaded to some location, that is accessible from local builds and CI.
  • Epic: Linux container arm64 is up and running
    Acceptance criterias: Linux container (arm64) is prepared, configured properly (ethernet/ssh access) and uploaded to some location, that is accessible from local builds and CI.
  • Epic: ITF framework is up & running.
    Acceptance criterias: ITF framework is integrated into bazel. ITF test job is set-up in CI and is part of check/gate pipeline. ITF can establish ssh connection to the image. As first test in the CI pipeline, ITF should deploy application under test to the Linux container and ensure, that this one is running.
  • Epic: ITF framework dlt support
    Acceptance criterias: ITF framework can receive dlt streams from the applications and provides infrastructure to evaluate DLT logs in runtime and post-mortem.

• Milestone: QNX Support

  • Epic: Integration of QNX toolchain.
    Acceptance criterias: QNX 8 toolchain is integrated into bazel. Users need to get the license from QNX everywhere program and put it some specific location for being able to use QNX 8 toolchain.
  • Epic: Building with QNX in CI.
    Acceptance criterias: CI jobs for building of applications are set-up for all currently existing applications and documentation is provided how set-up QNX CI jobs for future applications. QNX CI license is stored as GitHub Secret and allows unlimited execution of QNX CI jobs in parallel
  • Epic: QNX Compiler config.
    Acceptance Criteria: compiler config is agreed with Process team and compiler/linker flags are chosen to support ASIL development right from the beginning.

• Milestone: Reference integration QNX

  • Epic: Qemu with QNX image and x86 BSP
    Acceptance Criteria: Qemu with QNX image, x86 BSP and S-CORE applications can be built with bazel locally and in CI. There exist a voting CI job, that builds QNX Qemu image and executes all existing ITF tests with it.
  • Epic: Qemu with QNX image and Qualcomm (ARM) BSP
    Acceptance Criteria: Qemu with QNX image, Qualcomm BSP and S-CORE applications can be built with bazel locally and on demand on CI.

[johannes-esr]

2025-03-14

Participants

• @johannes-esr
• @antonkri
• @qor-lb
• @vinodreddy-g
• @markert-r

Agenda

• How to do further planning?

Meeting Minutes

• Meeting this afternoon to update PMP with information decided on https://github.com/orgs/eclipse-score/discussions/434#discussioncomment-12299310 & https://github.com/orgs/eclipse-score/discussions/434#discussioncomment-12445705
  • Breakdown of Workpackages
  • Labels to use
  • ...

[johannes-esr]

2025-03-19

Participants

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

Meeting Minutes

• Next week alignment meeting regarding Processes & Tools between AUTOSAR & S-CORE in Lüneburg, https://www.autosar.org/news-events/detail?tx_news_pi1%5Baction%5D=detail&tx_news_pi1%5Bcontroller%5D=News&tx_news_pi1%5Bnews%5D=304&cHash=a20923b48d9e091adb600c148ab6948f
  • @AlexanderLanin will attend the meeting
  • @antonkri to check if @aschemmel-tech will attend, too
• Proposal: TL Meeting on 31th March 2025, 9:00 - 12:30
  • Planning/Review of Milestones ending in June 2025, too much in parallel
• Tasks for next meeting:
  • Review of Milestone planning; some Epics are not assigned to a CFT/Community
• Change of Monday Meeting Series:
  • 9 - 10am only TL
  • 10 - 11am TL & Communities & CFTs
  • @qor-lb changed invitation, to check if everybody received the updated invitation

[johannes-esr]

2025-03-21

Participants

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

Agenda

• Open points from last discussion

Meeting Minutes

• AUTOSAR / S-CORE Meeting: @aschemmel-tech can just attend online
• TL Workshop: March 28, starting 12 pm (instead of March 31)
• Should Safety Linux be a target platform of S-CORE? -> To be addressed in PL Circle @antonkri
• Point for next PL Circle: Analysis AUTOSAR -> @antonkri

[qor-lb]

2025-03-24

Participants

• Tom Fleischmann
• Rebecca Markert
• Anton Kiroborodov
• Frank Scholter Peres
• Lars Bauhofer

Agenda

1. Current Status S-CORE Logo
2. Agenda for WS on 28th
3. Feedback productivity Tech Lead Sync

Meeting Minutes

to 1.

• An agenda of SteerCo but not update yet

to 2.
Proposals to be prepared until friday:

• More concrete milestone/roadmap planning - @antonkri / @markert-r
  • do we have all the dependencies?
  • how to get a better overview?
• Definition of meeting structure - @markert-r
  • who prepares the meeting?
  • what agenda is discussed
  • How to pass tasks between teams #410,
• How to contribute/how are feature requests managed? - @TomFleischmann / @qor-lb
  • Feature requests are prepared to reflect technical roadmap
  • Case A: FR open but no contributions yet (Feature is on roadmap but not implemented)
  • Case B: Feature not yet on roadmap (functionality not yet targeted by by S-CORE)
• Management of components within S-CORE (who can review & merge) - @FScholPer

misc:

• https://oss-review-toolkit.org/ort/

[qor-lb]

2025-03-26

Participants

• Tom Fleischmann
• Rebecca Markert
• Anton Kiroborodov
• Lars Bauhofer

Agenda

1. Slides for townhall
2. Move invite from zoom to teams

Meeting Minutes

to 1.

1. Welcome and Introduction - 5 min
2. Project Vision - 10 min - @markert-r
   - Goal S-CORE: source code standardization
3. Current Status & Overview Cross Functional Teams - 40 min
   • Content Tech - 20 min - @qor-lb
     • 0.5 components & how they were selected - i.e. Architecture WS, Selection Criteria, Components
     • Hint to 1.0 definitions in following months
   • Content Process & Tools - 20 min - @markert-r
     • Current status process - 5 min
     • Results from ekxida - 15 min
4. Roadmap (milestones) - 10 min - @FScholPer
5. How to contribute - 5min - @qor-lb
   - (CFT's & work structure)
6. Q&A - 20 min

to 2.

• accepted

misc:

• Preliminary slides: 20250320_S-CORE_Townhall_Meeting.pptx
• Community days slides:

[johannes-esr]

2025-03-28

Participants

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

Meeting Minutes

• docs: improved how to contribute section #776
• Review of Roadmap Planning
• Tasks for Monday Meeting:
  • https://github.com/eclipse-score/score/milestone/7 -> Status to be checked with Infrastructure Community
  • Status (~2min) of each CFT/Community in Monday Meeting

[FScholPer]

2025-03-31

Participants

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

Agenda

• Feedback for planning milestones

Meeting Minutes

• We need the participants for the architecture workshop A1 @qor-lb

[johannes-esr]

2025-04-02

Participants

@johannes-esr
@antonkri
@FScholPer

Agenda

• Review of Monday Meeting

Meeting Minutes

• Detailed check of tasks of Operational Community on Friday, 1:30 - 2:30pm

[TomFleischmann]

2025-04-07

Participants

@markert-r
@antonkri
@TomFleischmann
@qor-lb
@FScholPer
@guysagnes

Agenda

• Review last weeks cross functional community meeting
• Review roadmap for next meeting
• Craft agenda for next meeting
• Briefly discuss day & topic distribution for arch workshop

Meeting minutes

Review last weeks cross functional community meeting

• Some discussions touched on topics in parallel / double was observed
  -> could be improved to talk alongside the roadmap / epics board roadmap / epics board and teams then deep dive into their more detailed boards
• Invites are not easy to graps / have in every bodies calendar better, potential to improve meeting management for OSS projects (@TomFleischmann to ask EF what other projects successfully do)
• Potentially better: One sends out the invite per meeting and create a meeting overview page (When, Who, What, Link, ..)
• Maybe not good to the whole world in the project lead meeting - makes it hard to get topics done and not helpfull for new parties who want to contribute and join in

Review roadmap for next meeting

• Minor: some items have a wrong end date
• Discussed usage of templates including checks (req linking, ..) for repositories
• Pro: makes it easier for all subprojects to follow the same process (and adhere and enable later safety certification)
• Have a central solution and example for coding, unittest, req links, linting, compiler flags, ... makes sense to avoid "works in my subproject/works on my machine"
• Anton: Consensus of central bazel, yet CI config may need to differ (or define at a later point in time) in order to have 1st steps in the projects made easier and learn first
• A lot of bazel and CI work in repos currently -> Action: Extra discussion with Arch community to unblock @AlexanderLanin and to describe target picture

Craft agenda for next meeting

• Review roadmap and have everybody to give a status update and important dependencies
• Raise topic about central repository template to help prioritize (try-out defined process); needs an extra meeting with tooling community & tech leads & some of the feature teams ; @markert-r to make invite for an hour

Briefly discuss day & topic distribution for arch workshop from Tuesday to Thursday

• As we better know a 1.0 scope the question around what could be used/based on autosar is time wise good to have on Thursday.

[FScholPer]

2025-04-11

Participants

Agenda

• Currently there are many Stakeholder requirements which are outdated and the granularity differs much for example between com & feo.

Meeting minutes

[johannes-esr]

2025-04-11

Participants

@johannes-esr
@TomFleischmann
@FScholPer
@markert-r

Meeting Minutes

• Review Milestone Planning
  • Check with Alexander L. whether this intermediate milestones can be deleted
  • What to do with "Blueprint Definition" Milestone? To be checked in next TL circle

[johannes-esr]

2025-04-14

Participants

@johannes-esr
@TomFleischmann
@antonkri
@markert-r

Agenda

1. Review of TL Sync Meeting Slots
2. Meetings during easter holiday
3. What to do with "Blueprint Definition" Milestone
4. Outcome of Architecture Workshop
5. Agenda TL, CFT, Community Sync
6. General

Meeting Minutes

1. • Monday, 9 - 10 am
   • Wednesday, 9 - 10 am
   • Friday, 8:35 - 9 am
   • Friday, 1:30 - 2:30 pm
   • @qor-lb to delete invitations in Eclipse calender
   • @markert-r to invite for new meetings
2. • Meetings on 2025-04-18 & 2025-04-21 are cancelled
3. • Milestone renamed, https://github.com/eclipse-score/score/milestone/15
   • @FScholPer to break down into epics
4. • Scope for S-CORE v1.0 #908
   • Epic: Architectural gap analysis S-CORE v0.5 #904
5. • Deletion of intermedia milestones
6. • Review of "Modules Buildable" on 2025-04-28

[anmittag]

2026-08-10

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk

Agenda

• LLVMCOV vs GCOV @aschemmel-tech change code coverage #3137
  - there are still some discussion points which shall be clarified in the safety community (e.g. check qnx with gcov/lcov) @RolandJentschETAS
• Roadmap: Check Board
  - idea: add mandatory requirements field in issues (steak holder <-> product increment, feature <-> epic )
  - automate the checks, show the gaps
  - check the idea until next time
  - clean up older stuff @anmittag
• Update Codeownership for ".github/templates" (best would be a multiple agreement check, like ref int) @FScholPer , @anmittag

[FScholPer]

2026-08-06

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb

Agenda

• How to continue with the experimental flag(request from process)
  - the original idea of having a feature toggle is not used, just part of the feature template. It can be removed from template as well as from feature-index.rst files
• ToolQualification, ToolList via SBOM? Check the status of the SBOM tool and discuss in ref int meeting how to integrate it. @anmittag

Minutes

[anmittag]

2026-08-17

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk

Agenda

• "score/component_name/src" structure => proposal to drop the "src" directory (@aschemmel-tech)
  src can be deleted, but should be equally treated in every repository => adapt "module_template" accordingly
• status release v0.9:
  milestone is 09.September, we check the progress in the alignement meeting
  tools are unifying toolversions in module.bazel
  docs-as-code updates required to have the module`s documentation integrated into the release
  automated status reporting on the way
• LLVMCOV only
  Eclipse S-CORE current SCOPE is just testing on host not on targets => to be added in the general AoU

[anmittag]

2026-08-20

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk

Agenda

• Review of PRs, remind owners to get it towards closure

[anmittag]

2026-08-24

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk
• Gerald Spreitz (COVESA)

Agenda

• Status v0.9
  • ToDoes: Release v0.9 common checklist #3186
    • Inspection Checklists required => Module Verification Report to see the real status of the modules
    • Required Tools Updates: e.g. DocsAsCode v0.7, centralized llvmcov (change code coverage #3137)?
  • DR-0008 for Reference Integration implemented (https://eclipse-score.github.io/score/main/design_decisions/DR-008-int.html)
• Status Lobster vs Docs As Code
  • Discuss the migration scenario in the Infra Meeting
• SBOM Tooling
  • PR in preparation

[antonkri]

2026-08-27

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk
• Gerald Spreitz (COVESA)

Agenda

• Status v0.9
  • no updates on https://github.com/eclipse-score/reference_integration/tree/release_candidate_09
• Status Lobster vs Docs As Code
  • Prototype for bitmanipulation, that shows how sphinx/sphinx-needs and dependable elememt can live together.
    • Desc: elements from tooling/bazel/rules/rules_score access rst files directly. dependable_element generates a lobster report, that is then integrated into sphinx-needs build using new directive, lobster-traceability-report, in baselibs/score/bitmanipulation/docs/traceability/index.rst
    • Following repos and branches are relevant:
      • baselibs -> playground/bitmanipulation-seooc
      • docs-as-code -> playground/bitmanipulation-seooc-lobster-report
      • tooling -> poc/rst-package-param
      • score -> playground/bitmanipulation-seooc
    • to give it a try run in baselibs:
      • bazel test //score/bitmanipulation:dependable_element_bitmanipulation
      • bazel run //:live_preview

[antonkri]

2026-08-31

Participants

• [ ]
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk
• Gerald Spreitz (COVESA)

Agenda

• Status v0.9

  • https://github.com/eclipse-score/reference_integration/tree/release_candidate_09
  • What is the status of DR-8 implementation?
    • Add resolved-dependency override mechanism for DR-008 reference_integration#278 -> merged
    • DR-008 Option 4: two-stage test-execution workflow (PR 2 of 2) reference_integration#280 -> in Progress
  • Module verification report
    • feat: module verification report / complex templates docs-as-code#763
    • Should be integrated for v0.9 for baselibs, persistency, logging
  • Release notes
    • Create a commit with inital release notes for modules -> @antonkri
  • Should we move release by one week?

• AI Usage

  • docs: Add AI disclaimer to README inc_someip_gateway#275 (review)
  • What should we pay attention to when using AI generated code? -> @PhilippM-qorix
  • Clarify whether we could use Eclipse Foundation CoPilot license in CI -> @FScholPer
    • Ticket opened: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/work_items/7819

• Show & Tell

  • https://github.com/orgs/eclipse-score/discussions/categories/show-and-tell

[antonkri]

2026-09-03

Participants

• @antonkri
• @FScholPer
• @PhilippM-qorix
• @BjoernAtBosch
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk
• Gerald Spreitz (COVESA)

Agenda

• Status v0.9
  • in Progress, probably we will need to move the release v0.9 at least by one week
• AI Usage
  • Proposal for AI Usage in development area in S-Core will be sent to TLs by @PhilippM-qorix
• Daily Newsletter
  • https://github.com/orgs/eclipse-score/discussions/3233
  • @BjoernAtBosch will take it with him to announce to the community
  • @FScholPer is clarifying with Eclipse Foundation how we can ran this in CI.

[BjoernAtBosch]

* Daily Newsletter * @BjoernAtBosch<https://github.com/BjoernAtBosch> will take it with him to announce to the community I guess this is a mistake, isn't it? Herzliche Grüße / Best regards Bjoern Hornburg ***@***.******@***.***> ETAS GmbH, ETAS/PJ-SC-XPC-Hi Phoenixstraße 3, 31137 Hildesheim, Germany www.etas.com<https://www.etas.com/> ETAS – Empowering Tomorrow’s Automotive Software Managing Directors: Mariella Minutolo, Veronika Danner Chairman of the Supervisory Board: Dr. Walter Schirm Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB: 19033

…

________________________________ Von: Anton Krivoborodov ***@***.***> Gesendet: Donnerstag, 3. September 2026 14:21 An: eclipse-score/score ***@***.***> Cc: Hornburg Bjoern (ETAS/PJ-SC-XPC-Hi) ***@***.***>; Mention ***@***.***> Betreff: Re: [eclipse-score/score] Meeting Minutes - Tech Lead Sync (Discussion #516) 2026-09-03 Participants * @antonkri<https://github.com/antonkri> * [ ] @FScholPer<https://github.com/FScholPer> * @PhilippM-qorix<https://github.com/PhilippM-qorix> * [ ] @johannes-esr<https://github.com/johannes-esr> * @mlangerwisch<https://github.com/mlangerwisch> * @qor-lb<https://github.com/qor-lb> * @aschemmel-tech<https://github.com/aschemmel-tech> * @masc2023<https://github.com/masc2023> * @opajonk<https://github.com/opajonk> * Gerald Spreitz (COVESA) Agenda * Status v0.9 * in Progress, probably we will need to move the release v0.9 at least by one week * AI Usage * Proposal for AI Usage in development area in S-Core will be sent to TLs by @PhilippM-qorix<https://github.com/PhilippM-qorix> * Daily Newsletter * @BjoernAtBosch<https://github.com/BjoernAtBosch> will take it with him to announce to the community * @FScholPer<https://github.com/FScholPer> is clarifying with Eclipse Foundation how we can ran this in CI. — Reply to this email directly, view it on GitHub<#516?email_source=notifications&email_token=AKLUA3W7XJOP7LTLMVPWKSL5NFO5HA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGY4DEMRSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18268222>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKLUA3XQINBVGGFWYFND3ZL5NFO5HAVCNFSNUABHKJSXA33TNF2G64TZHM4DQOJQGU4DQMJZHNCGS43DOVZXG2LPNY5TQMBRGUYDEONBOYBA>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AKLUA3SAMKKHKNPT3VCOZDT5NFO5HA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGY4DEMRSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android<https://github.com/notifications/mobile/android/AKLUA3TRNNDRA5RWDCXMM735NFO5HA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGY4DEMRSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[b-rei]

Yes. Was a wrong @mention. its @b-rei

[b-rei]

2026-09-07

Participants

• @antonkri

• @FScholPer

• @PhilippM-qorix
  @johannes-esr

• @mlangerwisch
  @qor-lb
  @aschemmel-tech
  @masc2023

• @opajonk

• @b-rei

  Gerald Spreitz (COVESA)

Notes by: @b-rei

### Agenda

Status v0.9

• Release Notes need to be revised
• Acceptance requested at module owner
• Prepare a lessons learned to improve (Integration process, release notes, Docu, Patch handling, DR08)
• @FScholPer: will check to improve the creation of automated release note

General:

• Feedback AI Usage proposal: Please provide during the next 2/3 days.
• ML3 feedback can be expected after 14.09.
• Revision and refinement of RUST strategy and implementation approach needed.

[anmittag]

2026-09-21

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk

Agenda

• Status of Verification Reports / related Dashboard
  - feat: platform_verification_report template docs-as-code#839
  - feat: scope verification reports to a report_version via valid_from docs-as-code#843
  - dashboard or equal automated "coverage-check" currently not available
  - ref-int baseline vs "main" not covered at the moment
  - Q-Gates-KPIs not defined and monitored
• Propose DDS communication support for mw::com #3263
  - connected to DDS gateway #2726 , informed Architecture round, added reviewer
• Status Dependable Elements / Sphinx / Lobster / TRLC
  - there is a "gap-report" on the way for ML3 (@qor-lb and @PhilippM-qorix) => is there a intermediate overview available?
  - re-discuss on 2026-09-24, plan an onsite meeting

[FScholPer]

2026-09-24

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk
• @odra
• @PandaeDo

Agenda

• Autosd as first function platform

  • https://eclipse-score.github.io/score/main/modules/os/operating_systems/docs/functional/index.html
  • what does that mean:
    • similar to reference integration the integration ITF tests shall be executed
    • further discussions in the alignement meeting

• ML3

  Evaluation of S-CORE process applicability

  Baselibs and Persistency were selected as pilots
  Process areas were shown in the Exida Audits with evidences from the pilots
  Actual work is planned in Epic
  Product Increment: Processes for 0.10 #3257 with subtasks like Requirements Engineering ML3 process_description#664 that carries the evidences of Baselibs and Persistency

  Conclusion: S-CORE processes are applicable including the defined tooling. Rollout startet for all modules. Small adaptions & improvements confirm this conclusion.

  Quality status v0.9 ->v0.10 is shown in the table Product Increment: Processes for 0.10 #3257

  Fix Tool Management Audit Findings process_description#568

  => docs as code is sufficient for ML3, additional tooling like TLRC/Lobster etc is not required.

• IP Critical content: improve rust coding guidelines and add CodeQL #2984 (revert or IP check)

  https://github.com/orgs/eclipse-score/discussions/3254

[anmittag]

2026-09-28

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk
• @odra
• @PandaeDo
• @fscr

Agenda

• ML3 consequences

  docs-as-code sufficient; to be synched with @antonkri

• slack and browser (from Nov. 9th FireFox Version 144) alternative is e.g. Microsoft Edge or other browsers

[anmittag]

2026-10-01

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk
• @odra
• @PandaeDo
• @fscr

Agenda

1. S-CORE 1.0 Marketing & Communication plan

   1. KeyMessages/ Highlights S-CORE v1.0 -> Discuss on Monday

      • Reference Platform
      • Commercial Distributions based on S-Core
      • We have most of the functionality we wanted to have for v1.0 and we have examples of qualifiable modules.
        • Persistency is probably the best example for a complete qualifiable Feature/Module
        • Additionally we have to see that as much as possible of Baselibs components and Lifecycle are qualifiable as well.
      • Deep Dive: what was achieved so far
        - Maturity levels for modules
        - Maturity levels for Process
        - Maturity levels for Tooling

   2. Real S-Core Release -> @antonkri , @PhilippM-qorix

      • Reach out to Eclipse Foundation Team to enable official S-Core release till 14.12.2026

   3. Downloadable image -> Discuss on Monday (@odra , @opajonk)/Wednesday QNX (@AlexanderLanin)

      • Linux
      • QNX

   4. Manual for application developer -> @FScholPer

      • Improve developer documentation and place it in one place, also including module APIs.

2. Safety AI Process & AI Platform

3. Milestone v2.0

4. DR-008 Option 4: two-stage test-execution workflow (PR 2 of 2) reference_integration#280, https://eclipse-score.github.io/score/main/design_decisions/integration/DR-008-int.html

5. ML3 consequences

[anmittag]

2026-10-05

Participants

• @anmittag
• @antonkri
• @FScholPer
• @PhilippM-qorix
• @johannes-esr
• @mlangerwisch
• @qor-lb
• @aschemmel-tech
• @masc2023
• @opajonk
• @odra
• @PandaeDo
• @fscr

Agenda

• Docs As Code - TRLC (ML3) from @anmittag
  > There was a clear decision to continue with Docs As Code as our main tool
  > COM and CFG are not using Docs As Code at all
  > There is a work around on the way to generate useable reports out of TRLC
  > invite for a workshop @anmittag and inform the x-core council about the current blocking situation

• DR-008 from @anmittag
  > actually https://eclipse-score.github.io/score/main/design_decisions/integration/DR-008-int.html was decided
  > DR-008 Option 4: two-stage test-execution workflow (PR 2 of 2) reference_integration#280 e.g. ist pending since long
  > @antonkri mentioned alternatives (?): which ones
  > Q: How to proceed? => re-evaluate the decision record
  > @antonkri starts a "requirements list" for ref-Integration

• coding guidlines @anmittag
  "maybe not super important or only a problem in persistency 😉 ... but can we "finalize" the coding guidelines for C++ and Rust for functions / methods? The S-CORE docs don’t specify exact casing: the API guideline says to follow language idioms, and the C++ guideline says the coding style is not fully decided. Current repositories differ: baselibs does have a repository-local C++ PascalCase rule, so the clarification should say whether that is intended project-wide, persistency uses snake_case for Rust and C++. Used refs:

  [S-CORE API guideline](https://github.com/eclipse-score/score/blob/main/docs/contribute/development/api_guideline.rst)
  [S-CORE C++ coding guideline](https://github.com/eclipse-score/score/blob/main/docs/contribute/development/cpp/coding_guidelines.rst)
  [Writing Rust Code incl. Coding Guidelines](https://eclipse-score.github.io/score/main/contribute/development/rust/coding_guidelines.html)
  [api_guideline.rst](https://github.com/eclipse-score/score/blob/main/docs/contribute/development/api_guideline.rst)[eclipse-score/score]   (https://github.com/eclipse-score/score)[coding_guidelines.rst](https://github.com/eclipse-score/score/blob/main/docs/contribute/development/cpp/coding_guidelines.rst)[eclipse-score/score](https://github.com/eclipse-score/score)
  
  for rust there is the pr from dan https://github.com/eclipse-score/score/pull/3262 and for c++ we have to define what misra rules https://github.com/github/codeql-coding-standards/tree/main/cpp, clippy rules should be applied https://github.com/eclipse-score/score_cpp_policies     
  https://github.com/github/codeql-coding-standards/blob/main/docs/iso_26262_tool_qualification.md
  

  we shall create a common coding guidline @anmittag

• not anymore included repos back to incubators? @anmittag
  > we use the "quality stage" of a repos instead

• FEP Process Change from @qor-lb please review
  docs: add incubation path to the FEP guide #3299

• PoC NVIDIA SRAC in ref_int feat: add SRAC sidecar proof of concept reference_integration#370 please have a look inside

for next meeting:

• 1.0