We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 60 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.

Draft Meeting notes  2023-05-22

(Erik will not join)

  • 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 Status
      • V4.0 released  https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.0
      • Topics addressed during RC-phase. If someone wants an alternative solution as long term solution they are welcome to create a PR
        • d added as prefix to string literals that could be numbers, like '33'. Just using _33 is not supported by all code generators working on DDS IDL.
        • Type checker for structs updated to support arrays of struct
        • Error now given if type root is not a branch (as some tools like vspec2protobuf can not handle struct as root)
      • Daniel to introduce what has been done in VSSo (wiki page)
  • Decision on old open PRs
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting

Meeting notes  2023-05-16

  • 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.


Meeting notes  2023-05-09

  • 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.


Meeting notes  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
    • 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
  • 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

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
    • Structs Status
      • IDL: https://github.com/COVESA/vss-tools/pull/262
        • Related: https://github.com/COVESA/vehicle_signal_specification/pull/576/files
        • Discussion:
          • Sebastian: Proposal is a bit different, new concept, nothing prevents merging PR from Krishna so old style converter support structs, or wait with both
          • Neil: Do we want to restruct existing signals in catalog
          • Krishna: Not yet
          • Sebastian - but do we want hints, if tools are "perfect"?
          • Adnan: Could be an idea to collect starting points for struct candidates (after 4.0)
          • Ulf: A signal represent a datapoint, captured at a specific time, similar approach for structs, all properties within the struct are all captured at the same point in them. fits well to GPS, but not for example door/window signals as they are not captured at same point in time.
        • Decision: Do not add IDL for 4.0
      • For VSS 4.0 - status (to be confirmed):
        • Done: Protobuf, JSON, CSV, Yaml
        • Ongoing: DDSIDL
        • Not done: Overlays, Multi -vt, Franca, Binary, Ttl (contrib), Graphql
        • Needs revisit: Documentation (to indicate status)
      • Discussion:
        • Sebastian: What is our long term approach - will struct support in long run be added to Franca, Binary, Ttl (contrib), Graphql
        • Krishna: Needs expertise support
        • Ulf: Binary will come a few weeks after AMM
        • Pierre: What if we later detect if we need to change syntax of structs to support e.g. Graphql
        • Krishna: Seems to be acceptance of releasing VSS 4.0 with limitations, but fast resolving of remaining topics wanted
        • Erik: Ok to relase VSS 4.0, plan remaining tools/limitations to VSS 4.1
        • Daniel: Could possibly contribute to TTL, dependency to VSSo, refactoring discussion in progress
        • Neil: Have we an idea what signals should be put in struct
        • Stephen: Not intending to refactor existing tree. Best practices document needed.
        • Erik: What we have said so far - structs shall be restrictevly used in standard catalog, possible candidate Position (lat/lon)
        • Daniel: Not clear to me when to use struct vs aggregate. Risk using aggregate on branches if there is no rule-set to branches. There should simple rule-set for branches in general. No clear criteria used as of today.
        • Erik: branches as of today is mostly to get unique names
        • Krishna: Overlays and doc can be fixed for relase, but can we release withou strucs
    • Release 4.0 Planning
    • Screen off PR - https://github.com/COVESA/vehicle_signal_specification/pull/577
      • How to represent "off time" - duration or absolute time?
        • Duration in seconds
  • 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
  • Issues VSS-Tools
  • Prioritized topics for next meeting
    • VSS 4.0 release planning
      • Remaining features
      • Date for release and release candidate

Agenda  2023-04-11

  • 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
    • Structs Status
    • Display Idle Time - see https://github.com/COVESA/vehicle_signal_specification/issues/567
    • List DTCs in VSS
      • Currently there are signals for DTCs in OBD branch, but just a list of strings
      • Question: Shall we model "all" DTCs in the model?
      • Sebastian: Currently no ongoing work to model DTCs in VSS
      • V Raikar: Should signals corresponding to DTCs be represented in tree?
      • Erik: We have some signals representing errors today, but they are just boolean
      • Erik: A more specific proposal/idea would be interesting to discuss in this meeting.
  • 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
  • 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-04

  • Compliance statement


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.


  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Structs Status
      • Textual Update - Use "ComplexDataTypes"
      • ProtoBuf - convention one file per message
      • DDSIDL - is extension style valid
    • UUID update (postponed from next meeting)
      • Adnan:
        • Idea use UUID to define signal/property, not location
        • For binary exchange we need to share schema in advance. Can we use small UUIDs. One byte to identify vendor/overlay, other two bytes for every specific leaf. Stored in a unique way.
      • Krishna: We need to optimize transfer, assign unique identifier based on VSS. Shall it be left to implementer?
      • Erik: Should be possible to support multiple UUID-technologies in vss-tools
      • Sebastian: Canonical UUIDs with clear formula so they are reproducable are great
      • Nick: Have you considered ASN.1?
    • EV-charging repository: https://github.com/COVESA/ev_charging
  • 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
  • Issues VSS-Tools
  • Prioritized topics for next meeting

Meeting Notes 2023-03-28

  • Compliance statement


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 the 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.


  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Consolidating structs
      • Initial exporters - approach currently to get two files, ones for signals and one for types
      • Two files may not make sense for all exporters
      • Two files pro - matches input
      • One file pros - consolidated view, self sufficient,
      • Krishna wants input - what do we want.
      • Ulf: Value in one file, but configurable (where applicable) best
      • Sebastian: We do not need to do the same for all exporters. Better to have discussion tool by tool.
      • JSON:
        • Krishna: One usage imported into other tool, would be easier with single tool.
        • Sebastian: One file better
        • Could be user option.
        • Krishna: Will make output argument optional. if not present single file will be generated.
    • UUID update (postpone to next meeting)
    • Jeremy Vaysettes (Michelin)
  • Decision on old open PRs
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting

Meeting notes 2023-03-21


  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Albert Kos: Gaia-X - (http://www.gaiax4ageda.de/) interesting to get surrounding objects into VSS. Possible to setup a meeting?
      • Sebastian: Paul Boyes could organize meeting if needed
      • Ulf: No meeting necessarily needed, you could issue/PR.
      • Albert to start by creating issues (in 3 weeks)
    • VSS-Tools - Line endings JSON?
      • Result - no line breaks
    • Tool limitations
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting

Meeting notes 2023-03-14


  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Intro to VSS - 16.00 CET Tomorrow
    • VSS-Tools - Line endings JSON?
      • Result - no line breaks
    • Issue 526
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting

Meeting notes 2023-03-07

Meeting notes 2023-02-28

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • INFO: VSS 3.1 released
    • Wanted features for VSS 4.0 end of April (before AMM?)
      • Structs support, but what more?
      • Moving documentation to new repo?
        • Meeting notes -seems reasonable
    • AMM - what sessions are needed/wanted. What do we want to cover in the workshops
      • Ulf: Slot/presentation on how evolving VSS ("multiple trees")
        • Erik: Related to charging station tree discussion, we need to discuss governance of new catalogs, like where and how shall charging station tree be stored and maintained
      • Sebastian: CAN Feeder - dbc mapping
      • Sebastian: Security approaches - KUKSA tokens changes and comparison to VISS
      • Adnan: VSSo and Taxonomy - see https://github.com/COVESA/vehicle_signal_specification/issues/548
    • Open PRs - quite a lot
    • VSS structure
  • Decision on old open PRs
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting

Meeting notes 2023-02-21

Meeting notes 2023-02-14

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Struct support
      • Status report
      • Exporters - how do we expect them to handle struct data
        • Struct information generated in same file or other file
        • Likely straightforward to implement support in vspec2json, vspec2csv, vspec2yaml
        • Volunteers for vspec2binary, vspec2ddsidl, vspec2franca, vspec2graphql?
          • And contrib tools: vspec2protobuf, vspec2ttl
          • Daniel Alvarez will likely look at the vspec2ttl
          • Ulf feel responsibility for binary tool.
          • Sebastian can check with those who developed vspec2ddsidl
        • AP: Erik to update or create issue to track what is needed for the major release in April
    • Workshop this week
      • Agenda at Data Expert Group - Workshop 2023 - Q1
      • All welcome
      • Attendees: erik, Ulf, Daniel (partially, 14-16 CET), Adnan, Sebastian (partially, +0.25)
      • AP: Paul to cancel related COVESA meetings during the same timeslots.
    • "Extra day" at AMM for deeper discussions, possibly Friday after AMM, possibly half-day
    • New Pull requests
  • Decision on old open PRs
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting
    • Planning for minor release (around end of February, possibly the week Feb 27th - March 3rd)
      • What to include and what not to include:
        • Possibly wait with left/right - driver/passenger conversion until major, as breaking backward compatibility

Meeting Notes 2023-02-07

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Walk through Pull Requests and Issues VSS
  • Walk through Pull Requests and Issues VSS-Tools
  • Topics on hold
  • Older issues VSS & VSS-tools
  • Prioritized topics for next meeting

Meeting 2023-01-31

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Walk through Pull Requests and Issues VSS
  • Walk through Pull Requests and Issues VSS-Tools
  • Topics on hold
  • Older issues VSS & VSS-tools
  • Prioritized topics for next meeting


Meeting 2023-01-24

Work Package for Struct Proposal:
Details of the proposal in [PR 511](https://github.com/COVESA/vehicle_signal_specification/pull/511/)

A. Minor release with experimental struct support  
1. vss-tools can take in a types spec file and process sensor tree and the type tree together. struct/type support will be marked as an experimental feature.
    a. Syntactic check of struct definition
    b. Semantic check of type references in sensors
    c. Demonstrate working using the JSON exporter
2. Add disclaimer/warning when customer is using experimental feature 
3. Warning in exporters that structs are not yet supported
4. Warning in overlays that structs are not yet supported
5. Experimental feature documentation
Effort: 3 weeks

B. Exporters release  
1. Add support for struct types in other text-based available exporters in vss-tools - CSV, YAML
Effort: 1 week

C. Major release  
1. Overlay support
2. Documentation update
3. Add support for non-text exporters as needed - protobuf, DDSIDL, etc.
4. Add guidance around when and how to use struct types
Effort: 4 weeks


Meeting 2023-01-17

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
    • Neil Puthuff (RTI) presenting some initial observations as new to COVESA/VSS
    • Ford proposal - Fleet based range prediction
      • Christoph Schierjott presents EV Charging Event Data Aggregation Project
      • Data upload of various data to cloud
      • Cloud calculates correction factor individually and sends down to vehicle to correct fleet range prediction
    • Power Optimize
      • Mobis Architecture
        • Intention is to have a power manager that will select scheme, either based on user request or for example based on that remaining power drops below 20%
      • Pre-information Bosch proposal
        • Erik: Bosch has some ideas on representation that will be presented in the Power Optimize meeting this week
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting

Meeting 2023-01-10

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
    • None
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Information from Paul
    • Big interest at CES
    • We need to have a bigger discussion late January or February to how to simplify use of VSS.
    • Paul to discuss with Data Expert Group (Erik, Adnan) on how to proceed.
  • Prioritized topics for next meeting

Meeting 2022-12-20


  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Aggregate vs. structs - when do we see it need to be kept
      • From last week - Ulf/Erik: In favor of deprecating/removing aggregate keyword
      • Since then: Ulf requested a credible example, Erik stated that if we are to keep it we should better propose/specify how tools shall handle it
      • Adnan: Allow aggregate on deployment level, can use it when needed. For now good to only have it as information.
      • Krishna: Thinks aggregate makes changes, struct does not affect it. If we want to depricate we can do it later
      • Ulf: Does not have a strong opinion
      • Adnan: Good to document when structs vs aggregate shall be used
      • Erik: Can update the PR
      • Erik: Do you Krishna have interest in doing actual work.
      • Krishna: In January will start working on it, can help Erik
      • Erik; Then we can discuss later when we think it will be ready for VSS 4.0 release
    • Information: Overlays after expansion
      • Internal Bosch discussion if it would be better to refactor tooling so that only one parameter needed and tool is "smart enough" to deduce if given path refers to extended entity or not.
    • Discussion: PowerOptimize PR
      • Chandra: Intention to have one branch in each area, for infotainment we see brightness and audio volume
      • Chandra: Does not intend to duplicate, only want one signal, need only one
      • Erik: Isn't PowerOptimize only one of many use-cases for e.g. brightness, why need a PowerOptimize branch
      • Chandra: If scattered more difficult to find
      • Sebastian: OEM needs to decide what is part of his power optimization, do not understand the value of having them in separate branch
      • Adnan: What is difference
      • Pradeep: Adding a feature set, complete algorithm,
      • Adnan: If you are only proposing values, then it makes sense
      • Sebastian: Alternative usages could be e.g. overlay
      • Chandra: When we explain we see some signals are duplicated
      • Adnan: Best solution would if you prepare and show architecture on how it is intended
      • Adnan: Have not seen scope. Like to learn how
      • Pradeep: Do you have any public link describing how it is supposed to work.
      • Adnan: if you create some simple document you can attach it, then we can try to find best way
    • UUID elements
      • Adnan: Is anyone using UUIDs at the moment
      • Sebastian: We have never used them
      • Adnan: We saw a potential of UUID, could help versioning. We could UUID hash to validate. Has anyone any ideas. Otherwise we might create improvement proposal.
      • Sebastian: UUID are as of today generated based on tree structure.
      • Adnan: We need more, e.g. history. How do we move leave but keep UUID.
      • Sebastian: Could be a hash of only name/description/....
      • Erik: Please Adnan create an issue and ask if someone use UUIDs - if not you are free to do anything.
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting
    • Note: Dec 27th cancelled
    • Meeting as usual Jan 3rd

Agenda for Meeting 2022-12-13


  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Aggregate vs. structs - when do we see it need to be kept
      • Ulf/Erik: In favor of deprecating/removing aggregate keyword
      • Erik: Seems proposal is quite stable, lets wait discussing work packages until Jrishna is back, as he seemed interested in implementing in vss-tools
    • Summary for vote of Allowed (https://github.com/COVESA/vehicle_signal_specification/issues/502)
      • vote result: allow int and float for now
    • Meeting cancellations due to new year
      • Availability of participants Dec 20th?
      • Suggest cancelling Dec 27th?
      • Availability of participants Jan 3rd? (Erik unavailable)
      • Decision: Cancel Dec 27th, wait with decision on Dec 20th and Jan 3rd
      • Availability: (Paul: all, Ted: all,  Umang: all, Ulf: all)
      • Erik to check with Adnan (and Krishna)
    • Open Pull Requests (vss+tools, except struct) - approve/object before next week.
      • See PRs
    • Information: New issue for proposal from last week
    • Information: Overlays after expansion
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting

Meeting 2022-12-06


  • 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


Meeting 2022-11-29


Agenda Template

  • Compliance statement - TBD
  • Welcome and 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
  • Prioritized topics for next meeting



  • No labels

Privacy Policy | Cookie Policy