Meeting Minutes: 2025/02/27 OSI CCB

[AsamDiegoSanchez]

Location	MS Teams
Date	27/02/2025
Time	14:00 - 15:00 (CET)
Note taker	CoPilot

Antitrust reminder

Every participant acknowledges that they know the content of the antitrust reminder: ASAM Antitrust Reminder

Participants

Participant	Company
Pierre Mai
Tamir Benjo
Eli Alkhazov
Andreas Tingberg
Diego Sanchez
Yash Shah

---

Agenda/Goals

TOP	Topic	Status
1	TSC Meeting outcome
2	Prepare next steps: Budget and Roadmap for approved proposals
3	Assign Coordination Group responsibles (x2)
4	Organize meeting series: https://doodle.com/meeting/participate/id/aAW4rAOd

Minutes

Generated by AI. Make sure to check for accuracy.
Meeting notes:

Participation Reminder:
Diego reminded the group about the importance of active participation in projects and meetings, emphasizing that if someone misses three consecutive meetings without communication, the group can decide to remove them.

TSC Meeting Feedback:
Diego provided feedback from the recent TSC meeting, mentioning that 14 projects were presented and approved to start.
The final budget and roadmap for these projects will be presented in the next TSC meeting in April.

OSI Quality Checker Project:
Pierre and Yash discussed the TSC's concern about the lack of participants from the quality checker framework in the OSI Quality Checker project. Pierre explained that the technical coherence of projects should be ascertained by the CCBs and not necessarily by project participation. The quality checker framework people are expected to chime in through the CCB of the quality checker framework. He explained that the framework was designed to make the checks independent of the framework itself.
Yash mentioned that there was a sentence in the proposal indicating that changes in the quality checker framework might be needed for certain support. This was the reason for the TSC's concern. Pierre added that the project has a connection to the CCB of the quality checker framework to address any necessary changes or enhancements.

Coordination Group Participation:
Diego mentioned the formation of the Coordination Group with CCB members and the need for 2 volunteers: Pierre Mai and Andreas Tinberg volunteered to participate in the Coordination Group.

Project Budget and Roadmap:
Diego discussed the need to check the approved projects for budget requirements and roadmap planning. Pierre confirmed that the OSI projects do not require a budget, except for the optional part of the checker bundle improvements. This optional part involves integrating visualizations using ListPick, which may require additional funding.

Roadmap Planning: Diego highlighted the importance of roadmap planning for the approved projects. The roadmap will outline the steps and timeline for each project, ensuring that they are executed efficiently and effectively.

Sensor Modelling Improvements:
Pierre emphasized the importance of aligning with the ISO 23150 standard for sensor modelling improvements. He volunteered to lead the discussions with ISO and invited Andreas Tinberg to join.
Pierre stressed the importance of aligning the sensor modelling improvements with the ISO 23150 standard. This alignment is crucial to ensure that the standards are consistent and compatible.
He volunteered to lead the discussions with ISO regarding the alignment of sensor modelling improvements. He will coordinate with the relevant parties to ensure that the standards are harmonized.

OSI Multi-Trace File Format:
Pierre explained the goal of creating a multi-trace file format for OSI, using the mcap file format. He will start inviting participants for a meeting series to work on this project. The goal t is to create a file format that can bundle multiple traces into one file. This will improve the efficiency and usability of the trace files.
The project will use the mcap file format, which is lightweight and suitable for the needs of the OSI project. The mcap format is already used in various projects and has a codebase that can be built upon.
Pierre will start inviting participants for a meeting series to work on the OSI Multi-Trace File Format project. The meetings will focus on finalizing the specifications and implementation details of the new file format.

OSI Checker Bundle:
It aims to create a mapping of rule sets to the quality checker framework. He mentioned the optional part of integrating visualizations using LichtBlick (https://github.com/Lichtblick-Suite/lichtblick).
This will involve defining unique names for the rules and automatically generating the code needed to check them.
The project will integrate the rule sets with the quality checker framework, ensuring that the checks are compatible and effective. This will involve minimal changes to the quality checker framework itself.

The optional part of the project involves integrating visualizations using LichtBlick. This will enhance the usability of the checker bundle by providing visual representations of the checks and their results.

Maintenance Project:
Pierre and Diego discussed handling the maintenance project as part of the CCB work. They agreed to review the backlog of issues in GitHub and tag relevant issues for maintenance with the Label "OSIMaintenance".
Group agreed to review the backlog of issues in GitHub and tag relevant issues for maintenance. This will help prioritize and address the most critical maintenance tasks.

Project Participation and Coordination:
It was suggested mapping CCB members to the various projects to ensure proper involvement and coordination. Diego and Yash agreed to prepare a table with the names of participants in each project.

Follow-up tasks:

• Project Enrollment Update: Provide an up-to-date list of enrolled participants in each of the 14 projects. (ASAM)
• Contact Persival for OSI CCB involvement (ASAM)
• Coordination Group Meeting Schedule: Prepare a doodle poll to schedule the coordination group meetings and share it (ASAM)
• ISO Alignment Meeting: Schedule a meeting with the relevant ISO side to start discussions on the 23150 alignment. (Pierre)
• Maintenance: review of issues in GitHub repository (OSI CCB)

[jdsika]

The decisions of the CCB regrding different issues and pull requests should be documented in those as well. It is inconvinient to have decisions separate to the issue?

[AsamDiegoSanchez]

The decisions of the CCB regrding different issues and pull requests should be documented in those as well. It is inconvinient to have decisions separate to the issue?

Yes, this will be the intent, to have all the relevant decisions made by the CCB located in the meeting minutes. This issue here is just the placeholder to the upcoming meeting next week, to add or change points in the agenda prior the meeting.