Versions Compared

Old Version 40

changes.mady.by.user Stephen Lawrence

Saved on

compared with

New Version 41

changes.mady.by.user Stephen Lawrence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 9/3/2022 minutes

...

Related projects walk-through (every week):

ProjectPerson reportingUpdates
  • Kuksa.VAL
Sebastian (Bosch)  No change this week
  • W3C VISS specification (v2)


Ulf 
Ted as backup (both Geotab)

Closing out remaining issues for v2. Discussion of extending filtering  (range/compound) see https://github.com/w3c/automotive/issues/450. Looking to keep v2 changes to minimum, before starting bigger changes/new features towards v3
  • WAII VISS server implementation in Go
Ulf 

Ulf planning to add new Redis (CCS component) statestorage support. Timeline in 1-2 weeks.

Daniel Wilms (BMW)
(Erik J or Sebastian S as backup)

  • VSSo
Daniel W  
Ted  
  • VSC & Tools
Gunnar

Discussion of AMM demo around Bosch washer ECU service. Outline will be delayed by about a week whilst VSC Lead relocates continents.

Next task: architectural diagram and task split

  • CCS-components
Ulf  
  • AOS
Artem (EPAM)
No major update this week. Work continuing.
  • Android Automotive VSS→ Vehicle Properties
    Code Generator
Work continuing on Android 12 emulation environment
  • Covesa GraphQL components
Alexander Domin (BMW)No update this week(proposed.  worth tracking in CVII call?)(Thomas S) Steve (Renesas)Currently working on feeder to VSS Data Store code


Spec changes: int16->float for pitch/roll/yaw for better precision https://github.com/COVESA/vehicle_signal_specification/pull/422

Spec Changes: ADAS states also for EBD (Electronic brakeforce distribution) and EBA (Emergency Brake assist): https://github.com/COVESA/vehicle_signal_specification/pull/418/

Decision to try to release VSS V3.0 before All Members Meeting (end of April)

Discussion about what to do on AMM (to be collected in Wiki), and some roadmapping discussion, (layers, metadata, tools rewrite.. to be collected in Wiki) https://github.com/COVESA/vehicle_signal_specification/wiki/COVESA-AMM-Spring-22

  • VSSo
Daniel W  
Ted  		VSSo published as a First Public Working Draft at W3C
https://www.w3.org/TR/vsso-core/
  • VSC & Tools
Gunnar

Discussion of AMM demo around window wiper ECU service continuing. Tom working on draft high level arch diagram.

  • CCS-components
Ulf  See Redis support last week.
  • AOS
Artem (EPAM)
No major update this week. Work continuing.
  • Android Automotive VSS→ Vehicle Properties
    Code Generator

No change
  • Covesa GraphQL components
Alexander Domin (BMW)No update this week
(proposed.  worth tracking in CVII call?)(Thomas S) 

Maintainers can do from March 28th for presentation.

Getting started guide (website) https://www.eclipse.org/kanto/docs/getting-started/
GitHub: https://github.com/eclipse-kanto

Steve (Renesas)Currently working on feeder to VSS Data Store code.


  • Minutes:

    • Project Summary
      • Kanto
        • Tom reports that Maintainers can do a presentation from March 28th.
        • Discussion of content. Focus of deep dives is the scope of CVII Tech Stack, e.g. shared collab areas and understanding big architecture picture of how components fit together. Suggestion that 50% of time be presentation, 50% discussion of raised collab points.
  • Deep dive scheduling
    • Doodle results
      • 5pm CET has good support but clashes with bi-weekly HV call. Paul would prefer to avoid rescheduling it.
      • 4pm CET (old CCS time) slightly worse in support terms. Sebastian may not be able to attend some but says group should go ahead. Ted thinks he can reschedule clashing meeting.
    • Conclusion:
      • Try 4pm CET.
  • Deep dive topics
    • VSS / VSC integration
      • Seb: this overlaps with VSS and VSC groups and each has different participants. Needs coordination.
      • Steve: agree. I don't think "where" is important, i.e. not "owned" by Tech Stack, what is important is the topic.
      • Group participants are going to need to coordinate the topic. Upcoming AMM is going to be a good moment for everyone to be together.
      • Who is going to AMM?
        • Seb, Tom, Paul, Steve, Ulf, Florian (maybe), Nick (maybe), Erik, Philippe, Ted (would like to but obviously trans-atlantic)
    • General
      • Steve: please add your thoughts and topics to the deep dive page. Other the coming weeks we should refine and then prioritise to actually start the meetings.
  • AMM
    • Steve: Is one hour enough?
    • Agreement that two hours would be better for workshop. Is that possible?
    • Paul will discuss with schedule planners.

2022-02-03

Agenda:

  • Regular project recap
  • Continue the extra meeting discussions. Work on the "deep dive" topic list.k
    • Fill out the timing doodle if you have not already.
    • Add to the deep dive page.
  • AMM topic planning
  • Tech discussion with remaining time.

...