...

• First/early 'next steps'
  • How to organise project during its creation phase?
    • Move discussion to 24/7 online where possible for faster pace than weekly calls
    • Top level phases?
    • Record and comment on work breakdown.
    • Project management: where, what, how
  • Take a breath - are we aligned on top level goals and what/who/how? Who will be active? What are their interests?
  • Implementation
    • Check state of VISS Docker support
    • Confirm project setup for upstreams, e.g VISS, DBs
      • Can be considered part of early wider socialisation of project.
    • Planning for additional DBs, e.g. Apache IoTDB, Realm
  • Determine early Use Cases to be 'guided' by
  • Look at connection to MongoDB/BMW work. What is common?
  • Feeder link

Phase Planning

Phase 1 Create Early PoC

High level content:

• Playground
  • WAII VISS
  • Connect Realm DB to WAII
  • Connect Apache IoTDB DB to WAII
• Docker deployment of Playground
  • Scope: starts container chain containing above
• Documentation website
  • Scope: online instance (prove website framework has what we need at high level), with some representative (possibly placeholder documents)

Concept drawing in DrawIO: https://drive.google.com/file/d/1hxxDVgqianoMoXapPsYfjKgQVdc6Uume/view?usp=sharing

Best Practices

List of best practices that may become a best practices document for the Playground

• Docker
  • Official Docker project best practices:
    • https://docs.docker.com/develop/dev-best-practices/
    • https://docs.docker.com/develop/develop-images/dockerfile_best-practices/
    • https://docs.docker.com/develop/security-best-practices/

Project Management

In 25th Oct 2023 meeting (see minutes for details) following decisions were made:

...

1. How to handle Epics (dev themes) which is not a feature of Github Projects? e.g. use undated Milestones.
2. How to handle tasks in a ticket that are not directly development such as operational tasks? Could use enhancement label then have problem of filtering those from feature enhancements.

Use cases to be explored

Christian Muehlbauer Input (Proposal):

User Story:

"As a user of the Playground, for example, I would like to be able to quickly implement the following use case - representative for a Use Case “touching all touchpoints” of a data-centric automotive ecosystem - in a fast proof of concept implementation using Lego pieces from the Playground."

Validation Use Case:

(Based on: https://wiki.covesa.global/pages/viewpage.action?pageId=71074417)

Image Added

Ideally, the Playground Repo provides a selection of components for each „X“ for the corresponding target platform (SDK, or docker, etc):

Image Addedtbd

Steve input (brainstorm list):

...