Versions Compared

Old Version 119

changes.mady.by.user Stephen Lawrence

Saved on

compared with

New Version 133

changes.mady.by.user Stephen Lawrence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

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


Minutes:

  • Spring AMM sessions
    • Agreement to shorten session on Playground use in favour of discussing it in workshop segment
    • Discussion of workshop topics
      • Steve: add your ideas to the list on the planning page
      • Swen: interested in cloud
      • Christian/Haonan agree to present a few slides to kick-off discussion of knowledge layer
    • Steve has posted a note on LinkedIn advertising the session
  • Central Data Service Playground
    • Status reports
      • Steve has published the Implementation overview page on the doc site.
      • Next steps: point playground to use current upstream VISSR, some clean up and retest, before tagging 0.1.0 release.

27th March 2024

Agenda:

Minutes (retrospective summary):

  • Central Data Service Playground
    • Status reports / Kanban review
      • Steve: Baseline documentation has been published on site. Main content is the logical concept overview. Next will be implementation
      • Steve: Had a look at integrating RemotiveLabs virtual signal platform as a feeder. On hold whilst address issues accessing their cloud system via their CLI through corporate systems.
      • Ulf gave summary of VISSR feeder template
      • Steve: Thanks. I was planning to enable that for IoTDB as part of the backlog.

20th March 2024

Agenda:

  • Spring AMM sessions
    • Weaving in other sessions? Workshop at end of Playground 'use' session?
  • Central Data Service Playground
    • Status reports / Kanban review
    • Documentation site: content, theme
    • 0.1.0 release
    • Knowledge Layer Connector

Minutes:

  • Spring AMM sessions
    • Paul: can make changes to the timings if you need.
    • Discussion of making the end of the morning a working session.
    • AI: Need to calculate the timings. Three playground sessions, then working session.
  • Central Data Service Playground
    • Status reports / Kanban review
      • Steve:
        • WAII VISS Server IoTDB documentation and runtime configuration for connector merged upstream. Will rebase Playground on upstream after spent some time on playground documentation.
        • Working on content for Playground doc site to add baseline why/why/how introduction and getting started. Work taking place on my fork and presented as WIP PR here https://github.com/COVESA/cdsp/pull/27
      • Arnaldo:
        • Continuing work on Realm integration.
    • Documentation site
      • Brief discussion of Hugo themes. Steve seems some limitations in the current Learn theme and has done some experiments with Hextra that adds useful features like Cards and has more normal heading type size scaling. Small example here https://slawr.github.io/cdsp-doc-hextra-trial/docs/
    • Discussion of 0.1.0 release around time of AMM release

13th March 2024

Agenda:

  • Spring AMM sessions
    • Weaving in other sessions?
  • Central Data Service Playground
    • Covesa Board
    • Status reports / Kanban review
    • Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.
    • Roadmap/backlog/work package definition.
      • What does AMM release look like?
      • Feeders
    • Possible online hosting of Playground

Minutes:

  • Sml group: Swen, Steve, Paul, Haonan
  • Central Data Service Playground
    • Steve presented the development status to the Covesa board today
    • Status
      • Steve has sent PR upstream documenting use of Apache IoTDB as WAII Data Store backend. Covers for example runtime assumptions, e.g. schema, that a feeder or client developer would need to know about. Also how to seed the DB.
      • Content will be reusable in Playground.
      • He also rebased the code to add runtime configuration of the IoTDB connector through a config file on current upstream master and sent PR
    • Discussion of Swen's idea for online hosting
    • Discussion of app embedded DB schema
    • Steve summarised what the content of the likely first 0.1.0 release will be and plans for roll out.

6th March 2024

Agenda:

  • Spring AMM sessions
  • Central Data Service Playground
    • Status reports / Kanban review
    • Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.
    • Roadmap/backlog/work package definition.
      • What does AMM release look like?
      • Feeders
    • Possible online hosting of Playground
    AoB
    • / Kanban review
    • Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.
    • Roadmap/backlog/work package definition.
      • What does AMM release look like?
      • Feeders
    • Possible online hosting of Playground
  • AoB


Minutes:

  • Sml group: Ulf, Swen, Steve
  • Central Data Service Playground
    • Status reports
      • Apache IoTDB
        • Now upstream WAII VISS git rep move is complete Steve will rebase and upstream the config file support.
        • Extending WAII tutorial to document IoTDB connector is almost complete. Will send PR upstream.
    • Knowledge Layer Connector: Haonan has reported that Artifact JSON-RDF Converter outline has been updated.
    • Discussion of the likely content of the pre-AMM release.
    • Discussion of the current thinking for roll-out: get initial documentation in place, roll-out to active Covesa devs, then wider membership/community using blog/e-blast.
    • Swen outlined the benefits and possible method for online hosting of the Playground.
      • Wide ranging discussion of the possibilities: costs, connecting to other systems, scaling, flexibility etc.
      • Interesting idea that needs further discussion.

28th February 2024

Agenda:

...