Infrastructure Community Meeting Minutes

[AlexanderLanin]

All official meetings will be documented in this thread. So if you subscribe here, you'll get summaries of the meetings you missed.

Landing page for our team: #107

[AlexanderLanin]

Kick-Off

2025-01-28

Agenda

• Welcome new members; What is score?; What is this community?
• Introductions
• Current state & open topics / backlog
• Daily

Important Links

• https://github.com/orgs/eclipse-score/discussions/216

Committers

• Alexander Lanin @AlexanderLanin
• Nikola Radakovic @nradakovic (soon)
• Maximillian Sören Pollak, @MaximilianSoerenPollak (soon)

Contributors

• Dan Calavrezo @dcalavrezo-qorix
• Nicolae Dicu @nicu1989
• Sameer Srivastava @sameer6989
• Aymen Soussi
• Tomas Pereira

Part time contributors

• Daniel Woste @danwos
• Philip Partsch @PhilipPartsch

Stakeholders:

• Rebecca Markert
• Lukasz Tekieli @ltekieli
• VinodReddy GopiReddy
• Sven Bachmann
• Jochen Hoenle, @hoe-jo
• Michal Mueller

Meeting Minutes

• @AlexanderLanin to sync with https://github.com/orgs/eclipse-score/discussions/90
• @AlexanderLanin to clarify whether we can write clear names here!
• Chat: some people have trouble joining slack --> Contact your respective teach lead.
• How to proceed in case of conflicts? --> will be addressed in contributor guidelines by tech leads. For now decisions within the communities can be escalated to comitters, otherwise to tech leads.
• Reminder: everyone needs to sign the eclipse contributor agreement!
• Do we want to structure in sub teams? Let's address this after a few dailies to see how many will actually show up :-)
• how to assign tickets -> for now contact @AlexanderLanin via chat
• how do we get everyone into contributor status? Already in progress by tech leads! Rebecca wiill check again.
• how to assign reviewers -> for now post the PR into chat
• @AlexanderLanin & @ltekieli will look into fixing https://github.com/orgs/eclipse-score/teams/community-operational to reflect reality. Then we might be able to activate CODEOWNERS. @AlexanderLanin to create tickets for that.
• how do we prioritize? -> not answered yet
• how to start working? -> pull a ticket! :-)
• a wiki for already solved problems etc -> we need to be clear what goes into chat, issue, docs-as-code or wiki. @PhilipPartsch and @MaximilianSoerenPollak will discuss their ideas regarding wiki vs docs-as-code.
• A longer meeting will be required in addition to dailies! With an open backlog somewhere.
  • Daily Mo, Wed, Fr 10:30 (on Wednesdays a little longer)

Potential "topics":

• docs-as-code
• guidelines (pyton, rust, c++)
• automations, CI/CD
• OSS / licensing

[AlexanderLanin]

Daily

2025-01-28

Agenda

• Alignment on currently worked upon issues. Specifically identification of dependences and collaboration.

Participants

• Alexander Lanin @AlexanderLanin
• Nikola Radakovic @nradakovic
• Sameer Srivastava @sameer6989
• Maximillian Sören Pollak, @MaximilianSoerenPollak
• Aymen Soussi
• Rebecca Markert

Meeting Minutes

• Contribute to Issues via comment or via pull request. You'll need to fork the repository.
• Operational Backlog
• "Kick-Off": a few more people in our existing community
• Meeting Infrastructure: Meetings stay as they are for now. We'll switch to open eclipse infrastructure mid February: google calender & zoom meetings.
• Chat:
  • Chat-Access
  • Chat
• Let's make issues smaller, so they are estimatable and closed
• Let's create "milestones" what we aim to achieve e.g. end of january / february

OSS deep dive
split OSS (#82, #126) to sub-issues, e.g.:

• setup dash for python on PR (non blocking) -> dash: Integrate DASH tool in Bazel build #155
  • rename "license check" to something like "license dry run"
• automation: print problems as comment to pull request, see also bug: pr-preview comment #211
• create private key for automatic clearance
• extend automaton with automatic clearance
• add rust dependencies to dash (via bazel)
• add C++ dependencies to dash (via bazel)
• bazel modules
• change automation (daily / blocking / etc)

[AlexanderLanin]

Daily

2025-01-29

Agenda / Minutes

• Collect current member status (see below)
• Yet another issue organization attempt: INF - Infrastructure Community
• Collect what needs to be documented: document current setup #245
• Daily time -> 1 hour earlier? @nradakovic ok?
• Hint: good first issues
• esbonio setup broken? -> @MaximilianSoerenPollak

Participants

• Alexander Lanin @AlexanderLanin
• Nikola Radakovic @nradakovic (soon)
• Maximillian Sören Pollak, @MaximilianSoerenPollak (soon)
• Dan Calavrezo @dcalavrezo-qorix
• Nicolae Dicu @nicu1989
• Sameer Srivastava @sameer6989
• Aymen Soussi
• Tomas Pereira
• Daniel Woste @danwos
• Philip Partsch @PhilipPartsch
• Rebecca Markert
• Lukasz Tekieli @ltekieli
• VinodReddy GopiReddy
• Sven Bachmann
• Jochen Hoenle, @hoe-jo
• Michal Mueller
• Anton

Current member status

who	score-member (GitHub)	chat (Slack)
Alexander Lanin @AlexanderLanin	✔️	✔️
Nikola Radakovic @nradakovic	✔️	✔️
Maximillian Sören Pollak, @MaximilianSoerenPollak	✔️	✔️
Dan Calavrezo @dcalavrezo-qorix	✔️	✔️
Nicolae Dicu @nicu1989	✔️	✔️
Sameer Srivastava @sameer6989	❌	✔️
Aymen Soussi	requested ❓	✔️
Tomas Pereira	❌ (blocked by legal)	❌ (blocked by legal)
Daniel Woste @danwos	✔️	✔️
Philip Partsch @PhilipPartsch	✔️	✔️
Michael Mueller	❌	❌

[AlexanderLanin]

Daily

2025-01-31

Agenda / Minutes

• Attributes we need for GitHub Projects: assignee, estimated start, estimated end, status

• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.

• Multi-repo setup decision review/feedback requested. PR

• Python-tooling Issue organize vote inside slack python chat + expert meeting

Participants

• Alexander Lanin @AlexanderLanin
• Anton
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• Lukasz Tekieli @ltekieli
• Maximillian Sören Pollak, @MaximilianSoerenPollak (soon)
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic (soon)
• Philip Partsch @PhilipPartsch
• Rebecca Markert
• Sameer Srivastava @sameer6989
• Sven Bachmann
• Tomas Pereira
• VinodReddy GopiReddy

[MaximilianSoerenPollak]

Daily

2025-02-03

Agenda / Minutes

• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.

@MaximilianSoerenPollak will make meeting for python tooling discussion.

PR-Preview issue from forks:
-> Either manual approve PR to build preview
-> Or have a separate repository for the PR's

Branch naming should be restricted to ensure that we do not overwrite 'main' release documentation.

Participants

• Alexander Lanin @AlexanderLanin
• Anton
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• Lukasz Tekieli @ltekieli
• Maximillian Sören Pollak, @MaximilianSoerenPollak (soon)
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic (soon)
• Philip Partsch @PhilipPartsch
• Rebecca Markert
• Sameer Srivastava @sameer6989
• Sven Bachmann
• Tomas Pereira
• VinodReddy GopiReddy

[AlexanderLanin]

Daily

2025-02-05

Agenda / Minutes

• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.
• Discussion on PR Previews docs: preview in PRs from forks #194. Suggestion: separate repo (pages site) for previews.
  • @dcalavrezo-qorix will create a summary in docs: preview in PRs from forks #194 which everyone should read!
  • Collect feedback from eclipse experts -> separate repo for PR-Previews!
  • FYI New Repo: PR on https://github.com/eclipse-score/.eclipsefdn/blob/main/otterdog/eclipse-score.jsonnet
• New: #score-bazel-comminity in chat for bazel questions
• In Monday-Daily @hoe-jo will organize a presentation on existing bazel integrations of python & C++ tooling.
• How do people get Comitter/Contributor Status?
  • For Contributor: ask a comitter!
  • How to get Comitter: for now ask tech lead in your company, there is a voting based on contributions to the score project.
• Request: priorities and goals. What are the next things we want to implement? Potentially more alignment meetings.

Participants

• Alexander Lanin @AlexanderLanin
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• Maximillian Sören Pollak, @MaximilianSoerenPollak (soon)
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic (soon)
• Rebecca Markert
• Sameer Srivastava @sameer6989
• Sven Bachmann

[AlexanderLanin]

Daily

2025-02-07

Agenda / Minutes

• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.

Participants

• Alexander Lanin @AlexanderLanin
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• Maximillian Sören Pollak, @MaximilianSoerenPollak
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic
• Rebecca Markert
• Sameer Srivastava @sameer6989
• Sven Bachmann
• Lukasz @ltekieli
• @PhilipPartsch

[AlexanderLanin]

Daily

2025-02-10
To join the meeting, get in contact via Chat-Access + Chat

Agenda / Minutes

• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.
• C++: Prepare Decision: code analysis tool #244 discussed. Small comparison to other tools requested. Hint: usually C++ is checked by 2-4 tools in parallel to achieve usability AND compliance. Hint2: check commercial products for free licensing for OSS.
• C++: MISRA via GitHub CodeQL? #185 @AlexanderLanin to create sub-issue for C++ expert to try it out

Participants

• @AlexanderLanin
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• @MaximilianSoerenPollak
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic
• Rebecca Markert
• @sameer6989
• Sven Bachmann
• Lukasz @ltekieli
• @PhilipPartsch

[AlexanderLanin]

Daily

2025-02-12
To join the meeting, get in contact via Chat-Access + Chat

Agenda / Minutes

• Presentation of python tools, see python: tooling selection #259

Participants

• @AlexanderLanin
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• @MaximilianSoerenPollak
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic
• @sameer6989
• @PhilipPartsch
• Lukasz @ltekieli
• Sven Bachmann
• Rebecca Markert

Guests

• M.D. (BMW)
• S.M. (BMW)
• L.M. (BMW)
• J.N. (BMW)

[AlexanderLanin]

Daily

2025-02-14
To join the meeting, get in contact via Chat-Access + Chat

Agenda / Minutes

• Roadmap "pre-draft"
• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.

Participants

• @AlexanderLanin
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• @MaximilianSoerenPollak
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic
• @sameer6989
• @PhilipPartsch
• Lukasz @ltekieli
• Sven Bachmann
• Rebecca Markert

[AlexanderLanin]

Python tooling in bazel deep dive

2025-02-14
To join the meeting, get in contact via Chat-Access + Chat

Agenda / Minutes

• Sharing experience on how to best integrate python tools into bazel
• Sandbox Approach
• Dependency Management in Bazel
• Running Black as Bazel Aspect

Participants

• @hoe-jo
• @AlexanderLanin
• @MaximilianSoerenPollak
• @PhilipPartsch
• S.M. (BMW)
• L.M. (BMW)
• J.N. (BMW)
• D.M. (BMW)

[hoe-jo]

Python tooling in bazel deep dive follow up

2025-02-21
To join the meeting, get in contact via Chat-Access + Chat

Agenda / Minutes

• Continue on exchanging experiences with bazel IDE integration and linter support

Participants

• @hoe-jo
• @AlexanderLanin
• @MaximilianSoerenPollak
• @PhilipPartsch
• S.M. (BMW)
• L.M. (BMW)
• J.N. (BMW)
• D.M. (BMW)

[AlexanderLanin]

Daily

2025-02-17
To join the meeting, get in contact via Chat-Access + Chat

Agenda / Minutes

• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.
• First discussion of git: Implement pre-commit hooks #352

Participants

• @AlexanderLanin
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• @MaximilianSoerenPollak
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic
• @sameer6989
• @PhilipPartsch
• Lukasz @ltekieli
• Sven Bachmann
• Rebecca Markert

[AlexanderLanin]

How to reuse tools across repositories?

2025-02-17
To join the meeting, get in contact via Chat-Access + Chat

Agenda / Minutes

• How to reuse tools across repositories?
• We can use bazel (see https://eclipse-score.github.io/score/main/features/infrastructure/bazel_registry.html) to pull tools via bazel
• One repository per tool is too much
• One repository can hold multiple bazel modules
• one bazel module = one tool, or we group them:
• => start with one group and split as needed
• Example:
  • Setup: score-tooling with cr_checker
  • Scenario: bug in cr_checker
    • fix in score-tooling
    • release new score-tooling-group
    • update bazel-registry
    • update all users (e.g. Dependabot, Renovatebot?)
• Separate repo or keep in score?
  • For now we can use the score repository with modules as described above
  • Note: bazel_registry is even optional. Direct usage is also possible.
• Proposal: use both approaches
  • Move one tool (e.g. cr_checker) to a separate repository (tooling repo in https://github.com/eclipse-score/) -> POC by @nradakovic
  • Keep the rest in score for now. Depending on timeline, we wait for tooling POC.
• How to synchronize python versions across repositories / modules?
  • root repository sets the python version. tooling sets a minimal supported version.

Participants

• @AlexanderLanin
• Dan Calavrezo @dcalavrezo-qorix
• @MaximilianSoerenPollak
• Nikola Radakovic @nradakovic
• Lukasz @ltekieli
• @hoe-jo

[AlexanderLanin]

Daily

2025-02-19
To join the meeting, get in contact via Chat-Access + Chat

Agenda / Minutes

• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.
• GitHub PR Workflow #406 by @AlexanderLanin => Next daily, meeting will be used for follow up discussion.
• llvm: Add LLVM Toolchain config #413 discussion by @nradakovic => Set up example repositories, leave reusability for later discussion.
• IDE integration via 'virtualenv' but build via bazel. Virtualenv should strive to cover '100%' of use cases. but be 'okay' with that. => More discussion needed.

Participants

• @AlexanderLanin
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• @MaximilianSoerenPollak
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic
• @sameer6989
• @PhilipPartsch
• Lukasz @ltekieli
• Sven Bachmann
• Rebecca Markert

[dcalavrezo-qorix]

Weekly Rust 19-08-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix

NO SHOW ( probably due to vacation period)

[AlexanderLanin]

Infrastructure Weekly

Date: 24th August, 2026.

Participants

News

• renamed: process -> process_description
  • status: renamed in docs, score_platform, baselibs
  • automation: ready, but so far every repo needs manual rework. Mostly because they were not on the latest version pre-rename.

Agenda / Meeting Minutes

• Options rst-> trlc converter: Migration path rst to trlc tooling#441
  • Looked at Plan, no major concerns except direct rst parsing
  • Side-info: docs-as-code classification is available at https://eclipse-score.github.io/score/main/score_tools/tools_documentation/doc_as_code.html#doc_tool__doc_as_code
  • effort for qualification is currently not known --> @a-zw @MaximilianSoerenPollak (@AlexanderLanin)
• Handling of misra findings (centralization)
  • align on first/most important rules which we start fixing soon
  • increase list of for-now-ignore rules
  • next step: @FScholPer will talk to @LittleHuba
• SBOM generation way forward
  • see Add SBOM reference_integration#304
  • please review code change, and generated SBOM as attached to workflows (linux build and documentation build)
• Devcontainer version bump
  • @AlexanderLanin to move devcontainer dependency to dependabot-compatible format in all repos
• APM tooling
  • Ready to go AI-setup for S-CORE
  • Documentation: https://github.com/eclipse-score/mcp-servers/tree/local_harness_apm
  • Request for feedback, report to @FScholPer
• repo-sync handling more and more complex PRs
• caching
  • prototype ready to go: use cache from cicd-actions or cicd-workflows for a simple 80% solution on caching
  • --> @AlexanderLanin
• llvm
  • we can cache the download
  • llvm extraction alone takes ~220s via bazel while we can do it in ~70s.
  • POC done: use faster tool for extracting the exact same file
  • extended solution: fully wrap LLVM in bazel_cpp_toolchains
  • --> @nradakovic
• bazel_registry url adapted
  • bazel_registry was changed to api endpoint to support private modules
  • api endpoint is rate limited?
  • api endpoint would typically not be cached, if someone uses caching
  • find quick solution for 0.9, and proper long term solution --> @AlexanderLanin
• qnx sdp
  • status: draft agreement exists to cache the qnx sdp in s-core, however it must be restricted to s-core members + CICD
  • next steps: draft in review + setup private storage (restricted to s-core members + CICD) --> @dcalavrezo-qorix
• cache size: can we get 50GB storage on all (important) repos? --> @FScholPer

Next time

[dcalavrezo-qorix]

Weekly Rust 26-08-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix
@PLeVasseur
@odra

Meeting minutes:

• RUST coding guidelines
  [Coding Guideline]: CERT C MEM35 Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines#1234

• RUST coding guidelines SLack channel https://sdvworkinggroup.slack.com/?redir=%2Farchives%2FC0BQ24GBCM6%3Fname%3DC0BQ24GBCM6

• https://github.com/eclipse-score/tooling/tree/main/coverage

Action Items:
@PLeVasseur will introduce Luiz's coding guideline today in the Safety-Critical Rust Consortium's Coding Guidelines Meeting.

[AlexanderLanin]

Infrastructure Weekly

Date: 31st August, 2026.

Participants

News

• docs-as-code 8.1:
  • metamodel visualization
  • module verification report template
• modules/versions for S-CORE 0.9 release here

Agenda / Meeting Minutes

Updates on open points from last meeting

no updates

New topics

• ref int PR#320 for 0.9
  • does not quite compile etc
  • first docs build since months, therefore it does not work out of the box
• llvm caching can be improved via external cache, see feat: fast_llvm_repo bazel_cpp_toolchains#125
  • note also cicd-actions setup-bazel-cache reimplementation on cache branch

Next time

[dcalavrezo-qorix]

Weekly Rust 02-09-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix
@PLeVasseur
@FScholPer

Meeting minutes:

• https://sdvworkinggroup.slack.com/archives/C0BQ24GBCM6/p1788285544782919
• [Coding Guideline]: CERT C MEM35 Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines#1234 (comment)
• https://github.com/orgs/rust-sig/discussions/42
• https://www.sonair.com/journal/how-we-safety-certified-the-worlds-first-rust-implementation

[AlexanderLanin]

Infrastructure Weekly

Date: 07th September, 2026.

Participants

Agenda / Meeting Minutes

• Repo Policy Sync is now running with the first few policies
• Semi Maintained Ticket View

[dcalavrezo-qorix]

Weekly Rust 09-09-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix
@bharatGoswami8

Meeting minutes:

• based on the issues created by @bharatGoswami8

Could we upgrade to Rust Edition 2024? I've created ticket for it:

https://github.com/eclipse-score/score_rust_policies/issues/13
 https://github.com/eclipse-score/toolchains_rust/issues/42

Thanks!

we need to define as a Platform requirement in S-CORE the Rust edition that is being used in the project , see also issue #1499

[dcalavrezo-qorix]

Infrastructure Weekly

Date: 14th September, 2026.

Participants

Agenda / Meeting Minutes

Coverage tool split out of score_tooling

• What changed: the LLVM coverage pipeline (@score_tooling//coverage) now lives in its own
  repo and Bazel module, score_coverage 0.1.0 (registry release).
  Docs, requirements, architecture and verification report:
  https://eclipse-score.github.io/coverage_tool/main/index.html
• Consumer impact: no interface change, only labels
  (@score_tooling//coverage:… → @score_coverage//:…).
  First migration: Migrate coverage pipeline to score_coverage 0.1.0 baselibs#584
  (also fixes score's llvm_cov integration filters @flatbuffers//:include/flatbuffers/*.h in the report out baselibs#558).
• Rationale: the split follows the Tool Management Plan
  (https://eclipse-score.github.io/score/main/platform_management_plan/tool_management.html#evaluation):
  every tool is identified and evaluated, but only tools with TCL LOW must be qualified.
  A qualified tool needs a pinned version, its own tests and verification report, so it gets
  its own module instead of sharing a release cycle with evaluation-only tools.
• TCL in one line: Tool Confidence Level (ISO 26262-8, clause 11).
  • TCL HIGH: a malfunction cannot violate a safety requirement, or it would be caught downstream. Only an evaluation (Tool Verification Report) is needed.
    Examples in S-CORE: clang-format, rustfmt, clippy, GitHub.
  • TCL LOW: a malfunction can violate a safety requirement and nothing else would detect it. Qualification required; S-CORE's method is "validation of the software tool" (requirements, tests, verification report).
    Examples: gtest, Bazel, clang-tidy, qcc, Doc-as-Code, ITF, and now the coverage tool (over-reported coverage silently passes untested safety code).
  • Full list: https://eclipse-score.github.io/score/main/score_tools/score_tools_evaluation_list.html
• Open: review by the process team of the open points (TVR location, tool_req vs TRLC, approvers - e.g who will sign the approval workflow - safety manager, security mangager, project lead);

Status: it's working, it's being rolled out to all modules this week. Gaps will be covered by feature requests directly in the new repo.

new: how do we do tool classifications in score?

Useblocks already has open sourced an approach how this would be possible at https://safety.useblocks.com/
@dcalavrezo-qorix to compare what he did (above) to the useblocks approach
@AlexanderLanin to talk to process guys to compare their idea with the useblocks approach

Caching - any whishes?

e.g. https://github.com/eclipse-score/docs-as-code/actions/runs/34842776682
@AlexanderLanin to merge it this week

SBOM

SBOM exists in ref int workflows, but we should link it from somewhere... ask in process community what they expect when they say "you need to have an SBOM" --> @FScholPer

QNX Status

New week, new problem: https://excalidraw.com/#room=b01a3ea1500fb2d467f4,l_uSKYtqYuFwoQ1scqwpHA

[dcalavrezo-qorix]

Weekly Rust 16-09-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix
@martinu_avl

Meeting minutes:

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

[AlexanderLanin]

Infrastructure Weekly

Date: 21st September, 2026.

Participants

Agenda / Meeting Minutes

BUILD.bazel vs BUILD

• Currently it's a mix
  • ChatGPT recommends BUILD.bazel
  • We should issue a recommendation in score?!
  • We may even want to trigger alignment?!
  • Related discussion
• Discussion
  • On average people prefer BUILD.bazel
  • @nradakovic will check whether this will lead to problems in BMW

Centralized score_toolchain.bazelrc and MODULE.bazel

• Present idea/concept, @nradakovic @odra
• Status
  • Done: lifecycle
  • Almost: baselibs
  • This week: start 3rd module?!
  • Keep up to date: set up repo-policy-sync policy by @AlexanderLanin

QNX SDP

• Present idea/concept, @nradakovic
  • in score we'll host the SDP ourselves
  • split SDP package into smaller chunks, at least into x86 and arm.
  • support local-SDP mode
• Status
  • Currently "50% of CI jobs" fail due to download (quote from score community alignment meeting)
  • agreed: we'll host the SDP ourselves (for score members + CICD only)
  • no private storage available yet
  • @nradakovic is working on score-SDP-building-script
  • Note: limited storage implies we cannot store many older SDP versions

Ubuntu 26

The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see actions/runner-images#14748

• Do we use ubuntu-latest? ~100 hits
  • try global search-replace with ubuntu-24.04
• Ubuntu 22 will be dropped by April

[dcalavrezo-qorix]

Weekly Rust 23-09-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix
@PLeVasseur
@FScholPer

Meeting minutes:

[AlexanderLanin]

Infrastructure Weekly

Date: 28th September, 2026.

Participants

Agenda / Meeting Minutes

Board

See meeting column in INF - Infrastructure Community (view)

• Discussed docs-as-code 8.3.0, e.g. https://eclipse-score.github.io/docs-as-code/main/how-to/perform_tool_verification.html
  • Open point: do all classifications now move to their respective repositories? (process meeting tomorrow)
  • Open point: do we transform all existing tool classifications?
• Caching i sin place
• BUILD.bazel currently stilly unclear
• qnx sdp: empty repos created
• ubuntu 26: create concrete issues --> @AlexanderLanin
• coverage summaries "rejected"

ML3

• Next steps -> process meeting

#3269

• how to be sure that every repo uses the same structure?
• -> no obvious solution identified

umbrella targets

@kgraeper will provide use cases in #infrastructure slack channel, and a summary for these meeting minutes :-)

[dcalavrezo-qorix]

Weekly Rust 30-09-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix
@bharatGoswami8

Meeting minutes:

• RUST coding guidelines PR still opened: https://eclipse-score.github.io/score/pr-3262/contribute/development/rust/coding_rules/index.html
  Add Rust coding rules catalogue aligned with the SCRC MISRA C++ cross-reference (draft) #3262

[AlexanderLanin]

Infrastructure Weekly

Date: 05th October, 2026.

Participants

Agenda / Meeting Minutes

Board

See INF - Infrastructure Community (view)

• Open point: do all classifications now move to their respective repositories? (process meeting tomorrow)
• Open point: do we transform all existing tool classifications?
• BUILD.bazel currently stilly unclear
• qnx sdp: empty repos created
• coverage per component

umbrella targets

@kgraeper will provide use cases in #infrastructure slack channel, and a summary for these meeting minutes :-)

[dcalavrezo-qorix]

Weekly Rust 07-10-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix

Meeting minutes:

• no show
• RUST coding guidelines PR still opened: https://eclipse-score.github.io/score/pr-3262/contribute/development/rust/coding_rules/index.html
  Add Rust coding rules catalogue aligned with the SCRC MISRA C++ cross-reference (draft) #3262