Meeting Minutes #236

AlexanderLanin · 2025-01-28T09:04:29Z

AlexanderLanin
Jan 28, 2025
Collaborator

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 · 2025-01-28T09:05:59Z

AlexanderLanin
Jan 28, 2025
Collaborator Author

0 replies

AlexanderLanin · 2025-01-28T09:07:51Z

AlexanderLanin
Jan 28, 2025
Collaborator Author

Daily

2025-01-28

Agenda

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

Participants

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)

0 replies

AlexanderLanin · 2025-01-28T21:26:26Z

AlexanderLanin
Jan 28, 2025
Collaborator Author

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

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	❌	❌

0 replies

AlexanderLanin · 2025-01-31T08:29:57Z

AlexanderLanin
Jan 31, 2025
Collaborator Author

0 replies

MaximilianSoerenPollak · 2025-02-03T10:02:13Z

MaximilianSoerenPollak
Feb 3, 2025
Collaborator

0 replies

AlexanderLanin · 2025-02-05T09:20:44Z

AlexanderLanin
Feb 5, 2025
Collaborator Author

0 replies

AlexanderLanin · 2025-02-07T09:33:21Z

AlexanderLanin
Feb 7, 2025
Collaborator Author

0 replies

AlexanderLanin · 2025-02-07T11:33:36Z

AlexanderLanin
Feb 7, 2025
Collaborator Author

0 replies

AlexanderLanin · 2025-02-10T09:21:54Z

AlexanderLanin
Feb 10, 2025
Collaborator Author

0 replies

AlexanderLanin · 2025-02-12T14:07:32Z

AlexanderLanin
Feb 12, 2025
Collaborator Author

0 replies

AlexanderLanin · 2025-02-12T15:38:35Z

AlexanderLanin
Feb 12, 2025
Collaborator Author

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

0 replies

hoe-jo · 2025-02-14T14:57:35Z

hoe-jo
Feb 14, 2025
Collaborator

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

0 replies

AlexanderLanin · 2025-02-17T09:00:06Z

AlexanderLanin
Feb 17, 2025
Collaborator Author

0 replies

AlexanderLanin · 2025-02-17T10:01:42Z

AlexanderLanin
Feb 17, 2025
Collaborator Author

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

0 replies

AlexanderLanin · 2025-02-17T19:26:24Z

AlexanderLanin
Feb 17, 2025
Collaborator Author

0 replies

AlexanderLanin · 2026-03-24T09:25:04Z

AlexanderLanin
Mar 24, 2026
Collaborator Author

Weekly

2025-03-30
To join the meeting see calendar in #107

Participants

Agenda / Minutes

Topic	Who	Discussion	Conclusion
eclipse hint to use pinact and harden-runner	@AlexanderLanin	try using them?!	lets try in some repo
os_images QNX8	@jgetas	* Basic idea for testing: not create custom QEMU QNX IFS, use generic QEMU QNX IFS + custom test partition * requires new QNX SDP 8.0.3 tarball: should be aligned with default SDP in cpp toolchain	This will not work with parallel PR at eclipse-score/rules_imagefs#4, to be discussed offline by @jgetas and @nradakovic, e.g. whether one approach is better or how to support both
qnx update to 8.0.3	-	whom do we need to ask?	we merge and @nradakovic asks anton, and @AlexanderLanin addresses in CFT
gnu11 vs c11	@nradakovic	Use -std=gnu11 instead of -std=c11 on Linux	see comment in linked issue
feature injection in toolchains	@nradakovic	Add external feature injection to GCC toolchain (like toolchains_llvm extra_known_features)	No-one in infrastructure is aware of this repository or the approach here. We need documentation and a DR for the repository concept.
Presentation of fixed Source Code Linker in ref-integration (if there is time)	@MaximilianSoerenPollak	Showcase & Feedback	-
Repo Overview	@AlexanderLanin	FYI: categories now via jsonnet, see PR	-

3 replies

AlexanderLanin Mar 30, 2026
Collaborator Author

Are we on C11? Why not C17? Maybe even C99? :D
@AlexanderLanin to ask in architecture round

AlexanderLanin Mar 30, 2026
Collaborator Author

Info on "constrained links in sphinx-needs": docs-as-code is upgrading sphinx-needs dependency to 8.0 to allow first attempts of usage.

a-zw Mar 30, 2026
Collaborator

Created a task for Needs 8: eclipse-score/docs-as-code#456

dcalavrezo-qorix · 2026-03-25T13:03:10Z

dcalavrezo-qorix
Mar 25, 2026
Collaborator

Weekly RUST 25-03-2026

14:00-15:00 CET

Participants

@darkwisebear
@dcalavrezo-qorix
@bharatGoswami8
@johannes Lex
@pawelrutkaq

Agenda

Miri integration into Bazel
score_debug (?) https://github.com/eclipse-score/baselibs_rust/blob/7227b67c45dff719901d8f3763d5a37fb55aa0ad/src/log/score_log_fmt/fmt.rs#L121

0 replies

dcalavrezo-qorix · 2026-04-01T12:09:40Z

dcalavrezo-qorix
Apr 1, 2026
Collaborator

Weekly RUST 01-04-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix
@PLeVasseur

Agenda

Miri integration into Bazel

0 replies

dcalavrezo-qorix · 2026-04-08T12:09:07Z

dcalavrezo-qorix
Apr 8, 2026
Collaborator

Weekly RUST 08-04-2026

14:00-15:00 CET

Participants

@dcalavrezo-qorix
@PLeVasseur
@darkwisebear
@AlexanderLanin
@bharatGoswami8
@JochenSatETAS
@sophokles73

Agenda

Miri integration into Bazel - open PRs
pastey crate forking - reasons behind it ?

0 replies

AlexanderLanin · 2026-04-08T12:38:28Z

AlexanderLanin
Apr 8, 2026
Collaborator Author

Weekly

2025-04-13
To join the meeting see calendar in #107

Participants

Agenda / Minutes

NEW

Bazel: compatibility_level

Who: @AlexanderLanin
Discussion:
- No-op since Bazel 8.6
- Background: https://bazel.build/external/faq#compatibility-level
- Background: [8.6.0] Bzlmod: Make compatibility_level and max_compatibility_level noops bazelbuild/bazel#28615
- Proposal: drop compatibility_level everywhere and/or update Bazel
Conclusion:
- Upgrade 8.4.2 to 8.6.0 - try it out & to be addressed in CFT
  - Plan upgrade to 9.0.2 via CFT (e.g. for s-core 0.8 release). Ideally write down generic upgrade plan (e.g. release + 3 months).
- Afterwards we exclude compatibility_level from our bazel registry auto injection script.

Bazel: bazel_dep version

Who: @MaximilianSoerenPollak
Discussion:
- Should bazel_dep specify a version when it is overridden?
- See: Add version to Docs-as-code #2762
Conclusion:
- We should omit the version in bazel_dep when it is overridden, to avoid confusion. This is not some hard rule, just a recommendation.

Release automation

Who: @lurtz
Discussion:
- Try semantic versioning + automated weekly releases in devcontainer
- Question: can this scale to all S-CORE repos?
Conclusion:
- conventional commits + weekly releases will be tried in devcontainer. We'll then roll it out to other repos if it works well, docs-as-code seems like a good candidate for next one.

OLD

Eclipse tooling hint (pinact & harden-runner)

Who: @AlexanderLanin
Discussion:
- Try using:
  - pinact
  - harden-runner
Conclusion:
- Try in some repo
- Update: no update

OS images QNX8

Who: @jgetas
Discussion:
- Testing idea:
  - Use generic QEMU QNX IFS
  - Add custom test partition (instead of custom IFS)
- Requires new QNX SDP 8.0.3 tarball
- Should align with default SDP in C++ toolchain
Conclusion:
- Conflicts with parallel PR: Adding pkg_rules support rules_imagefs#4
- To be discussed offline by @jgetas and @nradakovic
- Goal: decide best approach or support both
- Update 2026-04-13: discussion ongoing

QNX update to 8.0.3

Who: —
Discussion:
- Who needs to approve?
Conclusion:
- Merge first
- @nradakovic asks Anton
- @AlexanderLanin addresses in CFT
- Update 2026-04-13:
  - addressed, feedback from CFT expected next Monday (which version do people need to have supported)
  - Release notes: https://support.qnx.com/developers/docs/relnotes8.0/com.qnx.doc.release_notes/topic/8.0.3_prod_release_notes/8.0.3_rn.html
  - Ideally we don't want to support both... but maybe we have to?
  - everything is prepared, reference integration can just try it (0.5.0 toolchain version)

GNU11 vs C11

Who: @nradakovic
Discussion:
- Use -std=gnu11 instead of -std=c11 on Linux bazel_cpp_toolchains#46
Conclusion:
- See comment in linked issue
- Addressed in CFT
- Update 2026-04-13: in discussion, e.g. one proposal is to split macros like cc_library into cc_library_gnu11 and cc_library_c11, and then have the user choose which one to use, or select via features / command line. To be involved: etas?, baselibs, communication. @nradakovic will prepare a decision proposal for next week.

Feature injection in toolchains

Who: @nradakovic
Discussion:
- Add external feature injection to GCC toolchain (like toolchains_llvm extra_known_features) bazel_cpp_toolchains#45
Conclusion:
- No awareness in infrastructure team
- Need documentation + DR for repository concept
- Update 2026-04-13: no real update. We'll request a proper decision record for score_cpp_policies (as a separate repo with feature injection), as no-one in infrastructure meeting understands the reasons for this approach. We see big problems in feature ordering.

Skipped

Extraction of cr_checker to pure Python & pre-commit

Who: @AlexanderLanin
Discussion:
- Who is interested?
Conclusion:
- (skipped)

0 replies

dcalavrezo-qorix · 2026-04-15T11:58:50Z

dcalavrezo-qorix
Apr 15, 2026
Collaborator

Weekly RUST 15-04-2026

14:00-15:00 CET

Participants

meeting was skipped

Agenda

Miri integration into Bazel - PRs merged
pastey crate forking - see the axios breakage attack

0 replies

AlexanderLanin · 2026-04-20T10:18:19Z

AlexanderLanin
Apr 20, 2026
Collaborator Author

Weekly

2025-04-20
To join the meeting see calendar in #107

Participants

Agenda / Minutes

OLD points, which are not closed yet

Bazel: compatibility_level

Who: @AlexanderLanin
Discussion:
- No-op since Bazel 8.6
- Background: https://bazel.build/external/faq#compatibility-level
- Background: [8.6.0] Bzlmod: Make compatibility_level and max_compatibility_level noops bazelbuild/bazel#28615
- Proposal: drop compatibility_level everywhere and/or update Bazel
Conclusion:
- Upgrade 8.4.2 to 8.6.0 - try it out & to be addressed in CFT
  - Plan upgrade to 9.0.2 via CFT (e.g. for s-core 0.8 release). Ideally write down generic upgrade plan (e.g. release + 3 months).
- Afterwards we exclude compatibility_level from our bazel registry auto injection script.
- Update 2026-04-20 update from tech lead and community alignment: upgrade to 8.6 is fine, assuming someone actually reads the changes and checks whether known issues exist --> @MaximilianSoerenPollak

OS images QNX8

Who: @jgetas
Discussion:
- Testing idea:
  - Use generic QEMU QNX IFS
  - Add custom test partition (instead of custom IFS)
- Requires new QNX SDP 8.0.3 tarball
- Should align with default SDP in C++ toolchain
Conclusion:
- Conflicts with parallel PR: Adding pkg_rules support rules_imagefs#4
- To be discussed offline by @jgetas and @nradakovic
- Goal: decide best approach or support both
- Update 2026-04-13: discussion ongoing

QNX update to 8.0.3

Who: —
Discussion:
- Who needs to approve?
Conclusion:
- Merge first
- @nradakovic asks Anton
- @AlexanderLanin addresses in CFT
- Update 2026-04-13:
  - addressed, feedback from CFT expected next Monday (which version do people need to have supported)
  - Release notes: https://support.qnx.com/developers/docs/relnotes8.0/com.qnx.doc.release_notes/topic/8.0.3_prod_release_notes/8.0.3_rn.html
  - Ideally we don't want to support both... but maybe we have to?
  - everything is prepared, reference integration can just try it (0.5.0 toolchain version)
- Update 2026-04-20:
  - Ok from tech lead & alignment round, if the change is indeed/still required. If optional, we should support 8.0.0 & 8.0.3!

GNU11 vs C11

Who: @nradakovic
Discussion:
- Use -std=gnu11 instead of -std=c11 on Linux bazel_cpp_toolchains#46
Conclusion:
- See comment in linked issue
- Addressed in CFT
- Update 2026-04-13: in discussion, e.g. one proposal is to split macros like cc_library into cc_library_gnu11 and cc_library_c11, and then have the user choose which one to use, or select via features / command line. To be involved: etas?, baselibs, communication. @nradakovic will prepare a decision proposal for next week.

Feature injection in toolchains

Who: @nradakovic
Discussion:
- Add external feature injection to GCC toolchain (like toolchains_llvm extra_known_features) bazel_cpp_toolchains#45
Conclusion:
- No awareness in infrastructure team
- Need documentation + DR for repository concept
- Update 2026-04-13: no real update. We'll request a proper decision record for score_cpp_policies (as a separate repo with feature injection), as no-one in infrastructure meeting understands the reasons for this approach. We see big problems in feature ordering.

NEW topics

Renovate Bot

Who: @AlexanderLanin
Discussion:
- renovate setup is rather trivial (with daily run, not as ad-hoc)
- Works best when pushed from one repo, instead of a workflow per repo
- Requires clean bazel mod graph execution (blocked by tooling 1.2.0)
- Example PRs: https://github.com/search?q=org%3Aeclipse-score+is%3Apr+is%3Aopen+label%3Arenovate+&type=pullrequests
Conclusion:
- no overlap with dependabot for now. We can discuss that in some weeks.
- keep renovatebot central, with no per-repo config for now - until people complain
- Note: PRs can just be closed if they are useless.
- Add to cicd-workflows repo with a daily/hourly run. Add to bazel_registry?

Test environment requirements for platform integration tests (system tests)

Who: @jgetas

ID	Text	comment
ENV1	The tester requires support for testing on Host Ubuntu x86_64.
ENV2	The tester requires support for testing on QEMU QNX8 aarch64.
ENV3	The tester requires support for testing on QEMU QNX8 x86_64.
ENV4	The tester requires support for testing on Hardware QNX8 aarch64.

OS1	The QEMU QNX8 OS image shall support using shared host directories using virtio-9p	<-- still under discussion!
OS2	The QEMU QNX8 OS image shall support mounting qnx6fs partitions if virtual disks are present by QEMU configuration.
OS3	The hardware QNX8 OS image shall support mounting qnx6fs partitions if qnx6fs partitions are present.
	Predefined mount points:
OS4	The QNX8 OS image shall support mounting qnx6fs partitions to mount point `/opt/score`.
OS5	The QNX8 OS image shall support mounting qnx6fs partitions to mount point `/opt/persist`.
OS6	The QNX8 OS image shall support mounting qnx6fs partitions to mount point `/opt/test`.
OS7	The QNX8 OS image shall support mounting qnx6fs partitions read-write by default.
OS8	The QNX8 OS image shall support mounting qnx6fs partitions read-only if configured.	maybe remount r/o if a file `/mount-read-only` is present on partition.
OS9	The OS image/test environment shall provide an option to reset the test environment state to a defined starting condition. Note: maybe re-formatting the qnx6fs partition.
OS10	The OS image shall support file transfer using ssh.
OS11	The OS image shall support extracting and creating tar.gz files.

FS1	The tester shall be able to use QEMU QNX8 OS IFS image.
FS3	The tester shall be able to create a qnx6fs file system and populate it with tester defined files.
FS4	The tester shall be able to create a FAT file system and populate it with tester defined files.
FS5	The tester shall be able to create a disk image out of partition images.

Assumption: no mac OS arm host support.

Conclusion:

Everyone welcome to provide feedback! Especially @dcalavrezo-qorix and @nradakovic
Timeframe till next Monday

Safety analysis process update

By: @ANegm-ETAS

adding a new extension to import xmls
Anegm/per fmea json #2789
adding new needs elements/options in the meta model
Update FMEA and DFA meta model docs-as-code#490
Create needs elements for FMEA and DFA faults docs-as-code#499

Discussion:

Source: rst is less convenient for live changes during a meeting compared to excel
Concern: Adding support for a 2nd format may be the start to support 20 different formats
Open: can we use the xml format for requirements? If not, why not? -> process
Re-address next time or reach out to @ANegm-ETAS
Is json a better format compared to xml? Can we re-use that? --> @MaximilianSoerenPollak

Tooling repo

The repo is basically unmaintained. Whats the current plan? pre-commit sync.

Discussion:

tools in tooling repo are basically obsolete -> @AlexanderLanin
python basics is deprecated maybe? -> @AlexanderLanin
pre-commit behaves differently locally and in CI -> short term: exclude those specific checks
discuss future tooling/pre-commit approach for score via slack in the next days, as its a little bit of a mess at the moment
template repo is probably out of date

Version mismatches: the versions from eclipse-score/devcontainer#115 are actually not used in most repositories

See also https://eclipse-score.github.io/score/main/design_decisions/DR-001-infra.html

Open: https://meetup.build/presentations/integrating-bazel-pre-commit.pdf

Backup

in case we have too much time *cough*

https://github.com/jvolkman/rules_pycross

1 reply

MaximilianSoerenPollak Apr 20, 2026
Collaborator

Quick info to Infra users. With Docs-As-Code 4.0+ 'versions' of requirements are now enabled and can be used. This is a 'silent' beta feature so far and we are not checking that you have declared versions in each requirement. This will become a non fatal warning and then mandatory in future releases.
How it works:

You can now link to versioned requirements via filter string (can also filter for any other attribute if wanted).

.. tool_req:
   id: tool_req_test1
   version: 1
   satisfies: stkh_req_test1[version=="1"]
   
.. stkh_req:
  id: stkh_req_test1
  version: 1

And if the version in the req that you specified is not the one in the filter string you get a sphinx warning message.

dcalavrezo-qorix · 2026-04-22T12:06:34Z

dcalavrezo-qorix
Apr 22, 2026
Collaborator

Weekly RUST 15-04-2026

14:00-15:00 CET

Participants

@PLeVasseur
@bharatGoswami8
@dcalavrezo-qorix
@jgetas
@satoshi58

Agenda

Hi community - I am new to Rust and have some stupid questions about end-customer use cases with respect to sharing binary code supported by S-CORE. I come from C/C++ development and we used to share dynamic libraries with customers.

Now, with Rust I read everywhere (but not on an official Rust site :thinking_face:) that there is no stable ABI, unless using the extern "C" ABI. Additionally, according to what I read I am not sure about how dynamic libraries are recommended in Rust. And I don't know what the S-CORE view on this is.

Therefore I have a set of questions/assumptions and I kindly ask you to comment.


Do we have any ABI requirements to public Rust APIs in our libraries in S-CORE that they must be "stable" - i.e. extern "C"?
If not, as there is no stable ABI in Rust: I assume the expectation for the end-customer is, that he/she builds his/her application and the S-CORE Rust libs always from source with his/her Rust toolchain. Re-using pre-built libraries has risks because nobody gives guarantees about the linker interfaces. Is this correct?
And we only support static linking with our Rust libraries, right?
I just found: https://docs.rs/abi_stable/latest/abi_stable/ - does anyone know what it is and does anyone use it?
(edited)

Minutes

we need an agreement on the set of flags ( compilation/linking )
sharing binary libraries in RUST is cumbersome at this point
atm we don't have a concrete use case ( but there is the risk this requirement will come in the future)
carbi ABI - attempt for a stable Rust ABI: Tracking Issue for the experimental crabi ABI rust-lang/rust#111423

0 replies

AlexanderLanin · 2026-04-27T09:53:28Z

AlexanderLanin
Apr 27, 2026
Collaborator Author

Weekly

2025-04-27
To join the meeting see calendar in #107

Participants

Agenda / Minutes

NEW points

devcontainer provides tools via bazel (@AlexanderLanin)

POC: feat: provide tools via bazel in addition to devcontainer devcontainer#116

planning resurrection

INF - Infrastructure Community (view)
limited scope: only things that people actually work on. No backlog. Backlog just piles up endlessly - no chance for now.

harden_runner

Examples: https://github.com/eclipse-score/bazel_registry/actions
Confrm with eclipse that this is required / makes sense -> @AlexanderLanin
Next: start rolling out to all workflows/jobs

OLD points, which are not closed yet

Upgrade to bazel 8.6 -> Backlog

OS images QNX8

Who: @jgetas
Discussion:
- Testing idea:
  - Use generic QEMU QNX IFS
  - Add custom test partition (instead of custom IFS)
- Requires new QNX SDP 8.0.3 tarball
- Should align with default SDP in C++ toolchain
Conclusion:
- Conflicts with parallel PR: Adding pkg_rules support rules_imagefs#4
- To be discussed offline by @jgetas and @nradakovic
- Goal: decide best approach or support both
- Update 2026-04-13: discussion ongoing
- Update 2026-04-20: 8.0.3 is ok from tech lead & alignment round, if the change is indeed/still required. If optional, we should support 8.0.0 & 8.0.3!
- Update 2026-04-27: @AlexanderLanin will organize a meeting with @jgetas, @nradakovic, someone from testing like Piotr, and ask Anton for someone from BMW.

GNU11 vs C11

done

Feature injection in toolchains

PR in review

Renovate Bot

no update

Test environment requirements for platform integration tests (system tests)

Who: @jgetas

ID	Text	comment
ENV1	The tester requires support for testing on Host Ubuntu x86_64.
ENV2	The tester requires support for testing on QEMU QNX8 aarch64.
ENV3	The tester requires support for testing on QEMU QNX8 x86_64.
ENV4	The tester requires support for testing on Hardware QNX8 aarch64.

OS1	The QEMU QNX8 OS image shall support using shared host directories using virtio-9p	<-- still under discussion!
OS2	The QEMU QNX8 OS image shall support mounting qnx6fs partitions if virtual disks are present by QEMU configuration.
OS3	The hardware QNX8 OS image shall support mounting qnx6fs partitions if qnx6fs partitions are present.
	Predefined mount points:
OS4	The QNX8 OS image shall support mounting qnx6fs partitions to mount point `/opt/score`.
OS5	The QNX8 OS image shall support mounting qnx6fs partitions to mount point `/opt/persist`.
OS6	The QNX8 OS image shall support mounting qnx6fs partitions to mount point `/opt/test`.
OS7	The QNX8 OS image shall support mounting qnx6fs partitions read-write by default.
OS8	The QNX8 OS image shall support mounting qnx6fs partitions read-only if configured.	maybe remount r/o if a file `/mount-read-only` is present on partition.
OS9	The OS image/test environment shall provide an option to reset the test environment state to a defined starting condition. Note: maybe re-formatting the qnx6fs partition.
OS10	The OS image shall support file transfer using ssh.
OS11	The OS image shall support extracting and creating tar.gz files.

FS1	The tester shall be able to use QEMU QNX8 OS IFS image.
FS3	The tester shall be able to create a qnx6fs file system and populate it with tester defined files.
FS4	The tester shall be able to create a FAT file system and populate it with tester defined files.
FS5	The tester shall be able to create a disk image out of partition images.

Assumption: no mac OS arm host support.

Conclusion:

Everyone welcome to provide feedback! Especially @dcalavrezo-qorix and @nradakovic
Timeframe till next Monday

Safety analysis process update

no update

Tooling repo

The repo is basically unmaintained. Whats the current plan? pre-commit sync.

Discussion:

tools in tooling repo are basically obsolete -> @AlexanderLanin
python basics is deprecated maybe? -> @AlexanderLanin
next: pre-commit behaves differently locally and in CI -> short term: exclude those specific checks
next: replace cr_checker with new approach as discussed in #infrastructure chat. Note: seems like reuse cannot be wrapped in bazel.
discuss future tooling/pre-commit approach for score via slack in the next days, as its a little bit of a mess at the moment
template repo is probably out of date

Version mismatches: the versions from eclipse-score/devcontainer#115 are actually not used in most repositories

See also https://eclipse-score.github.io/score/main/design_decisions/DR-001-infra.html

Open: https://meetup.build/presentations/integrating-bazel-pre-commit.pdf

FMEA

json can be used for needimport, see comment. This will allow stanrad importer and it will keep using validations. We still don't see a reason to not use rst/md files for FMEA.

ubCode support

Demo planned in process meeting on Thursday
TODO: document ubCode to docs-as-code relationship (GUI-nice-to-have addition for usability, ground of truth remains pure docs-as-code as-is)
PR: Feat/generate ubproject and schema validation docs-as-code#394

Centralized metrics (@FScholPer)

PR: feat: traceability metrics docs-as-code#484 (in progress)
Standard metrics and standard dashboards, so they measure and show the same stuff
Include check with thresholds like 20%...
Global overview in reference integration

Info: rust problem in communication

1. linking order was incorrect, @nradakovic will fix it
1. acl library is pulled in pre-compiled, which was compiled with different compiler flags (e.g. fpeg)

Not discussed

in case we have too much time *cough*

https://github.com/jvolkman/rules_pycross

7 replies

MaximilianSoerenPollak Apr 27, 2026
Collaborator

On every IDE or just VsCode?

arnoox Apr 27, 2026

vs code for now, via the ubcode extension. There are plans to make this more general but I need to check what exactly is in the pipeline...

chrisjsewell Apr 27, 2026

On every IDE or just VsCode?

What does "every" IDE mean? 😅

The core of the VS Code extension is IDE agnostic; An LSP, MCP and core compile engine.
Then the CLI is also obviously IDE agnostic

Things like Tree/Web views are specific to the VS Code API.

There is also some potential/speculative future plans to be able to "launch" some web views from the CLI directly, and thus be dtached from any specific IDE API

MaximilianSoerenPollak Apr 27, 2026
Collaborator

Well 'every' is a stretch :D and not feasable. Let me re-word it.
Does it only work via VsCode extension or does it use some open way like language servers etc. that 'in theory' it could be ported to other places?

FScholPer Apr 27, 2026
Collaborator

I would also throw eclipse-score/docs-as-code#484 in the round as it goes in the same direction of eclipse-score/docs-as-code#394. We should avoid double work. I think for the harness engineering we need a dedicated session (or AI community?!)

dcalavrezo-qorix · 2026-04-29T11:56:53Z

dcalavrezo-qorix
Apr 29, 2026
Collaborator

Weekly `Rust` 29-04-2026

14:00-15:00 CET

Participants

@PLeVasseur
@bharatGoswami8
@dcalavrezo-qorix
@FScholPer

Agenda

PRs for MIRI integration: miri: integrated MIRI kyron#79 miri: integrate Bazel Miri tests in baselibs_rust baselibs_rust#91
Bug: rust_binary linking fails for linux_aarch64_score_gcc_12_2_0_posix with non-PIC and missing outline atomic symbols toolchains_rust#27
low engagement in the community

0 replies

nradakovic · 2026-05-04T14:05:55Z

nradakovic
May 4, 2026
Collaborator

Weekly

Date: 4th of May, 2026.
Participants:

Facilitator: @nradakovic

Traceability Coverage Checker & CI Reporting Mode

Introduced the traceability coverage checker along with the CI reporting mode.
Reviewed the following pull requests:
Discussion points:
- Alignment of coverage expectations across repositories.
- Integration of reporting into CI pipelines.

Dependency Management Strategy

Renovate Bot
- Proposal to remove it from the workflow.
- Decision: Pending further confirmation.
Dependabot
- Decision: Keep as-is.
- Responsibility:
  - Module maintainers are responsible for final validation and merging of dependency updates.
- Module Template Repository
  - Open questions:
    - Who is the official owner/maintainer/code owner?
    - How will long-term support be handled?
Action Items:
- Clarify ownership and assign code owners.
- Define maintenance and support strategy for the repository.

ACL Toolchain Support

Reviewed progress on ACL toolchain support.
Relevant PR:
- GNU/Linux toolchain: Include ACL support in toolchain toolchains_gcc_packages#11
Discussion points:
- Compatibility and integration considerations.
- Next steps for validation and rollout.
Action Items:
- Complete testing of GNU/Linux toolchain integration.
- Provide support for other platforms/toolchains.
- Document setup and usage guidelines.

1 reply

AlexanderLanin May 6, 2026
Collaborator Author

@nradakovic why no renovate? I just finished the PR 🗡️
eclipse-score/cicd-workflows#104

dcalavrezo-qorix · 2026-05-06T12:15:23Z

dcalavrezo-qorix
May 6, 2026
Collaborator

Weekly `Rust` 06-05-2026

14:00-15:00 CET

Participants

@PLeVasseur
@bharatGoswami8
@dcalavrezo-qorix

Agenda

PRs have not been reviewed
https://public-docs.ferrocene.dev/main/certification/core/index.html

0 replies

AlexanderLanin · 2026-05-11T07:17:37Z

AlexanderLanin
May 11, 2026
Collaborator Author

Weekly

Date: 11th of May, 2026.
Participants:

Facilitator: @AlexanderLanin

Renovate

Last meeting said to not use it, so lets have a look again
eclipse-score/cicd-workflows#104

Note: renovate updates score -> score dependencies, everything else remains in dependabot (for now)

tools via bazel

Solution for running trivial tools uniformly via devcontainer/bazel is ready:
eclipse-score/docs-as-code#511

runner disk space

S-CORE runners have 90GB free disk space. Forks as well. Copies/mirros have 17GB. So S-CORE has/will become "not copyable", as workflows in copies will run out of disk space.

Homework: is that a problem for anyone here?

@AlexanderLanin to address that to tech leads.

LLM/Agent-Coding

Different Frameworks exist, e.g.:

@FScholPer will set up an interest group within S-CORE, as few users/experts are in the #infrastructure meeting.

0 replies

dcalavrezo-qorix · 2026-05-13T12:26:13Z

dcalavrezo-qorix
May 13, 2026
Collaborator

Weekly `Rust` 13-05-2026

14:00-15:00 CET

Participants

@PLeVasseur
@bharatGoswami8
@dcalavrezo-qorix
@darkwisebear

Agenda

PRs have not been reviewed
https://public-docs.ferrocene.dev/main/certification/core/index.html
upstream Miri introduction into official rules_rust

Minutes

rules_rs can be an alternative


Miri is now part of rules_rs

https://github.com/hermeticbuild/rules_rs/releases/tag/v0.0.78

if u want to raise it with score
https://registry.bazel.build/docs/rules_rs#rs-experimental-miri-miri_test-bzl

registry.bazel.build

[Bazel Central Registry](https://registry.bazel.build/docs/rules_rs#rs-experimental-miri-miri_test-bzl)

0 replies

odra · 2026-05-13T14:57:42Z

odra
May 13, 2026
Collaborator

Weekly

Date: 18th of May, 2026.

Participants:

Facilitator: @AlexanderLanin

bazel_cpp_toolchains and gcc versions

Requester: @odra
Topic: How to support different gcc versions (12 and 14) in bazel_cpp_toolchains?

toolchains, platforms and external development dependencies

Requester: @odra
Topic: Some modules (baselibs and cryto) are building parts of OpenSSL and/or LibACL from source, which can be reasonable for development. What happens if a supported S-CORE platform provides these same libraries?

0 replies

Eclipse S-CORE

Meeting Minutes #236

Uh oh!

Uh oh!

AlexanderLanin Jan 28, 2025 Collaborator

Replies: 121 comments · 44 replies

Uh oh!

Uh oh!

AlexanderLanin Jan 28, 2025 Collaborator Author

Kick-Off

Uh oh!

Uh oh!

AlexanderLanin Jan 28, 2025 Collaborator Author

Daily

Uh oh!

Uh oh!

AlexanderLanin Jan 28, 2025 Collaborator Author

Daily

Uh oh!

Uh oh!

AlexanderLanin Jan 31, 2025 Collaborator Author

Daily

Uh oh!

MaximilianSoerenPollak Feb 3, 2025 Collaborator

Daily

Uh oh!

Uh oh!

AlexanderLanin Feb 5, 2025 Collaborator Author

Daily

Uh oh!

Uh oh!

AlexanderLanin Feb 7, 2025 Collaborator Author

Daily

Uh oh!

Uh oh!

AlexanderLanin Feb 7, 2025 Collaborator Author

Daily

Uh oh!

Uh oh!

AlexanderLanin Feb 10, 2025 Collaborator Author

Daily

Uh oh!

Uh oh!

AlexanderLanin Feb 12, 2025 Collaborator Author

Daily

Uh oh!

Uh oh!

AlexanderLanin Feb 12, 2025 Collaborator Author

Python tooling in bazel deep dive

Uh oh!

hoe-jo Feb 14, 2025 Collaborator

Python tooling in bazel deep dive follow up

Uh oh!

Uh oh!

AlexanderLanin Feb 17, 2025 Collaborator Author

Daily

Uh oh!

Uh oh!

AlexanderLanin Feb 17, 2025 Collaborator Author

How to reuse tools across repositories?

Uh oh!

Uh oh!

AlexanderLanin Feb 17, 2025 Collaborator Author

Daily

Uh oh!

Uh oh!

AlexanderLanin
Jan 28, 2025
Collaborator

Replies: 121 comments 44 replies

AlexanderLanin
Jan 28, 2025
Collaborator Author

AlexanderLanin
Jan 28, 2025
Collaborator Author

AlexanderLanin
Jan 28, 2025
Collaborator Author

AlexanderLanin
Jan 31, 2025
Collaborator Author

MaximilianSoerenPollak
Feb 3, 2025
Collaborator

AlexanderLanin
Feb 5, 2025
Collaborator Author

AlexanderLanin
Feb 7, 2025
Collaborator Author

AlexanderLanin
Feb 7, 2025
Collaborator Author

AlexanderLanin
Feb 10, 2025
Collaborator Author

AlexanderLanin
Feb 12, 2025
Collaborator Author

AlexanderLanin
Feb 12, 2025
Collaborator Author

hoe-jo
Feb 14, 2025
Collaborator

AlexanderLanin
Feb 17, 2025
Collaborator Author

AlexanderLanin
Feb 17, 2025
Collaborator Author

AlexanderLanin
Feb 17, 2025
Collaborator Author