Page History

...

Historical note: the minutes for the previous project, the CVII Tech Stack, can be found here: CVII Technology Stack meeting notes

21st May 2024

Agenda:

• Playground Kanban: In-progress task status, major new items
• Knowledge Layer connector: code directory layout
• CVI call to discuss GM uServices mocker
• RL meeting

15th May 2024

Agenda:

• Playground Kanban: In-progress task status, major new items
• 0.1.0 release: I would like to make an initial release soon, but would like opinions if anyone has input on what/how
• Knowledge Layer connector
• Backlog generation
  • Use cases
    • Data processing/analytics
      • Commercial Vehicle BoF guidelines
      • CV Slack discussion incl. meta-data
    • Inquiry from GM about integrating a mocker
• AoB: related projects etc.

8th May 2024

Agenda:

• Playground Kanban
  • In-progress task status
  • 0.1.0 release
  • Completing project setup
• Backlog generation
  • Use cases
    • Data processing/analytics
      • Commercial Vehicle BoF guidelines
• AoB

Minutes:

• Playground status
  • Steve has a WIP PR to add the RemotiveLabs feeder/bridge he created for the Spring AMM. Documentation is next major step
  • Christian presented latest thinking on the Knowledge Layer connector. Extensive discussion of that.
  • Steve: we should look to make 0.1.0 release soon and complete project setup
• Limited timing remaining but some discussion of backlog generation and the need for use cases for data processing/analytics
  • Steve: Commercial Vehicle BoF has some guidelines
• AoB:
  • Ulf:
    • VISS/VISSR weekly project meetings starting Monday at 4-5pm CET
    • Commercial Vehicle Information Specifications project under Commerical Vehicle BoF being scoped. Starting with Tractor/Trailer trees.

1st May 2024

Minutes:

• May national holidays in EU meant missing active members so informal discussion held.
• General discussion of data sets, data processing and need for functional requirement input from industry.

24th April 2024

Agenda:

• AMM feedback
• Team backlog

Minutes:

• AMM
  • Feedback
    • Paul: Digital.auto came up a few times. Uncertain about what relationship to playground
      
      • Steve: Personally I see the core digital.auto functionality as being the visual ideation. For that part it could be both a data feeder of VSS data to the playground and a client which uses the playground as a source.
    • Swen: was useful as first time attendee. From CVI discussion yesterday will be sharing mental model of what I perceive as the bigger picture. We need to understand each other to design the right architecture.
    • Haonan: good conference. Good to meet people finally.
    • Steve: Had some interesting conversations in the Showcase with the Playground demo. Some people really got the concept and even talked about using it in their upcoming hackathon. Also had interest from an academic.
  • Thursday workshop
    • Whiteboard:

Image Added

• Backlog
  • Playground backlog slide from AMM:
    • Next (goal: enhance and use the playground):
      • Review 0.1.0 release and fill obvious doc gaps
      • Socialisation: COVESA groups, Webinars etc.
      • Concrete backlog generation (high lvl points below)
        • Main focus of Thurs Data Architecture team workshop
        • Feeders: VISSR feeder component, RemotiveLabs, etc.
        • Examples: agree data arch team early focus.
          • Data processing, touchpoints etc.
        • Connections to COVESA eco-system, e.g. CVI southbound, AOSP northbound
        • Embedded App DB (Realm)
        • DIKW Knowledge layer connector
        • Auto h/w deployment (mid term)
        • Complete project setup: release process etc
• Discussion in meeting:
  • Need data sets (at rest):
    • VSS data sets (real or simulated)
    • Other data models and rule sets.
  • Next week or two Steve will do some documentation polishing and publish the RemotiveLabs bridge sample code as an example (source is available in his github so ask if you want to know sooner)
  • Discussion of knowledge layer
    • Christian/Haonan are continuing to work on the connector
    • Discussion of rules example Haonan posted to the slack.
    • She explained she's currently bypassing some steps in the processing chain, but is just directly looking at the applicability of processing the timeseries data in RDFox to confirm approaches.

17th April 2024

No meeting due to AMM

10th April 2024

Agenda:

• 2024 Spring AMM Planning (Data Architecture and Infrastructure)
• Central Data Service Playground
  • Status reports
  • Release/preview tagging
  • AMM presentation
    • High level near-mid term backlog, e.g:
      • Feeders: VISSR feeder component, RemotiveLabs
      • Examples: agree data arch early focus. see workshop
      • Connections to COVESA eco-system, e.g. CVI southbound, AOSP northbound
      • Embedded App DB (Realm)
      • Knowledge layer connector
      • Auto h/w deployment (mid term)
      • Quality of life improvements: review 0.1.0 release and fill obvious getting-started or doc gaps
      • Agree on and complete project setup: release process, testing etc

Minutes:

• Spring AMM sessions
• Central Data Service Playground
  • Status reports
    • Steve:
      • Rebase on upstream VISSR complete and merged.
      • Quality of life Docker Compose improvements (code and doc) complete and merged.
      • Main branch now represents 'playground-core' of 0.1.0 release
      • Current: Now completing IoTDB guide for doc-site (preview here)
      • Next: showcase demo and AMM presentations
  • AMM presentation
    • Agreement on general high level themes for the backlog. Of course list to be actually debated in the workshop
    • Discussion of knowledge layer slides
  • Christian agrees it would be good idea to tag a release.

3rd April 2024

Agenda:

• 2024 Spring AMM Planning (Data Architecture and Infrastructure)
• Central Data Service Playground

...