Communication CFT Weekly [2025-12-08]

[LittleHuba]

Participants

Agenda

1. Status update from SOME/IP Breakout group.
   • Which pitch is the basis for the future work
   • What is the working model (feature branch/feature flag/etc.)

Meeting Minutes

[limdor]

Participants:
@ZoranCutura
@mikehaller
@JochenSatETAS
@mina-hamdi
@SebastianGrob
@Abhishek2581
@arsibo
@lurtz
@piotrchodorowski
@darkwisebear
@NEOatNHNG
@limdor
@bharatGoswami8
@alexandruiulian10
@dasoho

Which pitch is the basis for the future work:

• Three proposals have been made:
  • QORIX SOME/IP gateway PoC
  • ETAS initial SOME/IP gateway prototype
  • Elektrobits SOME/IP Gateway PoC
• If there are no objections in the following week, ETAS initial SOME/IP gateway prototype will be taken.
• Minuts from the workshop: [Contribution Request] SOME/IP Gateway #1769

How to proceed with the SOME/IP development:

• It could be continued on the incubator repository, but it will be required to change code in the communication repository. That might be quite hard.
• It could be done in a branch (preferred), but still would need to have committers rights to be able to accept changes in the feature branch. If we cannot make people from the SOME/IP group as committers, we can still informally nominate them as reviewers, and then the committers just approve it without further review if it is targeting the feature branch. An alternative would be to do it on a fork but the disadvantage is that then there is no common neutral place.
• In any case, it should be considered that it is done in a incremental way that later can be merged incrementally to not have huge PRs.
• Feature toggles should be used to be able to enable/disable the feature (see https://martinfowler.com/articles/feature-toggles.html)

Meetings during Christmas season:

• Proposal: Cancel meetings between December 22nd and January 6th

[FScholPer]

@limdor @LittleHuba please take a look on the eclipse-score/inc_someip_gateway#2 before merging