Attendees: Walt, Jan-Simon, Fulup, Jens, Michele

Agenda:

• Application Framework issues for SAT
  • Roadmap for 2017 - namespace, cgroup, containerization, criu-ization (see App FW EG)
  • Sharing resources (bindings, libraries, etc) between applications needs a larger discussion
  • Updating skins across applications (more Graphics and UI EG than App FW)
  • I18 mechanism to broadcast events and manage resource files across applications.
  • Consent management for managing resources and applications. Examples include payments, enabling LBS. Should be done securely per application and user

• Other 2017 Roadmap
  • Architecture for vehicle signaling. Getting CAN reference data from OEMs.
  • Define success for 2017 in terms of AGL being ready for production and what that looks like.
    • Quality improvements - “We don't have to have everything, but what we have needs to work.”
    • Documentation
    • Testing and published test results
  • Virtualization / Containers
    • New ARMv8 platforms are powerful enough to benefit from virtualization
    • New Virtualization Expert Group
      • a new webpage will be created on the wiki. A number of conference calls and face to face meetings will be set to define a possible roadmap for this EG.
      • a set of meeting slots will be proposed (the idea is to start after CES2017). Walt will prepare the needed meeting infrastructure when everything will be set.
      • Virtual Open Systems, plans to develop a specific PoC on this matter in 2017 (KVM hypervisor and TrustZone).
  • API tools and common description of APIs along with documentation
  • Expand binder API capability to an RTOS to prove interoperability of AGL
  • Device profiles
  • Homescreen improvements with secure APIs
  • Walt will start an email thread to collect ideas for 2017 roadmap. Need to complete the roadmap update by the end of January for the AMM.

Expert Groups:

• Graphics and UI
  • See latest meeting minutes.

• AGL Compositor - possible donation from Wind River (Ned) Same status per Kaz.
  • IP Scan in progress inside Wind River
  • Some cleanup of the code is required internal to Wind River
  • Will be presented to the Graphics and UI EG prior to SAT
  • Could be hosted in the agl staging area for review - Ned's guess is this about a month away (say Nov 1).
  • Features
    • Qt Waylon dependencies - elimination of Qt dependencies would need to be community effort
    • Window manager
    • Surface sharing
    • Multiple display support

• Navigation EG Update - see EG Navi Wiki page for more information. Need to get more interaction with SAT from this EG. We would like to see instructions on how to integrate a new map with the App. Code is well written according to Fulup but comments are all in Japanese and there is no documentation. EG is planning to add some new features for the CES demo.

• Speech Services - possible donation from Conti for TTS No Update.
  • 3 - 6 months until Conti legal and technical review can be completed.
  • The feature set you would get is basically a TTS with an API to put out “Speak” requests.
  • The API is used in our products and allows for
  • Different sources (Speech Dialog, Navigation, “Apps”…) to speak
  • Priority handling / arbitration of Applications using the TTS
  • Interruption of “Speak” requests

• Application Framework and Security
  • See latest meeting minutes.

• Connectivity
  • Bluetooth and Wifi Connectivity
    • Looking a common commercial BT/Wifi dongle to be used as part of a standard set up. IoT.bzh will do some testing and make a recommendation. Done. Recommendation on CES demo wiki page.
  • Vehicle messaging and signaling
    • Looking for some characterization of IVI system message rates from CAN bus in order to drive the design. Getting trace data from CAN buses is impossible on the internet. Walt will bring to Steering Committee to ask for date.
    • See https://github.com/iotbzh/txc-demo/blob/master/bench/result-bench-porter for some bench marks done by IoT.bzh for one vehicle trace from Ford (openxc) that was found on the internet.

• CIAT
  • Blowfish 2.0.4 released. Blowfish 2.0.5 in January should be final Blowfish update
  • CC schedule announced
    • RC 1 - At the conclusion of the integration session we need all updates to be submitted by the end of the day Sunday December 18. We will use the December 18 snapshot build as the basis for our RC1. Development will continue on the master branch.
    • RC 2 - We will create RC 2 on or about December 28. Depending on how settled the code is, we may create the Charming Chinook release branch at this point or continue to work on Master. That decision will be made by Jan-Simon and Walt.
    • CC Release - Scheduled for January 6. Charming Chinook release branch will be tagged and released. New work on master will be for the Daring Dab release.
  • Lava up and running for Porter.
  • For 2017 can we combine API and platform level testing in one front end UI? graphana.org or similar?

• Telematics (Proposed EG)
  • No news

Miscellaneous:

• Hypervisor
  • Open source reference architecture where we can run multiple instances of AGL running different profiles such as IVI and IC. Renesas Gen 3 hardware should be fast enough to support this use case.
  • Jailhouse
    • Ronan doing some work testing Jailhouse on RCar Gen 3. Collaborating with Siemens.
  • Also Abstract. Should consider transitioning to an EG page where we can gather all of the relevant information.

New Business:

• Can we collect usage information by including a “First Boot” application that requests the user to collect anonymous information about how the system is being used.

Attendees: Walt, Jan-Simon, Fulup, Jens, Dennis, Michele, Stephane

Agenda:

• Application Framework issues for SAT
  • Roadmap for 2017 - namespace, cgroup, containerization, criu-ization (see App FW EG)
  • Sharing resources (bindings, libraries, etc) between applications needs a larger discussion
  • Updating skins across applications (more Graphics and UI EG than App FW)
  • I18 mechanism to broadcast events and manage resource files across applications.
  • Consent management for managing resources and applications. Examples include payments, enabling LBS. Should be done securely per application and user

• Other 2017 Roadmap
  • Architecture for vehicle signaling. Getting CAN reference data from OEMs.
  • Define success for 2017 in terms of AGL being ready for production and what that looks like.
    • Quality improvements - “We don't have to have everything, but what we have needs to work.”
    • Documentation
    • Testing and published test results
  • Virtualization / Containers
    • New ARMv8 platforms are powerful enough to benefit from virtualization
    • New Virtualization Expert Group
      • a new webpage will be created on the wiki. A number of conference calls and face to face meetings will be set to define a possible roadmap for this EG.
      • a set of meeting slots will be proposed (the idea is to start after CES2017). Walt will prepare the needed meeting infrastructure when everything will be set.
      • Virtual Open Systems, plans to develop a specific PoC on this matter in 2017 (KVM hypervisor and TrustZone).
  • API tools and common description of APIs along with documentation
  • Expand binder API capability to an RTOS to prove interoperability of AGL
  • Device profiles
  • Homescreen improvements with secure APIs

Expert Groups:

• Graphics and UI
  • See latest meeting minutes.

• AGL Compositor - possible donation from Wind River (Ned) Same status per Kaz.
  • IP Scan in progress inside Wind River
  • Some cleanup of the code is required internal to Wind River
  • Will be presented to the Graphics and UI EG prior to SAT
  • Could be hosted in the agl staging area for review - Ned's guess is this about a month away (say Nov 1).
  • Features
    • Qt Waylon dependencies - elimination of Qt dependencies would need to be community effort
    • Window manager
    • Surface sharing
    • Multiple display support

• Navigation EG Update - see EG Navi Wiki page for more information. Need to get more interaction with SAT from this EG. We would like to see instructions on how to integrate a new map with the App. Code is well written according to Fulup but comments are all in Japanese and there is no documentation. EG is planning to add some new features for the CES demo.

• Speech Services - possible donation from Conti for TTS No Update.
  • 3 - 6 months until Conti legal and technical review can be completed.
  • The feature set you would get is basically a TTS with an API to put out “Speak” requests.
  • The API is used in our products and allows for
  • Different sources (Speech Dialog, Navigation, “Apps”…) to speak
  • Priority handling / arbitration of Applications using the TTS
  • Interruption of “Speak” requests

• Application Framework and Security
  • See latest meeting minutes.

• Connectivity
  • Bluetooth and Wifi Connectivity
    • Looking a common commercial BT/Wifi dongle to be used as part of a standard set up. IoT.bzh will do some testing and make a recommendation. Done. Recommendation on CES demo wiki page.
  • Vehicle messaging and signaling
    • Looking for some characterization of IVI system message rates from CAN bus in order to drive the design. Getting trace data from CAN buses is impossible on the internet. Walt will bring to Steering Committee to ask for date.
    • See https://github.com/iotbzh/txc-demo/blob/master/bench/result-bench-porter for some bench marks done by IoT.bzh for one vehicle trace from Ford (openxc) that was found on the internet.

• CIAT
  • Blowfish 2.0.4 released. Blowfish 2.0.5 in January should be final Blowfish update
  • CC schedule announced
    • RC 1 - At the conclusion of the integration session we need all updates to be submitted by the end of the day Sunday December 18. We will use the December 18 snapshot build as the basis for our RC1. Development will continue on the master branch.
    • RC 2 - We will create RC 2 on or about December 28. Depending on how settled the code is, we may create the Charming Chinook release branch at this point or continue to work on Master. That decision will be made by Jan-Simon and Walt.
    • CC Release - Scheduled for January 6. Charming Chinook release branch will be tagged and released. New work on master will be for the Daring Dab release.
  • Lava up and running for Porter.
  • For 2017 can we combine API and platform level testing in one front end UI? graphana.org or similar?

• Telematics (Proposed EG)
  • No news

Miscellaneous:

• Hypervisor
  • Open source reference architecture where we can run multiple instances of AGL running different profiles such as IVI and IC. Renesas Gen 3 hardware should be fast enough to support this use case.
  • Jailhouse
    • Ronan doing some work testing Jailhouse on RCar Gen 3. Collaborating with Siemens.
  • Also Abstract. Should consider transitioning to an EG page where we can gather all of the relevant information.

New Business:

• Can we collect usage information by including a “First Boot” application that requests the user to collect anonymous information about how the system is being used.

Attendees: Walt, Jan-Simon, Fulup, Kaz, Tanikawa, Jens

Agenda:

• Application Framework issues for SAT
  • Roadmap for 2017 - namespace, cgroup, containerization, criu-ization (see App FW EG)
  • Sharing resources (bindings, libraries, etc) between applications needs a larger discussion
  • Updating skins across applications (more Graphics and UI EG than App FW)
  • I18 mechanism to broadcast events and manage resource files across applications.
  • Consent management for managing resources and applications. Examples include payments, enabling LBS. Should be done securely per application and user

• Other 2017 Roadmap
  • Architecture for vehicle signaling. Getting CAN reference data from OEMs.
  • Define success for 2017 in terms of AGL being ready for production and what that looks like.
    • Quality improvements - “We don't have to have everything, but what we have needs to work.”
    • Documentation
    • Testing and published test results
  • Virtualization / Containers
  • Expand binder API capability to an RTOS to prove interoperability of AGL

Expert Groups:

• Graphics and UI
  • See latest meeting minutes.

• AGL Compositor - possible donation from Wind River (Ned) Same status per Kaz.
  • IP Scan in progress inside Wind River
  • Some cleanup of the code is required internal to Wind River
  • Will be presented to the Graphics and UI EG prior to SAT
  • Could be hosted in the agl staging area for review - Ned's guess is this about a month away (say Nov 1).
  • Features
    • Qt Waylon dependencies - elimination of Qt dependencies would need to be community effort
    • Window manager
    • Surface sharing
    • Multiple display support

• Navigation EG Update - see EG Navi Wiki page for more information. Need to get more interaction with SAT from this EG. We would like to see instructions on how to integrate a new map with the App. Code is well written according to Fulup but comments are all in Japanese and there is no documentation. EG is planning to add some new features for the CES demo.

• Speech Services - possible donation from Conti for TTS No Update.
  • 3 - 6 months until Conti legal and technical review can be completed.
  • The feature set you would get is basically a TTS with an API to put out “Speak” requests.
  • The API is used in our products and allows for
  • Different sources (Speech Dialog, Navigation, “Apps”…) to speak
  • Priority handling / arbitration of Applications using the TTS
  • Interruption of “Speak” requests

• Application Framework and Security
  • See latest meeting minutes.

• Connectivity
  • Bluetooth and Wifi Connectivity
    • Looking a common commercial BT/Wifi dongle to be used as part of a standard set up. IoT.bzh will do some testing and make a recommendation. Done. Recommendation on CES demo wiki page.
  • Vehicle messaging and signaling
    • Looking for some characterization of IVI system message rates from CAN bus in order to drive the design. Getting trace data from CAN buses is impossible on the internet. Walt will bring to Steering Committee to ask for date.
    • See https://github.com/iotbzh/txc-demo/blob/master/bench/result-bench-porter for some bench marks done by IoT.bzh for one vehicle trace from Ford (openxc) that was found on the internet.

• CIAT
  • Blowfish 2.0.4 upcoming.
  • Lava up and running for Porter,

• Telematics (Proposed EG)
  • No news

Miscellaneous:

• Hypervisor
  • Open source reference architecture where we can run multiple instances of AGL running different profiles such as IVI and IC. Renesas Gen 3 hardware should be fast enough to support this use case.
  • Jailhouse
    • Ronan doing some work testing Jailhouse on RCar Gen 3. Collaborating with Siemens.
  • Also Abstract. Should consider transitioning to an EG page where we can gather all of the relevant information.

New Business:

• Suggestion from Dominig to change branching strategy to align to Yocto strategy/ naming conventions. Walt suggested starting an email thread to see what problems people might be having and to add branching strategy to the “Contributing to AGL” wiki page.

—–

Attendees: Walt, Stephane, Tanikawa, Kusakabe, Fulup, Jan-Simon, Dennis, John, Michael, Michele

Agenda:

• Qt 5.7 for CC - transition completed by Tanikawa

Expert Groups:

• Graphics and UI
  • See latest meeting minutes.

• AGL Compositor - possible donation from Wind River (Ned) Same status per Kaz.
  • IP Scan in progress inside Wind River
  • Some cleanup of the code is required internal to Wind River
  • Will be presented to the Graphics and UI EG prior to SAT
  • Could be hosted in the agl staging area for review - Ned's guess is this about a month away (say Nov 1).
  • Features
    • Qt Waylon dependencies - elimination of Qt dependencies would need to be community effort
    • Window manager
    • Surface sharing
    • Multiple display support

• Navigation EG Update - see EG Navi Wiki page for more information. Need to get more interaction with SAT from this EG. We would like to see instructions on how to integrate a new map with the App. Code is well written according to Fulup but comments are all in Japanese and there is no documentation. EG is planning to add some new features for the CES demo.

• Speech Services - possible donation from Conti for TTS No Update.
  • 3 - 6 months until Conti legal and technical review can be completed.
  • The feature set you would get is basically a TTS with an API to put out “Speak” requests.
  • The API is used in our products and allows for
  • Different sources (Speech Dialog, Navigation, “Apps”…) to speak
  • Priority handling / arbitration of Applications using the TTS
  • Interruption of “Speak” requests

• Application Framework and Security
  • See latest meeting minutes.
  • replace Security Blueprint Update
    • First draft targeted for Nov 15. Release for CES. (At risk)
    • John O'Connor completing a draft of the scope of the document for the next EG meeting Not complete
    • Fulup asked the SAT to provide any customer questions/inputs from members to make sure address those in the document.
  • App FW Update (Fulup)
    • IoT.bzh needs green light to publish the documents they have created from Renesas. Done.
    • Need some more documentation on the wiki to allow people to proceed in using the App Framework. Done. See https://wiki.automotivelinux.org/agl-distro/app-framework)
    • Homescreen packaged with App FW for CC. Done. Ready for F2F meeting.
    • App FW is requirement for CES Apps so that is one way we will use to test the viability of the app framework.
    • Repackaging of existing CES/ALS demos is part of testing.
    • Current work
      • Reworking the App FW to use systemd for control of apps (Complete for CC)
      • Introduce cgroups (Will be included in CC. Additional work will be needed for DD)
      • Namespace (Will be included in Daring Dab)
      • Basically containerizing applications (LXC) (Requires namespace so DD or later)

• Connectivity
  • Bluetooth and Wifi Connectivity
    • Looking a common commercial BT/Wifi dongle to be used as part of a standard set up. IoT.bzh will do some testing and make a recommendation. Done. Recommendation on CES demo wiki page.
  • Vehicle messaging and signaling
    • Looking for some characterization of IVI system message rates from CAN bus in order to drive the design. Getting trace data from CAN buses is impossible on the internet. Walt will bring to Steering Committee to ask for date.
    • See https://github.com/iotbzh/txc-demo/blob/master/bench/result-bench-porter for some bench marks done by IoT.bzh for one vehicle trace from Ford (openxc) that was found on the internet.

• CIAT
  • Blowfish 2.0.3 release made this week.
  • Lava up and running for Porter,

• Telematics (Proposed EG)
  • No news

Miscellaneous:

• Hypervisor
  • Open source reference architecture where we can run multiple instances of AGL running different profiles such as IVI and IC. Renesas Gen 3 hardware should be fast enough to support this use case.
  • Jailhouse
    • Ronan doing some work testing Jailhouse on RCar Gen 3. Collaborating with Siemens.
  • Also Abstract. Should consider transitioning to an EG page where we can gather all of the relevant information.

New Business:

• Suggestion from Dominig to change branching strategy to align to Yocto strategy/ naming conventions. Walt suggested starting an email thread to see what problems people might be having and to add branching strategy to the “Contributing to AGL” wiki page.

—–

Attendees: Walt, Kaz, Jan-Simon, Dominig, Tanikawa, Stephane, Fulup, Jens

Agenda:

• Yocto 2.1 vs 2.2 Decision.
  • Charming Chinook will be 2.1 (krogoth). May have to back port PulseAudio 9 and Wayland from morty.
  • Daring Dab will be 2.2 (morty). Sandbox was created for morty by Ronan.
  • We will consider branching Charming Chinook after the f2f in Yokohama.

• Qt 5.7 for CC decision - The following was communicated to Steering Committee.

“We need to move to Qt version 5.7 for the CC release. This is the Qt version that switches to using LGPL v3 for its open source license. The fundamental reason for the switch is that we need some fixes for ivi-shell that are included in the qt-wayland component in version 5.7. While back porting these fixes is technically possible, we believe that the fixes would be LGPL v3 and would cause those files to have to be relicensed. Since there is overall better support for wayland and weston in the new version of Qt we feel it makes sense to make the switch.

Since Qt is not included in the AGL UCB distribution as defined in meta-agl and meta-agl-extras, it is only build and included in the root file system when building the AGL demo. Therefore, meta-agl and meta-gal-extra will continue to be licensed using earlier versions of the GPL and LGPL.”

Expert Groups:

• Graphics and UI
  • See latest meeting minutes.

• AGL Compositor - possible donation from Wind River (Ned) Same status per Kaz.
  • IP Scan in progress inside Wind River
  • Some cleanup of the code is required internal to Wind River
  • Will be presented to the Graphics and UI EG prior to SAT
  • Could be hosted in the agl staging area for review - Ned's guess is this about a month away (say Nov 1).
  • Features
    • Qt Waylon dependencies - elimination of Qt dependencies would need to be community effort
    • Window manager
    • Surface sharing
    • Multiple display support

• Navigation EG Update - see EG Navi Wiki page for more information. Need to get more interaction with SAT from this EG. We would like to see instructions on how to integrate a new map with the App. Code is well written according to Fulup but comments are all in Japanese and there is no documentation. EG is planning to add some new features for the CES demo.

• Speech Services - possible donation from Conti for TTS No Update.
  • 3 - 6 months until Conti legal and technical review can be completed.
  • The feature set you would get is basically a TTS with an API to put out “Speak” requests.
  • The API is used in our products and allows for
  • Different sources (Speech Dialog, Navigation, “Apps”…) to speak
  • Priority handling / arbitration of Applications using the TTS
  • Interruption of “Speak” requests

• Application Framework and Security
  • See latest meeting minutes.
  • replace Security Blueprint Update
    • First draft targeted for Nov 15. Release for CES. (At risk)
    • John O'Connor completing a draft of the scope of the document for the next EG meeting Not complete
    • Fulup asked the SAT to provide any customer questions/inputs from members to make sure address those in the document.
  • App FW Update (Fulup)
    • IoT.bzh needs green light to publish the documents they have created from Renesas.
    • Need some more documentation on the wiki to allow people to proceed in using the App Framework.
    • IoT.bzh working with Jens to integrate new Home Screen with App FW. Should be ready for Yokohama F2F.
    • App FW is requirement for CES Apps so that is one way we will use to test the viability of the app framework.
    • Repackaging of existing CES/ALS demos is part of testing.
    • Current work
      • Reworking the App FW to use systemd for control of apps
      • Introduce cgroups and namespace
      • Basically containerizing applications (LXC)

• Connectivity
  • Bluetooth and Wifi Connectivity
    • Looking a common commercial BT/Wifi dongle to be used as part of a standard set up. IoT.bzh will do some testing and make a recommendation.
  • Vehicle messaging and signaling
    • Looking for some characterization of IVI system message rates from CAN bus in order to drive the design. Getting trace data from CAN buses is impossible on the internet. Walt will bring to Steering Committee to ask for date.
    • See https://github.com/iotbzh/txc-demo/blob/master/bench/result-bench-porter for some bench marks done by IoT.bzh for one vehicle trace from Ford (openxc) that was found on the internet.

• CIAT
  • Servers all updated this week with new release from Red Hat.
  • Lava up and running for Porter, Vayu, and RPI, and QEMU so we can start running tests on those. These will be made public on a single server shortly.
  • Download server back up. Snapshots reworked to always have the latest working build available for each board avoiding the problem of not having a build on a given day when that day's build failed.

• Telematics (Proposed EG)
  • No news

Miscellaneous:

• Hypervisor open source reference architecture where we can run multiple instances of AGL running different profiles such as IVI and IC. Renesas Gen 3 hardware should be fast enough to support this use case.
  • Fulup suggested looking at Jailhouse. Dominig will follow up on email list with a link to recent presentation given at ECLE.

New Business:

• Suggestion from Dominig to change branching strategy to align to Yocto strategy/ naming conventions. Walt suggested starting an email thread to see what problems people might be having and to add branching strategy to the “Contributing to AGL” wiki page.
• Fulup gave a read out from the GENIVI AMM.

Face to Face Meeting in Berlin Attendees: Walt, Jan-Simon, Leon, Jens, Tanikawa, Dominig, Matt Porter, Phil Wise, Anton, Munakata, Stephane, Chris, Michael, Kusakabe

On-Line: Fulup

Agenda:

• Yocto 2.1 Update - Discussion of whether we should move to Yocto 2.2 (not released yet but is on the master branch of Yocto). SAT was split on whether this is a good idea. Walt will check with CES vendors to see if the switch to Yocto 2.2 will break compatibility in the short term (pre-CES).
  • Pros
    • Support for shared graphics (Intel)
    • According Doming the Intel boards build. IoT.bzh says the Renesas boards build, but not much testing has been done.
  • Cons
    • Expect a number of BSPs to break and recovery may not be possible for CES
    • The general strategy for AGL has been to wait for Yocto to settle down after their release and make our release with a nine month lag. Going to a three month lag with no notice will jeopardize the schedule.
    • RFPs for board vendors and app suppliers referenced Yocto 2.1.

• BSPs Building in Master
  • Minnowboard - Yes
  • Raspberry PI 2/3 - Yes
  • Porter - Yes. Glitches with gstreamer a few times during building per Stephane. Will create a Jira
  • SABRE - No
  • Vayu - ?
  • Dragon Board - ?
  • QEMU - Yes

• Qt 5.7 for CC
  • Tanikawa explained that ivi shell changes that we need were merged for qt-wayland in Qt 5.7. Backporting may be technically possible to 5.6 but that may not be legally possible due to lgpl licence change in Qt 5.7. Recommendation from SAT is to change to Qt 5.7. See Jira SPEC-265 Walt to push question to Steering Committee.

Attendees: Walt, Jan-Simon, Stephane, Michael, Jens, Ned, Tanikawa, Bai, Hammad,

Agenda:

• Yocto 2.1 Update
• BSPs Building in Master
  • Minnowboard - Yes
  • Raspberry PI 2/3 - Yes
  • Porter - Yes. Glitches with gstreamer a few times during building per Stephane. Will create a Jira
  • SABRE - No
  • Vayu - ?
  • Dragon Board - ?
  • QEMU - Yes

Expert Groups:

• Graphics and UI
  • Internode display protocol proposal (Tanibata) - Tanibata not present. Walt will schedule a special SAT call for next week.
  • AGL Compositor - possible donation from Wind River (Ned)
    • IP Scan in progress inside Wind River
    • Some cleanup of the code is required internal to Wind River
    • Will be presented to the Graphics and UI EG prior to SAT
    • Could be hosted in the agl staging area for review - Ned's guess is this about a month away (say Nov 1).
    • Features
      • Qt Waylon dependencies - elimination of Qt dependencies would need to be community effort
      • Window manager
      • Surface sharing
      • Multiple display support
  • Navigation EG Update
  • Speech Services - possible donation from Conti for TTS
    • 3 - 6 months until Conti legal and technical review can be completed.
    • The feature set you would get is basically a TTS with an API to put out “Speak” requests.
    • The API is used in our products and allows for
    • Different sources (Speech Dialog, Navigation, “Apps”…) to speak
    • Priority handling / arbitration of Applications using the TTS
    • Interruption of “Speak” requests

• Application Framework and Security
  • Security Blueprint Update
    • First draft targeted for Nov 15. Release for CES.
    • John O'Connor completing a draft of the scope of the document for the next EG meeting
    • Fulup asked the SAT to provide any customer questions/inputs from members to make sure address those in the document.
  • App FW Update (Fukup)
    • Call extended to test the current app framework.
    • Source code and binary from Jose's AMM presentation is available for testing and extending.
    • App FW is requirement for CES Apps so that is one way we will use to test the viability of the app framework.
    • Repackaging of existing CES/ALS demos is part of testing.
    • Current work
      • Reworking the App FW to use systemd for control of apps
      • Introduce cgroups and namespace
      • Basically containerizing applications (LXC)
• Connectivity
  • Bluetooth and Wifi Connectivity
    • Looking a common commercial BT/Wifi dongle to be used as part of a standard set up. IoT.bzh will do some testing and make a recommendation.
  • Vehicle messaging and signaling
    • Looking for some characterization of IVI system message rates from CAN bus in order to drive the design. Getting trace data from CAN buses is impossible on the internet. Walt will bring to Steering Committee to ask for date.
    • See https://github.com/iotbzh/txc-demo/blob/master/bench/result-bench-porter for some bench marks done by IoT.bzh for one vehicle trace from Ford (openxc) that was found on the internet.

• CIAT
  • New Jenkins and gerrit up and running
  • Jenkins job builder up and running
  • Download server? Not switched over yet. Earliest is tomorrow, which will give us snapshot builds on Friday.
• Telematics (Proposed EG)

New Business:

• Fulup posted an email on the APIs that PSA opened for up for Big Data services. Looking for feedback.
• Hypervisor open source reference architecture where we can run multiple instances of AGL running different profiles such as IVI and IC. Renesas Gen 3 hardware should be fast enough to support this use case.

Attendees: Walt, Tanikawa, John O'Connor, Ahmed, Fulup, Jens, Ashley, Michael, Okubi

Agenda:

• Review Roadmap Slides

• Reference and Community BSPs (see https://wiki.automotivelinux.org/agl-distro#supported_hardware)
  • Minnowboard
    • Noted that Dominig is working on a Minnowboard Quick start guide on the wiki.
    • Stephane - Minnowboard build that we create as part of the daily snapshots fail to boot the board from an SD card.
    • Jan-Simon/Fulup: Create a Jira issue and assign to Dominig.
    • Kaz - can boot the board from a USB stick with the AGL build. Kaz to send a summary of what he did to get it to boot to the mail list.
  • Discussion of criteria for adding and maintaining reference boards came up (see SAT meeting minutes from May 27,2016 add pointer). SAT would like the criteria and whether there are financial qualifications to being a reference board approved by the new SC.

• Yocto 2.1 - no showstoppers seen in transitions to Kergoth. All targets are building in Jan-Simon's sandbox except for the Porter board. Jan-Simon expects to push to master by the end of this week. We can use the AMM as an opportunity to get help closing any remaining issues.

• Security Blueprint document progress - move ahead with setting up github for AGL documentation since there is already infrastructure there for MD rendering and document review.
• Spec Updates for overall architecture - will move from DOORS NG to github once we have established the account and some basic processes as we develop the security spec.
  • GitHub organization established at https://github.com/automotive-grade-linux
  • Recommend getting a domain like docs.automotivelinux.org
  • Jan-Simon did some research on other LF collab projects and they use readthedocs.

Attendees: Walt, Michael, Jan-Simon, Stephane, Kaz, Jens, Fulup

Notes:

• Face to face meeting Sep 6 in Munich the day before the AMM starts. Starts at noon with lunch with conference bridge available from 12:45.
• Reviewed SPEC-132 and SPEC-134 updates from Connectivity EG. Walt will reserve one or two hours at the AMM to discuss removing AMB from AGL and replacing it with a different solution. We will brainstorm the ideas that have been researched by IoT.bzh, Microchip and anyone else regarding the potential solution. Done
  • Email to SAT - System Architecture Team proposes to close project “Add private API's to AMB” (see SPEC-132) and move forward with project “Automotive Bus Privacy and Security Concerns” (SPEC-134). Please respond with yea or nay vote by August 18. Done. Issue closed.

• Reference and Community BSPs (see https://wiki.automotivelinux.org/agl-distro#supported_hardware)
  • Minnowboard
    • Noted that Dominig is working on a Minnowboard Quick start guide on the wiki.
    • Stephane - Minnowboard build that we create as part of the daily snapshots fail to boot the board from an SD card.
    • Jan-Simon/Fulup: Create a Jira issue and assign to Dominig.
    • Kaz - can boot the board from a USB stick with the AGL build. Kaz to send a summary of what he did to get it to boot to the mail list.
  • Discussion of criteria for adding and maintaining reference boards came up (see SAT meeting minutes from May 27,2016 add pointer). SAT would like the criteria and whether there are financial qualifications to being a reference board approved by the new SC.

• Yocto 2.1 - no showstoppers seen in transitions to Kergoth. All targets are building in Jan-Simon's sandbox except for the Porter board. Jan-Simon expects to push to master by the end of this week. We can use the AMM as an opportunity to get help closing any remaining issues.

• Security Blueprint document progress - move ahead with setting up github for AGL documentation since there is already infrastructure there for MD rendering and document review.
• Spec Updates for overall architecture - will move from DOORS NG to github once we have established the account and some basic processes as we develop the security spec.
  • GitHub organization established at https://github.com/automotive-grade-linux
  • Recommend getting a domain like docs.automotivelinux.org
  • Jan-Simon did some research on other LF collab projects and they use readthedocs.

Other SAT topics (skipped this week)

• Jira requests for SAT (see https://jira.automotivelinux.org/issues/?filter=10418)
• GPLv3 Packages in AA release.
• Criteria for adding new boards
• The need to document “what is AGL” and how does it compare it to GENIVI, Tizen, Ostro, etc and the benefits of AGL compared to the others for OEMs and Tier Ones. Target audience is C level management so they can drive AGL adoption into their companies.
• AGL Test suites need to move up the stack into testing middleware so that Tier Ones have confidence in the platform when they start development.

Meeting starts at 013:00 UTC Attendees: Walt, Michael, Fulup, Kaz, Jens,

Notes:

• Agreed to schedule face to face meeting Sep 6 in Munich the day before the AMM starts
• Reviewed SPEC-132 and SPEC-134 updates from Connectivity EG. Walt will reserve one or two hours at the AMM to discuss removing AMB from AGL and replacing it with a different solution. We will brainstorm the ideas that have been researched by IoT.bzh, Microchip and anyone else regarding the potential solution.
  • Email to SAT - System Architecture Team proposes to close project “Add private API's to AMB” (see SPEC-132) and move forward with project “Automotive Bus Privacy and Security Concerns” (SPEC-134). Please respond with yea or nay vote by August 18.

• AGL Process Update and Approval - Walt
  • New layers created by Jan-Simon per last call
  • README.md files updated in meta-agl and meta-agl-demo to reflect the revised structure. Also Jan-Simon created a README-AGL.md that describes the overall project since README.md has a specific purpose in Yocto, which is to describe the layer itself and not the build procedure.
  • For rendered versions see
    • https://markdownshare.com/view/ad47c709-8521-4875-8a61-5151062855ed
    • https://markdownshare.com/view/a8192414-84c5-469d-bcae-e6f0acdbcabb
    • https://markdownshare.com/view/bdd960ea-a01c-41e8-aae6-08e98330d271

• Reference and Community BSPs (see https://wiki.automotivelinux.org/agl-distro#supported_hardware)

• Security Blueprint document progress - move ahead with setting up github for AGL documentation since there is already infrastructure there for MD rendering and document review.
• Spec Updates for overall architecture - will move from DOORS NG to github once we have established the account and some basic processes as we develop the security spec.

• Jira requests for SAT (see https://jira.automotivelinux.org/issues/?filter=10418)

Other SAT topics (skipped this week)

• GPLv3 Packages in AA release.
• Criteria for adding new boards
• The need to document “what is AGL” and how does it compare it to GENIVI, Tizen, Ostro, etc and the benefits of AGL compared to the others for OEMs and Tier Ones. Target audience is C level management so they can drive AGL adoption into their companies.
• AGL Test suites need to move up the stack into testing middleware so that Tier Ones have confidence in the platform when they start development.

Meeting starts at 04:00 UTC (13:00 JST)

Special Face-to-Face Meeting in Tokyo prior to ALS - Neptune Conference Room 4th Floor Plaza of Hotel Chinsanzo.

Agenda:

• BB results and CC/DD roadmap
• AGL Process Update and Approval
• Jira requests for SAT (see https://jira.automotivelinux.org/issues/?filter=10418)
• App Framework proposal from Toyota

Meeting starts at 013:00 UTC Attendees: Walt, Michael, Stephane, Jan-Simon, Fulup, Ned

Agenda: Joint meeting with App FW EG

• App Framework proposal from Toyota - no further review
• Web Browser / Engine - on hold until after ALS
• Demo Apps Update - no update from integration team in Japan on iDrive integration with the applications. F2F session planned for Friday in Tokyo.

SAT Call:

• AGL Process Update and Approval - Walt
  • Update from Jan-Simon and Stephane on Yocto layers
  • Further refinement of the process document based on Stephane and Jan-Simon's latest work. Also added meta-agl-devel as a new layer for on-going development and community BSPs
  • Renamed agl minimal to agl core
• Reference and Community BSPs (see https://wiki.automotivelinux.org/agl-distro#supported_hardware)
• Security Blueprint document progress
• Spec Updates for overall architecture

• Jira requests for SAT (see https://jira.automotivelinux.org/issues/?filter=10418)

Other SAT topics (skipped this week)

• GPLv3 Packages in AA release.
• Criteria for adding new boards
• The need to document “what is AGL” and how does it compare it to GENIVI, Tizen, Ostro, etc and the benefits of AGL compared to the others for OEMs and Tier Ones. Target audience is C level management so they can drive AGL adoption into their companies.
• AGL Test suites need to move up the stack into testing middleware so that Tier Ones have confidence in the platform when they start development.

Special Joint meeting with Application Framework Expert Group Attendees: Walt, Okubi, Tanikawa, Munakata, Stephane, Fulup, Ned, Nori, Hoshina, Matusmoto, Michael, Jose, Hiroshi, Kengo

Agenda:

• App Framework proposal from Toyota - Okubi-san - Okubi-san reviewed his document that updates the AGL Resquirements Spec for Home Screen and Applicaiton Framework which was email out earlier today.
• Demo Apps update
• Web browser update

Attendees: Walt, Jan-Simon, Stephane, Hoshina, Tanikawa, Fulup, Ned

Minutes:

• AGL Process Update and Approval - Walt
  • Fulup brought up questions about SAT voting procedures.
  • Discussion of meta-agl-demo vs. meta-agl and use of staging repo.
    • How to deal with mutually exclusive sets of new functionality. (e.g, competing audio or security solutions)
    • Need to include the Yocto layers in the document to better define what is considered “in” the official AGL build and how new code/features get promoted to the official build.
    • Approval deferred to the get the document updated and pending the template updates that JSM is working on.
    • Here is the whiteboard drawing that was shown during the call.
• Jira requests for SAT (see https://jira.automotivelinux.org/issues/?filter=10418)
  • Deferred https://jira.automotivelinux.org/browse/SPEC-205 Proposal to create Navi API EG (from AisinAW)
    • Discussed in some detail the presentation from AisinAW that is attached to the issue. Have some questions for AisinAW about the proposal and what the work products are. Walt will update the Jira issue with the comments and invite AisinAW to the next SAT call.
    • Some discussion about whether we need to specify a global API mechanism or tool such as GENIVI did with Franca. General agreement that we should be prepared to recommend a tool (maybe JSON), but that if something exists in a domain already we should not force it to use an AGL specific tool as this primarily just creates more work.

• Deferred https://jira.automotivelinux.org/browse/SPEC-196 - Move App FW from staging tree. Agreed that the gerrit change should be reverted to move the App FW out of meta-agl. Provoked additional discussion about layer set up and where this change belongs in the layer structure. Also realized that we need the new template structure being worked on by JSM to accommodate this type of request in the meta-agl-extra or meta-agl-demo layer. JSM will an initial version of the template structure available on Friday.

• Approved https://jira.automotivelinux.org/browse/SPEC-195 - Create /src directories for most driver and CAN/LIN driver

Meeting adjourned after 2.5 hours. Will continue with rest of agenda and remaining open items next time. Also agreed that we will have a face to face SAT meeting in Tokyo the afternoon before ALS.

• Reference and Community BSPs (see https://wiki.automotivelinux.org/agl-distro#supported_hardware)

• Security Blueprint document progress
• Spec Updates for overall architecture

07:00 UTC Continue with joint App FW EG Meeting.

• App Framework proposal from Toyota - Okubi
• Demo Apps update
• Web browser update

Other SAT topics (skipped this week)

• GPLv3 Packages in AA release.
• Criteria for adding new boards
• The need to document “what is AGL” and how does it compare it to GENIVI, Tizen, Ostro, etc and the benefits of AGL compared to the others for OEMs and Tier Ones. Target audience is C level management so they can drive AGL adoption into their companies.
• AGL Test suites need to move up the stack into testing middleware so that Tier Ones have confidence in the platform when they start development.

Attendees: Walt, Michael, Fulup, Stephane, Jens

Minutes: Old Business:

• Security Blueprint progress - no update, but we discussed usage of Pandoc to convert md files to other document types such as Dokuwiki or MS word docs. Walt will take the security blueprint and put it into a git documentation repo and create the MD5.
• Spec updates for overall architecture
  • Expecting an update for Application Framework from Okubi-san by June 15
  • Jose expects to have a public version of the Application Framework available early next week for review. Walt will get a technical writer to start review the content directly in gerrit. Will also start technical reviews by developers.
• Skip: GPLv3 Packages in AA release.
• Skip: Criteria for adding new boards
• The need to document “what is AGL” and how does it compare it to GENIVI, Tizen, Ostro, etc and the benefits of AGL compared to the others for OEMs and Tier Ones. Target audience is C level management so they can drive AGL adoption into their companies.
• AGL Test suites need to move up the stack into testing middleware so that Tier Ones have confidence in the platform when they start development.

New:

• Dev process updates - reviewed the current slide deck Walt has been working on to explain the process and clarify the rules around usage of the staging repo.

Attendees: Walt, Fulup, Stephane, Jan-Simon, Manuel, Tanikawa, others at Vannes F2F

Minutes: Old Business:

1. Security Proposal from IoT.bzh (http://lists.linuxfoundation.org/pipermail/automotive-discussions/2016-April/001821.html). - Need approval to go forward
   1. An update was presented at the F2F in Vannes
   2. Topic was reviewed at the Platinum member meeting in Japan on May 14
   3. Plan is to put together the TOC for the Security blueprint document later today at the F2F

1. Spec updates for overall architecture
   1. Expecting an update for Application Framework from Okubi-san by June 15

1. Skip: GPLv3 Packages in AA release.

1. Criteria for adding new boards
   1. Two categories proposed - Reference Boards and Community Supported Boards
      1. Reference boards
         1. Sponsoring company sets up test nodes in Lava, Full suite is run and test results reported.
         2. Need criteria for accepting a reference boards.
            1. Minimum of two boards provided for AGL test infrastructure
            2. Kick-start guide for downloading and building code and running the AGL demo code.
            3. Yocto BSP layer that passes AGL CIAT testing (>90% pass maybe)
            4. Snapshot builds available from AGL Jenkins
            5. Automated testing performed from AGL test environment with results posted publically
            6. Combo layers and SDK available for reference boards
         3. Criteria for de-referencing a board as the hardware goes obsolete or support is withdrawn by its sponsor
         4. Current reference boards - Porter, Minnowboard Max (need a kickstart)
         5. Propose to Steering Committee (or AB) that having a reference board requires Silver Level membership or above.
      2. Community board
         1. Best effort by the community
         2. Look at OpenWRT and their https://wiki.openwrt.org/toh/start : table of hardware for what is supported.

1. Request to add GENIVI components to AGL build. https://jira.automotivelinux.org/browse/SPEC-172
   1. Audio Manager (audio routing)
      1. Denso/Adit working on GENIVI AM plugins for pulse audio
      2. IoT.bzh working on a simplified Tizen (without murphy) solution for audio routing to be presented at the f2f.
      3. AGL solution will most likely look much different than current solution in the staging repo as we converge on a preferred audio routing mechanism.
      4. 27 May - Reviewed the audio manager and policy manager diagram created by Manuel with Tanibata and Isogai (need link to diagram).

New Business:

• Presentation from Graphics and UI EG on layer manager (Tanibata-san)
• The need to document “what is AGL” and how does it compare it to GENIVI, Tizen, Ostro, etc and the benefits of AGL compared to the others for OEMs and Tier Ones. Target audience is C level management so they can drive AGL adoption into their companies.
• AGL Test suites need to move up the stack into testing middleware so that Tier Ones have confidence in the platform when they start development.
• Walt to add a single table that list all meetings to the wiki page - done see meetings

Attendees: Walt, Michael, Tanikawa, Tanibata, Stephane, Fulup

Minutes: Old Business:

1. Security Proposal from IoT.bzh (http://lists.linuxfoundation.org/pipermail/automotive-discussions/2016-April/001821.html). - Need approval to go forward
   1. Fulup mentioned that they are preparing an update to be presented at the F2F in Vannes
   2. Tanibata made a comment saying this is a good starting point and looks forward to seeing the implementation on AGL.
   3. Topic will be reviewed at the Platinum member meeting in Japan on Friday.

1. Spec updates for overall architecture
2. Skip: GPLv3 Packages in AA release.
3. Skip: Criteria for adding new boards
4. Request to add GENIVI components to AGL build. https://jira.automotivelinux.org/browse/SPEC-172
   1. Audio Manager (audio routing)
      1. Denso/Adit working on GENIVI AM plugins for pulse audio
      2. IoT.bzh working on a simplified Tizen (without murphy) solution for audio routing to be presented at the f2f.
      3. AGL solution will most likely look much different than current solution in the staging repo as we converge on a preferred audio routing mechanism.

New Business:

• Presentation from Graphics and UI EG on layer manager (Tanibata-san)

Notes:

• The need to document “what is AGL” and how does it compare it to GENIVI, Tizen, Ostro, etc and the benefits of AGL compared to the others for OEMs and Tier Ones. Target audience is C level management so they can drive AGL adoption into their companies.
• AGL Test suites need to move up the stack into testing middleware so that Tier Ones have confidence in the platform when they start development.
• Walt to add a single table that list all meetings to the wiki page

Meeting starts at 13:00 UTC

Attendees: Walt, Jens, Jan-Simon, Tanikawa, Michael, Stephane,

Agenda:

Old business:

1. Connman progress (https://jira.automotivelinux.org/browse/SPEC-119)
   1. Close in terms of SAT approving Connman. Refer back to Connectivity EG.
2. Security Proposal from IoT.bzh (http://lists.linuxfoundation.org/pipermail/automotive-discussions/2016-April/001821.html).
   1. Defer further review to May 12 SAT call due to holiday in Japan this week.
3. Spec updates for overall architecture
4. GPLv3 Packages in AA release.
   1. Open action for Walt to check with LF resources on secure boot
   2. List of packages that use GPLv3. Not all will appear in the file system on the target board. Need guidance from OEM members on how to handle these because they will be responsible for shipping these in their products.
      1. gawk: GPL-3.0 gnutls: GPL-3.0+ libgcrypt: GPL-3.0+ gcc: GPL-3.0-with-GCC-exception gcc: GPL-3.0 coreutils: GPL-3.0+ m4: GPL-3.0 bash: GPL-3.0+ gdbm: GPL-3.0 cairo: GPL-3.0+ xz: GPL-3.0-with-autoconf-exception bison: GPL-3.0 binutils: GPL-3.0 elfutils: GPL-3.0 readline: GPL-3.0+ gettext: GPL-3.0+ screen: GPL-3.0+ gdb: GPL-3.0
   3. Defer to CC release on taking any actions on these. In the meantime we need to triage which of these might be false positive and which ones have logical replacements.

1. Criteria and plan for new boards

New business:

1. Request to add GENIVI components to AGL build. https://jira.automotivelinux.org/browse/SPEC-172
   1. Jan-Simon will work on Andre on resolving his gerrit issue.
   2. Will review his proposal once it has been uploaded to gerrit.

Attendees: Walt, Jan-Simon, Stephane, Fulup, Michael, Christian, Ned, Paul Nichols

1) Connman for Connectivity

• Stephane has documented proposal in https://jira.automotivelinux.org/browse/SPEC-119
• Stephane has submitted a patch in gerrit that allows switching between Connman and systemd.
• Fulup suggests that we need to write a test app with a simple GUI that allows a user to connect to Wifi and Bluetooth. Create https://jira.automotivelinux.org/browse/SPEC-170 to track.
• Paul: Are there any security provisions around connectivity through a cellular carrier or authentication mechanisms in the current solution? Need to look at what ofono offers for security. Concern is for the telematics use case with an embedded mobile.

2) GPLv3 packages in AA

• Would like clarification from LF on whether usage of GPLv3 prevents the use of a secure boot loader that would not allow a user to change the embedded OS.
• How does Ostro handle this?
• Create a list of the current components that use GPLv3 in the baseline distribution and whether those components on the target file system.
• There was a report that was sent to the mail list last year about re-use of GENIVI and the components. http://iot.bzh/download/public/2015/Audit_on_GENIVI_components_in_AGL_Phase-1.pdf

3) Security framework - reiterated the need to review the document and get feedback to the App FW EG so that IoT.bzh can plan their resource allocation appropriately.

4) Spec update plan for overall architecture.

• Need to work on the use cases as a first step.
• Will start wiki page with overall system use cases?
• Start with a 3 - 5 page white paper/blueprint that describes what AGL is.

5) Plan for adding boards to the distribution

• What commitment do we expect from the board owner to accept it into the build?
  • Define the difference between an “official reference board” and someone adding a board they are interested in.
  • Two boards (or more) to be provided for board farm.
  • Need resource commitment for the board sponsor to maintain the BSP
  • Start up kit (documentation) that gets a developer up and running on the board in a short amount of time.

Face to Face meeting at AMM Attendees: Walt, Fulup,, Jens Bocklage, Stephane Desneux, Ryota Okubi, Ned Miljevic,, Yoshiuki Ito, Bai, Goto, Hideo Yamashita, Tanikawa, Michael

Notes: Issues that were brought up that should be covered by the SAT.

• (Ned) User stories for overall system functionality
• (Ned) Release contents
• (Okubi) Requirement Spec concerns
  • Review the system architecture diagram that is in the system architecture document.
  • Which parts of the spec should be published
  • Gap between the spec and implementation
• (Okubi) How to guide for taking AGL Yocto layers and reusing them in a production project.
• (Walt) SAT should have ownership of Yocto layers and device profiles
• (Goto) Difficult to understand the architecture. Need more diagrams and documentation.
• (Tanikawa) Source code management. Create source code repos
  • Layer management
  • Package management
• (Fulup) Coordination of the Expert Groups
• (Fulup) Need to meet more often than the AMMs, possibly at other LF events such as ELC.
• (Fulup) Need to define what is supported/mandatory for AGL and what is left to the end (product) developer.
• (Michael) Need to fix the block diagram.

Attendees: Walt, Fulup, Michael Fabry, Jens Bocklage, Joel Hoffman, Stephane Desneux, Jan-Alexandru Vaduva, Ryota Okubi, Ned Miljevic, Agustin Benito, Yoshiuki Ito, Nuohan, Andrew Wells, Tsuyoshi Sakamoto, Jan-Simon Moeller, Bai, Goto, Hideo Yamashita

Notes: Kickoff meeting prior to the AMM.

Meeting Minutes February 5, 2015
Meeting Minutes January 29, 2015
Meeting Minutes January 15, 2015
Meeting Minutes December 18, 2014
Meeting Minutes December 11, 2014
Meeting Minutes November 20, 2014
Meeting Minutes November 13, 2014
Meeting Minutes November 6, 2014
Meeting Minutes October 30, 2014
Meeting Minutes October 23, 2014

Topics:

• Approval of Meeting Minutes of 9/25

• Announcements?

Old Business

• Yocto Project Build Update. (Team)
  • AI: Mikko to clarify Tizen IVI environment
  • Discuss next steps for Wind River proposal and proposed project.

• Gap Analysis Update (Yamamoto-san/ Nori)
  • No update this week. Face-to-face meeting scheduled for Friday in Japan

• Specification project
  • DOORS Update (Walt/ Paul)
  • Requirements Management Process?

• Face-to-Face Meetings
  • GENIVI AMM October 7-10 we will have a quorum
    • Agenda is being posted to f2f planning
    • AI: Walt working out a meeting time with the GENIVI SAT.

• AGL Specification Domain Structure
  • Wiki page was created using the email sent by Mikko.
  • Since this feeds directly into the DOORS NG structure we need to finalize this ASAP.
  • AI: Walt to send an email to SAT list with a request for comments. Goal is approve this at or before the GENIVI AMM face to face meeting.

• Security Framework
• Security viewed as a key topic that needs to be addressed by AGL
• Form and EG - Need outside expertise?
• Create manageable areas of focus like secure updates or network security
• Are there other automotive focused consortia that we can work with?

New Business:

• Software Configuration Management

Action Items:

• [Pending, 3rd week of September] Quality Attributes (Rick to start wiki page on this topic)

Topics:

• Approval of Meeting Minutes of 9/18
  • Approved

• Announcement that Renesas will now participate in the System Architecture Team. Yoshiyuki Miki will attend the SAT meetings representing Renesas.
• Announcement that Nori Fukuyasu of The Linux Foundation will not participate in the System Architecture Team as the representative from the Gap Analysis Expert Group.

• Yocto Project Build Update. (Team)
  • AI: Mikko to clarify Tizen IVI environment
  • AI: Walt will send out Wind River proposal for further analysis prior to meeting with Wind River [Closed]
  • Tabled until next week

• Gap Analysis Update (Yamamoto-san/ Nori)
  • Additional analyses were posted for the AGL spec to Tizen IVI 3.0 analysis that is in progress
  • Yamamoto has done some work on the AGL to GENIVI 6 gap analysis that has not been posted yet.

• DOORS Update (Walt)
• Specification Project
  • DOORS is now up and running and Phil has been able to put artifacts into the database. Paul meeting with him tomorrow and we will send out a further update.

• Face-to-Face Meetings
  • GENIVI AMM October 7-10 we will have a quorum
    • Agenda is being posted to f2f planning
    • Agenda topics need to finalized.
    • AI: Walt working out a meeting time with the GENIVI SAT.

• AGL Specification Domain Structure
  • Wiki page was created using the email sent by Mikko.
  • Since this feeds directly into the DOORS NG structure we need to finalize this ASAP.
  • AI: Walt to send an email to SAT list with a request for comments. Goal is approve this at or before the GENIVI AMM face to face meeting.

• New Business
• Security Framework
• Security viewed as a key topic that needs to be addressed by AGL
• Form and EG - Need outside expertise?
• Create manageable areas of focus like secure updates or network security
• Are there other automotive focused consortia that we can work with?

Action Items:

• [Pending, 3rd week of September] Quality Attributes (Rick to start wiki page on this topic)

Topics:

• Approval of Meeting Minutes of 9/11
  • Approved
• Future meeting times? 6:00 am PDT, 3:00 pm PDT, 9 pm PDT
• Yocto Project Build Update. (Team)
  • Tizen IVI build able using Yocto tools was announced on Tizen mail list this week.
    • Support is in parallel to OBS build
    • meta-ivi not included (P1 and some P2 GENIVI components)
    • meta-tizen is included (P1 GENIVI components)
      • AI: Mikko to clarify Tizen IVI environment
    • AI: Walt will send out Wind River proposal for further analysis prior to meeting with Wind River
• Gap Analysis Update (Yamamoto-san)
  • Nori reported out at Steering Committee meeting last night
  • Some documents need to be translated to english and will be published on wiki.
  • Next step will be to determine a plan to fill in the gaps between AGL spec and Tizen IVI
  • Next F2F meeting is first week of October
• DOORS Update (Walt)
• Specification Project
  • No progress. DOORS is considered a blocking point.
  • Need to clarify the targets for the gap analysis (There are currently five gap analysis proposals floating around) and the process for coming to agreement on the specification.
  • Had a discussion concerning how do we move forward with getting an agreed upon spec. Give DOORS another week then start coming up with alternate methods for making progress.

• Face-to-Face Meetings
  • GENIVI AMM October 7-10 we will have a quorum
    • Agenda topics need to finalized.
    • AI: Meeting with GENIVI SAT? Would like to get approval and goals from the SC prior to meeting with GENIVI SAT.
  • Dusseldorf - probably nothing formal. Not enough participation.
  • Wiki page created for f2f planning. Need SAT members to enter their availability.

Action Items from last meeting:

• [Pending, 3rd week of September] Quality Attributes (Rick to start wiki page on this topic)
• [Pending] Domain Structure for AGL Specification. Proposal received from Mikko that needs to be reviewed. Mikko to reply to last email on this topic to restart the discussion or preferably to start a wiki page to capture the approach.

Topics:

• Approval of Meeting Minutes of 8/14, 8/21, 8/28
  • Will be done by email
• Introductions (Team)
• Update from Steering Committee Meeting
  • Reviewed "Top 10" Project list
  • Took a quick look at IVI Full Prototype and Tizen Gap Analysis
• Yocto Project Build Update. (Team)
  • Walt will forward Wind River proposal to team and request a review with Wind River
• Gap Analysis Update (Yamamoto-san)
  • Japan AGL members meeting tomorrow to review their analyses.
• DOORS Update (Walt)
  • Progress made this week with IBM, but DOORS is not ready for release.
• Specification Project
  • No progress. DOORS is considered a blocking point.

• Face-to-Face Meetings
  • GENIVI AMM October 7-10 ?
  • Dusseldorf ?
  • Wiki page created for f2f planning. Need SAT members to enter their availability.

Action Items from last meeting:

• [Pending, 3rd week of September] Quality Attributes (Rick)
• [Pending] Domain Structure for AGL Specification
• [Pending] Planning of Face-to-face Meeting potentially at GENIVI AMM in Detroit

Attendees:

• Mikko Ylinen, Intel
• Tatsushi Yamamoto, Denso
• Isao Ishibashi, Fujitsu TEN
• Takehiko Yasuda, Panasonic

Topics:

• Approval of Meeting Minutes of 8/14
  • Meeting minutes have not yet been prepared
• Yocto Project Build
  • Rudi contacted Georg Doll at Wind River, who presented at the SC meeting, to set up meetings with the technical experts. No concrete dates yet as Georg is out of the office.
  • Participation is required from Holger Behrens who maintains the meta-ivi layer and Dominique Le Foll who manages the Tizen Yocto build.
• Mikko indicated that the Yocto team at Intel is now working on integrating Tizen IVI specific packages on top of Tizen Common. First results are expected in a couple of weeks.
• Gap Analysis
  • Yamamoto-san explains that currently six companies are working on the gap analysis: Aisin AW, Denso, Fujitsu TEN, Panasonic, Pioneer and Toyota.
  • There will be a f2f meeting on 9/12 on which the group will work out the details:
    • Strict rules on the target of the comparison to make it meaningful
    • Deep analysis on the component level e.g. GENIVI Audio Manager vs Murphy
  • Results will be shared with the broader AGL audience in 2 to 3 weeks.
• Specification Project
  • DOORS is still experiencing technical issues. Rudi is working with IBM support on the resolution. The root cause of the problem may be related to the IP and port forwarding since the issue does not occur when the client is on the local network.
  • Mikko is sending a proposal for a domain structure to the mailing list.
• Face-to-Face Meetings
  • Yamamoto-san proposes f2f meetings of the SC and the SAT at the GENIVI AMM taking place in Detroit on October 7 through 10.
  • Rudi will make this an agenda item for the SC meeting next week.
  • For the SAT, who is planning on attending the GENIVI AMM?

Action Items from last meeting:

• [Pending, 3rd week of September] Quality Attributes (Rick)
• [Pending] Domain Structure for AGL Specification

Action Items from this meeting:

• [Pending] Planning of Face-to-face Meeting potentially at GENIVI AMM in Detroit

Attendees:

• Rick De Vriese, STC
• Isao Ishibashi, Fujitsu TEN
• John Avery, Panasonic
• Paul Wheller, JLR
• Tatsushi Yamamoto, Denso

Topics:

• Approval of Meeting Minutes of 8/7
  • Unanimously approved

• Yocto Project Build
  • Need to understand what dependencies using the Wind River meta-ivi layer will impose on Tizen IVI.
  • It is currently unknown if meta-ivi works with meta-tizen or if there are conflicts and what they are. What trade-offs would need to be made and if they are acceptable to the SC and the companies' business goals and requirements.
  • As a first step we will need to bring the experts from Wind River and the Intel experts for meta-tizen together to analyze meta-ivi and meta-tizen and gain a better understanding.
  • Subsequently we will need to estimate effort, trade-offs and architecture in the light of the AGL business goals and develop a proposal for the SC.

• Gap Analysis
  • The gap analysis conducted by STC to get a structured overview of what can be built with Tizen IVI today and what is missing to meet requirements and use cases of a current IVI system.
  • The analysis was carried out by using the material published about Tizen IVI on the web as well as be analyzing the released code.
  • For AGL we may also want to consider other gap analyses such as features, components, specification, APIs etc.
• Codification / Documentation Project
  • It would be beneficial to better codify document Tizen IVI and AGL. This could be a value-adding project that the SAT could provide to the SC and the member companies.
  • For the most value we need to start with who the stakeholders are e.g. engineers, system architects, project managers, etc. Stakeholders have different perspectives.
• Specification Project
  • The SAT needs to work on a domain structure to organize the AGL specification.

Action Items from last meeting:

• [Pending, 3rd week of September] Quality Attributes (Rick)

Action Items from this meeting:

• [Pending] Domain Structure for AGL Specification (Mikko).

Attendees:

• Mikko Ylinen, Intel
• Takehiko Yasuda, Panasonic
• Rudolf Streif, Linux Foundation

Topics:

• Approval of Meeting Minutes of 8/7
  • Since we did not have a quorum the minutes were not approved
  • Approval via e-mail
• AGL Charter
  • Presented to SC via mailing list for review, commenting and approval
• AGL Specification
  • SAT should be responsible for the specification including procedures and structure to review
  • DOORS system is up but there is a technical issue that we are trying to resolve with IBM support
  • JLR hired Phillip Rutten who will be responsible for DOORS as the “master maintainer”
  • We will have individual maintainers for the various functional areas. These maintainers will need to be trained in usage of DOORS as well as the structure

Action Items from last Meeting:

• [Completed] Add version number to charter on wiki (Rudi)
• Quality Attributes (Rick)

Action Items from this Meeting:

• Ideas and suggestions on how to structure requirements and review process (all, Mikko to start thread on SAT mailing list)

Attendees:

• Rick De Vriese, STC
• Isao Ishibashi, Fujitsu TEN
• Yuichi Kusakabe, Fujitsu TEN
• Paul Weller, JLR
• Tatsushi Yamamoto, Denso
• Takehiko Yasuda, Panasonic
• Rudolf Streif, Linux Foundation

Topics:

• Approval of Meeting Minutes of 7/31
  • Unanimously approved
  • Ready to be published on wiki
• AGL Charter
  • Add version number to charter
  • Present to Steering Committee for approval
• Election of Chairperson
  • Nominations via e-mail
• Work Items
  • Quality Attributes
    • Rick to prepare a presentation for the SAT
  • GAP Analysis
    • Some of the Japanese companies are working on a gap analysis for AGL
    • Target is unclear since AGL spec has not yet been completed
    • SAT should and will support SC in the gap analysis but first we need to set up the DOORS requirements database
• Action Items from last Meeting
  • [Completed] Please review charter and respond to this e-mail whether you approve the charter for presentation to the Steering Committee at the meeting next week. This is not an approval for your company. It is for consensus among the SAT Core Members that we agree to present the charter to the SC. The SC members will then review and eventually approve.
  • [Completed] Subscribe to Wiki changes: the sidebar of each page now has an icon (an envelope). You manage your subscription to pages with it.
  • [Completed] Rudi to create a SAT mailing list.
• Action Items from this Meeting
  • [Completed] Add version number to the charter (Rudi)
  • Quality attributes (Rick)

Attendees:

• Dan Cauchy, Linux Foundation
• Rick De Vriese, STC
• Tatsushi Yamamoto, Denso
• Takehiko Yasuda, Panasonic
• Rudolf Streif, Linux Foundation

Topics:

• Review of AGL Charter
  • Clarified and improved wording
  • Expanded on Deliverables
• AGL Wiki
  • Wiki broken up into multiple pages to ease reading and editing:
    • agl-sat - Main SAT page
    • agl-sat-charter - Charter
    • agl-sat-meetings - Meeting Minutes
  • Enabling subscriptions and e-mail notifications of changes.
    • Once a day the Wiki will send e-mail notifications of changes made to pages to which registered Wiki users have subscribed to.
• SAT Meeting Minutes
  • SAT meeting minutes are published on the Wiki.
  • Minute taker will send out minutes to SAT members before; minutes will be reviewed during the next SAT meeting and published thereafter.

Action Items:

• Please review charter and respond to this e-mail whether you approve the charter for presentation to the Steering Committee at the meeting next week. This is not an approval for your company. It is for consensus among the SAT Core Members that we agree to present the charter to the SC. The SC members will then review and eventually approve.
• Subscribe to Wiki changes: the sidebar of each page now has an icon (an envelope). You manage your subscription to pages with it.
• Rudi to create a SAT mailing list.

Attendees:

• Takehiko Yasuda, Panasonic
• Tatsushi Yamamoto, Denso
• Richard De Vriese, STC
• John Avery, Panasonic
• Rudolf Streif, Linux Foundation

Agenda:

• Continued work on SAT Charter
• SAT deliverables and tools: documentation, architecture diagrams, interface specifications.
• Sparx Systems Enterprise Architect deemed to be a good solution for the task. GENIVI and member companies are using it already. Integration with Wiki and other tools important. Publish EA artifacts to the Wiki. PDF documents and diagrams are acceptable. Eventually linking them to EA documents.
• Complexity of defining an universal architecture that fulfills the requirements but also allows adopters to replace and/or omit components.

Action Items:

• Richard DeVriese: first definition of quality attributes and non-functional requirements
• Rudi Streif: proposal for remaining open items in charter

Attendees:

• Mikko Ylinen, Intel
• Paul Wheller, JLR
• Takehiko Yasuda, Panasonic
• Tatsushi Yamamoto, Denso
• Johan Thelin, Pelagicore
• Isao Ishibashi, Fujitsu TEN
• Rudolf Streif, Linux Foundation

Agenda:

• SAT Charter

Action Items:

• For next meeting everyone to review Charter, identify missing items, add and correct

Attendees:

• Yuichi Kusakabe, Panasonic
• Richard De Vriese, STC
• John Avery, Panasonic
• Paul Wheller, JLR
• Isao Ishibashi, Fujitsu TEN
• Rudolf Streif, Linux Foundation

Agenda:

• SAT Charter - Continue work on charter, definition of terms

Attendees:

• Paul Wheller, JLR
• Mikko Ylinen, Intel
• Richard De Vriese, STC
• Tatsushi Yamamoto, Denso
• Johan Thelin, Pelagicore
• Isao Ishibashi, Fujitsu TEN
• Rudi Streif, Linux Foundation

Agenda:

• SAT Charter - Initial discussion about the SAT charter as summarized below, all SAT members are asked to contribute and review so that we can present the charter to the SC for review and acceptance within the allocated time frame of 4 weeks from the this initial meeting.
• SAT Chairperson - We deferred the nomination and election of a chairperson until the charter is established which will contain the necessary provisions for nominating and electing the chairperson.
• SAT Meeting Cadence - We will meed weekly during the first 4 to 8 weeks until the charter is established and the first projects are kicked off. After that bi-weekly meetings with coordination via e-mail and other communication.