You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
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.
- Compliance statement - TBD
- Welcome and agenda discussion - anything that needs to be added?
- Prioritized topics
- Open Pull Requests VSS
- Open Pull Requests VSS-Tools
- Issues VSS
- Issues VSS-Tools
- Prioritized topics for next meeting
If you have a topic you want to prioritize please add it here. We do however have the ambition to regularly discuss recent issues and pull requests, so no need to explicitly mentions a PR unless it needs to be prioritized:
- Compliance statement - TBD
- Welcome and agenda discussion - anything that needs to be added?
- Prioritized topics
- Continued struct decision, focus on recommendations/limitations, why we need it, rationale (https://github.com/COVESA/vehicle_signal_specification/pull/511)
- Meeting notes:
- Krishna - for types - there could be subtrees working as namespace. Erik to improve description.
- Adnan - we need to come up with how to use "Aggregate"
- Krishna - could be useful for aggregating
- Adnan - we need to explain advantage of aggregate vs struct
- Erik to create proposal in document
- If no further comments, next step is to identify work packages in detail and do estimation for roadmap
- Ulf to present some roadmap ideas (15-20 minutes)
- Proposals:
- Reason - to get a domain agnostic taxanomy
- Move "rule set" to new specification project, VSS keeps the catalog.
- Sebastian: Could be an idea to scope it to "mobility only"
- Erik: Could at least be idea to have a vision/mission for the "rule set" to primarily support mobility use cases
- Daniel: Integrating/reference domains in Yaml does not make sense, Ontology is a better choice. This is the next step of VSSo.
- How to proceed:
- Document to be uploaded
- Discussion to be continued at some later time (not urgent)
- Interesting topic for next AMM, including VSS ↔ VSSo relationship
- Summary for vote of Allowed (https://github.com/COVESA/vehicle_signal_specification/issues/502)
- PR/Change governance (https://github.com/COVESA/vehicle_signal_specification/issues/515)
Overlays on expanded tree (https://github.com/COVESA/vss-tools/issues/201)Release Cadence/Roadmap (https://github.com/COVESA/vehicle_signal_specification/issues/513)
- Open Pull Requests VSS
- Open Pull Requests VSS-Tools
- Issues VSS
- Issues VSS-Tools
- Prioritized topics for next meeting
Meeting 2022-11-29
- Compliance statement - TBD
- Welcome and agenda discussion - anything that needs to be added?
- Prioritized topics
- Open Pull Requests VSS
- Skipped due to lack of time
- Open Pull Requests VSS-Tools
- Skipped due to lack of time
- Issues VSS
- Skipped due to lack of time
- Issues VSS-Tools
- Skipped due to lack of time
- Prioritized topics for next meeting
- Continued struct decision, focus on recommendations/limitations, why we need it, rationale
- Ulf to present some roadmap ideas (15-20 minuets)
- Summary for vote of Allowed
- Release cadence/Roadmap
Agenda Template
- Compliance statement - TBD
- Welcome and agenda discussion - anything that needs to be added?
- Prioritized topics
- Open Pull Requests VSS
- Open Pull Requests VSS-Tools
- Issues VSS
- Issues VSS-Tools
- Prioritized topics for next meeting