Meeting Minutes (TL & Communities & CFTs) #434

johannes-esr · 2025-02-20T15:44:38Z

johannes-esr
Feb 20, 2025
Collaborator

Discussion containing all Meeting Minutes for the TL, Communities & CFT exchange meeting

johannes-esr · 2025-02-20T15:47:26Z

johannes-esr
Feb 20, 2025
Collaborator Author

2025-02-24

Participants

Agenda

Feedback from the Technical Leads
1. How to pass tasks between teams #410
  - Proposal: One Label per Community; Sync Meeting on Monday (this meeting)
2. Discussion of Roadmap Planning: https://github.com/orgs/eclipse-score/discussions/305
Feedback from the Community Leads
1. Operational
2. Testing
3. Software Development Process
4. Marketing & Communication
Feedback from the CFT Leads
1. Persistency
2. FEO
3. Communication
4. Logging
General/Open Points

Meeting Minutes

1. Usage of labels for communities (community:architecture, community:infrastructure, community:testing, community:process, community:marcom) and CFTs (cft:persistency, cft:feo, cft:communication, cft:logging)
2. Update of Roadmap
3. Define creation of documentation in processes, @johannes-esr

Milestones	Date	Description
Process & Tools enable Development	31.03.2025	Left side of V-Model done. Acceptance Criteria: - Process & Tooling for requirements & architecture is available (`sphinx-needs` incl. additional checks for verifying traceability/consistency). - Process & Tooling for Detailed design, implementation & unit verification defined and implemented (e.g. `spinx-test-reports`). - CI/CD is capable to automatically verify the consistency & traceability. - Tooling for test coverage & static code analysis. Prerequisites: - Selection of tooling (e.g. static code analysis).
Modules Buildable	15.04.2025	All MVP defined features (FEO, IPC, Logging, Common Libraries, Persistency) can be built in software module repositiories. Until then, the modules are handled within the incubation repositories. Acceptance Criteria: - All modules use a common repository template (build, CI, gitlint, README, ...); to be checked by operational whether Git submodule/bazel module can be used to avoid code duplication. - All modules are built with `bazel`, (C++17: `clang` for `x86` Linux with `-Wall`, `-Wextra`, `-pedantic`; Rust: `rustc 1.83.0`). - Unit tests are built and run, also via GitHub Actions. - No strict adherence to coding guidelines, but coding guidelines are available. - How to guide for reference build & test environment. - Result: every software module can be built inside of its repository. No common integration so far, no running image. Prerequisites: - MS "Process & Tools enable Development" mostly done
Reference Integration Linux	15.04.2025	Acceptance Criteria: - A reference integration repository is available which depends on all feature/module repositories and the `score` main repository. - reference Linux image (Docker) is available - There are integration tests available which run on Linux image. - Usecases for the integration tests are defined. Prerequisites: - MS "Process & Tools enable Development" & "Modules Buildable"
Process & Tools enable Testing	31.05.2025	Testing strategy is defined and corresponding tooling is implemented. Acceptance Criteria: - Process and Tooling for Testing (e.g. component or integration tests) are available.
Functional GAP Analysis finished	01.06.2025	- For all existing solutions for Release v0.5 analysis of missing features (GAP analysis) is finished, POCs has confirmed possible implementation solutions and everything is documented in Feature Requests. - Feature Requests are confirmed in the TL round and Software Architecture community, tickets are created and prioritized for implementation accrodingly
QNX Support	01.06.2025	The project supports the QNX toolchain. Acceptance Criteria: - The existing modules can be built with `qcc`. Prerequisites: - QNX Version and license defined
Reference Integration QNX	01.07.2025	Acceptance Criteria: - reference QNX image (Qemu) is available (ethernet) - There are integration tests available which run on QNX images. - Image is built and tested as part of automated CI/CD pipeline. Prerequisites: - 'QNX support' milestone - 'Reference Integration Linux' milestone
S-CORE v0.5 Release Candidate	01.06.2025	The features of the 0.5 MVP are according to the S-CORE processes and all artefacts are created initially. Acceptance Criteria: - All necessary artifacts (requirements, tests, architecture) exist in S-CORE format and are generated/executed in CI pipeline for the Release v0.5 components
Audit on Processes definition completed	01.07.2025	Acceptance Criteria: - All processes are defined. - Samples are available. - Maturity Level: Managed
S-CORE v1.0 specification	01.08.2025	- scope for Release v1.0 is defined in Software Architecture community and agreed with TL/PL-circle. - Feature requests for missing Release v1.0 modules are created and agreed. - POCs are done to show possible implementation approach
Reference Hardware for Release v0.5	01.10.2025	- Reference hardware and reference OS are defined. - Reference hardware farm is connected to S-CORE CI. - Integration tests on hardware are running periodically (e.g. nightly). - Define hardware relevant integration tests, e.g. performance, and corresponding KPIs
Release v0.5 feature complete	01.10.2025	- All Feature requests that are relevant for Release v0.5, including the ones resulting from the GAP analysis, are implemented according to the S-CORE software development process (requirements, architecture, dd, implementation and unit verification, integration tests)
Audit on Processes execution completed	01.10.2025
Tool Evaluation/Qualification prepared	01.10.2025	- List of all used tools available
Tool Evaluation/Qualification completed	01.11.2025
Release v0.5 certifiable	01.12.2025	The features of the 0.5 MVP are in a state to be safety certifiable. Acceptance Criteria: - Release v0.5 components have all necessary working products (also release and config mgmt documents) according to the S-CORE software development process - All corresponding tools are certified
All Audit findings resolved	01.12.2025
Release 0.5 Use Case implementation

gantt
   dateFormat YYYY-MM-DD
   title S-CORE Roadmap
   excludes weekends
   tickInterval 1month
   v0.5 Feature Complete : vert, v2, 2025-10-01, 0D
   v0.5 Certifiable : vert, v2, 2025-12-01, 0D

  section Project Milestones
      Release v0.5 feature complete incl. reference QNX integration: milestone, m2, 2025-10-01, 0D
      Release v0.5 Certifiable: milestone, m3, 2025-12-01, 0D
   
  section Software Modules v0.5
      Modules Buildable: done, milestone, m4, 2025-06-02, 0D
      Features follow S-CORE Process: milestone, m5, 2025-10-01, 0D
      GAP Analysis finished: active, milestone, m6, 2025-07-02, 0D

   section Process & Tools
      Process & Tools enable Development: crit, milestone, m7, 2025-07-31, 0D
      Process & Tools enable Testing: crit, milestone, m8, 2025-07-31, 0D
      Audit on Processes definition completed: milestone, m8, 2025-09-01, 0D
      Audit on Processes execution completed: milestone, m8, 2025-10-01, 0D
      Tool Evaluation/Qualification prepared: milestone, m8, 2025-10-01, 0D
      Tool Evaluation/Qualification completed: milestone, m8, 2025-11-01, 0D
      All Audit findings resolved: milestone, m8, 2025-12-01, 0D

   section Reference Environment
      Reference Integration QNX: crit, milestone, m10, 2025-08-01, 0D      
      QNX Support : done, milestone, m11, 2025-06-15, 0D
      Reference Hardware for Release v0.5: milestone, m12, 2025-10-01, 0D

   section Software Modules v1.0
      S-CORE v1.0 specification: active, milestone, m13, 2025-08-01, 0D

Next Steps:

Roadmap to be checked by project members, Feedback in meeting next Monday
@johannes-esr to create tickets for milestones and add milestone description, to be finalized on Monday
Refinement of first milestones in next meeting on Monday

0 replies

johannes-esr · 2025-02-24T11:04:55Z

johannes-esr
Feb 24, 2025
Collaborator Author

2024-03-03

Participants

@johannes-esr
@masc2023
@antonkri
@vinodreddy-g
@arsibo
@FScholPer
@AlexanderLanin
@Dk1601

Agenda

Review of milestone planning done in https://github.com/orgs/eclipse-score/discussions/434#discussioncomment-12265274

Meeting Minutes

- Granularity of planning:
  - Dimension One:
    - Level 0: S-CORE Project (Milestones)
    - Level 1: Sub-Project/Technical committees (Community/CFT via GitHub Label); Level of Project & Technical Leads
    - Level 2: Epic (GitHub Issues) -> assigned to exactly one/multiple Community/CFT via Label; Level of Community/CFT Leads with collaboration of Technical Leads; Planning in common meeting
    - Level 3: Ticket (GitHub Issues) -> assigned to exactly one Community/CFT via Label; Level of Developers/Community Leads/CFT Leads
  - Dimension Two: Roadmap (GitHub Milestones) on Level 0; Epics/Tickets are assigned to the "latest" milestone the Epic has to be done, but can span over multiple Milestones; Level of Technical Leads
- How to do planning yet open; To be discussed within Process Community & Technical Leads
- Tasks:
  - Update PMP Planning Document https://eclipse-score.github.io/score/main/platform_management_plan/project_management.html#planning -> @johannes-esr to check in CW11
  - Move created Milestone Tickets to "normal" Milestones -> @johannes-esr before Wednesday
  - Definition of Epics appearing in the first milestones
    - Draft to be prepared in TL meeting on Wednesday
    - Check with Communities/CFTs 10:30 - 12am -> @FScholPer to invite

0 replies

LittleHuba · 2025-02-24T14:15:12Z

LittleHuba
Feb 24, 2025
Collaborator

Missing architecture community label

1 reply

HartmannNico Feb 24, 2025
Maintainer

Just added

johannes-esr · 2025-03-10T07:45:08Z

johannes-esr
Mar 10, 2025
Collaborator Author

2025-03-10

Participants

@johannes-esr
@antonkri
@masc2023
@vinodreddy-g
@AlexanderLanin
@Dk1601
@guysagnes
@markert-r
@LittleHuba

Agenda

Review TL breakdown of first Milestones https://github.com/eclipse-score/score/milestones
Next steps: Breakdown of Epics by CFTs/Communities; Re-Assignment of existing Tasks to Epics

Meeting Minutes

Epics = Workpackage which can be done in few weeks (1 - 4 weeks), must be assigned to MS, planning granularity for TL
Tasks = Breakdown of Epic, can also have Subtasks, assigned to same MS as Epic, planning granularity for CFT/Community
For functional grouping of Epics labels are used
Maturity Level of a Epic are included in Epic title
Main planning is done in score Repository

0 replies

johannes-esr · 2025-03-17T07:52:05Z

johannes-esr
Mar 17, 2025
Collaborator Author

2025-03-17

Participants

Agenda

Presentation of proposal "How to plan"
Planning of first milestones
Where to put Lessons Learned?

Meeting Minutes

@antonkri presented new planning approach
- accepted
- S-CORE Roadmap (view)
- TLs to update planning document: Update Planning in PMP #697
"Lessons learned" also to be saved in official documentation to be visible on website, mostly in Contribute section

0 replies

FScholPer · 2025-03-31T07:18:21Z

FScholPer
Mar 31, 2025
Collaborator

2025-03-31

Participants

@qor-lb
@johannes-esr
@AlexanderLanin
@masc2023
@arsibo
@Dk1601
@markert-r

Agenda

Status of each Community (2 minutes)
Milestone planning
- S-CORE Roadmap
- Do we have blockers?
- Does each of us reach the timeline goals
- June Release -> planning?
- Roadmap of the Epics (priority, start date / due date). Does each epic has a subtask?
Questions / Problems?

Meeting Minutes

Status
- Tooling: Epic: (Initial) Set-up basic repository & build infrastructure #585 (comment)
- Logging: https://github.com/orgs/eclipse-score/discussions/770 (gap analysis)

0 replies

johannes-esr · 2025-04-14T08:44:45Z

johannes-esr
Apr 14, 2025
Collaborator Author

2025-04-14

Participants

Meeting Minutes

Review of S-CORE Roadmap Project
TLs need Board for Change Requests (Feature Modification & Component Modification Label) -> @markert-r creates board
@antonkri checks with @ramceb regarding location of FEO tickets

0 replies

johannes-esr · 2025-04-28T09:00:58Z

johannes-esr
Apr 28, 2025
Collaborator Author

2025-04-28

Participants

@johannes-esr
@markert-r
@arsibo
@AlexanderLanin
@LittleHuba
@qor-lb
@masc2023
@guysagnes
@dneail1601
@FScholPer
@antonkri

Agenda & Meeting Minutes

Review of S-CORE Roadmap (view)
- General: Keep tickets up to date!
- Communication, Logging & Base Libs will be published until next week
- FEO: Tickets to be planned
- Persistency
- Testing: Current approach shall be presented
- Process
- Architecture
- Infrastructure

0 replies

FScholPer · 2025-04-29T10:54:29Z

FScholPer
Apr 29, 2025
Collaborator

2025-05-05

Participants

@johannes-esr
@AlexanderLanin
@markert-r
@arsibo
@dneail1601
@LittleHuba
@antonkri
@qor-lb
@masc2023
@FScholPer

Agenda & Meeting Minutes

Review of S-CORE Roadmap (view)
- Infrastructure and tooling
  - Community not stuffed enough -> at least 6 full time needed
  - Unclear priorities and scaled like 100 devs -> many wish tickets and no focus
  - gitlint really needed?!
  - https://github.com/orgs/eclipse-score/discussions/977 ??
- 321 Issues open in main repo
Multi-repo apprach
- Enables requirement linkage & traceability between repositories
Process audit next Monday

0 replies

FScholPer · 2025-05-12T08:06:41Z

FScholPer
May 12, 2025
Collaborator

2025-05-12

Participants

@johannes-esr
@AlexanderLanin
@markert-r
@arsibo
@dneail1601
@LittleHuba
@antonkri
@masc2023
@FScholPer
@guysagnes

Agenda & Meeting Minutes

Review Feature Planning

Infrastructure & Tooling
- @AlexanderLanin mentioned that all repositories can now build documentation. Multi repository is still in progress (Will take about about 1 week to finish).
- Rust on qnx, multirepo setup, linking between repositories.
- @AlexanderLanin proposed to do a regular demo meeting.
- Demo proposal : https://sdvworkinggroup.slack.com/archives/C0894QGRZDM/p1747037795081439?thread_ts=1747037764.219969&cid=C0894QGRZDM"
- Question about state of template repositories from @antonkri. @AlexanderLanin answered that a decision was made that one part tests without and the other with the template
Testing
- @dneail1601 mentioned that Concept of C++ is finished. The community wants to wait until real production code is available not only demo code -> https://github.com/qorix-group/Score-Testing/blob/main/Proposal/Data%20flow%20tests%20with%20gtest%20combined%20with%20extended%20unit%20tests%20-%20compilable.cpp
- @AlexanderLanin said that we should order the tests in order of duration.
- Daniel said that their is a discussion if only unit tests should be fixed by the developers and the broken other tests should be fixed be the testers
- @AlexanderLanin asked about release strategy meeting. Daniel proposed to postpone the discussion until their is real code.
- @antonkri proposed to the test community that we need a test plan who does what and so on.
- TL will check
FEO
- Currently they wait until the Process Pilot is finished
- @markert-r said they should use the blocking label
- @antonkri We need feature requirements and epics for described for each release (due date 05.30 for existing and the rest 06.06.)
- Until next meeting setup cft for common libs should be done -> TL should do that in next TL meeting
Persistency
- Feature priority for file system base unclear
  - C++ api & implementation already there in common libs
  - Com & Persistency will make a meeting AI: @LittleHuba & @guysagnes
- C++ Class Result dependency to common/base libs
- Security Layer in Persistency should be discussed in the architecture community
Logging
- Components Requirements next step
- Gap Analysis is finished
Communication
- Next task Requirements & Architecture fitting to pilots to be created
- Requirements sync mechanism has to be defined in each company
- Proposal for Snapshot mechanism to feo already there: https://github.com/orgs/eclipse-score/discussions/861#discussioncomment-13040972
Question if feature architecture is interconnection between features or if it is high level description -> should be high level description -> discussion with @hoe-jo to be done

0 replies

qor-lb · 2025-05-19T09:04:15Z

qor-lb
May 19, 2025
Collaborator

2025-05-19

Participants

@guysagnes
@dneail1601
@markert-r
@AlexanderLanin
@antonkri
@FScholPer
Padmakumara Malikaarachige Damith Lakmal

Agenda

Review Feature Planning

Meeting Minutes

to 1.

Infrastructure
- "initial" process & tools enable development done (basic setup)
  - Further development for tool support once concrete gaps are identified
  - Pilots to identify gaps in basic setups
  - Clear responsibilities for infrastructure in both C++ & Rust pilots to enable gap analysis in community
  - Epic: Process Pilot #760
Communication
- LoLa is now buildable; 0.5 gap analysis on-going
- To be clarified: Com API for 0.5 or 1.0 (+ Rust support)
Testing
- Testing examples for 0.5 modules in progress and planned until end of May
- Epic: Process Pilot #760 to also target piloting the verification as a follow-up
FEO
- missing attendees, skipped
Persistency
- Feature for file system alignment with existing part of baseLib to be taken to Gap analysis
- Security Layer in Persistency rely on system, no additional security parameter to be handled
- Requirement review based on: https://eclipse-score.github.io/score/pr-1069/process/process_areas/requirements_engineering/guidance/requirements_inspection_checklist.html
- Persistence Feature KVS
  - Final review/rework on feature level
  - Draft architecture based on template (Pilot)
  - Draft component requirement based on template (Pilot)
- C++ KVS implementation
  - PoC Implementation of Wrapper over Rust
  - Decision: specific implementation of C++ Library
Logging
- Logging is now buildable; 0.5 gap analysis on-going
- missing attendees, skipped

0 replies

johannes-esr · 2025-05-26T08:44:01Z

johannes-esr
May 26, 2025
Collaborator Author

2025-05-26

Participants

@johannes-esr
@Dk1601
@timkl7
@antonkri
@AlexanderLanin
@arsibo

Meeting Minutes & Agenda

Review Roadmap
- Communication:
  - Epic: LoLa buildable & existing tests runnable #586 can be marked as done
  - Epic: Functional gap analysis for feature "Communication" #881 will be done by @LittleHuba
  - Epic: Create requirements for feature "Communication" #886, Epic: Create architecture artifacts for feature "Communication" #937 will be checked until next Monday
- Logging:
  - Epic: Logging buildable & existing tests runnable #587 must be cleaned up, to be checked if everything builds
  - Epic: Functional gap analysis for feature "Logging" #884 to be updated in Logging meeting tomorrow
  - Epic: Create requirements for feature "Logging" #939, Epic: Create architecture artifacts for feature "Logging" #942 in progress, to be updated in Logging meeting tomorrow
- FEO:
  - Overview of what CI jobs are running
  - Epic: Functional gap analysis for feature "Fixed Execution Order" #883, to be checked if something is missing
  - Epic: Create requirements for feature "FEO" #938, Epic: Create architecture artifacts for feature "FEO" #941: first PRs are present
- Persistency:
  - Update to be checked afterwards
- Testing:
  - PoC for Persistency in review
  - Will be presented on testing meeting wednesday, afterwards roll out
- Process: no representative present
- Infrastructure:
  - Problems with proxies, to be analyzed
  - Workstream meetings organized: https://github.com/orgs/eclipse-score/discussions/1095#discussioncomment-13248530

Offline report
Summary for the Persistency FT

Feature Request for Persistency · Issue #95 · eclipse-score/score -> closed
Focus on Key-Value Store, File system aspect will be part of the gap analysis
Persistency Feature KVS
- Final release on feature level
- Review started: architecture based on template (Pilot)
- Review started: component requirement based on template (Pilot)
C++ KVS implementation
- Implementation started: specific implementation of C++ Library
Info - Requirements handling follows Reference:
- requirements_inspection_checklist
- requirements_templates
Clarification requested
- How should be the separation on module level in respect to selected language?
  -> Proposition a single repository containing the different language (Rust / C++)
  -> Process adaptation for the template to be adapted
- Do we have the plan to use at least C++ 2020 and when?
  -> Question related to maps handling inside C++ 2017
- How is the design constrain to be taken in account for dynamical types (e.g. String, Vector, …)
  -> MISRA rules reported type – Ref. rules 21.6.1 / 21.6.2

0 replies

johannes-esr · 2025-06-02T08:57:53Z

johannes-esr
Jun 2, 2025
Collaborator Author

2026-06-02

Participants

@johannes-esr
@vinodreddy-g
@guysagnes
@AlexanderLanin
@arsibo
@PiotrKorkus
@Dk1601
@FScholPer
@aschemmel-tech
@markert-r

Meeting Minutes

Review of S-CORE Roadmap (view)
Communication: No update available
Logging:
- Buildable: Probably can be closed after adding README file
- Gap Analysis & Requirements ongoing
FEO:
- Gap Analysis, Requirements & Architecture ongoing
Persistency:
- Also tracked in process pilots
Testing:
- ITF set up in progress
- CFT Lead will be taken over by @PiotrKorkus
Process:
- Update tickets that cannot be done to another epic
Infrastructure:
- Rust started, overall ongoing
- C++ Stream needed? -> @eclipse-score/automotive-score-technical-leads
Baselibs
- Feature Team needed -> @eclipse-score/automotive-score-technical-leads

0 replies

FScholPer · 2025-06-05T12:43:46Z

FScholPer
Jun 5, 2025
Collaborator

2025-06-16

Participants

@masc2023
@FScholPer
@markert-r
@antonkri
@qor-lb
@PiotrKorkus
@guysagnes
@TomFleischmann
Daniel Klotz

Agenda

S-CORE Roadmap

Meeting Minutes

##Modules builable

Persistency Full test Coverage will be there until next week

QNX Support

Process for : Safe Use of QNX -> AI: @aschemmel-tech
QNX Support -> Refinement Meeting should be set up -> AI: @antonkri

Functional Gap Analysis

Architectural Gap Analysis is in Progress currently
Persistency: KVS already done but Filesystem open
Communication -> no update

Process Definition Audit Completed

ITF will probably not feasible until End of July -> Change to another milestone because not needed for next Audit

Process and Tools Enable Development

Rust is ongoing
@markert-r will request @FScholPer to get some support for initial Setup

Functional Gap Analysis S-CORE v.0.5 Completed

Also Planning finished is needed for implementation of the gaps
Persistency: Filesystem is part of 1.0 and should be created as feature request

2026-06-23

Participants

@FScholPer
@qor-lb
@PiotrKorkus
@masc2023

Agenda

S-CORE Roadmap

Meeting Minutes

Testing

The duedate of some ITF Tickets have been moved to later date. Could be last week of July

Process

Friday Audit needs Quality Management until end of this week
@qor-lb asked about the status of the Audit findings: Tickets created -> https://github.com/eclipse-score/process_description/releases/tag/v1.0.0 & https://github.com/eclipse-score/process_description/releases/tag/v1.0.1
Infrastructure Community had meeting with Process Community to align gap analysis
Where is the first Assessment to go over the Pilots -> October
First Version of Tool Requirements already merged in doc-as-code repository
Could be an overlap between Tool Requirements and Sphinx Needs Extension Implementation / Commercial Offering
Doc-as-Code not acessible from main S-CORE page

0 replies

johannes-esr · 2025-06-26T11:37:50Z

johannes-esr
Jun 26, 2025
Collaborator Author

2025-06-26

Participants

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

Agenda & Meeting Minutes

TLs to review Feature team creation #1281
https://github.com/orgs/eclipse-score/discussions/1283
Eclipse Foundation wants to join TL Circle meetings -> @markert-r to invite
Contributors from Continental to be added -> @markert-r to invite

0 replies

johannes-esr · 2025-06-30T07:27:29Z

johannes-esr
Jun 30, 2025
Collaborator Author

2025-06-30

Participants

@johannes-esr
@AlexanderLanin
@qor-lb
@markert-r
@PiotrKorkus
@guysagnes
@FScholPer
@masc2023
@arsibo

Agenda & Meeting Minutes

Review S-CORE Roadmap (view)
- General: Keep due dates up to date
- Communication: Nobody available in call
- Logging: No update / progress
- FEO: Still ongoing
- Testing: Progress regarding ITF
- Process:
  - Process description with ML 1 will be released (Version 1.0.x)
  - Next steps to be defined, next audit in October 2025
- Architecture
- Infrastructure: Progress in taks & planning
- Baselibs: Nobody available in call
- Persistency:
  - repository handling: incubator to final repository
  - Namespace for KVS Public Interfaces: score::mw::per namespace or score::per
  - Versioning - Modules and APIs
    - proposition to get unique version controlling API and Module
    - how to handle version of the shared object library - typical approach from Linux?
  - Presentation of the proposition - mockable code (rust)
    - Start writing Rust API guidelines for S-CORE #1282 -> https://eclipse-score.github.io/score/pr-1282/contribute/development/rust/rust_api_design.html
  - Organization of the source repositories
    - Get tests folder parallel of the source folder on component level inside the language related folder
Expectations towards FT Leads regarding Architecture F2F Workshop

0 replies

johannes-esr · 2025-07-14T08:55:13Z

johannes-esr
Jul 14, 2025
Collaborator Author

2025-07-14

Participants

@4og
@antonkri
@MaximilianSoerenPollak
@PiotrKorkus
@guysagnes
@FScholPer
@masc2023
@arsibo
@johannes-esr
@markert-r

Meeting Minutes

Presentation https://github.com/orgs/eclipse-score/discussions/1387
- Mono/Multi Repo
  - Should be still structured in different bazel modules
Short Recap of Architecture WG: https://github.com/orgs/eclipse-score/discussions/1247
Review S-CORE Roadmap (view)
- Communication: No gaps for 0.5, Work on 1.0 and Rust support
- Logging: @arsibo to cleanup Epics
- FEO: Blocked due to no Rust API of Logging & Communication
- Persistency: -
- Testing: Setup of ITF, normal progress of tasks
- Process: Update next week
- Architecture: Already discussed in workshop
- Infrastructure: Progress ongoing, see tickets
- Baselibs: Ticket linkage missing

0 replies

johannes-esr · 2025-07-18T09:00:12Z

johannes-esr
Jul 18, 2025
Collaborator Author

2025-07-21

Participants

Agenda

Proposal Integration Repository: https://github.com/nradakovic/score/blob/nradakovic-ci-infra/docs/features/infrastructure/ci_repo_structure_draft.md
S-CORE Roadmap (view)

Meeting Minutes

Communication:
- Rust API for 0.5 is already merged. Commits: mw::com: Minimal API POC in Rust #1212 (comment)
Logging:
- Requirements & and Documentation ongoing
- HowTo: Issue to be created
Testing:
- DLT Support will be coming shortly
- Tracability and test documentation ongoing
Process:
- Planing updated
- Process Description and Implementation currently done in parallel
- October not reachable -> Will come in January. We need more people to also finish until January.
  - Process description and pilots are scope.
- TSF pilot -> Next process community state will be shared
Architecture:
Feature Request -> Discussion and kickoff meetings invite in architecture community
Infrastructure
- Mapping between tools requirements and process requirements still ongoing ->
Persistency
- Consistency to the library currently ongoing
Baselibs
- Feature Architecture ongoing, Detailed Design ongoing (format change), TSF some questions open

0 replies

FScholPer · 2025-07-28T07:49:36Z

FScholPer
Jul 28, 2025
Collaborator

2025-07-28

Participants

@markert-r
@FScholPer
Mina Hamdi
@4og
@arsibo
@AlexanderLanin
@masc2023
@mohamed BEIJIJOU
Paul Sherwood
@PiotrKorkus
@hth9fe
Lakmal

Agenda

Feature Teams update

Meeting Minutes

Communication
- Highlevel Architecture -> in progress
- Detail Design -> in progress
- Rust Support -> more Capacity added
- Testability -> current in progress with "tunneling" application
Logging
- Replanning needed -> update next week
FEO
- no update
Persistency
- no update
Testing
- POC Feature Testing
- Bazel Learning -> Driven Forward in discussion
Process
- Please use the Bugfix Template for all bugfixes
- Additional Steps like labeling needed from TL
- Audit moved to January
- ML Process Execution Audit Complete needed for the next Audit
Infrastructure
- Simplifying of doc-as-code
- IDE optimizations
- Update https://eclipse-score.github.io/docs-as-code/main/how-to-use/faq.html
Baselibs
- nlohmann approach proceeded this week in process community
- @FScholPer Removes Epic: S-CORE v0.5 Baselibs Feature Complete #1149 and assign the epics directly to the ML.
Tool Evaluation: Identify Tools #1482 -> Collecting all Tools. Add to the TL LOP
Change the cadence of the Monday Meetings because of vacation time -> until mid september proposal

0 replies

Eclipse S-CORE

Meeting Minutes (TL & Communities & CFTs) #434

Uh oh!

johannes-esr Feb 20, 2025 Collaborator

Replies: 20 comments · 1 reply

Uh oh!

Uh oh!

johannes-esr Feb 20, 2025 Collaborator Author

2025-02-24

Participants

Agenda

Meeting Minutes

Uh oh!

Uh oh!

johannes-esr Feb 24, 2025 Collaborator Author

2024-03-03

Participants

Agenda

Meeting Minutes

Uh oh!

LittleHuba Feb 24, 2025 Collaborator

Uh oh!

HartmannNico Feb 24, 2025 Maintainer

Uh oh!

Uh oh!

johannes-esr Mar 10, 2025 Collaborator Author

2025-03-10

Participants

Agenda

Meeting Minutes

Uh oh!

Uh oh!

johannes-esr Mar 17, 2025 Collaborator Author

2025-03-17

Participants

Agenda

Meeting Minutes

Uh oh!

Uh oh!

FScholPer Mar 31, 2025 Collaborator

2025-03-31

Participants

Agenda

Meeting Minutes

Uh oh!

johannes-esr Apr 14, 2025 Collaborator Author

2025-04-14

Participants

Meeting Minutes

Uh oh!

johannes-esr Apr 28, 2025 Collaborator Author

2025-04-28

Participants

Agenda & Meeting Minutes

Uh oh!

Uh oh!

FScholPer Apr 29, 2025 Collaborator

2025-05-05

Participants

Agenda & Meeting Minutes

Uh oh!

Uh oh!

FScholPer May 12, 2025 Collaborator

2025-05-12

Participants

Agenda & Meeting Minutes

Uh oh!

qor-lb May 19, 2025 Collaborator

2025-05-19

Participants

Agenda

Meeting Minutes

Uh oh!

Uh oh!

johannes-esr May 26, 2025 Collaborator Author

2025-05-26

Participants

Meeting Minutes & Agenda

Uh oh!

johannes-esr Jun 2, 2025 Collaborator Author

johannes-esr
Feb 20, 2025
Collaborator

Replies: 20 comments 1 reply

johannes-esr
Feb 20, 2025
Collaborator Author

johannes-esr
Feb 24, 2025
Collaborator Author

LittleHuba
Feb 24, 2025
Collaborator

HartmannNico Feb 24, 2025
Maintainer

johannes-esr
Mar 10, 2025
Collaborator Author

johannes-esr
Mar 17, 2025
Collaborator Author

FScholPer
Mar 31, 2025
Collaborator

johannes-esr
Apr 14, 2025
Collaborator Author

johannes-esr
Apr 28, 2025
Collaborator Author

FScholPer
Apr 29, 2025
Collaborator

FScholPer
May 12, 2025
Collaborator

qor-lb
May 19, 2025
Collaborator

johannes-esr
May 26, 2025
Collaborator Author

johannes-esr
Jun 2, 2025
Collaborator Author

FScholPer
Jun 5, 2025
Collaborator