VSOMEIP Meeting Notes

20240819 Meeting

Agenda

• Release 3.5.1 done
  • Has a bug in it.  3.5.2 will be release soon
  • Release page will be updated https://github.com/COVESA/vsomeip/releases
  • Need to communicate clearly
• Discussed https://github.com/COVESA/capicxx-someip-runtime/pull/37
  • Is a bug.  If greater than 1 byte no serialization.
• https://github.com/COVESA/capicxx-someip-runtime/issues/36
• Potential
  • 1 Releases per quarter
  • Hard to do planned release due to other issues
  • Discuss how to communicate plans internally
  • Defects and features
  • Use monthly meetings to communicate/understand what is important

20240819 Meeting

Agenda

• Recommendations from Technical Steering Team review of vsomeip project
  • Identify and elect additional maintainers from other organizations
  • Define and adopt governance and way of working
    • Contribution Process 
      • Draft Process Start
    • Release Process
  • Determine best way to increase velocity
• Issues and Discussions

20230821 Meeting

Agenda

A discussion of how to handle specific vSOMEIP issues with the maintainers.

• Decided to meet monthly on the third Monday of each month at 7am PT / 10am ET / 16:00 CET.  See the Community Calendar to subscribe.
• Will use GitHub Issues as needed
• Will use Slack and this wiki 
• Next Meeting Sept 18

20230201 Meeting

Agenda

A discussion of how to handle specific vSOMEIP issues with the maintainers.

• Discuss code changes in the vSOMEIP Open Source Project.
• Discuss future maintenance

Attendees

Aram

Adnan Bekan - BMW

Alex Jasper - Mercedes

Andre Oliveira - BMW

Fabio Monteiro - BMW

Gonçalo - BMW

Gunnar Anderson - Mercedes

Jürgen Gehring - BMW

Saravana Raja - BMW

Paul Boyes - COVESA

Notes

Group discussed how to best manage and submit issues, commits and pull requests to vSOMEIP. 

This was an initial meeting.  It is expected there will be more

Issues listed were:

• Subscribing to events
• Current version
• Maintenance gaps between version 2 and 3

An open, ongoing meeting was suggested.  

What is required to commit was questioned.  

Action Items

Paul Boyes to follow back up with group on what is required to contribute code/interact

Gunnar Andersson to follow up with Mercedes to determine how they would like to interact