Project Lead Circle [2025-07-18]

[antonkri]

Agenda

1. Approval of Meeting minutes for last meeting
2. QNX & Rust
   • QNX wants to extend Ferrocene compiler with support for QNX 8
   • Discussed with Ferrocene which functionality from core and std libraries is needed by S-Core and should be qualified
   • Ferrocene (now also part of Eclipse SDV as supporting member) should be supported with money to achieve qualification of agreed scope
     a. Eclipse SDV supports Ferrocene
     b. some of the partners supports Ferrocene
   • help from PLs needed
3. Production target AoUs
   • currently QNX AoUs and Safety Manuals are not part of "QNX everywhere project", but they are crucial for Platform Safety Case, as they provide restrictions to the applications. Without QNX AoUs, developed applications and platform modules can violate those and therefore qualification will not be possible
   • Ideally, we convince QNX to put their AoUs open source, as they are anyhow part of evaluation license and are kind of "open secret", at least for all core partners of the S-Core project
   • Otherwise we need to specify AoUs towards OS, that "per chance" will match the AoUs of QNX 8
     • Potential risk with QNX IP, it would be better if would involve QNX in defining these AoUs towards OS
     • QNX needs to provide QNX 8 Safety Manuals and AoUs at least to one of the S-Core partners, so that we could define our own AoUs based on it
4. Task Force
   • https://github.com/orgs/eclipse-score/discussions/1387
5. xCore Council
   • short update
6. Hackathon in Berlin/Porto
   • Yes or no?
7. Tech lead meeting invitation

Meeting minutes

• to 1
  • Approval last meeting minutes (BMW (@antonkri) pushes forward to accept meeting minutes, @qor-lb second the motion)
• to 2
  • Eclipse strategic round would be the right place to discuss this, @TomFleischmann will take this point with him to the next meeting and will make everyone aware.
  • @TomFleischmann will draft a resolution proposal and S-Core project will review it.
  • Resolution proposal will be presented later in Eclipse strategic round.
• to 3
  • Do we need some help from Dana from Eclipse process working group? -> yes, why not, as other projects will also face the same problem.
  • @TomFleischmann will talk to John from QNX as soon as possible and ask him for assistance
  • @TomFleischmann is currently preparing an additional clarification note on the "QNX everywhere license" and will share it with us.
  • Additionally we could do it over xCore Council, if this role gets approved on Monday in the Eclipse SDV strategic membership group
• to 4
  • PLs agree on special group targets proposal
  • Discussion on the capacity will take place next week
  • Valeo will approach TLs regarding how they can help
  • In case we need some help with infa from Eclipse SDV, we need to approach them early enough. @markert-r will discuss this with Alexander Lanin
• to 5
  • new role xCore council, to represent multiple projects from various vehicle domains
  • basic ides: strategic decisions, communication to external organizations, external representation.
  • should be approved next week in Eclipse SDV strategic membership group
• to 6
  • We don't have to present any S-Core challenge (we are already too late for this)
  • but we could just join as a S-Core team and participate in other challenges to get to know other Eclipse projects
  • We need to think about this, feedback next week from PLs
• to 7
  • TLs have currently four meetings a week
  • All these meetings were in Eclipse calender and this was not working out (mainly due to issues with google calender and company policies)
  • Christian tries to improve the situation and schedule/maintain meetings in the Eclipse calender
  • We would like still to have "internal" meetings between TLs to be more efficient.
  • Conclusion:
    • Invitation to all TL meetings should be available to everyone, we can stay with Teams but the meeting details should be published in the TL meeting discussions.
    • TLs can still decide on the meeting rules, e.g. "listen but not talk"
    • Rebecca will publish the Teams invite to the TL meeting minutes