Communication CFT Weekly [2025-07-21]

[LittleHuba]

Participants

@LittleHuba
@dasoho
@kalu-an
@ZoranCutura
@FelixMoelders
@mishu-dev
@alexandruiulian10
@vinodreddy-g
@darkwisebear

Agenda

1. Status update from FR teams
2. Status from Rust API
3. Status of tickets and PRs

Minutes

to 1.

Gateway

@ZoranCutura

Interest group to be created

Five sub-issues were created
Work on tickets is distributed
Branch from Zoran must be moved to S-CORE repository to satisfy OSS process from BMW so that BMW-colleagues can work based on that branch.

ABI Datatypes

@awillenbuecher-xq-tec (representative in this round @vinodreddy-g)

Interest group to be created

Updates to the FR PR are added

• List of datatypes was agreed
• Type reflection is for now removed

InterVM

@FScholPer

https://github.com/orgs/eclipse-score/discussions/1468

to 2.

API available for producer and consumer
Example for both sides available
Example with cross-programming-language scenario is not fully implemented (hash calculation is not performed on Rust side)

Meeting for missing feature in Rust API is created for this week

Please try the API out! We need usecases to see whether the API is usable.

to 3.

eclipse-score/communication#23 (to be check in more exhaustive test suite)
-> consider this PR once the above one is merged: eclipse-score/communication#26
eclipse-score/communication#24 (conflict resolution necessary, author not in meeting: no status update)

List of tickets to distribute in next sync

• Epic: Revisit feature requirements of communication #763
• Migrate UMLet to PlantUML communication#24 (review of diagrams)