Page History

...

• Participants:
• Topics from last week revisited - structure the topics (tasks / timing / roadmap).
• tools are limiting factor at the moment.
• Sabine: Just a proposal for discussion how we could structure it:

  
  

  Category	Task	Description	contributors	until when
  Specification	Requirements	gather and document requirements on this WIKI → José and analyse tasks regarding automotive host COVESA AAOS Emulator Requirements
  Ressources	build & host critical path.	where?  Crave for building → Viktor? → Viktor to provide requirements, done monthly? on every pull request? CI needed. COVESA → hosting? → gerrit instance on virtual machine. Viktor to specify. How do we collaborate → go to every repo we are hosting - bundling automatically not easy on Github. → for bundling gerrit better. second option: manually. make the emulator available in the SDK.
  Component	Push Notifications	be able to use Push Notifications in the emulator → part of the requirements. pre-installed apk.
  Component	Vehicle Data access	Vision: Be able to use vehicle data in the emulator & description on how to do it (e.g. via adb shell commands). Authentication system service. needed: → simulating the data and data streams. → get back to the data stream working group. google has some (python) scripts to feed the emulator. see VISS tooling →  Swen would address it in the data group VSS/VISS. → managing access & permissions.
  Component	Open Source map	emulator extension to render maps in open source map
  Component	SDK	emulator extensions for all (future) SDK parts
  ...	Automotive host decision	as input to emulator.

...