QNX 2026-01-28 15:00 CET

[AlexanderLanin]

QNX 2026-01-28 15:00 CET

Link to join the meeting is in #score-infrastructure slack channel

⚠️ Beware parallel edits of this discussion.

We’re planning a meeting with QNX on short notice (~24h). Apologies for the rush—please share any topics you’d like to discuss.

• How to update QNX Tarball with new features
  • Process for tarball update (contact person/update every 2 weeks/S-Core ticket)
  • Current request: Update & Extension needed for efficient image generation:
    • QNX® SDP 8.0.3 (or later) with following additional QNX SDP packages integrated:
    • QNX® SDP 8.0 Networking - io-sock Virtio Drivers
    • QNX® SDP 8.0 Virtualization Drivers (Block)
    • QNX® SDP 8.0 Virtualization Drivers (Startup)
    • Raspberry pi 5 BSP support
• Publishing QNX-based S-Core images on GitHub as part of the S-Core releases (do we have a problem with „High risk application“ definition)
• Do we need a technical user license in CI (currently running with private Anton’s license)

---

Meeting Minutes

Participants

@AlexanderLanin (ETAS)
A. Gryc (QNX)
C. Sinnot (QNX)
@dcalavrezo-qorix (Qorix)
@jgetas (ETAS)
J Hanam (QNX)
@antonkri (BMW)
@odra (RedHat)
@FScholPer (Mercedes Benz)
@evinoth1206 (ETAS)

Minutes

• QNX wants to provide a regulary updated tarball (first one within 1-2 weeks)
  How to update QNX Tarball with new features

  • Requested packages can be included
  • Cadence: no internal monthly release, so monthly tarball update would not make much sense
  • Contact on QNX side is J Hanam.
  • First tarball as-as, later potential optimizations as in next point

• Storing tarball / image in S-CORE for testing, delivery and demos
  Publishing QNX-based S-Core images on GitHub as part of the S-Core releases (do we have a problem with „High risk application“ definition)

  • QNX needs to clarify internally

• Future optimizations

  • QNX will support score to generate the tarball ourselves via QNX Everywhere
    • Potentially by providing the recipe to individuals
  • S-CORE demand is probably: one size fits all, for a reference build
  • Outside S-CORE individual parties have their own QNX contracts as required for customized builds

• BSPSs:

  • Pi5 and qemu are available from software center, either source or prebuild.

• Technical User:
  Do we need a technical user license in CI (currently running with private Anton’s license)

  • QNX needs to clarify internally. Maybe based on an eclipse email address? Any other ideas by score?

• Follow-Up meeting in ~2 weeks

[AlexanderLanin]

QNX 2026-02-11 15:00 CET

Participants

@AlexanderLanin (ETAS)
A. Gryc (QNX)
C. Sinnot (QNX)
@jgetas (ETAS)
J Hanam (QNX)
@antonkri (BMW)
@pawelrutkaq
@FScholPer (Mercedes Benz)

Minutes

• QNX can provide opt-in multi user non-commercial license for "high risk" development, in addition to the current QNX non-commercial everywhere license which does not allow development of "high risk" applications. To be signed by participating companies as they see it as a requirement. Basically the new license allows "high risk" development, without any guarantees.
  • Note: we are not lawyers. The actual license text applies.
  • A. Gryc (QNX) will follow up with next formal steps.
  • QNX needs to know the S-CORE legal entity name. @FScholPer will provide it to angryc@qnx.com
• Prebuild QNX image can be provided by S-CORE, but must include a very clear statement that a QNX license is required, e.g. the everywhere license or this new license type.
  • After the license above is established, we can align on a concrete solution e.g. README text.
  • Note: for now the tarball still cannot be stored in S-CORE and must be downloaded every time on demand.
    • A. Gryc (QNX) to follow up on public hosting possibilities of the tarball.
    • @AlexanderLanin to follow up on private hosting possibilities in S-CORE (accessible to all committers + CICD)
• tarball
  • QNX: new tarball almost ready
  • S-CORE feedback: new tarball has super slow download (30 minutes, 10.000% slower). QNX to follow up.
  • S-CORE feedback: current/old tarball download fails very very often. This script is used for download. QNX will follow up. Example failure. Used core to trigger the error. S-CORE contact i.e. @pawelrutkaq (reach via Slack)
• Do we need a technical user license in CI (currently running with private Anton’s license) --> @FScholPer will clarify with Eclipse Foundation.
• We'll try Slack chat for faster iterations: Initial subscription, and then direct link to the chat: #score-qnx

Follow-Up

Bi-Weekly Wednesday 15:00 CEST (UTC+1) - S-CORE & QNX Meeting

• iCal (Outlook import)
• Web View
• Google Calendar
• Direct Zoom Link: https://eclipse.zoom.us/j/85906130055?pwd=G44Cg6MSbtrL28ThxBI0VOFRay6aQe.1

[JohnAtQNX]

Howdy! I think we have worked through the two tarball-related points above:

• slow download caused by no regional cloud caching (solved, hopefully)
• CI fails to download tarball solved by CI config change

[pawelrutkaq]

slow is still as slow as it was ;(