Communication CFT Weekly [2026-01-26]

[LittleHuba]

Participants

@darkwisebear
@SebastianGrob
@lurtz
@crimson11
@NEOatNHNG
@JochenSatETAS
@bemerybmw
Vadim Selinger
@mina-hamdi
@dasoho
@alexandruiulian10
@LittleHuba

Agenda

1. Presentation of current status of support for methods (by @bemerybmw)
2. How to retain our meeting minutes

Minutes

to 1.

• Methods functional but not feature complete (partially pending review)
• Pending:
  • Partial restart
  • Message passing
  • Further integration tests
    Feature description: https://github.com/eclipse-score/communication/blob/main/score/mw/com/design/methods/README.md

Timeline: merging of all pending changes within the week (potential bugfixes excluded)

Q: What about safety qualification?

Requirements are created and opensourced
FMEA: WIP
Quality KPIs are not yet achieved: WIP

Q: Are there architectural documents? / Is there user POV documentation?

Not yet fully created -> Will be opensourced as soon as finished
We are working on getting full doxygen documentation for our public API.
Some methods are already covered, others will follow.
High-level documentation of classes is currently missing.

Q: Where there changes to the configuration for method support?

Yes, at least commit eclipse-score/communication@f0aa57b (please check the history of this file to see if there are more)

Q: Did you implement a single method restriction for methods?

E.g. block an allowed consumer to access a single method?

There is currently no mechanism to restrict access to specific items of an interface for specific consumers.
Proxies can tailor what methods they want to use (spend resources for) but this is not enforced by the Skeleton side.
Implementation (only concerning methods) is feasible but currently nobody raised interest in adding this functionality.

to 2. How to retain our meeting minutes

We are running out of discussions in the project (number limited by GitHub).
TLC raised the question of how to handle this in the future.
To come up with a proposal from the actual users, we want to collect ideas how to solve this for communication.
Proposal will be discussed in TLC to align all modules to a common way.

Please prepare ideas for our next meeting.

@LittleHuba Create PRs for meeting minutes to retain them in the repository
@lurtz Create PRs and merge them after one week (in next meeting minutes)
@darkwisebear First point on the agenda always to approve the last meeting minutes

Questions:

• Do we want to have this in our repository or in a separate one?
• How to handle attachments (powerpoint slides for example)?
• Common search structure for meeting minutes?