This page intends to contain the agenda for next meeting and notes from previous meeting. At the bottom is a template for the agenda. General agenda points like discussion on PRs and issues may be skipped if discussion on prioritized topics takes too long time.

...

Agenda  2023-05-02

• Welcome and Compliance statement

Welcome to the COVESA VSS Meeting!

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

• Agenda discussion - anything that needs to be added?
• Prioritized topics
  • Release 4.0 Planning
    • Agree on what needs to be in - which PRs/features
      • Struct overlay and documentation.
        • Overlay part fixed, minor doc update remaining.
      • https://github.com/COVESA/vehicle_signal_specification/pull/540
      • https://github.com/COVESA/vehicle_signal_specification/pull/546
      • https://github.com/COVESA/vehicle_signal_specification/pull/577
      • https://github.com/COVESA/vehicle_signal_specification/issues/574
        • Still relevant?
    • Proposal from meeting before AMM
      
      • Feature Freeze May 2nd (just after AMM)
      • Pre-release/Release-candidate to be released first week of May
        • To be done by Erik
      • Actual release two weeks later
      • Any fixes (PRs) needed for VSS 4.0 after release candidate must be directed to specific branch (release/4.0)
        • Erik to describe release candidate workflow
  • New Issue 586.
  • Best practices - VSS design principles
    • Stephen
      • Would be good to have design principles that we can refer to, like doing X is aligned with principle Y
      • I will ask Felix and Daniel to get input, like on "what is a branch" from a data science view
      • I will drive it.
    • Daniel: I can support
    • Nick: Would be a good idea, a lot of collective opinions is not documented
      • Including how we express what language to use (american vs english), date formats, ...
    • Erik: Where to handle calls/meetings, in this or in other. This meeting is often quite busy.
    • Where/how to be synched on slack
    • Announced in this meeting.
    • Daniel: One ontology work that is ongoing is to come up with keywords, calls 30 minutes before this one, I can share link
  • Fulup presented https://github.com/eclipse/kuksa.val.feeders/issues/94
    • Concerns "security tags" in VSS - an area where COVESA might do something
• Decision on old open PRs
• Open Pull Requests VSS
  • Please review, minor ones will be merged next week unless there are remarks
• Open Pull Requests VSS-Tools
  • Please review, minor ones will be merged next week unless there are remarks
• Issues VSS
  • Please check https://github.com/COVESA/vehicle_signal_specification/issues/567
• Issues VSS-Tools
• Prioritized topics for next meeting
  • VSS 4.0 release planning
    • Remaining features
    • Date for release and release candidate

Meeting Notes  2023-04-18

• Welcome and Compliance statement

...