Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added embedded build recipe interest

...

  • Stephen Lawrence: I am interested in discussing areas lower in the in-vehicle stack that are current pain points in the industry that we can collaboratively improve. I am thinking of things like points Unknown User (alexander.domin) raised in Tech Stack call 19/6 about interfacing above and below VISS and the issues of integrating buses. Related would be issues around the nexus of cross-domain functionality. This might start purely as information sharing from which like minded groups are identified.
  • Short summary of survey, especially where people are willing to contribute, etc.
    • (full PDF available but not presented all details)
  • Backdrop for taking next step is proof of adoption of VSS&VSSo. 
    • BMW any news?  Microsoft connection?
  • VSC / interface language next steps (status, options, dialog) 
    • Status = language proposal, open questions
    • APIs being defined "elsewhere" (digital key being defined via Android?, other necessary standard interfaces?)
    • Are you willing to put forward descriptions?
    • Survey results + input from this meeting
    • Drivers for industry standard interfaces → Rental companies?
  • Alignment Track:  ISO ExVe current state and plans?  (Florian)
  • Alignment Track:  OPIN and eSync progress.
  • AOS ?
  • Stephen Lawrence : Hard to summarise the possible scope here but I have been thinking about in-vehicle and wondering about integration into embedded build systems. Is there discussion to be had at this point about the usefulness, or not, of shared development of embedded distro recipes, e.g. Yocto, or perhaps the current focus on containers is sufficient?

Agenda


TopicSpeaker/moderatorComments