Versions Compared

Old Version 5

changes.mady.by.user Erik Jaegervall

Saved on

compared with

New Version Current

changes.mady.by.user Erik Jaegervall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

2022-01-27:

Participants: Gerald, Ramona, Steve Crumb, Bernd Mattner, Erik, Sami, Jan, Stephen



Image Added

Topics:

  • (Currently not published here, potentially confidential)

2022-01-20:

Participants: Sami, Pawel, Piotr, Adnan, Erik, Paul, Stephen

Topics:

  • Charter Status
    • MQTT adapter
      • SAMI: We need one, AUTOSAR will do it
      • Piotr: legal group must discuss how MQTT Adapter can be published
    • ECH is transport agnostic
    • Data mapper
      • to be generated, so scope is instead tool chain which generate data mapper
    • Simulate API
    • PoC- licenses
      • Sami: Focus is to use MIT-based licenses.
      • Sami: How to handle licenses questions
      • Paul: Send to Steve Crumb or Michael
      • Piotr: Where to store questions related to licenses?
      • Paul: Wherever you find most useful
  • AUTOSAR Classic
    • Stephen: COVESA interest in classic, mentioned in charter, both for spec and poC. A bit worrying if in spec but not tested. Renesas also interested in Classic.
    • Stephen: Have you in AUTOSAR discussed Classic for Vehicle API
    • Sami: Classic is on the Radar. Should come at some point. But pushing first for adaptive.
    • Stephen: May be some interest to get some guidance on how to implement in Classic
    • Sami: We intend to be able to read data from classic in adaptive, but you mean implementing on classsic?
    • Sami: We have not considered implementing gateway on classic
  • https://github.com/langroodi/Adaptive-AUTOSAR
    • Adnan: Could it possibly be used for simulation, some seem to use it?
    • Adnan: Could we possibly use it to emulate AUTOSAR env?
    • Pawel: Require some checks on our side
    • Adnan: Sami needs to give some feedback, is what they are doing fine from license perspective
    • Stephen: What are dependencies? In-house?
    • Sami to contact Michael (AUTOSAR legal) on if this repo can be used, anyway need to consult team
  • Next steps
    • What to discuss next week in sync, what is left for meeting 3rd?
    • What to do after steering body meeting Feb 3rd
      • Format charter outside google, generate PDF to have something fixed to review?
    • Collaboration structure after next steering group
      • Erik: Shall we continue with this slot also after 3rd feb?
      • Paul: Seems good
      • Sami: Once concluded with charter, we hopefully also have license agreement in place as we may need to discuss more
      • Stephen: Ask Steve/Niclas how collaboration can be set up, we need to sync on legal check
    • Discussion
      • Adnan: we proposed a draft, circulate a few days in advance, include what Tieto presented at CES
        • Pawel: Will check, can provide something beginning of next week
      • Stephen: Get statement on license, highlight open topics
        • Erik: Shall we send to license group for questions
        • Paul: Yes
        • Sami: Could we have next call with them, charter say we shall align with legal group, invite them to next Friday
    • Action Points
      • Erik: Integrate latest comments, cleanup of doc
      • Erik: Ask Legal team (Steve Crumb, Niclas Höret) if they can join next week, send them charter. Also ask for meeting legal framework.
      • Pawel: Provide material from (or link to info on) Tieto CES PoC
      • Erik: Paul to create meeting link for continued meeting series (after Feb 3rd)




2022-01-13:

Participants: Sami, Pawel, Piotr, Adnan, Erik

...