We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

General Information

Weekly Meeting: Monday, 5-6pm CEST (Teams Link)

Slack: https://covesacommunity.slack.com/archives/C05EB6A6J5R

GitHub: https://github.com/COVESA/aosp-app-framework-standardizatiion

10th July 2023 - Virtual Meeting

ToDos are underlined (smile)

  • Participants: BMW, Cariad, General Motors, Mercedes, Forvia/Faurecia Aptoide, Harman, Snapp, Remotive Labs, Ansys, Intellias, GrapeUp, Bosch, drimaes, Elektrobit, KPIT, COVESA, Tietoevry, L&T Technologies, HAAS, Geotab

  • Preferred license: Potentially Apache
    @All: 17.7. confirming if this license can be chosen for code and documentation

  • @Matthias Ostermeier (Cariad) & Albert Jordan (Harman): 17.7. Feedback if willing to contribute to collection of best pratices / developer documentation

    → Proposal: Starting a collection with learnings of different OEMs / App Store Providers

    → Longterm having more full-blown developer documentation

  • Differences between OEMs that Faurecia Aptoide found next to the ones listed in F2F Meeting: Media Player Integration, Car API, DRM, Toasts/Snackbar Usage

    → To be revisited after priority list

  • Handling of different workstreams:
    • For now aligned within Monday meeting
    • Potentially seperate sessions needed where members can loop in their experts
  • Stream Owners:

    1. Cross-OEM Emulator: Juhani Lehtimäki (Snapp) with support of Emil Dautovic (Remotive Labs)

      → First session on emulator on 17th July

    2. Camera API: BMW
      → @All: 17.7. Clarifying if reference implementation in PDF document from F2F meeting (22.6.) works across OEMs

    3. Push Notifications: tbd.

      → @José Freitas (Faurecia Aptoide): giving overview on 24th July

      → @Melina Mascolo (BMW): Sharing first proposal with José

    4. Best Practices: tbd.

  • General communication channel for workstreams: Slack

    → Link will be shared with group

  • @All: 24.7. Clarifying if attending AMM in Detroit (10.-12.10.) would be possible

    → Idea would be to combine it with longer workshops, e.g. with communication app providers

22 June 2023 - Face to Face Workshop

  • Details
  • Consolidated Meeting Notes, participants and presentations (in PDF)
  •  


Charter Show as link230622_F2F_Meeting_Garching.pptx230622_F2F_Meeting_Garching.pptx230622_F2F_Meeting_Garching.pptx



  • No labels