Meeting Minutes

[johannes-esr]

General Discussion for all Meeting Minutes

[johannes-esr]

2025-02-26

Participants

@johannes-esr
@markert-r
@qor-lb
@antonkri

Meeting Minutes

• New weekly timeslot: Wednesday 9 - 10am, @johannes-esr to ask @FScholPer to invite
• Planning Concept:
  • Milestones are Issues of the type 'Milestone' -> @johannes-esr to add this issue type
  • Milestones only have sub-issues of the type 'Epic' -> @johannes-esr to add this issue type
  • Epics have sub-issues of the type Task

[johannes-esr]

2025-02-28

Participants

@johannes-esr
@markert-r
@vinodreddy-g
@antonkri
@FScholPer

Meeting Minutes

• Additional weekly slot: Friday, 1:30 - 2:30pm -> @FScholPer to invite
• @markert-r to schedule meeting for March 20 for new interested companies
• New agenda points for PL Circle:
  • Date of Townhall
  • Combination of https://eclipse-score.github.io/ & https://eclipse-score.github.io/score/main/ to allow next step of Contribution One Pager

[johannes-esr]

2025-03-06

Participants

@pahmann
@antonkri
@FScholPer
@johannes-esr

Agenda

• Breakdown of first to Milestones in Epics

Meeting Minutes

• Milestone: Process & Tools Enable Development
  • Epic: (Initial) Processes Requirements #581
  • Epic: (Initial) Tooling Requirements & Architecture #582
  • Epic: (Initial) Processes Detailed Design, Implementation #583
  • Epic: (Initial) Tooling Detailed Design, Implementation, Unit Verification #584
• Milestone: S-CORE v0.5 Modules Buildable
  • Epic: (Initial) Set-up basic repository & build infrastructure #585
  • Epic: LoLa buildable & existing tests runnable #586
  • Epic: Logging buildable & existing tests runnable #587
  • Epic: Persistency buildable & existing tests runnable #588
  • Epic: FEO buildable & existing tests runnable #589
  • Epic: ITF buildable & existing tests runnable #590
  • Epic: (Initial) Coding Guidelines C++ #591
  • Epic: (Initial) Coding Guidelines Rust #592
  • Epic: (Initial) Coding Guidelines Python #593
• Tasks for Communities / CFTs:
  • All existing issues which are matching to the Epics of the Milestone shall be attached
  • Add Milestone to all linked Issues

[antonkri]

2025-03-07

Participants

@johannes-esr
@antonkri
@vinodreddy-g
@FScholPer

Agenda

• Breakdown further Milestones

Meeting Minutes

• Milestone: Reference Integration Linux

  • Epic: Linux container x86_64 is up and running
    Acceptance criterias: Linux container (x86_64) is prepared, configured properly (ethernet/ssh access) and uploaded to some location, that is accessible from local builds and CI.
  • Epic: Linux container arm64 is up and running
    Acceptance criterias: Linux container (arm64) is prepared, configured properly (ethernet/ssh access) and uploaded to some location, that is accessible from local builds and CI.
  • Epic: ITF framework is up & running.
    Acceptance criterias: ITF framework is integrated into bazel. ITF test job is set-up in CI and is part of check/gate pipeline. ITF can establish ssh connection to the image. As first test in the CI pipeline, ITF should deploy application under test to the Linux container and ensure, that this one is running.
  • Epic: ITF framework dlt support
    Acceptance criterias: ITF framework can receive dlt streams from the applications and provides infrastructure to evaluate DLT logs in runtime and post-mortem.

• Milestone: QNX Support

  • Epic: Integration of QNX toolchain.
    Acceptance criterias: QNX 8 toolchain is integrated into bazel. Users need to get the license from QNX everywhere program and put it some specific location for being able to use QNX 8 toolchain.
  • Epic: Building with QNX in CI.
    Acceptance criterias: CI jobs for building of applications are set-up for all currently existing applications and documentation is provided how set-up QNX CI jobs for future applications. QNX CI license is stored as GitHub Secret and allows unlimited execution of QNX CI jobs in parallel
  • Epic: QNX Compiler config.
    Acceptance Criteria: compiler config is agreed with Process team and compiler/linker flags are chosen to support ASIL development right from the beginning.

• Milestone: Reference integration QNX

  • Epic: Qemu with QNX image and x86 BSP
    Acceptance Criteria: Qemu with QNX image, x86 BSP and S-CORE applications can be built with bazel locally and in CI. There exist a voting CI job, that builds QNX Qemu image and executes all existing ITF tests with it.
  • Epic: Qemu with QNX image and Qualcomm (ARM) BSP
    Acceptance Criteria: Qemu with QNX image, Qualcomm BSP and S-CORE applications can be built with bazel locally and on demand on CI.

[johannes-esr]

2025-03-14

Participants

• @johannes-esr
• @antonkri
• @qor-lb
• @vinodreddy-g
• @markert-r

Agenda

• How to do further planning?

Meeting Minutes

• Meeting this afternoon to update PMP with information decided on https://github.com/orgs/eclipse-score/discussions/434#discussioncomment-12299310 & https://github.com/orgs/eclipse-score/discussions/434#discussioncomment-12445705
  • Breakdown of Workpackages
  • Labels to use
  • ...

[johannes-esr]

2025-03-19

Participants

@johannes-esr
@markert-r
@antonkri
@timkl7
@qor-lb

Meeting Minutes

• Next week alignment meeting regarding Processes & Tools between AUTOSAR & S-CORE in Lüneburg, https://www.autosar.org/news-events/detail?tx_news_pi1%5Baction%5D=detail&tx_news_pi1%5Bcontroller%5D=News&tx_news_pi1%5Bnews%5D=304&cHash=a20923b48d9e091adb600c148ab6948f
  • @AlexanderLanin will attend the meeting
  • @antonkri to check if @aschemmel-tech will attend, too
• Proposal: TL Meeting on 31th March 2025, 9:00 - 12:30
  • Planning/Review of Milestones ending in June 2025, too much in parallel
• Tasks for next meeting:
  • Review of Milestone planning; some Epics are not assigned to a CFT/Community
• Change of Monday Meeting Series:
  • 9 - 10am only TL
  • 10 - 11am TL & Communities & CFTs
  • @qor-lb changed invitation, to check if everybody received the updated invitation

[johannes-esr]

2025-03-21

Participants

@johannes-esr
@FScholPer
@qor-lb
@antonkri

Agenda

• Open points from last discussion

Meeting Minutes

• AUTOSAR / S-CORE Meeting: @aschemmel-tech can just attend online
• TL Workshop: March 28, starting 12 pm (instead of March 31)
• Should Safety Linux be a target platform of S-CORE? -> To be addressed in PL Circle @antonkri
• Point for next PL Circle: Analysis AUTOSAR -> @antonkri

[qor-lb]

2025-03-24

Participants

• Tom Fleischmann
• Rebecca Markert
• Anton Kiroborodov
• Frank Scholter Peres
• Lars Bauhofer

Agenda

1. Current Status S-CORE Logo
2. Agenda for WS on 28th
3. Feedback productivity Tech Lead Sync

Meeting Minutes

to 1.

• An agenda of SteerCo but not update yet

to 2.
Proposals to be prepared until friday:

• More concrete milestone/roadmap planning - @antonkri / @markert-r
  • do we have all the dependencies?
  • how to get a better overview?
• Definition of meeting structure - @markert-r
  • who prepares the meeting?
  • what agenda is discussed
  • How to pass tasks between teams #410,
• How to contribute/how are feature requests managed? - @TomFleischmann / @qor-lb
  • Feature requests are prepared to reflect technical roadmap
  • Case A: FR open but no contributions yet (Feature is on roadmap but not implemented)
  • Case B: Feature not yet on roadmap (functionality not yet targeted by by S-CORE)
• Management of components within S-CORE (who can review & merge) - @FScholPer

misc:

• https://oss-review-toolkit.org/ort/

[qor-lb]

2025-03-26

Participants

• Tom Fleischmann
• Rebecca Markert
• Anton Kiroborodov
• Lars Bauhofer

Agenda

1. Slides for townhall
2. Move invite from zoom to teams

Meeting Minutes

to 1.

1. Welcome and Introduction - 5 min
2. Project Vision - 10 min - @markert-r
   - Goal S-CORE: source code standardization
3. Current Status & Overview Cross Functional Teams - 40 min
   • Content Tech - 20 min - @qor-lb
     • 0.5 components & how they were selected - i.e. Architecture WS, Selection Criteria, Components
     • Hint to 1.0 definitions in following months
   • Content Process & Tools - 20 min - @markert-r
     • Current status process - 5 min
     • Results from ekxida - 15 min
4. Roadmap (milestones) - 10 min - @FScholPer
5. How to contribute - 5min - @qor-lb
   - (CFT's & work structure)
6. Q&A - 20 min

to 2.

• accepted

misc:

• Preliminary slides: 20250320_S-CORE_Townhall_Meeting.pptx
• Community days slides:

[johannes-esr]

2025-03-28

Participants

• @johannes-esr
• @qor-lb
• @markert-r
• @antonkri
• @FScholPer

Meeting Minutes

• docs: improved how to contribute section #776
• Review of Roadmap Planning
• Tasks for Monday Meeting:
  • https://github.com/eclipse-score/score/milestone/7 -> Status to be checked with Infrastructure Community
  • Status (~2min) of each CFT/Community in Monday Meeting

[FScholPer]

2025-03-31

Participants

• @johannes-esr
• @qor-lb
• @markert-r
• @antonkri
• @FScholPer
• @guysagnes

Agenda

• Feedback for planning milestones

Meeting Minutes

• We need the participants for the architecture workshop A1 @qor-lb

[johannes-esr]

2025-04-02

Participants

@johannes-esr
@antonkri
@FScholPer

Agenda

• Review of Monday Meeting

Meeting Minutes

• Detailed check of tasks of Operational Community on Friday, 1:30 - 2:30pm