Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: completed minutes for 4/5/2022

...

Minutes:

  • AMM feedback
    • Paul
      • Workshop
        • ROS/DDS to/from VSS,  input Input from Ricardo/NNG on interfacing VSS to ROS RTOS and its DDS messaging
          • Reached out waiting for reply to advance discussion
        • BMW / (Adnan) input about links to big tech company links
          • Meeting As above meeting needed to scope out
      • Next timeAMM
        • Need input on what ppl want to do to make workshops flow more organically
    • Sebastian
      • Workshops
        • Ppl coming to expect came expecting 'readout' rather than workshop.
        • Positive : good attendanceFlip is was the good attendance and many newcomers, but the flipside of that was it was less 'workshopping'
    • Christian
      • Good discussions
      • Mixed expectations of new members/visitors vs old stagerscall regulars
      • Good attendance of in workshops despite them being scheduled at being the end
      • It was cool
    • Florian
      • Good balance between panels, biz/tech track and workshops
    • Ted
      • Attended virtually
      • Enjoyed BMW presentation on VISS integration
  • CVII Tech Stack Workshop talking points
    • SomeIP / Autosarwork occuring in Autosar. No schedule but something to follow.
    • BMW Android/VISS presentation. BMW, Major: VISS + Android VHAL feeder, Minor: GraphQL backend.
      • See deep dive discussion below
    • ROS / ADAS DDS to VSS
      • See Paul comment above
    • VSS Feeders / Data Store
      • Seb : update on kuksa.val CAN
        • Loosely coupled, i.e. easily reusable
        • CAN feeder in python. Nice for prototype but for production likely look C++, Rust
        • CANOPI
        • Next step: wider discussion about reusing this work in eco-system. More eyes on the code etc.
      • VSS Feeder and Data Store abstractionAbstraction
        • CCS Component status as starting point
          • Ulf's CCS component slides as possible starting point to deep dive
        • Need to discuss to what extent abstraction is possible or makes sense and for which use cases.
          • e.g. CCS Component current abstraction is simple single key/value API. Fine for low volume but would not scale.
          • In some cases might make sense to just use highest speed native API
      • Steve suggests start planning Deep Dive to discuss VSS Feeders and Data Stores
        • 1st might be:
          • 20-30 min Ulf present CCS slides, followed by wider discussion about abstraction.
        • Ulf sent apologies today. Steve will discuss with him either next week or slack
    • Deep dive next
      • Steve: What other things do you want to discuss in coming weeks?
      • Seb:
      Deep dive next
      • Seb: Dig into what BMW needed/took from VISS protocol to understand their needs. Input may be useful towards to VISS v3.
      • Ted will maintain has been having OSS roadmap discussion . Schedule with BMW. Idea is to schedule meeting with Adnan about above when code available.
      • If meeting is in W3C slot then Ted will arrange 'visitor pass' for CVII members to attend.

2022-04-20

Agenda:

  1. Project Status
  2. AMM Sessions

...