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: Infrastructure
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

dcalavrezo-qorix · 2025-10-13T09:43:07Z

dcalavrezo-qorix
Oct 13, 2025
Collaborator

Weekly

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

Participants

@dcalavrezo-qorix
@ubmarco
@denis Akhmerov
@odra
@walid-salhi
@AyJebri
@nicu1989
@tmewett
@istilkerich
@nradakovic
@nick-hildebrant-etas

Agenda / Minutes

clarifications to understand what dev_dependency means & how to use it.
QNX toolchain: flag -std=gnu++17 is set by default.
QEMU image moving out of reference_integration repo
Next steps to continue on static / dynamic code analsysis

0 replies

dcalavrezo-qorix · 2025-10-20T12:34:44Z

dcalavrezo-qorix
Oct 20, 2025
Collaborator

Weekly

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

Participants

@dcalavrezo-qorix
@ubmarco
@denis Akhmerov
@walid-salhi
@AyJebri
@nicu1989
@nick-hildebrant-etas
@sameer6989
@odra
@i0b
@FScholPer
@kgraeper

Agenda / Minutes

Running test for QNX8 /aarch64 : https://github.com/eclipse-score/persistency/actions/runs/18650586061
Groom Unit-tests execution on host with GCC toolchain #1326
Compiler flags & static code analysis

0 replies

dcalavrezo-qorix · 2025-10-22T12:24:42Z

dcalavrezo-qorix
Oct 22, 2025
Collaborator

RUST Meeting 22-10-2025

Participants:

Topics Discussed

toolchains_rust has been updated with the config for both host (x86_64) and target ( qnx8/ aarch64) - with restrictions ( still -but those are from from toolchains_qnx )
rustc 1.91. ( beta) will be released on the 30th of Oct - we need to test it and check rules_rust rules from Bazel as well, whether it will need an update too
arch workshop (~ 2 weeks) - safety qualified RUST: we need to figure out what is needed in our dev. process to support this ( tools, build)
- there is no official date yet
- we need proactively define action items in preparation for this - target should be S-CORE 1.0 milestone
- https://github.com/rustfoundation/safety-critical-rust-coding-guidelines
- https://github.com/rustfoundation/safety-critical-rust-consortium
- https://coding-guidelines.arewesafetycriticalyet.org/
- Action Item @darkwisebear : let's bring this up on the common S-core channel - have a separate meeting ( east-coast time friendly) in which we can define the necessary GH issues and next steps @masc2023
logging topic: use the log crate from RUST - [Story] Rust logging MVP for S-Core #1896
- is the baselib req. a deal-breaker? @darkwisebear
- do we go with the temp solution ?
- can we find another logging framework that suits our req/needs? do we have to write our own?
- check if it is possible to import the crate using the crate_universe in baselibs with Bazel ? @4og
- the log crate isn't actually modified within the baselibs

1 reply

darkwisebear Oct 23, 2025
Collaborator

I checked with Andrey from the baselibs team, and the requirement is to not have deps to S-Core repos. It is fine, though, to depend on external sources. So my suggestion is as follows:

Add the log crate to https://github.com/eclipse-score/score-crates.
Import score-crates to baselibs (yes, this is technically an S-Core crate, but it's just a proxy module).
Create an alias from baselibs to the log crate. This alias can then later be changed to point to whatever log frontend we will use in the future.

AlexanderLanin · 2025-10-27T12:33:10Z

AlexanderLanin
Oct 27, 2025
Collaborator Author

Weekly

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

Participants

Agenda / Minutes

Module naming:
- Allowed names: score_[a-z_]+
- Exact naming by module owners. not too long :)
- Trigger: Add logging to the registry bazel_registry#134
- create issue to verify that regex for (new) modules -> @AlexanderLanin
  (for now in bazel_registry)
How to run common checks in all the repositories, like the one just mentioned
-> write decision record, e.g. common on_pr workflow in cicd-workflows --> @AlexanderLanin, @nick-hildebrant-etas
Decision Record 004 #1930
--> separate meeting. @AlexanderLanin, @ubmarco, @a-zw
docs-as-code declaration proposal by @ubmarco
--> same meeting
docs-as-code has lots of open (unwritten) DRs
--> same meeting
Reminder: tool + config wrapper POC in https://github.com/etas-contrib/score_score-pyright, but unfortunately no progress in the last weeks
current state of reference_integration: baselibs, communication, persistency, logging can be compiled from reference_integration (locally). Currently local patches to communication and baselibs are necessary (@nradakovic will check for communication contact).
v0.5 is planned for 11th of November. That's rather soon 😆
communication unit tests require bazels linux-sandbox and are not compatible with default Ubuntu 24 (except specific setup). And not with devcontainers, unless they are run in privileged mode. See Enable linux-sandbox also for Ubuntu 24.04 devcontainer#40. Impact not 100% clear, it's local testing that is mostly affected now, as CI is currently not using devcontainer.

0 replies

AlexanderLanin · 2025-11-03T14:43:11Z

AlexanderLanin
Nov 3, 2025
Collaborator Author

Weekly

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

Participants

Agenda / Minutes

state of arm builds? specifically with qnx?

orchestration repo (rust) builds for arm qemu
- with some local patches for iceoryx2
- this includes some c++ code as well (dependencies)
other modules unknown

reference_integration current state

Ideally we get add basic bazel files reference_integration#10 merged today, which adds ~5 modules to reference_integration

reference_integration, qnx_qemu, itf -> what depends on what?

does itf run qnx, or does reference_integration run qnx and itf? --> sync with testing community
integration tests are currently planned to be within reference_integration, but that does no longer find alignment. --> rediscuss location of integration tests --> @AlexanderLanin will invite: testing community, @nradakovic, @kgraeper, Vinoth
proper location for qnx_qemu? remove module.bazel file from qemu? --> sync with testing community

0.5 release tasks: https://github.com/orgs/eclipse-score/discussions/434#discussioncomment-14857236

see other ticket

QNX SDP is missing packages

There was a request to add additional packages within the SDP archive.
No response yet. @dcalavrezo-qorix to ask @antonkri to ping QNX guys.

score-tools

current score-tools implementation: https://github.com/eclipse-score/tools/tree/dev
bazel integration not started

devcontainer: building for qnx does not work out of the box

e.g. license file from local location / local server, environment variables from local machine
devcontainers use vscode user, which is incompatible with typical qnx licenses which expect a certain username (local user)
--> enhance readme or devcontainer
@dcalavrezo-qorix to create a new issue in devcontainer repository

bazel_registry_ui not up to date

issue: Auto Update bazel_registry_ui#7
blocker: our token is still not working. @AlexanderLanin to ping helpdesk again.

CODEOWNERS

We currently cannot use GitHub Teams for CODEOWNERS (as they don't have write access to repos)
Proposal was to use an action to ensure reviews, but it doesn't seem ideal.
Demand: one reviewer per team (e.g. feature team + safety experts) is not handled by that action
--> find/write a fitting github action for reviews
by the way: bazel_registry now has a CODEOWNERS file

0 replies

AlexanderLanin · 2025-11-03T20:57:38Z

AlexanderLanin
Nov 3, 2025
Collaborator Author

Weekly

2025-11-10
To join the meeting see calendar in #107

Participants

@AlexanderLanin
@AyJebri
@dcalavrezo-qorix
J Zimmermann
@kgraeper
@odra
@nick-hildebrant-etas
@nicu1989
@opajonk
@a-zw
@ubmarco
@jgetas
@evinoth
@tobiwan3
vinoth_etas
@nradakovic

Agenda / Minutes

reference_integration versioning

Proposal:

Contrary to all other repos, reference_integration will follow "marketing naming"
e.g. it will contain v0.5.0-alpha tag, regardless of SemVer meaning.
--> accepted (no better ideas)

docs-as-code 2.0.0 release

breaking change
@a-zw, @guejan, @AlexanderLanin will update score, process_description, reference_integration.
Any other repo - with more than a onepager? --> no, just those 3.

reusable build workflow

We need to setup docker, secrets etc for build, especially for qnx builds. Sounds like something reusable?

Example by @nradakovic

jobs:
    build_host_x86-64_linux:
        ...
        uses:  /path/to/cicd_repo/docker-build.yml
        env: # optional
            SCORE_QNX_LICENSE: ${{ secrets.SCORE_QNX_LICENSE }}
            SCORE_QNX_USER: ${{ secrets.SCORE_QNX_USER }}
            SCORE_QNX_PASSWORD: ${{ secrets.SCORE_QNX_PASSWORD }}
        with:
            output_user_cache: "path/to/cache"
            command: "build" or "test" # or whatever we want to support
            targets:
              - "//path/to/target:1"
              - "//path/to/target:2"
            configs:
              - "bl_x86-64_linux"
            options: # for flags
              - "-//path/to/flag"
            exclude_targets:
              - "//path/to/exclude/target:1"

makes sense :-)
We need @antonkri to clarify / properly set up the secrets -> @AlexanderLanin will trigger
let's have a detailed discussion: @nradakovic @dcalavrezo-qorix @nick-hildebrant-etas --> @AlexanderLanin to create some issue/discussion
Hint: consider max n parallel qnx builds in the entire system

request: cross compiling support

We have bazel_platforms, toolchains, "target" etc... how does it work? Where is it documented? by J. Gittinger.
Adopt bazel_platforms as the single source of truth for build platforms #1879 (comment)
--> no real progress or documentation. We need @nradakovic to lead the cross repo toolchain discussion & setup.
e.g. gcc setup
See also https://eclipse-score.github.io/score/main/requirements/platform_assumptions
See also Change Request: Tiered SW Platform (Operating System) Integration Process for Eclipse S-CORE #1740
@AlexanderLanin to organize follow-up / next steps

gcc toolchain compiler flags

eclipse-score/toolchains_gcc#22

PR discussed
Do not use anything compiler/platform specific in bazel MODULE or BUILD files

0 replies

AlexanderLanin · 2025-11-17T12:14:00Z

AlexanderLanin
Nov 17, 2025
Collaborator Author

Weekly

2025-11-17
To join the meeting see calendar in #107

Participants

Agenda / Minutes

Lots of time went into releasing 0.5.0-alpha
Now lots of cleanup will be required in reference_integration.
We need to start setting up os_images.
- Potentially starting with qnx_qemu, but keep the others in mind. Rather different approaches!
- --> V Eswaran
Currently not all main branches in all repositories are buildable (together)
- do not attempt to update baselibs and communication. Stick to 0.5.0-alpha release.
- @AlexanderLanin to revive Tier-definition for modules regarding CI support
Reminder: https://github.com/orgs/eclipse-score/discussions/1968 --> @AlexanderLanin will invite: testing community, @nradakovic, @kgraeper, Vinoth, @opajonk

0 replies

dcalavrezo-qorix · 2025-11-24T14:03:35Z

dcalavrezo-qorix
Nov 24, 2025
Collaborator

Weekly

2025-11-24
To join the meeting see calendar in #107

Participants

Agenda / Minutes

unified toolchain repository structure ( for CPP code)
docs-as-code - integrate into modules - DR (https://eclipse-score.github.io/score/pr-2089/design_decisions/DR-005-infra.html)
baselibs cross-compilation for EBCL issues
toolchains_qnx PR qnx: do not rely on /proc/self toolchains_qnx#35 from @pawelrutkaq
- PoC how to remove /proc/self paths so build works in cases where you don't invoke CC from bazel sandbox root
- @nradakovic solution is not really reliable/ durable - looking for a better option, we can approve it with some caveats
@opajonk devcontainer updates: arm64/amd64 builders + gdb and gh command client => we should release it as 1.0.0
we should conduct some cleaning up of our repos ( for 0.5 release there were many "temporary" solutions) considering that we need a more consolidated approach for release 1.0 ( @AlexanderLanin we should define a set of immediate actions in this direction).

0 replies

darkwisebear · 2025-11-26T13:15:31Z

darkwisebear
Nov 26, 2025
Collaborator

Weekly

14:00-15:00 CET

Participants

@PLeVasseur
@FScholPer
@dcalavrezo-qorix
@darkwisebear
@pawelrutkaq

Agenda

Update on safety qualification efforts
Introducing Iceoryx dependencies

Minutes

Safety qualification efforts

@pawelrutkaq libcorecertification: Opened PR rust: add libcore to certification doc #2249: Describing the gap
@pawelrutkaq scanned the code for libcore usage. Ferrocene has a compiler switch to do that automated.
@FScholPer will find documentation about the terms of usage for Ferrocene
Misra will soon start to talk about Rust
Request: Have a look at https://coding-guidelines.arewesafetycriticalyet.org/, https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/blob/main/CONTRIBUTING.md
Todo: Check whether rules_rust need to be adapted to Ferrocene. @pawelrutkaq will add a ticket to the board if needed
Idea: have a tailoring guideline in the SCRC to help people to apply the SCRC CGs to their project

Introducing Iceoryx dependencies

deps: Add orchestrator deps score-crates#16 will be merged. As soon as methods and "signal" support is in score/com, we migrate away from Iceoryx.

0 replies

dcalavrezo-qorix · 2025-12-03T13:20:34Z

dcalavrezo-qorix
Dec 3, 2025
Collaborator

Weekly RUST 03-12-2025

14:00-15:00 CET

Participants

@PLeVasseur
@FScholPer
@dcalavrezo-qorix
@pawelrutkaq
@odra
@rafael - ETAS
@darkwisebear
@sophokles73

Agenda

go over our Board https://github.com/orgs/eclipse-score/discussions/236

Minutes

static code analysis using clippy
- set of rules will come from the safety consortium ( based on that we will decide whether clippy suffices or we need to create an extension or even rely on 3rd party tools)
- add the clippy checks to all Rust based repos from the alfa 0.5 release (@dcalavrezo-qorix )
- https://github.com/rustfoundation/safety-critical-rust-coding-guidelines ( end of March - some degree of completeness )
QNX 8 support on Rust ( pthread signature issue - Allow Neutrino QNX SDK dependent values for PTHREAD_MUTEX_INITIALIZER rust-lang/libc#4192)
groom the old RUST tickets Tooling: Enable rust development #80 and close what is relevant ( or at least comment) @pawelrutkaq
- Epic: (Initial) Coding Guidelines Rust #592

Safety qualification efforts

1 reply

PLeVasseur Dec 7, 2025
Collaborator

Hey there, this is @PLeVasseur 👋 following up on steps to move nto-qnx from Tier 3 to Tier 2.

I reached out to the target maintainers, two of whom I know somewhat, on the Rust Zulip to hear their thoughts on challenges / concerns.

I read the Tier 2 target policy. Seems most of these should be okay, but the target maintainers will know better.

I also reached out to an Rust Project Infrastructure Team member I know to ask for next steps which were: draft a post and post it publicly in the right spot (#t-infra). I've drafted the post, but am waiting to hear back from the target maintainers before proceeding.

AlexanderLanin · 2025-12-08T10:25:42Z

AlexanderLanin
Dec 8, 2025
Collaborator Author

Weekly

2025-12-08
To join the meeting see calendar in #107
(Zoom meeting broken, switched to Teams via slack channel)

Participants

@AlexanderLanin
@opajonk
@a-zw
@dcalavrezo-qorix
@nicu1989
@ubmarco
@evinoth1206
@AyJebri

Agenda / Minutes

Info: interesting topics in progress:
- common c++ toolchain
- new bazel_registry rewrite automation/scripts bazel_registry#190, e.g. version info can be removed from MODULE.bazel files
- on_pr workflow for modules to trigger reference_integration via prepare script for integration feedback on PR #1852
- monorepo view (gita) onto score via reference_integration
- rust SCA
- os_images stuck due to old QNX --> keep going and call it "community supported" !?
Info: Release "0.5 beta" on 18th December.
Request: Can someone review github secrets from forks #1983?
docs: For full docu build we need an score_platform release -> @AlexanderLanin & @dcalavrezo-qorix
docs: versioned links in concept phase, in discussion with process_description experts. Links via docs: Add versioned links docs-as-code#314, Versioned links for tracking suspicious links useblocks/sphinx-needs#1352, Tech concept for edge properties useblocks/sphinx-needs#1481
docs: sphinx-needs-6 metamodel validation as automatic translation from current metamodel.yml (for now anyway) in progress.

1 reply

AlexanderLanin Dec 8, 2025
Collaborator Author

Forgot to mentioned another in progress topic:

dash-license-scan as POC to replace calling tools via bazel. See poc for entire flow dash-license-scan#3

dcalavrezo-qorix · 2025-12-10T13:15:13Z

dcalavrezo-qorix
Dec 10, 2025
Collaborator

Weekly RUST 10-12-2025

14:00-15:00 CET

Participants

@PLeVasseur
@dcalavrezo-qorix
@darkwisebear
@FScholPer
@chulhee Lee
@pawelrutkaq

Agenda

go over our Board https://github.com/orgs/eclipse-score/discussions/236

Minutes

clippy was added to persistency and refrence_integration (PR) - the rest to follow ( hopefully together with rustfmt)
update from @PLeVasseur https://github.com/orgs/eclipse-score/discussions/236#discussioncomment-15188240
PRs from rules_rust won't be merged any time soon
Find out what tooling can be used for branch coverage #2013 (comment)
- https://public-docs.ferrocene.dev/main/coverage/index.html
consider switching to the ferrocene compiler within a POC repo using bazel toolchains - let's go with persistency ( @infra team)
agreement on proposal from Find out what tooling can be used for branch coverage #2013 (blanket)
review needed: formatting: score configuration score_rust_policies#4

0 replies

AlexanderLanin · 2025-12-15T10:47:38Z

AlexanderLanin
Dec 15, 2025
Collaborator Author

Weekly

2025-12-15
To join the meeting see calendar in #107

Participants

@dcalavrezo-qorix
@nicu1989
@ubmarco
@nradakovic
@odra
@jgetas
@MayurMysoreNagaraja

Agenda / Minutes

QNX license issue?
- escalation needed - some PRs are opened for more than 10 days
Limit workflows to forks? (Collect idea, schedule follow up?) -> https://sdvworkinggroup.slack.com/archives/C0894QGRZDM/p1765795691165719
Update from last weeks topics:
- common c++ toolchain
  - via https://github.com/eclipse-score/bazel_cpp_toolchains
- new bazel_registry rewrite automation/scripts bazel_registry#190, e.g. version info can be removed from MODULE.bazel files
  - via rewrite scripts bazel_registry#188
- on_pr workflow for modules to trigger reference_integration via prepare script for integration feedback on PR #1852
  - delayed
- monorepo view (gita) onto score via reference_integration
  - progress?
- rust SCA
  - progress?
- os_images stuck due to old QNX --> keep going and call it "community supported" !?
  - progress?
  - AP: reping QNX folks
- dash-license-scan as POC to replace calling tools via bazel. See poc for entire flow dash-license-scan#3
  - blocked due to .eclipsefdn still stuck
Info: Release "0.5 beta" on 18th December.
On QORIX side, we have consciously decided not to continue the project unchanged under the current setup. Given the market and budget conditions, this would neither be strategically sound nor economically responsible. Instead of tying up resources and creating expectations we cannot reliably meet, we are executing a controlled ramp-down. This decision is not an exit from the topics and not a reflection of the quality. It is a deliberate focus to create the conditions to rebuild with clear priorities, a stable setup and reliable commitment
AP: evaluate the integration of the AutoSD toolchain into our common / aggregated toolchain

0 replies

dcalavrezo-qorix · 2025-12-17T13:06:19Z

dcalavrezo-qorix
Dec 17, 2025
Collaborator

Weekly RUST 17-12-2025

14:00-15:00 CET

Participants

@dcalavrezo-qorix
@darkwisebear
@bharatGoswami8
@pawelrutkaq

Agenda

clippy: added clippy support communication#117 - was rejected
ferrocene builder
QNX builds in S-Core

Minutes

we shall clarify the rules_rust vs Aspect till the end of the week and proceed with the agreed approach
ferrocene builder not working atm in CI
QNX 8 SDP available in S-CORE is outdated ( virtio packages are also missing - no QEMU support for aarch64, no mkifs support for real hw targets)
update on the safety rust guidelines: https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/milestone/1

0 replies

anmittag · 2025-12-29T16:41:10Z

anmittag
Dec 29, 2025
Collaborator

2026-01-??

Please review your open issues. Close them, adapt the description or delete them https://github.com/eclipse-score/score/issues?q=is%3Aissue%20state%3Aopen%20label%3Acommunity%3Ainfrastructure

0 replies

Eclipse S-CORE

Meeting Minutes #236

Uh oh!

Uh oh!

AlexanderLanin Jan 28, 2025 Collaborator

Replies: 85 comments · 10 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: 85 comments 10 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