...
- AMM VSS Topics - Topic proposals
- VSS Working Session 9.45-11.30 Wednesday (DEG also have some time for working sessions)
- Moved to afternoon 15.30-17.30 for allow for remote participation
- Anything particular someone wants to bring up or present?
- Suggestions:
- Erik: Instance handling and "VSS Expanded Tree" - How do you want to handle instances? How do you handle instances today
- VSS Format and Tooling (Erik)
- General AMM
- Still possible to propose slots to Paul but filling up
- New and old PRs
- New issues
- Issue handling - general
- What to do with issues where there has not been any progress in many months
- Keep forever or decide on an auto-close policy?
- Should be doable at least for suggestions/discussions
- For limitations/defects - possibly manage elsewhere? Like in documentation for the related tool.
- Example: Signal Accuracy - https://github.com/COVESA/vehicle_signal_specification/issues/105
- Possible improvement area, but no-one seems to be interesting actively driving it
- Example: Emission standards - https://github.com/COVESA/vehicle_signal_specification/issues/394
- Possible improvement area, but no-one seems to be interesting actively driving it
- Issues are of different types today, some maybe fit better as discussion, but also then we have a question on how long we want them to exist
- Possible improvement areas
- Actual limitations/error (which no-one intends to fix)
- Proposed Handling (to be discussed):
- Close issues after 6 months of inactivity
- If we have agreed/decided something in the discussion - reflect that in VSS or VSS-tools documentation before closing the issues
- If the issue concerns a known limitation/error, then document that in a file for known limitations in the repo
- Example: Generator
vspec2something
cannot handle the signal name ggg
as that is a a reserved word in something
.
- MoM:
- Daniel: think it is good to have something, so that issues are decreasing
- No objection to closing inactive items
- Android tooling
- https://github.com/COVESA/vss-tools/issues/192
- Erik:
- My assumption is that we want to keep the work but that no-one intends to create a real tool out of it in the next year(s)
- Suggestions:
- Create a better branch name and add a wiki page explaining purpose of the branch
- Or integrate it into current as "prototype"
- MoM (old): Think about it, discussion to be continued
- MoM: No opinion
Meeting notes 2024-02-13:
...
{"serverDuration": 126, "requestCorrelationId": "5040f3b6e46ca37c"}