Base Libs FT Meeting Minutes

[4og]

All regular meetings of the Base Libs Feature Team will be documented in this thread. If you subscribe here, you'll get summaries of the meetings you missed.

[4og]

Weekly 2025-06-18

Participants

@ramceb
Felix Moelders
@FScholPer
mishu-dev
@RAHUL2054
Alekhya Reddy
@4og

Agenda & Meeting Minutes

1. Introduction & work mode
   • Base libs FT scope. Repos: https://github.com/eclipse-score/baselibs (except for mw::log) and inc_json
   • Work mode
     • Team goal: To drive the development of Base Libraries in S-CORE while ensuring S-CORE processes are followed and providing support to other feature teams.
     • How to become a contributor: https://www.eclipse.org/projects/handbook/#contributing
   • Communication channels
     • See https://github.com/orgs/eclipse-score/discussions/1223
   • Meeting time. Is it ok for everyone?
     • We keep the current timeslot.
2. GitHub Project for the Base Libs: Base Libs FT
3. Roadmap for S-CORE 0.5
   • Focus on fulfilling the S-CORE process for the code in https://github.com/eclipse-score/baselibs and getting the json lib qualified.
4. Qualification of the JSON library. Summary of https://github.com/orgs/eclipse-score/discussions/1181 & https://github.com/orgs/eclipse-score/discussions/1225 and the next steps.
   • Practical example for TSF is needed. @mishu-dev to invite Paul and Daniel Krippner (can be found on Slack), @masc2023. The next Baselibs FT meeting is to be dedicated to applying TSF to nlohmann json.
   • "Daniel Krippner: Trustable Service Mesh via Eclipse uProtocol & Trustable Software Framework" https://www.youtube.com/watch?v=SBAqX7EyEDY&ab_channel=EclipseSoftwareDefinedVehicle
   • Component request for json parser: Feature Request: JSON Parser #822. The stakeholder requirement is to be converted to a feature requirement.

[4og]

Weekly 2025-06-25

Participants

@ramceb
@masc2023
@mishu-dev
@devcurmudgeon
@FelixMoelders
@alexandruiulian10
@Erikhu1
@lennartbecker-d
@NilsEb
@AnotherDaniel
@sankurm
@kalu-an
@FScholPer
@mishu-dev
@RAHUL2054

Agenda & Meeting Minutes

1. Deep-dive Trustable framework for nlohmann json
2. Intro to the approach from d-fine @lennartbecker-d
   • see https://score-json.github.io/inc_json/pr-12/
   • [test coverage for nlohmann](json https://coveralls.io/github/nlohmann/json)
   • link calibration training for SME
3. Open topics:
   • Requirements elicitation for the safe json library
   • Collect AoUs.
   • Linkage to the existing tests.
   • Rationale for all items https://score-json.github.io/inc_json/pr-12/trustable/report.html

[4og]

Weekly 2025-07-02

Participants

@4og
@FScholPer
@kalu-an
Alekhya Reddy
@lennartbecker-d
@LuNieb
@mishu-dev
@FelixMoelders
@RAHUL2054
@arsibo

Agenda & Meeting Minutes

1. Open topics from the last meeting w.r.t. JSON lib qualification.
   • @mishu-dev will check with Communication FT and other FTs if any extra reqs for JSON are needed? E.g. w.r.t restriction to RFC. The new requirements are to be added the component request Feature Request: JSON Parser #822.
   • Do we have platform requirements? This will be discussed on 7.7.2025 in a special Tech Lead WS.
   • TSF is iterative, so new requirements can be incorporated on demand. Drastic changes in requirements (e.g. changing the JSON standard) will result in rework.
   • Logging lib should fulfill FFI. The safety decomposition needs to be done for the entire system to know the impact on the JSON lib.
2. Currently the entire Logging system is in baselibs repo. The long-term plan is to refactor it such way that only the interface is kept in the baselibs repo, and the rest moved to a separate module. The Logging FT will take care of refactoring.
3. It's still not clear how to bring the original nlohmann code to S-CORE with keeping the history and with a possibility to make changes. Is forking nlohmann_json repo to eclipse-score org an option? @mishu-dev will approach the Operation Community.
4. Anything to bring to the Architecture Community F2F Workshop next week? https://github.com/orgs/eclipse-score/discussions/1247
   • The Base libs FT meeting next week will be canceled due to the workshop

[FelixMoelders]

Please find attached the Application Example of TSF as pdf and the assertion to test mapping in the excel file:

• TrustableSoftwareFramework_JSON_library.pdf
• test_mapping.xlsx

[mishu-dev]

[heart] Haraga, Mihai reacted to your message:

…

________________________________ From: Felix Mölders ***@***.***> Sent: Thursday, July 3, 2025 6:17:35 AM To: eclipse-score/score ***@***.***> Cc: Haraga, Mihai ***@***.***>; Mention ***@***.***> Subject: Re: [eclipse-score/score] Base Libs FT Meeting Minutes (Discussion #1239) CAUTION: This is an external email. Do not click or open any attachments unless you recognize the sender and know that the content is safe. (http://links.conti.de/mailcheck) Please find attached the Application Example of TSF as pdf and the assertion to test mapping in the excel file: * TrustableSoftwareFramework_JSON_library.pdf<https://github.com/user-attachments/files/21030782/TrustableSoftwareFramework_JSON_library.pdf> * test_mapping.xlsx<https://github.com/user-attachments/files/21030786/test_mapping.xlsx> — Reply to this email directly, view it on GitHub<#1239 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BQSAKRKOZPLPSIS5GK66VO33GTDH7AVCNFSM6AAAAAB7PUMJN2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRUHAZDENA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[4og]

Weekly 2025-07-16

Participants

@4og
@arsibo
@FelixMoelders
@mishu-dev
@alexandruiulian10
@NilsEb
@chheis
Ankur Satle
Rahul Singh
Richard Trippel
Alekhya Reddy
@aschemmel-tech

Agenda & Meeting Minutes

1. Update from the Architecture Community F2F Workshop: https://github.com/orgs/eclipse-score/discussions/1247
   • Kickoff for defining assumed Platform AoU: https://github.com/orgs/eclipse-score/discussions/472?sort=new#discussioncomment-13751269
   • We will need to figure out where to place base libraries written in Rust. This will probably be a separate repository (= bazel module)
   • The scope of Baselibs FT is to take care of qualifying other third-party libraries.
2. The https://github.com/qnx-ports includes several JSON libs, but not nlohmann_json
   • Reason why nlohmann_json is chosen: @mishu-dev will provide a link where it was decided to use it.
3. Current status of JSON lib qualification.
   • Progress on applying TSF: setting up the trustable graph & assertions
   • Location of the fork/mirror: It will be a fork in eclipse-score github org pointing to the latest nlohmann_json release. TSF artefacts will be added to the fork. CI pipelines will be taken over from the upstream repo.
   • Feature Request: JSON Parser #822: is ready to be merged.
     - Introduce two components: for API (lib/json in baselibs repo) and the nlohmann_json .
     - Requirements need to be split to lib/json in baselibs and nlohmann_json fork.
     - Common reqs: e.g. the RFC8259: this one should be in the set of reqs of the fork.
4. Next steps for Feature Request: JSON Parser #822:
   • @arsibo will try to move the Modules structure from Com to Modules tab and inform about it in score-baselibs Slack channel.
   • Component requirements for JSON are to be relocated to Modules. Eventually, the structure should be similar to https://eclipse-score.github.io/process_description/main/folder_templates/modules/module_name/component_name/docs/index.html
   • Merge the PR to establish the basis.
   • Address changes in follow-up PRs (e.g. split to multiple components)

[lennartbecker-d]

Regarding 2:
I created some impressions on the motives to choose the nlohmann/json instead to other existing libraries here.

[4og]

Weekly 2025-07-23

Participants

@4og
@Jonas-Kirchhoff
@NilsEb
@aschemmel-tech
Alekhya Reddy
@mishu-dev
Rahul Singh
@FelixMoelders
Ankur Satle
Rutik Akolkar
Rahul Thakre
@kalu-an

Agenda & Meeting Minutes

1. TSF Framework will be presented in the Process Community meeting next week. @FelixMoelders
   • Direct nlohmann_json fork will be created with Create Nlohmann JSON FORK .eclipsefdn#58
2. Status of Feature Request: JSON Parser #822
   • Should S-CORE have a generic error-handling guideline? Ankur will raise a github issue
   • The communictaion+feo: move modules to the rigth folder #1438 is still not merged. After it is merged, the JSON Component Requests and the Requirements should be relocated to the next structure in the Modules tab.
3. Board Base Libs FT (view)
   • When adding new issues, always add ft:baselibs label
4. C++ Exceptions
   • https://github.com/orgs/eclipse-score/discussions/301 @mishu-dev, please leave a comment there to revive the discussion.
   • Helper in baselibs: https://github.com/eclipse-score/baselibs/tree/main/score/language/safecpp/aborts_upon_exception
   • From the safety perspective, it's ok to replace throws with abort.

[AlekhyaBendhi]

Weekly 2025-07-29

Participants

@aschemmel-tech
@Jonas-Kirchhoff
@alexandruiulian10
@FelixMoelders
@sankurm
@NilsEb
@richard Trippel
@RSingh1511

Agenda & Meeting Minutes

1. As agreed in the TL & Communities & CFTs Epic JSON library qualification using TSF (C++) #1460 will be part of 2025-10-01 Process Execution Audit Completed milestone to be delivered in January .
2. For ABI Compatible data types the concept is being discussed and will be part of SCORE V 1.0 ABI Data Types
3. Status of PR : Feature Request: JSON Parser #822 - to be closed and pushed it to Eclipse Score after approval @aschemmel-tech.
4. TSF Documentation and trudag tool is for TSF reports is being Demo'ed and once done they will be a PR raise for SCore. @FelixMoelders

[AlekhyaBendhi]

Weekly 2025-08-06

Participants

@aschemmel-tech
@Jonas-Kirchhoff
@alexandruiulian10
@FelixMoelders
@NilsEb
@erik
@mihai
@kalu-an

Agenda & Meeting Minutes

1. Generic comments on JSON:
   The PR:
   Comment 1: Feature Request: JSON Parser #822 (comment)
   higher level issue created: Improvement: Add an API implementation guideline #1533
   Comment 2: Feature Request: JSON Parser #822 (comment)
   Looks like this section was added: https://eclipse-score.github.io/score/pr-822/modules/baselibs/json/docs/index.html#future-extensions
2. Status of PR : Feature Request: JSON Parser #822 - to be closed and pushed it to Eclipse Score after approval @aschemmel-tech.
3. Open discussions for general topics can be found at Discussions
4. Trudag tool - continue with tool for alpha version, discussion on having versioning system is ongoing.
5. Clarification on comment for Comment to be done with @sankrum
6. Handling of C++ Exceptions as discussed in meeting with reference to nlohmann JSON - Abort is acceptable in context of nlohmann json library but not acceptable in context of eclipse score json wrapper

[aschemmel-tech]

Weekly 2025-08-13

Participants
@aschemmel-tech
@sankurm
@Jonas-Kirchhoff
@alexandruiulian10
@FelixMoelders
@Erikhu1
@mishu-dev
@RSingh1511
@arsibo

Agenda & Meeting Minutes

• @aschemmel-tech as a stand-in for @AlekhyaBendhi for this meeting
• Committers of the project are documented here: https://projects.eclipse.org/projects/automotive.score/who but additionally the CODEOWNERS files define which Committer needs to approve: see e.g. https://github.com/eclipse-score/score/blob/main/.github/CODEOWNERS
• PR Feature Request: JSON Parser #822 - finally merged
• Baselibs architecture: @arsibo asked if he can extend the baselibs module architecture according to 0.5 architecture as in https://github.com/orgs/eclipse-score/discussions/1247, at least for the components needed by logging module like "Filesystem" and "OSAL" - agreed, @arsibo will provide PR for review.
• C++ exception topic: see https://eclipse-score.github.io/score/main/contribute/development/api_guideline.html and PR Update api_guideline.rst #1610
• Discussion on Comment for Feature Request: JSON Parser #822 (comment) : @sankurm will provide example of possible solution as a comment to this MoM
  Note: C++20 is maybe possible in the future: see https://eclipse-score.github.io/score/main/contribute/development/cpp/coding_guidelines.html
  Writing C++ Code — S-CORE 0.1 documentation
• Reminder to @aschemmel-tech to provide branch for testing (by Nils over Slack)

[mishu-dev]

Weekly 2025-08-20

Participants:
@FelixMoelders
@Jonas-Kirchhoff
@alexandruiulian10
@Erikhu1
@sankurm
@RSingh1511

Agenda & Meeting Minutes:

• Discussion on Comment for Feature Request: JSON Parser #822 (comment) : @sankrum will provide example of possible solution as a comment to this MoM - preparation still in progress from @sankurm
• branch created but is mirroring the wrong repository , this should be fixed when @aschemmel-tech is back
• Update api_guideline.rst #1610 - our understanding is that allowing abort in exceptional use cases is enabled with this PR
• Decision based for nlohmann json selection for eclipse s-core - https://github.com/orgs/eclipse-score/discussions/1239#discussioncomment-13794352
• slack architecture community score-architecture-community - Markus Schu can help with process vs architecture questions

[4og]

Weekly 2025-09-03

Participants

@4og
@sankurm
@Jonas-Kirchhoff
@FScholPer
@Erikhu1
@FelixMoelders
@rtrippel-dfine
@aschemmel-tech
@AlekhyaBendhi
@RSingh1511

Agenda & Meeting Minutes

1. Review of open points from the last meeting
   • Update api_guideline.rst #1610 should be raised in Arch Community as a request for review. @qor-lb please add it to the agenda.
2. Status of TSF in S-CORE
   • D-fine is working on TSF documentation
   • It's not clear yet how the fork is updated from the upstream (issue: Define the process how the nlohmann fork is updated #1700).
   • Trudag tool is to be used in S-CORE as a pilot (agreed in the Process community). The tool generates a trustable report for a release. The safety arguments to the code, and if the code changes, the tool detects it and invalidate the affected arguments.
   • Safety qualification of TSF and its tooling is in scope of the Process community. The auditors are aware of S-CORE using TSF.
   • @Jonas-Kirchhoff will share the current state of applying TSF for nlohmann for @aschemmel-tech to review. @FelixMoelders will schedule an appointment with @aschemmel-tech this Friday.
   • Library-agnostic data types in S-CORE.
     • It's part of the JSON wrapper in baselibs repo.
   • Should we have separate repos?
     • Currently the json_test_data is a branch in https://github.com/eclipse-score/inc_nlohmann_json/tree/json_test_data_version_3_1_0_mirror
     • for documentation, nlohmann_json fork, and the test data (fork of https://github.com/nlohmann/json_test_data).
     • according to TSF, all dependencies must be mirrored.
     • It's probably ok to have 2 repos: nlohmann_json fork with added documentation and the json_test_data fork. @FScholPer will discuss this with @AlexanderLanin.
     • The https://github.com/eclipse-score/inc_json can be deleted. @FScholPer will discuss this with @AlexanderLanin.
3. Current work on align the code in Baselibs with S-CORE process
   • Feature architecture for Baselibs: Committing Base Libs Architecture Document  #1656 please review.
   • Component description, architecture, and requirements are WIP at BMW.
4. For the next week meeting: have a demo of the current state of TSF (if it's ready).

[4og]

Weekly 2025-09-10

Participants

@4og
@Jonas-Kirchhoff
@FelixMoelders
@Erikhu1
@mishu-dev
@FScholPer
@RSingh1511

Agenda & Meeting Minutes

1. Reviews
   • Update api_guideline.rst #1610
   • Committing Base Libs Architecture Document  #1656
2. Outcome of the meeting last week regarding the current state of applying TSF for nlohmann json.
   • @aschemmel-tech and @masc2023 provided a review on the current state of the TSF documentation: TSF documentation findings score-json/json#73
   • The https://github.com/score-json reflects the current state of the TSF documentation. Later the documentation is going to be migrated of eclipse-score org.
3. Demo of the current state of TSF.
   • See https://score-json.github.io/json/main/report.html
   • Feedback is welcome.
4. Conclusion on the repository discussion.
   • Keep the https://github.com/eclipse-score/inc_nlohmann_json repository and three branches (mirror of upstream develop branch, mirror of the test data, and a pinned release that is subject for qualification).
   • Keep the https://github.com/eclipse-score/inc_json for now.
   • This decision will be revisited after S-CORE 0.5 release.
5. Rust library for manipulating JSON files
   • Currently not in scope for Baselibs FT (for S-CORE 0.5).
6. QNX platform for use in the reference integration is not ready. It means that we won't be able to provide any evidence in the trustable report yet.
   • See also https://github.com/orgs/eclipse-score/discussions/1692
7. AoUs in TSF
   • They are part of the report. See example: https://score-json.github.io/json/main/generated/trustable_report_for_Software.html#compliance-for-aou
   • How are platform AoU handled in TSF? @masc2023