Versions Compared

Old Version 30

changes.mady.by.user Stephen Lawrence

Saved on

compared with

New Version 31

changes.mady.by.user Stephen Lawrence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added 2022-02-23 outline
Quick links: [ CVII home page ] [ Tech Stack components ]

2022-02-23

agenda:

  • project recap
  • extra meeting discussion
  • dev org
    • recording task list
  • AoB

Related projects walkthrough (every week):

ProjectPerson reportingUpdates
  • Kuksa.VAL
Sebastian (Bosch)  
  • W3C VISS specification (v2)


Ulf 
Ted as backup (both Geotab)


  • WAII VISS server implementation in Go
Ulf 

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


  • VSSo
Daniel W  
Ted  
  • VSC & Tools
Gunnar
  • CCS-components
Ulf  
  • AOS
Artem (EPAM)

  • Android Automotive VSS→ Vehicle Properties
    Code Generator


  • Covesa GraphQL components
Alexander Domin (BMW)
(proposed.  worth tracking in CVII call?)(Thomas S) 
Steve (Renesas)


Minutes:

2022-02-16

agenda:

  • project recap
  • extra meeting discussion
  • dev org
    • recording task list
  • AoB

...

Related projects walkthrough (every week):

ProjectPerson reportingUpdates
  • Kuksa.VAL
Sebastian (Bosch)  Skipped - no Bosch engineer this week
  • W3C VISS specification (v2)


Ulf 
Ted as backup 

Ulf: Volvo starting on "explainer" of v2 which is a needed deliverable for finalising the v2 spec. Discussions about enhancements for access between ECUs concluded cost/benefit of allowing sensor values to be set by VISS were too high.

  • WAII VISS server implementation in Go
Ulf No change - WAII fully implements VISS v2 spec so no plan for large functional enhancements currently

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

Some signals in private branch of standard catalog have uncertain license and useage. Decision taken to delete for now.
Work on re-formatting of standard catalog signals to fit tightened guidelines continues.

  • VSSo
Daniel W  
Ted  

Published first working draft.

Considering how best to handle workshop - something at AMM? MS willing to do DTDL talk about mapping. Ted will talk to Paul offline

  • VSC & Tools
GunnarDiscussions about Wiper ECU test case continue.
  • CCS-components
Ulf  No change - expected as CCS meetings suspended as discussions about extra CVII Tech Stack meeting, in which CCS may be merged, continue.
  • AOS
Artem 
No major change. Fuller documentation being worked on. Various smaller source update.
  • Android Automotive VSS→ Vehicle Properties
    Code Generator

Discussion about improvements to the packaging of the converter.

  • Covesa GraphQL components
Alexander Domin (BMW)

Skipped - Alex not present. Its noted there have been some fixes pushed to the components.

(proposed.  worth tracking in CVII call?)(Thomas S) Skipped - no Bosch engineer this week
StevePublished data model for simulator in vspec. Working on code generator. Have identified common code in VHAL source than can migrate to shared "utils" area for use across multiple projects.


Minutes:

  • Extra meeting discussion
    • Steve: I emailed a proposal to the list

      • After the extra meeting discussion last week I thought of one proposal on how to run them. In the Hypervisor group we would have what we called "deep dive" topics. A meeting dedicated to a single subject. We could do the same for the extra meeting. It would be on a set day and time to be agreed for continuity. However it will only go ahead if a topic has been agreed ahead of time, in the regular meeting. This avoids the trap of unproductive meetings and allows people to be selective about their interests.

    • Ulf: I like it.
    • Paul also supports the idea.
    • No other proposals made,
    • When?
      • AI: Paul will put up a doodle to identify some options of when ppl are available
      • Old CCS time should be one option: 4pm CET Monday
      • Time zones. More than one time slot may be needed. Doodle might gives us a couple of options from which we could select depending on topic participants.
    • Why?
      • Ulf: Integration of CCS scope including PoC for tech stack and CCS architecture diagrams.
      • Similar with Tech Stack work to date.
      • Anchoring discussions in shared architecture and terminology. Mapping prop
    • Naming
      • Weds: Tech Stack - eco-system/project coordination/sync
        • 1st half: recap
        • 2nd half: design work
      • New meeting: Tech Stack - detailed design
    • Topics backlog:
      • AI: Steve add page to add topic descriptions
      • (Alex) GraphQL implementation with VSS data feeders and storage. AI: Steve ask Alex to expand
      • Gunnar: Can translation is common request.
      • Gunnar: Refer CVII component list, e.g. protobuf, grpc.
      • Steve: Interfacing VSS Data Storage to VSS Data Servers
  • Dev org
    • JIRA tickets
      • List things people can pick-up
      • In-progress collaborative development, e.g. VHAL project showing what tasks are planned, which in turn defines when work is done.

...