...

• Agenda discussion - anything that needs to be added?
• Prioritized Topics:
• Decision on old open PRs
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Discussions VSS
• Discussions VSS-tools
• Prioritized topics for next meeting

Meeting notes  2024-11-19

• GraphQL discussion (15 minutes)
• Wiki-pages - https://github.com/COVESA/vehicle_signal_specification/wiki
  • Some of them quite outdated - which makes it difficult to read
  • Proposal: Delete old layers and struct pages
    • They will still exist in history at if you clone https://github.com/COVESA/vehicle_signal_specification.wiki.git 
  • FAQ - Anyone interested in contributing? Or integrate into documentation?

Meeting notes  2024-11-12

• Decision on old PRs (from 2023)
• What to do with old issues
  • Alignment: OK to close older inactive issues.
  • Add comment before closing
  • Stefan; Keep insurance issue open
  • Ted: Interested in mathematical - https://github.com/COVESA/vehicle_signal_specification/issues/738
  • AP: Erik to clean up, close obvious ones, if in doubt keep or discuss

Meeting notes  2024-11-05

• PRs/Issues
• Old PRs (from 2023)
  • Erik propose to close them if no progress is planned
  • Stephen: If close add a positive stamenet, like "You are welcome to reopen on progress)
  • To be further discussed next week

Meeting notes  2024-10-29

• PRs/Issues

Meeting notes  2024-10-22

• Vehicle Motion PR- https://github.com/COVESA/vehicle_signal_specification/pull/785
  • Daniel (BMW): Relationship to ISO standard
    • Markus: Based on ISO8855 where relevant
  • Sebastian Schildt: Intended use-cases
    • Traction control, autonomous driving
  • Sebastian: Could possibly be overlay
  • Erik: Signals in PR today added to a separate subbranch Vehicle.MotionManagement.
  • Daniel: we need to tackle that instancea are repeated
  • Daniel: Are all datastreams, so data will change during driving
  • Matthias: All changing, sensor used for feedback channel, no attributes
  • Discussion on duality of sensor/actuator.
  • Daniel: If we allow different signals for target/current value - we need to consider it also for other areas.
  • erik: please review and discuss internally, continued discussion next meeting.
• Ulf: VISSR - File transfer - try to generate binary file from catalog with struct
  • Erik: You need to specify that the exporter support types

Meeting notes  2024-10-15

• VSS 5.0 released - https://github.com/COVESA/vehicle_signal_specification/releases/tag/v5.0

Meeting notes  2024-10-01

• VSS RC https://github.com/COVESA/vehicle_signal_specification/releases/tag/v5.0rc0
  • Give comments comments before end of this week
  • Erik to create official release next week
• AMM thoughts
  • Erik: Showed slides from wrapup session
  • Presentations: COVESA All Member Meeting ~ September 25-26, 2024
  • Paul: VSS to Android mapping, interest in AOSP group to revisit that
    • Erik: See https://github.com/COVESA/vss-tools/blob/master/obsolete/vspec2aaproperties/vspec2prop_mapping.yml
    • https://wiki.covesa.global/download/attachments/12124756/AOSP-VSS-Mapping-v1.7.xlsx?version=1&modificationDate=1676939208750&api=v2
    • VSS to AOSP translation - WBS
    • If we have multiple OEMs Google is interested in listening
  • Paul: How does camera data fit with VSS was mentioned
    • Erik: Historical approach - VSS solutions (like VISS, Kuksa) not suited for streaming data like camera
    • Stefan: Does not be videos, can be stream of objects like obstacles, could be input to VSS
    • Erik: There have been in discussions in the past to support events in VSS, but no majority in favor at that time.
  • Next AMM (Spring 2025) planned for Milan, Italy, dates still uncertain

Meeting notes  2024-09-17

• No meeting next week (AMM)
• VSS-tools 5.0
  • Review "Release Blockers"
  • Code freeze OK after that?
  • If so - goal to create Release Candidate end of this week
    • COnclusion: Ok

Meeting notes  2024-09-10

• VSS-tools 5.0 (pre-release)
  • Anything remaining?
    • Remaining items SAMM
  • Vspec2ttl - currently broken - anyone interested in maintaining it - see https://github.com/COVESA/vss-tools/issues/403
  • Release content for "new" tools? - see https://github.com/COVESA/vehicle_signal_specification/pull/772
    • Sebastian Schl: vote for mandatory in make
• Object Detection
• Stefan SellSchopp - VSS - AOSP discussions ongoing

Meeting notes  2024-09-03

• Regular
  • VSS PR
  • VSS-Tools PR
  • VSS Issues
  • VSS-Tools Issues
  • VSS Discussions
• VSS (tools) 5.0 release - pre-release
• Need for 4.2.1 release - see https://github.com/COVESA/vss-tools/pull/397
  • Just tag?
• Formatting Proposal (Adnan)
  • https://github.com/COVESA/vehicle_signal_specification/pull/771

Meeting notes  2024-08-27

ApiGear intro by Siili Auto (https://github.com/COVESA/vss-tools/pull/391) - merged 

VSS-tools:

• https://github.com/COVESA/vss-tools/pull/395 : Prerequisite for a good way of removing vss-tools submodule, (and general quality-of-life improvement for binary users)

Meeting notes  2024-08-20

APIgear Intro will be NEXT meeting (27th)

VSS-Tools

• merged core rework: Let's see what the fallout is, if any https://github.com/COVESA/vss-tools/pull/382

VSS

• Do we still need the submodule:https://github.com/COVESA/vehicle_signal_specification/issues/767

Meeting notes  2024-08-13

VSS-spec

• PR 755, approved by Sebastian and merged.
• PR 761, merged.

...