User Tools

Site Tools


agl-sat-meetings

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
agl-sat-meetings [2019/11/07 15:35]
waltminer
agl-sat-meetings [2020/07/02 13:58] (current)
wminer
Line 1: Line 1:
 ====== AGL System Architecture Team (SAT) Meetings ====== ====== AGL System Architecture Team (SAT) Meetings ======
  
-Meetings of the System Architecture Team are held every other Thursday at 14:00 UTC. The upcoming schedule can be found below. ​+Meetings of the System Architecture Team are held every other Thursday at 13:00 UTC. The upcoming schedule can be found below. ​
  
 Conference Information:​ Conference Information:​
Line 17: Line 17:
 ----- -----
  
-==== November ​7, 2019 ====+==== July 2, 2020 ==== 
 +Attendees: Walt, Jan-Simon 
 + 
 +   * DRM Lease RFQ - SPEC-3388 
 +   * Fast Boot RFQ - SPEC-3371 -Reviewed the updated version that is uploaded in the Jira ticket. Added review comments in the ticket.  
 + 
 +   * Toyota Update - No update. Will be providing an update to the Steering Committee and AB. Will review the proposal with the SAT on the July 17 SAT/EG meeting.  
 + 
 +   * Reference Hardware was received in Yokohama. Will shipped out next week to members who requested it.  
 +     * Board documentation can be found on the [[https://​wiki.automotivelinux.org/​eg-rhsa#​specification | RHSA EG group page]] 
 +     * Scott commented that the documentation is insufficient without schematics for the boards.  
 +     * Walt will request the schematics from Panasonic,​ 
 +     ​* ​7/2 -Reviewed the disclaimer in the RHSA manuals.  
 + 
 +New Business: 
 +    * DRM Lease RFQ will be sent out to mail list and the responses reviewed by the IC EG. 
 +    * Sound System RFQ review. Nishiguchi-san will create a JIRA ticket for the review. ​ Would like George to take part in the review. Will ask George to participate in the July 17 SAT/EG meeting and added a time slot for the review. ​  
 + 
 + 
 + 
 +==== June 182020 ==== 
 +Attendees: Walt, Jan-Simon 
 + 
 +   * DRM Lease RFQ - SPEC-3388 
 +   * Fast Boot RFQ - SPEC-3371 - Kusakabe-san not available today. ​ Haraki-san reported that he spoke to Kusakabe-san and he will update the RFQ document for the next meeting. He will add the M2 as an alternative device as well as address the concerns from the last review.  
 + 
 +   * Toyota Update - No update. Will be providing an update to the Steering Committee and AB. 
 +   * Reference Hardware was received in Yokohama. Will shipped out next week to members who requested it.  
 +     * Board documentation can be found on the [[https://​wiki.automotivelinux.org/​eg-rhsa#​specification | RHSA EG group page]] 
 +     * Scott commented that the documentation is insufficient without schematics for the boards.  
 +     * Walt will request the schematics from Panasonic,​ 
 + 
 +New Business: 
 +    * DRM Lease RFQ will be sent out to mail list and the responses reviewed by the IC EG.  
 + 
 + 
 + 
 + 
 +==== June 4, 2020 ==== 
 +Attendees: Walt, Jan-Simon, Yamaguchi, Michael, Kurokawa, Hosokawa, Nomoto, Scott, Hanaoka, Sekine, Tanikawa, Haraki, 
 + 
 +   * Yamaguchi-san to [[https://​confluence.automotivelinux.org/​display/​IC/​Document+storage | present a proposal from the IC EG]] for the development process for IC.  
 +   * Toyota Update - Ohiwa-san not available 
 + 
 +   * Virtual AMM CFP closes on Friday. 
 + 
 + 
 + 
 + 
 +==== May 28, 2020 ==== 
 +Attendees: Walt, Jan-Simon, Scott, Kusakabe, Kurokawa, Daniel, Hosokawa, Joel Catala, Jesus Cabrera, Nishiguchi, Haraki, Bernd Niedermeier,​ Anusha,  
 + 
 + 
 +Special meeting to review IC EG RFQs 
 + 
 +   * DRM Lease RFQ - SPEC-3388 
 +   * Fast Boot RFQ - SPEC-3371 
 + 
 +==== May 21, 2020 ==== 
 +Attendees: Walt, Haraki, Scott, Sekine, Kurokawa, Nomoto, Tanikawa 
 + 
 +  * 2020 Roadmap Review  
 +     * Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list.  To be reviewed at SAT F2F at the AMM.  
 +     * Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]]. 
 + 
 +   * Yocto version discussion 
 +      * Renesas plans to use 4.14 kernel for dunfell this year and would upgrade to 5.4 for the LL release.  
 +      * SAT agreed on the following plan for YP versioning + Renesas BSP kernel version. Other platforms will support 5.4 kernel at initial release.  
 +        * JJ - YP 3.1 + 4.14 kernel (best case end of June to IoT.bzh with release in July) 
 +        * KK - YP 3.1 + 4.14 kernel 
 +        * LL - YP 3.1 + 5.4 kernel.  
 +        * MM - YP 3.1 + 5.4 Kernel  
 +      * Yamaguchi-san asked about support for Ubuntu 20.4.  Probably has not been tested. Ubuntu release is 1 day before the YP release so it is unlikely to be explicitly support on day 1.  Jan-Simon will check with YP on their plans for 20.4 support.  
 +    * 4/23 - Plan to merge next with dunfell (YP 3.1) to master. Scott has built all platforms except Renesas.  
 +      * YP 3.1 was released April 21 (Tuesday) 
 +      * Noted an issue with using the QEMU image on Intel hardware that needs to be addressed.  
 +      * QEMU runs fine 
 +      * H3 and BBE do not work in CI.  
 +      * Jan-Simon notes that H3 would boot to kernel with old version of the BSP by adding Ronan'​s patches in gerrit plus another one. Would need to skip H3 from test suite until official patch comes out from Renesas. Could leave it in CI and only run boot test.  
 +      * BBE fails uboot so it needs to be updated by Sanclound. Will need to be skipped in CI 
 +      * Target from Renesas is May 18 for the starter kit BSP update.  
 +      * Ubuntu 20.4 releases today and Fedora 32 is coming out soon, We expect that the next point release of 3.1 will include support for both of them.  
 +      * Proposal is to merge next to master next week.  
 +    * 5/5 - Merge to master is complete. Work is ongoing for RCar H3 BSP. Will be pushed to their GitHub end of next week.  
 +    * 5/21 - Merge complete. Looking pretty good.  Yocto accepting patches upstream and about two start a two week cycle for merging updates. Schedule for point releases is still under discussion. 3.1.1 current plan is to release July. Will stick to point releases only for master and our release branches.  
 + 
 +   * Reviewed the Fast Boot RFQ developed by Kusakabe-san for the IC EG 
 +     * Kusakabe-san will post the document for further review.  
 +     * Plenty of comments were provided. Another round of updates will take place and a new version will be available in two weeks (Kusakabe-san to confirm the timing) for the next SAT call.  
 +     * 4/23 - Revised version was delayed due to coronavirus issues at Denso-Ten. ​ Should be ready for the next meeting.  
 +     * 5/5 - Updated version was posted to the SC, but not generally to the community. We will release the document to the community and review it at the next SAT call.  
 +     * 5/21 - Document posted to SPEC-3371. ​ Added comments in the Jira ticket during the call.  IC EG needs to review with Kusakabe-san, ​
  
-   * Daniel getting window manager into Gerrit for Karlsruhe next week.  
    * SPEC-2927 - Window Manager for WAM    * SPEC-2927 - Window Manager for WAM
  
    * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}.    * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}.
-     * 8/29 Panasonic is reviewing ​ + 
-     ​* ​9/12 Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco. ​ +     ​* ​5/PO went out last week, Delivery expected end of May 
-     ​* ​9/26 - Still in review ​at PanasonicSekine-san expects a reply soon +     ​* ​5/21- Still expecting hardware ​at the end of Maywill be shipped to Yokohama LF office and then sent to companies that have requested itSoftware delivery from Panasonic will not be downloadablebut provided on media. Expected deliverable ​will be patches against ​the Renesas BSP
-     * 10/10 - Sekine-san thinks ​Panasonic will release the RFQ in time to be reviewed in Monte CarloWalt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.  +
-     * 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week+
    
-   ​* ​Gap analysis ​- Denso Ten will release documentation for radio and tuner functions by the end of September.  +   ​* ​Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September.  
-     ​* ​9/12 - document ​is 60% translated to english. Kusakabe ​will present an update at the dev call next week.  +     ​* ​3/26 Kusakabe-san prepared a draft document ​that will be reviewed during ​the Connectivity EG meeting ​next week. 
-     * 9/26  +
-       ​* ​ **Radio API review ** +
-       * Sample API of Denso Ten released in staging/​documents +
-       * Goal is to refine the radio api with additional functions found in the review of above +
-       * focus on generic calls over hw specifics +
-       * Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM +
-       * Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done +
-     * 10/10 +
-       * Kusakabe posted the API to Gerrit https://​git.automotivelinux.org/​staging/​documents/​log/?​h=sandbox/​kusakabe/​radio-api +
-       * Kusakabe to release additional APIs by the end of the month +
-       * Scott needs to review. Need some additional Tier 1 or OEM reviewers.  +
-     * 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API+
  
    * LTS  ​    * LTS  ​
Line 63: Line 139:
       * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​       * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​
       * Will add to SC agenda for next week.        * Will add to SC agenda for next week. 
 +    * 11/21 - SC did not get to this topic, Will be addressed at December meeting. ​
 +    * 12/5 - Following up next week. 
 +    * 1/16 - Added LTS to the SC agenda for February. ​
 +    * 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting, ​
  
    * Toyota Code Drop    * Toyota Code Drop
Line 69: Line 149:
        * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,        * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
      * 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.       * 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC. 
 +     * 11/21 - 
 +     * Notes from SC meeting ​
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure. ​
 +     * Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents. ​
 +     * 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.  ​
 +       * Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended.
 +       * Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash). ​
 +       * Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.  ​
 +     * 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://​confluence.automotivelinux.org/​display/​TC/​Documents
 +     * 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0. 
 +     * 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.{{:​sat_meetings:​document_for_sat_20200312.pdf|latest status}} ​
 +     * Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG. 
 +     * 3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions. ​
 +     * 4/9 - SPEC-3322 written with details on the code that was uploaded to gerrit including build instructions and other documentation in [[https://​confluence.automotivelinux.org/​pages/​viewpage.action?​spaceKey=TC&​title=Documents | Confluence.]] ​
 +     * 4/23 - Ohiwa-san reviewed the use cases that he added to SPEC-3322. Questions about the specifics of the use cases. ​
 +       * Positioning - What is the difference between what agl-service-gps and the Toyota code that was dropped and what benefits are there to changing to it?  AGL is using open source components that are well maintained upstream. ​
 +       * Communication - What is difference between agl-service-can-low-level and Toyota'​s communication component and what benefits do we derive from switching the Toyota component?
 +       * Tanikawa-san - Is there a statement of what the purpose of the code drop is? What is Toyota'​s expectation and vision for contributing this code? How are we going to use this code?
 +       * Additional questions can be added to the [[https://​confluence.automotivelinux.org/​x/​YoAAAQ | Confluence Q&A page]] ​
 +     * 5/5 - Presentation is being prepared to address the questions asked at the last meeting and should be ready in early June.  ​
 +       * Ohiwa-san showed a comparison of the Toyota code with the AGL positioning and low CAN service and concluded that there is no large gap between the what AGL has and the Toyota code. 
 +     * 5/22 - Nothing to report. Ohiwa-san out sick. 
 + 
 + 
 +   * ELISA updates
 +     * ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found [[https://​elisa.tech/​announcement/​2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/​ | here]] ​
 +     * ELISA groups.io page can be found [[https://​lists.elisa.tech/​g/​devel | here ]]
 +     * New ELISA development process subgroup has formed. See their [[ https://​lists.elisa.tech/​g/​devel/​topic/​please_join/​61718502?​p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 | groups.io page]] for more information and to sign up. 
 +     * 4/26 - Dr. Yamaguchi provided an update on the [[https://​wiki.automotivelinux.org/​_media/​sat_meetings/​agl_elisa_collabo_v3.pdf | ELISA AGL cooperation proposal]]. ​
 +     * 5/5 - Preparing for the ELISA virtual workshop later this month. There is a new automotive working group that will be kicked off during the workshop. ​
 +     * 5/22 - ELISA workshop was held this week. Slides from presentations are still be updated. Dr. Y will provide further updates during the next SAT meeting. Automotive WG was kicked off and is working out their charter. Dr. Y will propose to the AGL AB that Walt participate in the ELISA Automotive WG by attending their meetings and reporting back to the SAT and SC on their progress. ​
  
-   Navi EG met last week with Momiyama-san ​and they will present a new architecture ​at the November SAT call.  +  
-     ​11/More discussion needed before Navi EG is ready to present the new architecture+ 
 +FOSSology/ License Review 
 +   So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work.  Will be brought up to AB at their next meeting. ​  
 +   * Open Chain reported that we have 320 different licenses. ​ How do we plan to collaborate with OpenChain?​ 
 +   * Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.  
 +   * 3/26 - Multiple issues blocking getting FOSSology server going,  
 +   * 4/23 - 9.0.1 run and results sent to Li.  360,000 files that need to be cleared if we look at the entire code base including the kernel. ​ Li asked if we can limit it to just the AGL created code which would limit it to 2000ish files.  
 +   ​5/Li started reviewing the QEMU results today and should be finished this week.  
 +   * 5/22 - Review ​is ongoing. Open question of what to with packages that were not reviewed. Only AGL developed packages are currently being reviewed 
  
 New Business: New Business:
-  
-- SPEC-720 - Run-time hardware detection - Stephane discussed the current status of the work IoT.bzh has done. No objections to what they have done so far.  
  
 +   * Kurokawa-san completed the first draft of the DRM sharing RFQ. Will put in a JIRA ticket and we will schedule a separate SAT call for next Thursday to review since we anticipate the next regular SAT call to be busy with the new Toyota proposal. Will also see if we can get Kusakabe-san on the call to discuss the fast boot RFQ.
  
  
-==== October 10, 2019 ==== 
-Attendees: Walt, Jan-Simon, Nick, Scott, Haraki, Sekine 
  
-  * HH 8.0.2 Pre-release sent out. Edi is currently testing and should be done tomorrow. ​+==== May 7, 2020 ==== 
 +Attendees: Walt, Jan-Simon, Scott, Li, Michael, Andrey, Mikhail, Leonid, Sebastien, Hosokawa, Ohiwa, Nishiguchi, Dr, Yamaguchi, Mr, K, Haraki, ​
  
 +  * 2020 Roadmap Review ​
 +     * Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list.  To be reviewed at SAT F2F at the AMM. 
 +     * Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]].
 +
 +   * Yocto version discussion
 +      * Renesas plans to use 4.14 kernel for dunfell this year and would upgrade to 5.4 for the LL release. ​
 +      * SAT agreed on the following plan for YP versioning + Renesas BSP kernel version. Other platforms will support 5.4 kernel at initial release. ​
 +        * JJ - YP 3.1 + 4.14 kernel (best case end of June to IoT.bzh with release in July)
 +        * KK - YP 3.1 + 4.14 kernel
 +        * LL - YP 3.1 + 5.4 kernel. ​
 +        * MM - YP 3.1 + 5.4 Kernel ​
 +      * Yamaguchi-san asked about support for Ubuntu 20.4.  Probably has not been tested. Ubuntu release is 1 day before the YP release so it is unlikely to be explicitly support on day 1.  Jan-Simon will check with YP on their plans for 20.4 support. ​
 +    * 4/23 - Plan to merge next with dunfell (YP 3.1) to master. Scott has built all platforms except Renesas. ​
 +      * YP 3.1 was released April 21 (Tuesday)
 +      * Noted an issue with using the QEMU image on Intel hardware that needs to be addressed. ​
 +      * QEMU runs fine
 +      * H3 and BBE do not work in CI. 
 +      * Jan-Simon notes that H3 would boot to kernel with old version of the BSP by adding Ronan'​s patches in gerrit plus another one. Would need to skip H3 from test suite until official patch comes out from Renesas. Could leave it in CI and only run boot test. 
 +      * BBE fails uboot so it needs to be updated by Sanclound. Will need to be skipped in CI
 +      * Target from Renesas is May 18 for the starter kit BSP update. ​
 +      * Ubuntu 20.4 releases today and Fedora 32 is coming out soon, We expect that the next point release of 3.1 will include support for both of them. 
 +      * Proposal is to merge next to master next week. 
 +    * 5/5 - Merge to master is complete. Work is ongoing for RCar H3 BSP. Will be pushed to their GitHub end of next week. . 
 +
 +   * Reviewed the Fast Boot RFQ developed by Kusakabe-san for the IC EG
 +     * Kusakabe-san will post the document for further review. ​
 +     * Plenty of comments were provided. Another round of updates will take place and a new version will be available in two weeks (Kusakabe-san to confirm the timing) for the next SAT call. 
 +     * 4/23 - Revised version was delayed due to coronavirus issues at Denso-Ten. ​ Should be ready for the next meeting. ​
 +     * 5/5 - Updated version was posted to the SC, but not generally to the community. We will release the document to the community and review it at the next SAT call. 
 +
 +   * SPEC-2927 - Window Manager for WAM
  
    * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}.    * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}.
Line 90: Line 238:
      * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.       * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon. 
      * 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.       * 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG. 
 +     * 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week. 
 +     * 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP.  Also will get a quote for creating the BSP from Konsulko.  ​
 +     * 12/4 - Block diagram [[ https://​wiki.automotivelinux.org/​_media/​eg-rhsa/​r-car_h3_reference_hardware_blockdiagram_20191126.pdf | uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday. ​
 +     * 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP. 
 +     * Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic. ​
 +     * 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely. ​
 +     * 3/26 - BSP RFI responses to be reviewed. AB tentatively approved purchasing the boards pending the Qualcomm and BSP discussions. ​
 +     * 5/5 - PO went out last week, Delivery expected end of May
    
-   ​* ​Gap analysis ​- Denso Ten will release documentation for radio and tuner functions by the end of September.  +   ​* ​Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September.  
-     ​* ​9/12 - document ​is 60% translated to english. Kusakabe ​will present an update at the dev call next week.  +     ​* ​3/26 Kusakabe-san prepared a draft document ​that will be reviewed during ​the Connectivity EG meeting ​next week. 
-     * 9/26  +
-       ​* ​ **Radio API review ** +
-       * Sample API of Denso Ten released in staging/​documents +
-       * Goal is to refine the radio api with additional functions found in the review of above +
-       * focus on generic calls over hw specifics +
-       * Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM +
-       * Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done +
-     * 10/10 +
-       * Kusakabe posted the API to Gerrit https://​git.automotivelinux.org/​staging/​documents/​log/?​h=sandbox/​kusakabe/​radio-api +
-       * Kusakabe to release additional APIs by the end of the month +
-       * Scott needs to review. Need some additional Tier 1 or OEM reviewers+
  
    * LTS  ​    * LTS  ​
Line 120: Line 265:
   * '​core'​ LTS vs. IVI or Cluster LTS   * '​core'​ LTS vs. IVI or Cluster LTS
     * depends on changes required e.g. by IC      * depends on changes required e.g. by IC 
 +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.  ​
 +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects. ​
 +      * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​
 +      * Will add to SC agenda for next week. 
 +    * 11/21 - SC did not get to this topic, Will be addressed at December meeting. ​
 +    * 12/5 - Following up next week. 
 +    * 1/16 - Added LTS to the SC agenda for February. ​
 +    * 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting, ​
  
    * Toyota Code Drop    * Toyota Code Drop
      * 10/10       * 10/10 
        * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion. ​        * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion. ​
-       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community, ​+       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community, 
 +     * 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.  
 +     * 11/21 -  
 +     * Notes from SC meeting  
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.  
 +     * Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents.  
 +     * 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas. ​  
 +       * Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended. 
 +       * Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).  
 +       * Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting. ​  
 +     * 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://​confluence.automotivelinux.org/​display/​TC/​Documents 
 +     * 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.  
 +     * 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.{{:​sat_meetings:​document_for_sat_20200312.pdf|latest status}}  
 +     * Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG.  
 +     * 3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions.  
 +     * 4/9 - SPEC-3322 written with details on the code that was uploaded to gerrit including build instructions and other documentation in [[https://​confluence.automotivelinux.org/​pages/​viewpage.action?​spaceKey=TC&​title=Documents | Confluence.]]  
 +     * 4/23 - Ohiwa-san reviewed the use cases that he added to SPEC-3322. Questions about the specifics of the use cases.  
 +       * Positioning - What is the difference between what agl-service-gps and the Toyota code that was dropped and what benefits are there to changing to it?  AGL is using open source components that are well maintained upstream.  
 +       * Communication - What is difference between agl-service-can-low-level and Toyota'​s communication component and what benefits do we derive from switching the Toyota component?​ 
 +       * Tanikawa-san - Is there a statement of what the purpose of the code drop is? What is Toyota'​s expectation and vision for contributing this code? How are we going to use this code? 
 +       * Additional questions can be added to the [[https://​confluence.automotivelinux.org/​x/​YoAAAQ | Confluence Q&A page]]  
 +     * 5/5 - Presentation is being prepared to address the questions asked at the last meeting and should be ready in early June.   
 +       * Ohiwa-san showed a comparison of the Toyota code with the AGL positioning and low CAN service and concluded that there is no large gap between the what AGL has and the Toyota code.  
 +  
 +  
 +   * ELISA updates 
 +     * ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found [[https://​elisa.tech/​announcement/​2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/​ | here]]  
 +     * ELISA groups.io page can be found [[https://​lists.elisa.tech/​g/​devel | here ]] 
 +     * New ELISA development process subgroup has formed. See their [[ https://​lists.elisa.tech/​g/​devel/​topic/​please_join/​61718502?​p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 | groups.io page]] for more information and to sign up.  
 +     * 4/26 - Dr. Yamaguchi provided an update on the [[https://​wiki.automotivelinux.org/​_media/​sat_meetings/​agl_elisa_collabo_v3.pdf | ELISA AGL cooperation proposal]].  
 +     * 5/5 - Preparing for the ELISA virtual workshop later this month. There is a new automotive working group that will be kicked off during the workshop.  
 + 
  
-   Navi EG met last week with Momiyama-san ​and they will present a new architecture ​at the November SAT call+FOSSology/ License Review 
 +   So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work.  Will be brought up to AB at their next meeting. ​  
 +   * Open Chain reported that we have 320 different licenses. ​ How do we plan to collaborate with OpenChain?​ 
 +   * Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.  
 +   * 3/26 - Multiple issues blocking getting FOSSology server going,  
 +   * 4/23 - 9.0.1 run and results sent to Li.  360,000 files that need to be cleared if we look at the entire code base including the kernel. ​ Li asked if we can limit it to just the AGL created code which would limit it to 2000ish files.  
 +   * 5/5 - Li started reviewing the QEMU results today and should be finished this week
  
 New Business: New Business:
- +   * New AGL service binder proposal for cloud proxy. See [[https://​jira.automotivelinux.org/​browse/​SPEC-3351 | SPEC-3351]]
  
  
-==== September 262019 ==== +==== April 232020 ==== 
-Attendees: Walt, MichaelOhiwaSekineother attendees at Berlin F2F Meeting+Attendees: Walt, Jan-SimonScottYamaguchiKurokawa, Abe, Tanikawa, Haraki, Ohiwa
  
-  * HH 8.0.1 released+  * 2020 Roadmap Review  
-   ​GG 7.0.4 almost readyEdi almost done with testing and so far it is positive.  ​+     * Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list To be reviewed at SAT F2F at the AMM.  
 +     ​Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]].
  
 +   * Yocto version discussion
 +      * Renesas plans to use 4.14 kernel for dunfell this year and would upgrade to 5.4 for the LL release. ​
 +      * SAT agreed on the following plan for YP versioning + Renesas BSP kernel version. Other platforms will support 5.4 kernel at initial release. ​
 +        * JJ - YP 3.1 + 4.14 kernel (best case end of June to IoT.bzh with release in July)
 +        * KK - YP 3.1 + 4.14 kernel
 +        * LL - YP 3.1 + 5.4 kernel. ​
 +        * MM - YP 3.1 + 5.4 Kernel ​
 +      * Yamaguchi-san asked about support for Ubuntu 20.4.  Probably has not been tested. Ubuntu release is 1 day before the YP release so it is unlikely to be explicitly support on day 1.  Jan-Simon will check with YP on their plans for 20.4 support. ​
 +    * 4/23 - Plan to merge next with dunfell (YP 3.1) to master. Scott has built all platforms except Renesas. ​
 +      * YP 3.1 was released April 21 (Tuesday)
 +      * Noted an issue with using the QEMU image on Intel hardware that needs to be addressed. ​
 +      * QEMU runs fine
 +      * H3 and BBE do not work in CI. 
 +      * Jan-Simon notes that H3 would boot to kernel with old version of the BSP by adding Ronan'​s patches in gerrit plus another one. Would need to skip H3 from test suite until official patch comes out from Renesas. Could leave it in CI and only run boot test. 
 +      * BBE fails uboot so it needs to be updated by Sanclound. Will need to be skipped in CI
 +      * Target from Renesas is May 18 for the starter kit BSP update. ​
 +      * Ubuntu 20.4 releases today and Fedora 32 is coming out soon, We expect that the next point release of 3.1 will include support for both of them. 
 +      * Proposal is to merge next to master next week. 
  
-   ​* ​RHSA RFQ - updated ​the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}. +   ​* ​Reviewed the Fast Boot RFQ developed by Kusakabe-san for the IC EG 
-     ​* ​8/29 Panasonic is reviewing  +     ​* ​Kusakabe-san will post the document for further review.  
-     * 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during ​the AMM in Monaco.  +     ​* ​Plenty of comments were provided. Another round of updates will take place and a new version will be available ​in two weeks (Kusakabe-san to confirm the timing) ​for the next SAT call.  
-     ​* ​9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.  +     ​* ​4/23 Revised version was delayed due to coronavirus issues at Denso-Ten ​Should be ready for the next meeting. ​
-  +
-   * Gap analysis - Denso Ten will release documentation ​for radio and tuner functions by the end of September.  +
-     ​* ​9/12 document is 60% translated ​to englishKusakabe will present an update at the dev call next week.  +
-     * 9/26 - See Berlin F2F meeting ​minutes +
- +
-New Business: +
-     * Michael reported that the steering wheel LIN controller is now working.  +
- +
-==== September 12, 2019 ==== +
-Attendees: Walt, Jan-Simon, Kurokawa, Haraki, Yamaguchi, Scott, Stephane, Fulup. Stephane, Michael, Sekine, Sebastien +
- +
-   * HH 8.0.1 released. +
-   * GG 7.0.4 almost ready. Edi almost done with testing and so far it is positive.  ​+
  
 +   * SPEC-2927 - Window Manager for WAM
  
    * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}.    * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}.
Line 162: Line 359:
      * 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco. ​      * 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco. ​
      * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.       * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon. 
 +     * 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG. 
 +     * 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week. 
 +     * 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP.  Also will get a quote for creating the BSP from Konsulko.  ​
 +     * 12/4 - Block diagram [[ https://​wiki.automotivelinux.org/​_media/​eg-rhsa/​r-car_h3_reference_hardware_blockdiagram_20191126.pdf | uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday. ​
 +     * 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP. 
 +     * Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic. ​
 +     * 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely. ​
 +     * 3/26 - BSP RFI responses to be reviewed. AB tentatively approved purchasing the boards pending the Qualcomm and BSP discussions. ​
    
-   ​* ​Gap analysis ​- Denso Ten will release documentation for radio and tuner functions by the end of September.  +   ​* ​Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September.  
-     ​* ​9/12 document is 60% translated to english. ​Kusakabe will present an update at the dev call next week. +     ​* ​3/26 - Kusakabe-san prepared a draft document that will be reviewed during ​the Connectivity EG meeting ​next week. 
  
-   ​* ​Discuss LF Edge and EdgeX and how much interest is working with those groupsShould this be included ​in an existing EG or new EG? Push topic to V2C EG to see if there is interest there. Too many other higher priorities and not enough interest ​in this topic to create a new EG +   ​* ​LTS   
-     ​8/29 No update+     * 9/26 (Berlin F2F) 
 + * AI: identify base servicesWhat is in core-image-minimal that is available ​in all profiles.  
 +  * lifecycle 
 +    * apps vs platform (which applications  
 +    *  
 +  * API definition & documentation & Schema 
 +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/​browse/​SPEC-1903 
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md 
 +    Follow-up on SAT 
 +  * API versions 
 +    * -> APPFW Jose
  
-New Business: +  * '​core'​ LTS vs. IVI or Cluster LTS 
-  Agenda for Berlin +    depends on changes required e.g. by IC  
-  * Merging ​of Jose's sandbox ​for cyanara replacement? ​ +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.  ​ 
-    * API + Implementation.  +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects.  
-    Not really cyanara anymoreWhat do we call this?  Marketing decision. Will talk to Dan offline about that.  +      Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing.  
-    * Will be hosted ​at AGL+      * Will add to SC agenda for next week.  
 +    * 11/21 - SC did not get to this topic, ​Will be addressed at December meeting.  
 +    * 12/5 - Following up next week.  
 +    * 1/16 - Added LTS to the SC agenda for February.  
 +    * 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update ​at the next SAT meeting, ​
  
- +   * Toyota Code Drop 
-==== August 29, 2019 ==== +     * 10/10  
-Attendees: Walt, Jan-Simon, Ashvinid, Daniel, George, Haraki-san, Hosokawa-san, Kurokawa-san, Yamaguchi-san, Scott, Stephane, Sebastien +       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.  
- +       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community, 
-   ​HH 8.0.0 +     * 11/7 Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.  
-     ​* ​Edi needs to test on Halibut branch +     * 11/21 -  
-     ​* ​Scott +     ​Notes from SC meeting ​ 
-       * SPEC-2687 - Audio not working for tuner appGeorge looking at.  +     ​* ​Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure. ​ 
-       ​Kingfisher tuner not working with non-root user space rules (platform scope processes cannot access audio). Can make it work with a one-line changeWould cause respin ​of 8.0.0.   +     ​* ​Ohiwa-san is working ​on providing the context ​for the API documentsFirst task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents.  
-       ​SPEC-2707 POI app "quite broken"​. App starts but searching ​for anything causes it to crash.  +     ​12/4 Ohiwa-san presented Persistent Data Manager ​(Backup Manageruse case ideas  
-     ​* ​8/29 8.0.0 is out+       * Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended. 
- +       * Discussion of whether the backed up data is in Linux file system, a proprietary file system, or managed memory ​of some sort (battery backed RAM or flash) 
-   RHSA RFQ updated ​the RFQ document with commentsThe revised version is {{:eg-rhsa:agl_referencehardware_rfq_v0.2.pdf|here}}. +       * Other requirements need to be documented that were discussedOhiwa-san will update and we will review further at the next SAT meeting.   
-     ​* ​8/29 Panasonic ​is reviewing ​+     ​12/19 Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document ​to the Toyota code drop Confluence pagehttps://​confluence.automotivelinux.org/​display/​TC/​Documents 
 +     ​* ​1/16 - New version of the specification was uploaded to Confluence last weekCode will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.  
 +     ​3/12 Ohiwa-san showed a presentation on the latest status from Toyota.{{:sat_meetings:document_for_sat_20200312.pdf|latest status}}  
 +     * Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG.  
 +     ​* ​3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions.  
 +     * 4/9 - SPEC-3322 written with details on the code that was uploaded to gerrit including build instructions and other documentation in [[https://​confluence.automotivelinux.org/​pages/​viewpage.action?​spaceKey=TC&​title=Documents | Confluence.]]  
 +     * 4/23 - Ohiwa-san reviewed the use cases that he added to SPEC-3322. Questions about the specifics of the use cases.  
 +       * Positioning - What is the difference between what agl-service-gps and the Toyota code that was dropped and what benefits are there to changing to it?  AGL is using open source components that are well maintained upstream.  
 +       * Communication - What is difference between agl-service-can-low-level and Toyota'​s communication component and what benefits do we derive from switching the Toyota component?​ 
 +       * Tanikawa-san - Is there a statement of what the purpose of the code drop is? What is Toyota'​s expectation and vision for contributing this code? How are we going to use this code? 
 +       * Additional questions can be added to the [[https://​confluence.automotivelinux.org/​x/​YoAAAQ | Confluence Q&A page]] ​
    
- 
-   * Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September. ​ 
- 
-   * Discuss LF Edge and EdgeX and how much interest is working with those groups. Should this be included in an existing EG or new EG? - Push topic to V2C EG to see if there is interest there. Too many other higher priorities and not enough interest in this topic to create a new EG 
-     * 8/29 No update 
- 
-New Business: 
-  * Summary of IC F2F results 
-    * Documents in https://​confluence.automotivelinux.org/​display/​IC 
-  * from appfw eg: igalia working on landscape -> need draft (new) homescreen/​wm code 
-    * Daniel will get back to Igalia ​ 
-  * Agenda for Berlin will be prepared next week 
- 
-Next deadlines: 
-  * 8.0.1 planned for 9/7, submit code by 8/30 ! 
-  * 7.0.4 planned for 9/13, submit code by 9/6 ! 
- 
-==== August 15, 2019 ==== 
-Meeting cancelled due to holidays/​vacations. 
- 
- 
- 
-==== August 1, 2019 ==== 
-Attendees: Walt, Sebastien, Michael, Guy, Fulup, Nakadachi, Hosokawa, Kurokawa, Kusakabe, Yamaguchi, Ohiwa, George, Scott 
- 
-   * HH 8.0.0 
-     * Edi needs to test on Halibut branch 
-     * Scott 
-       * SPEC-2687 - Audio not working for tuner app. George looking at.  
-       * Kingfisher tuner not working with non-root user space rules (platform scope processes cannot access audio). Can make it work with a one-line change. Would cause a respin of 8.0.0.  ​ 
-       * SPEC-2707 - POI app "quite broken"​. App starts but searching for anything causes it to crash. ​ 
-     ​* ​ 
-   * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}. ​ 
    
-   ​* ​Gap analysis - Denso Ten will release documentation ​for radio and tuner functions by the end of September.  +   ​* ​ELISA updates 
-   ​Discuss LF Edge and EdgeX and how much interest is working with those groups. ​Should this be included in an existing EG or new EG? - Push topic to V2C EG to see if there is interest thereToo many other higher priorities and not enough interest in this topic to create a new EG +     * ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting ​for ELISA is in Brussel the Thursday ​and Friday before FOSDEMRegistration information can be found [[https://​elisa.tech/​announcement/​2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/​ | here]] ​ 
- +     ​ELISA groups.io page can be found [[https://​lists.elisa.tech/​g/​devel | here ]] 
- +     * New ELISA development process subgroup has formed. See their [[ https://​lists.elisa.tech/​g/​devel/​topic/​please_join/​61718502?​p=,,,20,0,0,0::​recentpostdate%2Fsticky,,,20,2,0,61718502 | groups.io page]] for more information and to sign up.  
-==== July 18, 2019 ==== +     ​3/26 - Dr. Yamaguchi provided an update ​on the [[https://wiki.automotivelinux.org/​_media/sat_meetings/agl_elisa_collabo_v3.pdf | ELISA AGL cooperation proposal]]
-Meeting held in Tokyo as part of the F2F meeting prior to ALS. See notes here +
- +
-===July 42019 ==== +
-Attendees: WaltJan-SimonMichaelSebastienStephaneHarakiMarcKusakabeGeorgeGuyKurokawaYamaguchi, Sekine, Ohiwa, Scott,  ​ +
- +
-   Updates ​on HH RC2 - Testing in progress of RC2 prerelease  +
- +
-   * AGL API gap analysis(Tier1 Linux based PF vs AGL(GG)) from Denso Ten +
-     https://confluence.automotivelinux.org/​download/attachments/9404524/​APIGapAnalysis_20190704.pdf?​version=1&​modificationDate=1562320632158&​api=v2 +
- +
-   * Steering Wheel controller for CES demo +
-     * 7/4 - Haraki-san will prepare one steering wheel in time for ALS. Will give that to Microchip. Michael investing a microcontroller for ADC to LIN conversion.  +
- +
-   * Agenda for ALS F2F +
-   * ALS Demo - Set for now.  +
-   *  +
-   * RHSA RFQ +
- +
-==== June 20, 2019 ==== +
-Attendees: Walt, Jan-Simon, Eric, Scott, Stephane, George, Daniel, Bechir, Nakadachi, Kurokawa, Sekine+
    
-   * Updates on HH RC2 - Not running as root, etc.  
-     * Not running as root merged this week. Builds come up in the CI lab. Audio not working. ​ 
-     * This [[https://​download.automotivelinux.org/​AGL/​snapshots/​master/​2019-06-20-b1183/​qemux86-64/​deploy/​ | morning'​s snapshot build]] has everything built in. Can use to test while people wait for their local builds to complete. ​ 
  
 +FOSSology/ License Review
 +   * So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work.  Will be brought up to AB at their next meeting.  ​
 +   * Open Chain reported that we have 320 different licenses. ​ How do we plan to collaborate with OpenChain?
 +   * Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year. 
 +   * 3/26 - Multiple issues blocking getting FOSSology server going, ​
 +   * 4/23 - 9.0.1 run and results sent to Li.  360,000 files that need to be cleared if we look at the entire code base including the kernel. ​ Li asked if we can limit it to just the AGL created code which would limit it to 2000ish files. ​
  
-   * Denso Ten analysis? +New Business:
-   * Steering Wheel controller for CES demo.  +
-   * Agenda for ALS F2F +
-   * ALS Demo - docker build by IoT.bzh https://​github.com/​iotbzh/​AlexaDocker +
-     * Need to get running on guppy. Thierry was working on master.  +
-   * RHSA RFQ+
  
  
-==== June 11, 2019 ==== 
-Attendees: Walt, Jan-Simon, Ronan, Michael, Fulup, Sebastien, Stephane, Hosokawa, Marc, Kurokawa, Nakadachi, Kusakabe, Yamaguchi, Scott, Li 
  
-Reviewed and updated the AGL LTS requirements and assumptions. https://​confluence.automotivelinux.org/​x/​X4CP+==== April 9, 2020 ==== 
 +AttendeesWalt, Jan-Simon, Michael, Stephane, Kusakabe, Kurokawa, Yamaguchi, Haraki, Hosokawa, Tanikawa, Nomoto, Abe, Ohiwa, Scott, ​
  
-Took a quick look at the AGL Production Readiness Confluence page. Kusakabe-san said that he will be ready to show the Denso Ten review of AGL APIs at the next SAT meeting+   * 2020 Roadmap Review  
 +     * Create Jira tickets for components ​that may be moved to AGL core and post a request for comments on the mail list.  To be reviewed at SAT F2F at the AMM.  
 +     * Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]].
  
-Walt will send out the RHSA RFQ for review+   * Yocto version discussion 
 +      * Renesas plans to use 4.14 kernel for dunfell this year and would upgrade to 5.4 for the LL release.  
 +      * SAT agreed on the following plan for YP versioning + Renesas BSP kernel version. Other platforms ​will support 5.4 kernel at initial release.  
 +        * JJ - YP 3.1 + 4.14 kernel (best case end of June to IoT.bzh with release in July) 
 +        * KK - YP 3.1 + 4.14 kernel 
 +        * LL - YP 3.1 + 5.4 kernel.  
 +        * MM - YP 3.1 + 5.4 Kernel  
 +      * Yamaguchi-san asked about support for Ubuntu 20.4.  Probably has not been tested. Ubuntu release is 1 day before ​the YP release so it is unlikely to be explicitly support on day 1.  Jan-Simon will check with YP on their plans for 20.4 support
  
 +   * Reviewed the Fast Boot RFQ developed by Kusakabe-san for the IC EG
 +     * Kusakabe-san will post the document for further review. ​
 +     * Plenty of comments were provided. Another round of updates will take place and a new version will be available in two weeks (Kusakabe-san to confirm the timing) for the next SAT call. 
  
 +   * SPEC-2927 - Window Manager for WAM
  
- +   * RHSA RFQ updated ​the RFQ document ​with commentsThe revised version is {{:eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}. 
-==== June 6, 2019 ==== +     ​* ​8/29 Panasonic ​is reviewing ​ 
-Attendees: Walt, Jan-Simon, Scott, Tanikawa, George, Kusakabe, Marc, David Fries (SanCloud), Michael, Daniel, Guy, Sebastien, Yamaguchi +     ​9/12 Panasonic still in reviewSekine-san will check with Panasonic about EG review during ​the AMM in Monaco.  
- +     ​* ​9/26 Still in review at PanasonicSekine-san expects a reply soon.  
-   * Weston 6.0 discussion +     ​* ​10/10 Sekine-san thinks Panasonic will release the RFQ in time to be reviewed ​in Monte Carlo, Walt will be in Yokohama in November, We should ​plan a F2F meeting at that time with Panasonic ​and RHSA EG.  
-     * i.Mx6 unstable startup, but probably not a Weston issue. Scott working on updating ​the changes.  +     ​* ​11/SC to meet next week and make recommendation ​to ABWe will make sure that Panasonic ​and Mazda RHSA team members are invited ​to that portion of the SC meeting next week.  
-     * No major problems identified on other boards. Daniel looking at problem ​with QEMU not starting +     ​* ​11/21 SC meeting ​last week in YokohamaWaiting on block diagram from Panasonic which was promised ​for two weeks (next week)There is a meeting ​next week in Tokyo to discuss furtherThere is a on-going discussion between Panasonic ​and Renesas about BSP.  ​Also will get a quote for creating ​the BSP from Konsulko  
- +     ​* ​12/Block diagram [[ https://wiki.automotivelinux.org/​_media/eg-rhsa/r-car_h3_reference_hardware_blockdiagram_20191126.pdf uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday.  
-   * Update from Daniel on Window Manager architecture +     ​* ​12/19 No update. ​Was reviewed by SC last weekWill forward and RFI to Konsulko ​for creating and maintaining ​the BSP.  
-     * Scott (NZ) working on getting the existing demo home screen working.  +     ​* ​Panasonic ​to get agreement with Qualcomm ​to release firmware ​for the BT/Wifi chipNo update ​on this topic.  
- +     ​* ​1/16 Panasonic ​and Qualcomm ​are talking at the executive level about licensing ​the WiFi and Bluetooth chip firmware using a click-thru license most likely.  
-   * Update from George on PipeWire +     ​* ​3/26 BSP RFI responses ​to be reviewedAB tentatively approved purchasing ​the boards pending ​the Qualcomm ​and BSP discussions
-     * See Jan-Simon'​s ​{{:audio_system_recipes_in_hh-2.pdf|presentation on build and configuration}}.  +
-     ​* ​Decision by SAT as documented in the presentation:​ Pipewire only solution for HH.  +
-         * PipeWire ​is a new switch in aglsetup. Remove the 4a switch. Leave Sound Manager switch intact. ​ +
-         ​+  Easier code implementation. Can remove #ifdefs in apps and services that require knowledge of which audio implementation is in use +
-         * +  Audio will work but policy plugin available in Icefish  +
-         * +  Apps are already ported and need less code (if old code removed) +
-         * - unicens/agl-service-unicens needs to be ported (target 8.0.1) +
-         ​* ​Knife switch. HH will not support 4a. Sound Manager sources will be included, but will not be built or tested by AGL.  +
-         * - Bluetooth audio will not be functional in 8.0.0. Target patch release 8.0.1 for Bluetooth audio +
- +
- +
-   * Doc site update +
-     * Common method for documenting the APIs is needed so that developers know what is expected of them for documentation and we have a method for displaying the APIs on the doc website. Walt will send an email to address this.  +
-     * Need some help with CSS and layout. There are known issues that need to be addressed.  +
-     * Need to have layout very wide to see the branch switching, etc +
- +
-   * RHSA Update +
-     ​* ​Nakadachi-san {{::​rhsa_update_20190411.pdf|provided this update}}. Requirements spec 0.2 is available on the RHSA page. Revised plan is for SAT to review ​the spec at the F2F meetingPlan is for 10 units to be available by the end of September.  +
-     ​* ​5/23 Initial ​RFQ based on the spec from the EHSA EG to be reviewed ​at next SAT call.  +
- +
-   * Navi EG +
-     * new navigation app (Mapbox based) - https://​gerrit.automotivelinux.org/​gerrit/#/​c/​21032/​ +
-     * Remove old navigation app from recipe +
-     * POI should ​work out of the box with the new Navi app +
-     * 5/23 - New Navi EG held first meeting in Japanese and posted some meeting minutes and roadmap to their [[eg-navi|wiki page.]]  +
- +
- +
-   * Yocto - thud 2.6.2 was just released with our fixes. Need to bump for master.  +
-     * warrior 2.7 is now released. Can revive agl-next branch to start tracking warrior.  +
-     * 5/23 - Need Jira ticket for bump to 2.6.2. Assign to Tom.  +
-     * 6/6 - Done. Master now on 2.6.2.  +
- +
-     * Site for Sep F2F Meeting (week 37 (Sep 9) interferes ​with Linux Plumbers) +
-     * Suggestion week 38 in Europe due to other conferences the weeks before ​and after. Check with Amazon on their availability. Lorient is a possible site. Need to check with Amazon on their availability location-wise.  +
-     ​* ​Add LTS and production readiness to next SAT agenda +
-     * ALS demo being shipped to Japan on Tuesday. ​ Need to check with Amazon on the token and API site still being available.  +
-     * Ask Scott to post to wiki page or doc site instructions for building CES 2019 demo units.  +
-     * Jan-Simon asking for comments on gerrit 21389, restructure of the folder layout in gerrit.  +
-       * 6/Now targeted for RC2 +
- +
-   * New Business +
-     * Schedule a follow-up SAT call for Tuesday morning in CIAT slot.  +
- +
-==== May 23, 2019 ==== +
-Attendees: Walt, Jan-Simon, Sebastien, Kurokawa, Daniel, Eric , Yamaguchi, Hosokawa, Guy +
- +
- +
-   * Weston 6.0 discussion +
-     * All targets except i.MX6 now build.  +
-     * No major problems identified yet. M3, Vayu, and RPI still need to be verified. +
- +
-   * Update from Daniel on Window Manager architecture +
-     * See yesterday'​s App FW EG Meeting minutes +
- +
-   * Update from George on PipeWire +
-     * George having some problems joining +
- +
-   * Doc site update +
-     * New doc site is now live with the multi-branch switcher. ​  +
-     * XDS documentation being updated by Scott R.. Link checker was run and found about 25 broken links within the page that need to be fixedScott working on that as well.  +
-     * Common method for documenting the APIs is needed so that developers know what is expected of them for documentation ​and we have a method for displaying the APIs on the doc website. Walt will send an email to address this.  +
-     * Need some help with CSS and layout. There are known issues ​that need to be addressed.  +
-     * Need to have layout very wide to see the branch switching, etc.  +
- +
-   * RHSA Update +
-     * Nakadachi-san {{::​rhsa_update_20190411.pdf|provided this update}}. Requirements spec 0.2 is available on the RHSA page. Revised plan is for SAT to review the spec at the F2F meeting. Plan is for 10 units to be available by the end of September.  +
-     * 5/23 - Initial RFQ based on the spec from the EHSA EG to be reviewed at next SAT call +
- +
-   * Navi EG +
-     ​* ​new navigation app (Mapbox based) - https://​gerrit.automotivelinux.org/​gerrit/#/​c/​21032/​ +
-     * Remove old navigation app from recipe +
-     * POI should work out of the box with the new Navi app +
-     * 5/23 New Navi EG held first meeting in Japanese and posted some meeting minutes and a roadmap to their [[eg-navi|wiki page.]]  +
- +
- +
-   * Yocto - thud 2.6.2 was just released with our fixes. Need to bump for master +
-     * warrior 2.7 is now released. Can revive agl-next branch to start tracking warrior.  +
-     * 5/23 - Need Jira ticket for bump to 2.6.2. Assign to Tom.  +
- +
-   * New Business +
- +
-     * Site for Sep F2F Meeting (week 37 (Sep 9) interferes with Linux Plumbers) +
-     * Suggestion ​week 38 in Europe due to other conferences the weeks before and afterCheck with Amazon on their availability. Lorient ​is a possible site. Need to check with Amazon ​on their availability location-wise.  +
-     * Add LTS and production readiness to next SAT agenda +
-     * ALS demo being shipped to Japan on Tuesday.  ​Need to check with Amazon on the token and API site still being available.  +
-     ​* ​Ask Scott to post to wiki page or doc site instructions for building CES 2019 demo units.  +
-     * Jan-Simon asking for comments on gerrit 21389, restructure of the folder layout in gerrit.  +
- +
- +
-==== May 9, 2019 ==== +
-Attendees: ​//Upcoming Meeting// +
-F2F Meeting in Spain  +
- +
- +
-==== April 25, 2019 ==== +
-Attendees: Walt, Jan-Simon, Tom, Alexey, Scott, Eugeniy, Lorenzo, Stephane, George, Kusakabe, Nakadachi, Yamaguchi, Sebastien, Michael F, Michael T, Eric, Hosokawa +
- +
- +
-   * Layers reorg (move things from m-a-devel to m-agl or m-a-extra) + AGL profiles layers organization (cluster/​telematics/​ivi/​adas ...) - https://gerrit.automotivelinux.org/​gerrit/21118 +
- +
-   * AGL boards status ​https://​gerrit.automotivelinux.org/​gerrit/​21031 +
- +
-   * ARC HSDK board support ​https://​gerrit.automotivelinux.org/​gerrit/#/​c/​21079 +
- +
-   * Review [[agl-distro:​may2019-f2f#​agenda|F2F Meeting Agenda]] for Spain  +
- +
-   * Update from Daniel on Window Manager architecture +
-     * Daniel not available. +
- +
-   * Update from George on PipeWire +
-     * Working on Pipewire session manager for policy management. Julian also working on the project to get Bluetooth running (A2DP now working. HFP in progress). George is working on session manager for the F2F meeting in May. Will also work with Wim on outstanding PipeWire design issues for automotive.  +
- +
-   * Doc site update +
-     * New doc site is now live with the multi-branch switcher. ​  +
-     * Need some help with CSS and layout. There are known issues that need to be addressed.  +
-     * Mobile support not working (404 errors)- Fixed  +
-     * Need to have layout very wide to see the branch switching, etc +
- +
-   * RHSA Update +
-     ​* ​Nakadachi-san {{::​rhsa_update_20190411.pdf|provided this update}}Requirements spec 0.2 is available on the RHSA page. Revised plan is for SAT to review the spec at the F2F meeting. Plan is for 10 units to be available by the end of September +
- +
-   * Navi EG +
-     ​* ​new navigation app (Mapbox based) - https://​gerrit.automotivelinux.org/​gerrit/#/​c/​21032/​ +
-     * Remove old navigation app from recipe +
-     * POI should work out of the box with the new Navi app +
- +
- +
-   * Yocto - thud 2.6.2 was just released with our fixes. Need to bump for master.  +
-     * warrior 2.7 is now at M3  +
- +
-   * New Business +
-     * None +
- +
- +
-==== April 11, 2019 ==== +
-Attendees: Walt, Jan-Simon, Nakadachi, Sebastien, Lorenzo, Stephane, Truong, Kusakabe, Kurokawa, Kusakabe, Guy, George, Julian, Fulup +
- +
- +
-   * Update from Daniel on Window Manager architecture +
-     * Daniel not available. +
- +
-   * Update from George on PipeWire +
-     * Working on Pipewire session manager for policy management. Julian also working on the project ​to get Bluetooth running. Plan is to have a working session manager and Bluetooth stack for the F2F meeting in MayWill also work with Wim on outstanding PipeWire design issues for automotive +
- +
-   * Doc site update +
-     ​* ​New doc site is now live with the multi-branch switcher. ​  +
-     * Need some help with CSS and layout. There are known issues that need to be addressed.  +
-     * Mobile support not working (404 errors). Need to have layout very wide to see the branch switching, etc.  +
- +
-   * RHSA Update +
-     * Nakadachi-san {{::​rhsa_update_20190411.pdf|provided this update}}. Requirements spec 0.2 is available on the RHSA page. Revised plan is for SAT to review the spec, then the hardware design will be kicked off with Panasonic. Plan is for 10 units to be available by the end of September +
- +
-   * Navi EG +
-     ​* ​No one on the call +
- +
-   * Yocto master now updated ​to thud. CI loop is currently broken, but will be fixed shortly +
- +
- +
-==== March 28, 2019 ==== +
-Attendees: Walt, Jan-Simon, Michael, Yamaguchi, Kurokawa, Nakadachi, Stephane, Sebastien, Daniel, Eric, Momiyama, George +
- +
-   * Update from Daniel on Window Manager architecture +
-     * Daniel has a {{:​2019-03-28_-_agl_sat_-_window_manager_replacement.pdf|new presentation}} which he will send to the mail list and we will review fully during ​the graphics EG call on Monday. +
- +
-   * Update from George on PipeWire +
-     * Wim will attend the May F2F meeting to help work out upstream issues with PipeWire +
- +
-   * Doc site update +
- +
-   * RHSA Update +
-     * Spec update in progress within the EG and will not be completed by the end of the month. Will take another 2 weeks and Nakadachi-san will update us again during the next call.  +
- +
-   * Navi EG +
-     * New EG leader will be Wakazono-san from MicWare. ​ He joined the SAT call, but was disconnected+
    
 +   * Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September. ​
 +     * 3/26 - Kusakabe-san prepared a draft document that will be reviewed during the Connectivity EG meeting next week. 
  
-==== March 14, 2019 ==== +   * LTS  ​ 
-AttendeesWalt, Jan-Simon, Daniel, George, Guy, Daniel, Eric, Tanikawa, Travis Taylor ​(Panasonic), Fulup, Stephane, Yamiguchi, Kusakabe, Lorenzo+     * 9/26 (Berlin F2F) 
 + * AIidentify base services. What is in core-image-minimal that is available in all profiles.  
 +  * lifecycle 
 +    * apps vs platform ​(which applications  
 +    *  
 +  * API definition & documentation & Schema 
 +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/​browse/​SPEC-1903 
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md 
 +    * Follow-up on SAT 
 +  * API versions 
 +    * -> APPFW / Jose
  
-Topics:+  * '​core'​ LTS vs. IVI or Cluster LTS 
 +    * depends on changes required e.g. by IC  
 +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.   
 +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects.  
 +      * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing.  
 +      * Will add to SC agenda for next week.  
 +    * 11/21 - SC did not get to this topic, Will be addressed at December meeting.  
 +    * 12/5 - Following up next week.  
 +    * 1/16 - Added LTS to the SC agenda for February.  
 +    * 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting, ​
  
-   ​* ​Review {{:​agl_roadmap_tokyo_2019_amm.pdf|Roadmap slides from AMM}}  +   ​* ​Toyota Code Drop 
- +     ​* ​10/10  
-   * Review of [[agl-distro:​mar2019-f2f|meeting minutes]] from last week's F2F meeting in Tokyo +       ​* ​No update. ​Will need some decisions about how we want APIs to be formatted based on LTS discussion.  
-     ​* ​Audio +       ​Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback ​to the AGL community
-     * Window Manager and graphics ​ +     ​* ​11/7 Toyota documents are quite large. Were posted ​on ConfluenceOhiwa-san is working ​on splitting them up and providing header files Ohiwa-san will be in Yokohama ​next week to discuss ​the next steps with the SC.  
-       ​* ​{{:​2019-03-14_-_agl_sat_-_compositor_plans.pdf|Presentation from Daniel}} on progress with Window Manager and Compositor.  +     ​* ​11/21 -  
-         * Lots of good feedback. Tanikawa noted that the presentation does not include separation of home screen and window manager services as agreed to in Tokyo. Daniel confirmed that this is an oversight and will update ​accordingly +     ​* ​Notes from SC meeting ​ 
- +     ​* ​Discussed ​the need to take each of the API documents and deep dive the contents with the appropriate developers within ​the AGL communityWill need Toyota to do some analysis ​of the architecturaldesign gaps between AGL and their proposed code changes and work with the community to fill those gapsFor example, the “Peripheral API” document has a lot of details ​about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall ​architecture. ​There may be parts of it that are already covered by AGL. Suggestion is for Toyota ​to pick an API to focus on and develop the higher level context ​with the AGL community to figure out how to fit it into the existing structure. ​ 
-     * Video - skipped due to time +     ​* ​Ohiwa-san is working on providing the context ​for the API documentsFirst task will be System Manager API in the System Service Document (see [[https://confluence.automotivelinux.org/​display/TC/Documents ​Confluence]] for more on the documents.  
-     * System Spec - skipped due to time +     ​* ​12/4 Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.   
-     * Instrument Cluster EG - skipped due to time +       ​Discussion on whether the existing AGL [[ https://git.automotivelinux.org/apps/agl-service-data-persistence/tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended
-     * RHSA - skipped due to time +       ​Discussion of whether the backed up data is in Linux file system, a proprietary file system, or managed memory ​of some sort (battery backed RAM or flash).  
- +       ​Other requirements need to be documented that were discussedOhiwa-san will update and we will review further at the next SAT meeting  
-   * Latest ​on updates to documentation site +     ​* ​12/19 Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the second requirement for review camera after start up. Ohiwa-san will upload ​the document ​to the Toyota ​code drop Confluence page. https://confluence.automotivelinux.org/​display/TC/​Documents 
-     * AGL APIs specification format (for documentation,​ code generation, QA ...) +     ​* ​1/16 New version of the specification was uploaded to Confluence last weekCode will be uploaded to gerrit in the next week or twoWill be licensed under Apache 2.0.  
-     ​Proposal/​example for GPS API: +     * 3/12 Ohiwa-san showed a presentation ​on the latest status ​from Toyota.{{:sat_meetings:document_for_sat_20200312.pdf|latest status}} ​ 
- +     ​* ​Nomoto-san showed analysis of Bluetooth use casesHe will forward ​to the mail list or post in the meeting ​minutes, Detailed discussion will pick up in the Connectivity EG.  
-https://​git.automotivelinux.org/​apps/​agl-service-gps/​tree/​api/​gps-service-geolocation-with-states.yml?​h=sandbox/​benierc/​newapis +     ​* 3/26 - Ohiwa-san can start to upload ​the code now that it has been approved internally. Code will be uploaded ​on Monday unless he cannot go to the office due to Coronavirus restrictions.  
- +     ​4/9 - SPEC-3322 written with details ​on the code that was uploaded ​to gerrit including build instructions ​and other documentation in [[https://​confluence.automotivelinux.org/​pages/​viewpage.action?​spaceKey=TC&​title=Documents | Confluence.]] 
-   * docs-agl is now deprecated (archived in fact == read-only) +
- +
-   * activate "docs-next": preview available at https://​docs-next. iot.bzh/ +
-  expected steps: +
-  1) extensive review +
-  2) fixes +
-  3) publish ​and replace existing site on docs.automotivelinux.org +
- +
- +
-==== February 28, 2019 ==== +
-Meeting canceled due to Embedded World +
- +
-==== February 142019 ==== +
-Attendees: Walt, Jan-Simon, Tanikawa, Kurokawa, Momiyama, Jose, Michael, Yamaguchi +
- +
-   * Update from Navi EG +
-     ​* ​Momiyama-san can no longer work on the Navi EG tasks due to other tasks within AisinAW +
-     * Seek new leadership for the Navi EG +
-     * Momiyama-san asked Micware to be new leader for EG and they are considering it +
-   * Roadmap updates +
-   * App FW Roadmap (continued from App FW call) +
- +
-   * **Agenda for F2F SAT meeting in Japan on Thursday March 7** +
-     * Window manager ​and home screen proposal +
-     * Future of audio in AGL - 4a and pipewire discussion +
-     * Speech EG updates +
-     * Graphics and UI updates +
-     * App FW EG updates +
-     * Spec 2.0  +
-     * FOSDEM debriefing and having an embedded room in 2020 +
-     * Functional safety project update +
-     * Autonomous driving update  +
-     * Steering Committee Meeting in parallel with a wrap-up at the end of the day +
- +
-   * GG ready to go - release notes will be finalized today.  +
- +
-   * Poll of members of who is using which version of AGL to gauge how long we need to support EE, FF, GG, etc.  +
-   * Latest documentation site updates can be found at https://​docs-next.iot.bzh/​docs/​getting_started/​en/​dev/​  +
-     * We will move this over to the public site in the next few weeks as we finish ​the GG release +
- +
- +
-==== January 31, 2019 ==== +
-Attendees: Walt, Michael, Kurokawa, Lorenzo, Daniel, Jim, Yamaguchi, Stephane, Sebastien +
- +
-   * Roadmap updates +
- +
-   * **Agenda for F2F SAT meeting in Japan on Thursday March 7** +
-     ​* ​Window manager and home screen proposal +
-     * Future of audio in AGL 4a and pipewire discussion +
-     ​* ​Speech EG updates +
-     ​* ​Graphics and UI updates +
-     * App FW EG updates +
-     * Spec 2.0  +
-     * FOSDEM debriefing and having an embedded room in 2020 +
-     * Functional safety project update +
-     * Autonomous driving update  +
-     * Steering Committee Meeting in parallel with a wrap-up at the end of the day +
- +
-   * GG final merges +
-   * Poll of members of who is using which version of AGL to gauge how long we need to support EE, FF, GG, etc.  +
-   * Latest documentation site updates can be found at https://​docs-next.iot.bzh/​docs/​getting_started/​en/​dev/​  +
-     * We will move this over to the public site in the next few weeks as we finish ​the GG release +
- +
- +
-==== January 17, 2019 ==== +
-Attendees: Jan-Simon, Kurokawa-san,​ Michael, Kusakabe-san,​ Dominig, Guy +
- +
-  * CES feedback +
-    * {{img_1557.jpg?​200}} +
-    * {{img_8440.jpg?​200}} +
-  * Prepare YP '​Thud'​ uprev, -next branch (qemuarm, qemux86-64, qemuaarch64) +
-  * GG rc4, FF 6.0.4 (code in gerrit today 1800 UTC) +
-  * New topics ? +
-    * None +
- +
-==== January 3, 2019 ==== +
-Attendees: //Upcoming Meeting// +
-Cancelled +
- +
-==== December 20, 2018 ==== +
-Attendees: Walt, Michael, Kurokawa, Kusakabe, Lorenzo, Guy, Jan-Simon, Mitsunari +
- +
-   * SPEC-1689 - Static library usage as a replacement for afb-helper submodules.  +
-   * Latest on window manager and home screen restructuring. +
-     * [[ https://​confluence.automotivelinux.org/​x/​PQAq ​ | Confluence page]] started to document future architecture,​ use cases, etc.   +
-   * FOSDEM - discussed what the plan is for AGL and embedded in general at FOSDEM +
- +
-==== December 11, 2018 ==== +
-Attendees: Walt,  Kurokawa, Julie, Tanikawa, Scott, Fulup, Mitsunari +
- +
-   * Tanikawa presented a slide that shows the current status ​of the Qt/QML, XDG, Window Manager, Home Screen architecture +
-   * Discussed current state of Julie'​s ​work on SPEC-1920 +
-   * Reviewed past presentations from the Window Manager/ Home Screen BoF from Dresden and Lorient +
-   * We agreed that we while we have a lot of information ​about the flaws in the current implementation and ideas about what and how things need to be fixed we do not have a final architecture ​diagram or plan for what we want AGL to look like +
-     * Mix of synchronous and asynchronous APIs in the implementation ​that lead to deadlocks +
-     * No consistent Cplus plus API for interacting ​with Window Manager +
-     ​* ​Surface management ​for Web Apps and native apps that require more than 1 surface +
-     * and more....  +
-   * Agreed that the team in San Francisco ​will draft an architecture and present it in two days for review.  +
- +
- +
-==== December 6, 2018 ==== +
-Attendees: Walt, Jan-Simon, Thierry, Michael, Sebastien, Stephane, Kurokawa, Julie, Jose, Abhijeet, Kusakabe, George, Guy, Dominig, Jacobo +
- +
-   * WAM integration into gerrit. See [[https://jira.automotivelinux.org/​issues/?​jql=status%20%3D%20Resolved%20AND%20labels%20%3D%20WebAppMgr ​resolved Jira issues]]  +
-     * Reviewed SPEC-1885 - Moving WAM into AGL +
-       * In-flight in gerrit ​for FF/ CES Demo. Jacobo agreed to cherry pick to master as soon  as Flounder is done so we can include it in GG release even if all testing is not completed ​on master+
-     ​* ​Review SPEC-1920 Refactor libhomescreen and libwindowmanager +
-       * Will hold special meeting next week once Tanikawa is availalbe ​.  ​Tuesday @ 17:00 PST. Wed @ 10 am JST +
- +
-   George presented pipewire as a future multimedia framework. Presentation can be downloaded {{:​pipewire_agl_20181206.pdf|here}}.  +
-     * Dominig brought up non-technical issues that were [[ https://arunraghavan.net/2018/10/update-from-the-pipewire-hackfest| discussed in this article.]]  +
-     * Thierry brought up some technical concerns with using pipewire.  +
- +
-   SMACK usage and not running as root +
-     * Jose agreed with George'​s email that there is a regression whereby removal ​of capabilities in SMACK does not work at this timeJose to write a ticket in JIRA and fix for GG +
-     ​Not running as root is in Jose's sandbox and is targeted more HH release +
- +
-   * SPEC-495 - app workflow changesSee https://​gerrit.automotivelinux.org/​gerrit/#/​q/​status:​open+SPEC-495 +
- +
-   * API documentation proposals and update on documentation effort +
-     ​* ​Jose has an example API specification that was used here https://​git.automotivelinux.org/​src/​app-framework-binder/​tree/​src/​devtools/​idl-monitor.json?​h=sandbox/​jobol/​wip +
-     * Step 1 - Have Jose complete his specification ​for describing AGL APIs.  +
-     * Step 2 - Get feedback from community to agree on the this description methodology by providing a presentation ​to each EG and SAT to gather feedback and gain consensus on the specification +
-     * Step 3 - Write automatic ​code generator to provide content for web site and marshalling/​ un-marshalling of JSON +
-     * Step 4 - Develop API tests based on the new API description +
- +
-  * Next meeting +
- +
-    * Another update from Igalia on libwindowmanger and libhomescreen +
-    * IoT.bzh application launcher updates +
- +
- +
-==== November 22, 2018 ==== +
-Attendees: Walt, Jan-Simon, Stephane, Tanikawa, Franz, Sebastien, George, Jacobo, Lorenzo, Michael, Dominig, Fulup, Abhijeet,  +
- +
-   * WAM integration into gerrit. See [[https://jira.automotivelinux.org/​issues/?​jql=status%20%3D%20Resolved%20AND%20labels%20%3D%20WebAppMgr | resolved Jira issues]] ​ +
-     ​* ​Reviewed SPEC-1885 - Moving WAM into AGL +
-     * Review SPEC-1920 - Refactor libhomescreen and libwindowmanager +
- +
-   * SPEC-495 - app workflow changes. See https://​gerrit.automotivelinux.org/​gerrit/#/​q/​status:​open+SPEC-495 +
- +
-   * API documentation proposals and update on documentation effort +
-     * Jose has an example API specification ​that was used here https://git.automotivelinux.org/​src/​app-framework-binder/​tree/​src/​devtools/​idl-monitor.json?​h=sandbox/​jobol/​wip +
-     * Step 1 - Have Jose complete his specification for describing AGL APIs.  +
-     ​* ​Step 2 - Get feedback from community to agree on the this description methodology by providing a presentation to each EG and SAT to gather feedback and gain consensus on the specification +
-     * Step - Write automatic code generator to provide content for web site and marshallingun-marshalling of JSON +
-     * Step 4 Develop API tests based on the new API description +
- +
-  * Next meeting +
-    * George to present pipewire as a future multimedia framework +
-    * Another update ​from Igalia on libwindowmanger and libhomescreen +
-    * IoT.bzh application launcher updates +
- +
-==== November 8, 2018 ==== +
-Meeting cancelled due to Yokohama F2F meeting +
- +
-==== October 28, 2018 ==== +
-Attendees//Upcoming Meeting// +
- +
-==== October 11, 2018 ==== +
-AttendeesWalt, Jan-Simon, Franz, Dominig, Kurokawa, Kusakabe, Momiyama, Yamaguchi +
- +
-   * Email asking for feedback on Speech, Virtualization,​ and V2C topics +
-     * Major blocker to the system is seen as graphics area.  +
-     ​* ​Need an effort similar to 4a to tackle this problem long term. +
-     * Will bring up to AB next week. BoF session planned with Tanikawa to try to addressAlso will add to Friday agenda.  +
-     *  +
- +
-   * Agenda for F2F meeting ​next week +
-   +
-    * Window Manager and Homescreen Plan for 2018 +
-      * Need additional SAT oversight and open up of the work.  +
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposal. Tanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend.  +
-      * 4/26 - Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo.  Need to get something in writing from Toyota on their schedule of features for this year.  +
-      * 5/24 - Surface ID management proposal from Tanikawa-san is being updated for Monday'​s Graphics and UI EG call. Additional discussions on the plan for Window Manager and Homescreen will be discussed in Lorient in two weeks. Need to get ADIT's schedule for updating the ID agent to ensure ​that it will be available and working in FF.  +
-      * 6/7 - Tanikawa working ​on high level design for window manager and homescreen ​to be reviewed at the June 19 F2F SAT meeting in Tokyo. Will also need a plan for staffing and timing ​to be presented to the AB in Tokyo. ​ Plan from Toyota in SPEC-1467. ​ It looks like splitting App Launcher from Homescreen will happen by late June from Toyota. Rest of their work is planned for September or later, but they will not be working with us as a community.  +
-      8/2 - Push to next SAT call +
-      * 9/13 Toyota plan for GG features.  +
-        * Toyota planning and software process is still very closed/ opaque. SAT relying ​on second hand information to determine what is going on.  +
-        * Change Home screen service to use application role instead of name for surface management. Unclear whether ​the Toyota design is sufficient for our needs.  +
-        * Window Manager - plan to support multiple surfaces ​and grouping of surfaces for a single applicationRequirements are being driven by navigation and map use cases   +
-        * We have not had a chance to review these proposals with ToyotaNo dates for getting this software either+
    
- 
-   * Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  
    
-   ​* ​Web app framework - Updates from LG/Igalia? +   ​* ​ELISA updates 
-     ​* ​5/24 - Nothing ​to report. +     ​* ​ELISA and IC EG are recruiting AGL members ​to participateThe next F2F meeting for ELISA is in Brussel ​the Thursday and Friday before FOSDEMRegistration information can be found [[https://​elisa.tech/​announcement/​2019/10/17/elisa-brussels-workshop-january30-31-2020/​ | here]] ​ 
-     * 6/7 - Stephane will create a summary report of the findings from this weeks meetings including a list of action items to pursue. +     ​* ​ELISA groups.io page can be found [[https://lists.elisa.tech/​g/​devel | here ]] 
-     * 8/Stephane reports: +     ​* ​New ELISA development process subgroup has formed. See their [[ https://lists.elisa.tech/​g/​devel/​topic/please_join/​61718502?​p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 | groups.io page]] for more information and to sign up.  
-       * Jose pushed example html5 apps and a few fixes +     ​* ​3/26 DrYamaguchi provided an update ​on the ELISA AGL cooperation proposal
-       * meta-agl-lge: Status is that it works with EE, the FF branch is still WIP with master. Sebastien will take over when back. +
-     ​* ​9/13 - Santa Clara F2F +
-       * Sebastien has some services working on FFWill add WebAppManager to main build as a patch release to Flounder and call it a "​preview"​ which main work continues on masterGG  +
- +
-   * Possibility that Suzuki could contribute new design for CES 2019.  Tanikawa says they had proposal that was shown at local Japan meeting this week.  +
-     ​* ​5/24 - Nothing to reportNext Japanese local meeting is next weekWill get an update for next SAT meeting.  +
-     * 6/7 - Nothing to reportNeed to figure out if this is real by ALS or pursue getting an updated design elsewhere.  +
-     ​* ​8/Nothing new. +
-     * 9/13 - Tanikawa does not have any more details from Suzuki ​on their schedule or plans.  +
- +
- +
-  * SPEC-1601 - discussion on Pulse Audio: +
-    * 4a pulse plugin makes pulse a client to 4a  +
-    * for FF:  +
-      * 4a plugin for PulseAudio now available for FF.  +
-      * Need to do some testing with audio roles for 4a and PA plugin. Navigation will be tested by IoT.bzh team+
    
-    * for GG:  
-      * AGL core image should not include PulseAudio, only by upper layer request 
-      * Binary feed should include PulseAudio so it is there if someone wants to use it and can be installed later on.  
-      * pulse to have minimal config by default, and fragments add configuration bits in separate package 
  
-   Instrument Cluster profile ​and demo +FOSSology/ License Review 
-     ​Konsulko taking lead in creating IC demo to replace existing CES IC using latest AGL App FW.  +   So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work.  Will be brought up to AB at their next meeting.  ​ 
-     ​Use current ethernet video feed for center display and move to Waltham receiver module later+   ​Open Chain reported that we have 320 different licenses How do we plan to collaborate with OpenChain? 
 +   ​Fujitsu has volunteered ​to do some work sorting out the licensing which will get started in the new year 
 +   * 3/26 - Multiple issues blocking getting FOSSology server going, ​
  
-New: +New Business:
-   * SPEC-633/​SPEC-639 - Make it easy to mount logs using a network file system.  ​+
  
-   * SPEC-1754 - Modify Application code for divide homescreen label with windowmanager role  
-     * Proposed by Mitsunari. Will need to review with Graphics and UI EG.  Mistsunari will push sample code to review in gerrit prior to the review by the EG.  
-   * SPEC-1747 - Add ability to chose image upgrade mechanism at build time (SOTA, dnf , ...) 
-     * Updated the description in the ticket based on discussion and sent an email to Anton to make sure he sees it.  
  
-   * Walt to send email to LG about moving WAM repositories to gerrit. ​ 
  
 +==== March 26, 2020 ====
 +Attendees: Walt, Jan-Simon, Scott, Dr. Yamaguchi, Ohiwa, Nomoto, Abe, Kusakabe, Haraki, Hosokawa, Stephane, Parth, Nishiguchi, Tanikawa
  
-==== September 27, 2018 ==== +   * 2020 Roadmap Review ​ 
-AttendeesWalt, Jan-Simon, Kusakabe, Stephane, Sebastien, Fulup, Kurokawa+     * Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list.  To be reviewed at SAT F2F at the AMM.  
 +     * Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]].
  
-   * Discussed Issues with Final FF release 
-     * Last audio issue in gerrit (16771) being tested. Stephane sees a problem on H3 board with Bluetooth device not ready when 4a asks for it. Seems like a race condition that only appears on H3. Stephane to a temp fix (delay in requesting BT) that write a ticket to analyze the root cause. ​ 
-     * Need someone to test Minnowboard since Stoyan having an issue with build. Stephane to test after the call.  
-     * Jan-Simon to merge the patch (16771) so Stoyan can download that build for Minnowboard. ​ 
-  
  
-   * Reviewed and edited ​[[agl-distro:release-notes#​funky_flounder|Funky Flounder release notes]] +[[ https://​jira.automotivelinux.org/​browse/​SPEC-2538 SPEC-2538]] - Remove support for multiple versions of widgets to be installed simultaneously.  
-     * Decision taken that 4a will be the default build option for 6.0.0 (and 5.1.0 the next eel release)+   ​2/13 Sandbox tested out and will be included in JJ releaseBuild option will be available for keeping multiple versions, ​ 
-     ​Update 8/was merged as https://​gerrit.automotivelinux.org/​gerrit/#/​c/​15499/​ +   ​3/26 Merged
-     ​9/13 Slights updates. Matt kicking off Vayu testing. Need to list known issues+
  
-    ​Window Manager and Homescreen Plan for 2018 +   Icefish final release 
-      * Need additional SAT oversight and open up of the work.  +     ​Done
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposal. Tanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend.  +
-      * 4/26 - Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo.  Need to get something in writing from Toyota on their schedule of features for this year.  +
-      * 5/24 - Surface ID management proposal from Tanikawa-san is being updated for Monday'​s Graphics and UI EG call. Additional discussions on the plan for Window Manager and Homescreen will be discussed in Lorient in two weeks. Need to get ADIT's schedule for updating the ID agent to ensure that it will be available and working in FF.  +
-      * 6/7 - Tanikawa working on high level design for window manager and homescreen to be reviewed at the June 19 F2F SAT meeting in Tokyo. Will also need a plan for staffing and timing to be presented to the AB in Tokyo. ​ Plan from Toyota in SPEC-1467. ​ It looks like splitting App Launcher from Homescreen will happen by late June from Toyota. Rest of their work is planned for September or later, but they will not be working with us as a community.  +
-      * 8/2 - Push to next SAT call +
-      * 9/13 - Toyota plan for GG features.  +
-        * Toyota planning and software process is still very closed/ opaque. SAT relying on second hand information to determine what is going on.  +
-        * Change Home screen service to use application role instead of name for surface management. Unclear whether the Toyota design is sufficient for our needs.  +
-        * Window Manager - plan to support multiple surfaces and grouping of surfaces for a single application. Requirements are being driven by navigation and map use cases. ​   +
-        ​We have not had a chance to review these proposals with Toyota. No dates for getting this software either. ​+
    
 +   * SPEC-2927 - Window Manager for WAM
  
-   ​* ​Review ​[[https://jira.automotivelinux.org/​issues/?​filter=11710 ​Jira tickets for SAT]] +   ​* ​RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}. 
 +     * 8/29 Panasonic is reviewing  
 +     * 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.  
 +     * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.  
 +     * 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.  
 +     * 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.  
 +     * 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP.  Also will get a quote for creating the BSP from Konsulko. ​  
 +     * 12/4 - Block diagram ​[[ https://wiki.automotivelinux.org/​_media/eg-rhsa/​r-car_h3_reference_hardware_blockdiagram_20191126.pdf ​uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday.  
 +     * 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.  
 +     * Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.  
 +     * 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely.  
 +     * 3/26 - BSP RFI responses to be reviewed. AB tentatively approved purchasing the boards pending the Qualcomm and BSP discussions. ​
    
-   ​* ​Web app framework - Updates from LG/​Igalia?​ +   ​* ​Radio architecture and Tuner API Denso Ten will release documentation for radio and tuner functions by the end of September.  
-     * 5/24 - Nothing to report. +     ​* ​3/26 Kusakabe-san prepared ​draft document ​that will be reviewed during ​the Connectivity EG meeting next week
-     * 6/7 Stephane ​will create a summary report of the findings from this weeks meetings including a list of action items to pursue+
-     ​* ​8/Stephane reports: +
-       * Jose pushed example html5 apps and few fixes +
-       * meta-agl-lge:​ Status is that it works with EE, the FF branch is still WIP with master. Sebastien will take over when back. +
-     * 9/13 - Santa Clara F2F +
-       * Sebastien has some services working on FF. Will add WebAppManager to main build as a patch release to Flounder and call it a "​preview"​ which main work continues on master/ GG +
  
-   ​* ​Possibility that Suzuki could contribute new design for CES 2019.  Tanikawa says they had proposal that was shown at local Japan meeting this week.  +   ​* ​LTS   
-     ​* ​5/24 - Nothing to reportNext Japanese local meeting ​is next week. Will get an update for next SAT meeting.  +     ​* ​9/26 (Berlin F2F) 
-     ​6/7 Nothing to reportNeed to figure out if this is real by ALS or pursue getting an updated design elsewhere + * AI: identify base servicesWhat is in core-image-minimal that is available in all profiles.  
-     * 8/Nothing ​new. +  lifecycle 
-     ​9/13 Tanikawa does not have any more details from Suzuki ​on their schedule or plans. ​+    * apps vs platform (which applications  
 +    *  
 +  * API definition & documentation & Schema 
 +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/browse/SPEC-1903 
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md 
 +    Follow-up on SAT 
 +  * API versions 
 +    * -> APPFW / Jose
  
 +  * '​core'​ LTS vs. IVI or Cluster LTS
 +    * depends on changes required e.g. by IC 
 +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.  ​
 +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects. ​
 +      * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​
 +      * Will add to SC agenda for next week. 
 +    * 11/21 - SC did not get to this topic, Will be addressed at December meeting. ​
 +    * 12/5 - Following up next week. 
 +    * 1/16 - Added LTS to the SC agenda for February. ​
 +    * 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting, ​
  
-  ​SPEC-1601 discussion ​on Pulse Audio: +   Toyota Code Drop 
-    4a pulse plugin makes pulse client ​to 4a  +     * 10/10  
-    * for FF:  +       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.  
-      4a plugin for PulseAudio now available for FF.  +       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,​ 
-      Need to do some testing with audio roles for 4a and PA pluginNavigation ​will be tested by IoT.bzh team+     * 11/7 - Toyota documents are quite large. Were posted ​on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.  
 +     ​11/21 -  
 +     * Notes from SC meeting  
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has lot of details about CAN messaging but it is difficult ​to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure. ​ 
 +     ​Ohiwa-san is working on providing the context ​for the API documents. First task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents. ​ 
 +     ​12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas  
 +       ​Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended. 
 +       * Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).  
 +       * Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting. ​  
 +     * 12/19 - Ohiwa-san presented ​some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start upOhiwa-san will upload the document to the Toyota code drop Confluence page. https://​confluence.automotivelinux.org/​display/​TC/​Documents 
 +     * 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or twoWill be licensed under Apache 2.0.  
 +     * 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.{{:​sat_meetings:​document_for_sat_20200312.pdf|latest status}}  
 +     * Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG.  
 +     * 3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions
    
-    * for GG:  
-      * AGL core image should not include PulseAudio, only by upper layer request 
-      * Binary feed should include PulseAudio so it is there if someone wants to use it and can be installed later on.  
-      * pulse to have minimal config by default, and fragments add configuration bits in separate package 
- 
-   * Instrument Cluster profile and demo 
-     * Konsulko taking lead in creating IC demo to replace existing CES IC using latest AGL App FW.  
-     * Use current ethernet video feed for center display and move to Waltham receiver module later. ​ 
- 
-New: 
-   * SPEC-1754 - Modify Application code for divide homescreen label with windowmanager role  
-     * Proposed by Mitsunari. Will need to review with Graphics and UI EG.  Mistsunari will push sample code to review in gerrit prior to the review by the EG.  
-   * SPEC-1747 - Add ability to chose image upgrade mechanism at build time (SOTA, dnf , ...) 
-     * Updated the description in the ticket based on discussion and sent an email to Anton to make sure he sees it.  
- 
-   * Walt to send email to LG about moving WAM repositories to gerrit. ​ 
- 
- 
- 
-==== September 13, 2018 ==== 
-Attendees: Walt, Jan-Simon, Kurokawa, Kusakabe-san,​ Fulup, Sebastien, Stephane, Scott, ​ 
- 
-   * Discussed Issues with FF RC6 
-     * Identified a handful of patches to included in RC7. Jan-Simon will kick off RC7 build so people can start testing on Friday or later today in Santa Clara. 
    
- +   ELISA updates 
-   Reviewed and edited [[agl-distro:​release-notes#​funky_flounder|Funky Flounder release notes]] +     ​* ​ELISA and IC EG are recruiting AGL members to participateThe next F2F meeting for ELISA is in Brussel ​the Thursday and Friday before FOSDEMRegistration information can be found [[https://elisa.tech/announcement/2019/10/17/elisa-brussels-workshop-january30-31-2020/​ | here]] ​ 
-     ​* ​Decision taken that 4a will be the default build option for 6.0.0 (and 5.1.0 the next eel release). +     ​* ​ELISA groups.io page can be found [[https://lists.elisa.tech/g/devel | here ]] 
-     * Update 8/2 - was merged as https://gerrit.automotivelinux.org/gerrit/#/c/15499+     ​New ELISA development process subgroup has formedSee their [[ https://lists.elisa.tech/g/​devel/​topic/​please_join/​61718502?​p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 | groups.io page]] ​for more information ​and to sign up.  
-     ​* ​9/13 - Slights updatesMatt kicking off Vayu testingNeed to list known issues.  +     ​3/26 DrYamaguchi provided an update ​on the ELISA AGL cooperation proposal
- +
-    * Window Manager and Homescreen Plan for 2018 +
-      * Need additional SAT oversight and open up of the work.  +
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposal. Tanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend. ​ +
-      4/26 - Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo Need to get something in writing from Toyota on their schedule of features for this year.  +
-      * 5/24 - Surface ID management proposal from Tanikawa-san is being updated for Monday'​s Graphics and UI EG callAdditional discussions on the plan for Window Manager and Homescreen will be discussed in Lorient in two weeksNeed to get ADIT's schedule for updating the ID agent to ensure that it will be available and working in FF.  +
-      * 6/7 - Tanikawa working on high level design for window manager and homescreen to be reviewed at the June 19 F2F SAT meeting in TokyoWill also need a plan for staffing ​and timing ​to be presented to the AB in Tokyo. ​ Plan from Toyota in SPEC-1467. ​ It looks like splitting App Launcher from Homescreen will happen by late June from Toyota. Rest of their work is planned for September or later, but they will not be working with us as a community.  +
-      8/Push to next SAT call +
-      * 9/13 - Toyota plan for GG features +
-        * Toyota planning and software process is still very closed/ opaque. SAT relying ​on second hand information to determine what is going on.  +
-        * Change Home screen service to use application role instead of name for surface management. Unclear whether ​the Toyota design is sufficient for our needs.  +
-        * Window Manager - plan to support multiple surfaces and grouping of surfaces for a single application. Requirements are being driven by navigation and map use cases. ​   +
-        * We have not had a chance to review these proposals with Toyota. No dates for getting this software either+
    
  
-   ​* ​Review ​[[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  +FOSSology/ License ​Review 
-  +   ​* ​So far there has been no action taken on FOSSology reportsDan brought up starting ​new project ​to evaluate license file, conflicts etc. and funding someone to go do that work.  Will be brought up to AB at their next meeting.  ​ 
-   ​* ​Web app framework - Updates from LG/​Igalia?​ +   ​Open Chain reported ​that we have 320 different licenses. ​ How do we plan to collaborate ​with OpenChain?​ 
-     * 5/24 - Nothing to report. +   * Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.  
-     * 6/7 - Stephane will create ​summary report of the findings from this weeks meetings including a list of action items to pursue. +   ​3/26 Multiple issues blocking getting FOSSology server going, ​
-     * 8/2 - Stephane reports: +
-       * Jose pushed example html5 apps and a few fixes +
-       ​meta-agl-lge:​ Status is that it works with EE, the FF branch is still WIP with master. Sebastien ​will take over when back+
-     ​9/13 Santa Clara F2F +
-       * Sebastien has some services working on FF. Will add WebAppManager to main build as a patch release to Flounder and call it a "​preview"​ which main work continues on master/ GG.  ​+
  
-   * Possibility that Suzuki could contribute new design for CES 2019.  Tanikawa says they had proposal that was shown at local Japan meeting this week.  +New Business:
-     * 5/24 - Nothing to report. Next Japanese local meeting is next week. Will get an update for next SAT meeting.  +
-     * 6/7 - Nothing to report. Need to figure out if this is real by ALS or pursue getting an updated design elsewhere.  +
-     * 8/2 - Nothing new. +
-     * 9/13 - Tanikawa does not have any more details from Suzuki on their schedule or plans. ​+
  
- +   * SPEC-3295 Apply yocto metadata license file format ​to AGL layers.  
-  ​* SPEC-1601 discussion on Pulse Audio: +   ​New repository requests ​for POI (SPEC-3291 ​and SPEC-3293) ​
-    * 4a pulse plugin makes pulse a client ​to 4a  +
-    * for FF:  +
-      * 4a plugin for PulseAudio now available for FF.  +
-      Need to do some testing with audio roles for 4a and PA plugin. Navigation will be tested by IoT.bzh team.  +
-  +
-    * for GG:  +
-      * AGL core image should not include PulseAudio, only by upper layer request +
-      * Binary feed should include PulseAudio so it is there if someone wants to use it and can be installed later on.  +
-      * pulse to have minimal config by default, and fragments add configuration bits in separate package+
  
  
-New: 
-   * Instrument Cluster profile and demo 
-     * Konsulko taking lead in creating IC demo to replace existing CES IC using latest AGL App FW.  
-     * Use current ethernet video feed for center display and move to Waltham receiver module later. ​ 
  
 +==== March 12, 2020 ====
 +Attendees: Walt, Jan-Simon, Scott, Stephane, Li, Ohiwa, Kusakabe, Kurokawa, Tanikawa, Haraki, Abe, Hosokawa, Dr. Yamaguchi, Nomoto
  
 +   * 2020 Roadmap Review ​
 +     * Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list.  To be reviewed at SAT F2F at the AMM. 
 +     * Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]].
  
  
 +[[ https://​jira.automotivelinux.org/​browse/​SPEC-2538 | SPEC-2538]] - Remove support for multiple versions of widgets to be installed simultaneously. ​
 +   * 2/13 - Sandbox tested out and will be included in JJ release. Build option will be available for keeping multiple versions, ​
  
-==== August 30, 2018 ==== +   * Icefish final release 
-Attendees: Walt, Jan-Simon, Kurokawa, Kusakabe-san,​ Fulup, George, Sebastien, Yamaguchi, Stephane, Michael, Guy, Mitsunari, Momiyama +     ​Being slowed down by issues ​with CI.  
- +     * Waiting for a fix from Igalia on the WAM issue reported by Scott on Tuesday (SPEC-3181). ​
-   Discussed Issues ​with FF RC4+
    
 +   * SPEC-2927 - Window Manager for WAM
  
-   ​* ​Reviewed and edited [[agl-distro:release-notes#​funky_flounder|Funky Flounder release notes]] +   ​* ​RHSA RFQ updated the RFQ document with comments. The revised version is {{:eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}. 
-     ​* ​Decision taken that 4a will be the default build option for 6.0.0 (and 5.1.0 the next eel release)+     ​* ​8/29 Panasonic is reviewing  
-     ​* ​Update 8/was merged as https://​gerrit.automotivelinux.org/​gerrit/#/​c/​15499/​ +     * 9/12 - Panasonic still in review. Sekine-san ​will check with Panasonic about EG review during ​the AMM in Monaco.  
- +     ​* ​9/26 Still in review at PanasonicSekine-san expects a reply soon.  
-    ​Window Manager and Homescreen Plan for 2018 +     ​10/10 - Sekine-san thinks Panasonic ​will release ​the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should ​plan F2F meeting at that time with Panasonic and RHSA EG.  
-      * Need additional SAT oversight and open up of the work.  +     ​11/SC to meet next week and make recommendation to ABWe will make sure that Panasonic and Mazda RHSA team members are invited ​to that portion ​of the SC meeting next week.  
-      * 3/29 Tanikawa meeting with Toyota next week about their proposal. Tanikawa ​will present ​the Toyota ​plan at the F2F in Karlsruhe since Toyota cannot attend.  +     ​11/21 SC meeting last week in YokohamaWaiting ​on block diagram from Panasonic which was promised ​for two weeks (next week)There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP.  Also will get a quote for creating ​the BSP from Konsulko  
-      4/26 Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo ​Need ​to get something in writing from Toyota on their schedule ​of features for this year.  +     ​12/Block diagram [[ https://​wiki.automotivelinux.org/​_media/​eg-rhsa/​r-car_h3_reference_hardware_blockdiagram_20191126.pdf | uploaded ​to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday.  
-      5/24 Surface ID management proposal from Tanikawa-san is being updated for Monday'​s Graphics and UI EG callAdditional discussions ​on the plan for Window Manager and Homescreen will be discussed in Lorient in two weeks. ​Need to get ADIT's schedule ​for updating ​the ID agent to ensure that it will be available and working in FF.  +     * 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko ​for creating ​and maintaining the BSP.  
-      6/Tanikawa working on high level design for window manager and homescreen ​to be reviewed at the June 19 F2F SAT meeting in Tokyo. Will also need a plan for staffing ​and timing ​to be presented ​to the AB in Tokyo Plan from Toyota in SPEC-1467. ​ It looks like splitting App Launcher from Homescreen will happen by late June from Toyota. Rest of their work is planned for September or later, but they will not be working with us as a community.  +     * Panasonic ​to get agreement with Qualcomm ​to release firmware for the BT/Wifi chipNo update on this topic.  
-      8/Push to next SAT call+     ​1/16 Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely. ​
    
-    ​V2C EG +   Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September. ​ 
-      Kicks off July 16Meetings planned every two weeks.  +     ​9/12 - document is 60% translated to englishKusakabe will present an update at the dev call next week.  
-      2/8 - 2 meetings meanwhile, +     ​9/26  
-        Collecting use cases https://wiki.automotivelinux.org/​eg-v2c#​business_use_case_candidates +       ​ ​**Radio API review ** 
-        Feedback welcome +       * Sample API of Denso Ten released in staging/​documents 
-        Overlap and differences ​to Connectivity EG +       * Goal is to refine the radio api with additional functions found in the review of above 
 +       * focus on generic calls over hw specifics 
 +       * Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM 
 +       * Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done 
 +     * 10/10 
 +       * Kusakabe posted the API to Gerrit ​https://git.automotivelinux.org/​staging/​documents/​log/?​h=sandbox/​kusakabe/​radio-api 
 +       ​Kusakabe to release additional APIs by the end of the month 
 +       ​Scott needs to review. Need some additional Tier 1 or OEM reviewers.  
 +     * 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API.  
 +     * 11/21 - No update.  
 +     * 12/4 - No update. Further translations from Denso Ten may be available at the end of December.  
 +     * 12/19 - No update 
 +     * 1/16 - No update. Scott will start looking at it now that he is done with CES.  SPEC-1903 - IoT.bzh will provide a POC for the radio API.
  
 +   * LTS  ​
 +     * 9/26 (Berlin F2F)
 + * AI: identify base services. What is in core-image-minimal that is available in all profiles. ​
 +  * lifecycle
 +    * apps vs platform (which applications ​
 +    * 
 +  * API definition & documentation & Schema
 +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/​browse/​SPEC-1903
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md
 +    * Follow-up on SAT
 +  * API versions
 +    * -> APPFW / Jose
  
-   ​* ​Review ​[[https://jira.automotivelinux.org/issues/?​filter=11710 | Jira tickets for SAT]]  +  * '​core'​ LTS vs. IVI or Cluster LTS 
-  +    ​* ​depends on changes required e.g. by IC  
-   ​Security Blueprint ​SPEC-1454  +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.   
-     ​Security Expert Group discussed dropping ​the old blueprint from the doc site.+    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects.  
 +      * Stephane posted link for [[https://wiki.centos.org/Manuals/ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​ 
 +      * Will add to SC agenda for next week.  
 +    11/21 SC did not get to this topic, Will be addressed at December meeting.  
 +    * 12/5 Following up next week.  
 +    1/16 - Added LTS to the SC agenda for February
  
-   ​* ​Web app framework - Updates from LG/Igalia? +   ​* ​Toyota Code Drop 
-     ​* ​5/24 - Nothing ​to report+     ​* ​10/10  
-     ​* ​6/7 - Stephane ​will create a summary report of the findings ​from this weeks meetings including ​list of action items to pursue+       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion 
-     ​* ​8/2 Stephane reports+       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community, 
-       ​* ​Jose pushed example html5 apps and few fixes +     ​* ​11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san ​will be in Yokohama next week to discuss ​the next steps with the SC.  
-       ​* ​meta-agl-lgeStatus is that it works with EE, the FF branch is still WIP with masterSebastien ​will take over when back.+     * 11/21 -  
 +     * Notes from SC meeting  
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has lot of details about CAN messaging but it is difficult ​to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.  
 +     ​* ​Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents.  
 +     * 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.  ​ 
 +       ​* ​Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended. 
 +       * Discussion of whether the backed up data is in Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash). ​ 
 +       ​* ​Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting. ​  
 +     * 12/19 Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://​confluence.automotivelinux.org/​display/​TC/​Documents 
 +     * 1/16 - New version of the specification was uploaded to Confluence last weekCode will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.  
 +     * 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.{{:​sat_meetings:​document_for_sat_20200312.pdf|latest status}}  
 +     * Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG
  
-   * Possibility that Suzuki could contribute new design for CES 2019.  Tanikawa says they had proposal that was shown at local Japan meeting this week.  
-     * 5/24 - Nothing to report. Next Japanese local meeting is next week. Will get an update for next SAT meeting. ​ 
-     * 6/7 - Nothing to report. Need to figure out if this is real by ALS or pursue getting an updated design elsewhere. ​ 
-     * 8/2 - Nothing new. 
  
-   ​* ​Dynamic library link usage. See SPEC-1454. Added a comment to it. Assigned to Jose.  +   ​* ​Navi EG met last week with Momiyama-san and they will present a new architecture at the November SAT call.  
- +     ​* ​11/More discussion needed before Navi EG is ready to present the new architecture.  
-New: +     ​11/21 Navi EG presented an update last week in Yokohama. Need to get the document ​from Micware
-  * SPEC-1601 - discussion on pulse: +
-    * 4a pulse plugin makes pulse a client to 4a  +
-    * for FF:  +
-      * agl-demo be 4a+pulse (pulse active ​with plugin), option to build w/o pulse +
-        * additive agl-nopulse feature to aglsetup: removes the pulse DISTRO_FEATURE/​BACKFILL +
-      * we can merge george patches +
-    * for GG:  +
-      * core should not ship pulse , only by upper layer request +
-      * pulse to have minimal config by default, and fragments add configuration bits in separate package +
-      * binary image can install lateron +
- +
- +
-==== Aug 2, 2018 ==== +
-Attendees: Jan-Simon, Stephane, Kurokawa, Michael, Ronan, Tanikawa-san,​ Kusakabe-san,​ Nick, Fulup, George, Jose, Momiyama-san ​ +
- +
-   * Discussed Issues with FF RC2 +
-     * Fixing the black display issue requires reverting policy manager change (Jan-Simon will use gerrit 15461) due to bit bake failures. Once the revesion is finished Jan-Simon will merge change from Tanikawa'​s display fix.  +
-     * Race condition between home screen ​and launcher. If launcher wins the home screen is useless.  +
-     * Audio - discussed how to make 4a the default audio in aglsetup.sh so that pre-built binaries use 4a and users who do their own builds default to 4a unless ​they override the selection to use soundmanager or pulse.  +
-     * Schedule - revised FF schedule for RC2, RC3, and final release ​  +
-     * RC2 finished, release email soon +
-     * Tanikawa'​s work:  +
-       * set of changes in gerrit to reduce memory used +
-       * navigation and poi do not support that mode +
-       * mixer needs to be checked (Tanikawa-san ​will push try to sandbox, Loic will check) +
-     *  +
- +
-   * Reviewed and edited [[agl-distro:​release-notes#​funky_flounder|Funky Flounder release notes]] +
-     * Decision taken that 4a will be the default build option for 6.0.0 (and 5.1.0 the next eel release)+
-     ​* ​Update 8/was merged as https://​gerrit.automotivelinux.org/​gerrit/#/​c/​15499/​ +
- +
-    * Window Manager and Homescreen Plan for 2018 +
-      * Need additional SAT oversight and open up of the work.  +
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposal. Tanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend.  +
-      4/26 Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo.  Need to get something in writing from Toyota on their schedule of features for this year.  +
-      * 5/24 - Surface ID management proposal from Tanikawa-san is being updated for Monday'​s Graphics and UI EG call. Additional discussions on the plan for Window Manager and Homescreen will be discussed in Lorient ​in two weeks. Need to get ADIT's schedule for updating ​the ID agent to ensure that it will be available and working in FF.  +
-      * 6/7 - Tanikawa working on high level design for window manager and homescreen to be reviewed at the June 19 F2F SAT meeting in Tokyo. Will also need a plan for staffing and timing to be presented to the AB in Tokyo. ​ Plan from Toyota in SPEC-1467 It looks like splitting App Launcher from Homescreen will happen by late June from Toyota. Rest of their work is planned for September or later, but they will not be working with us as a community.  +
-      * 8/2 - Push to next SAT call+
    
-    * V2C EG 
-      * Kicks off July 16. Meetings planned every two weeks. ​ 
-      * 2/8 - 2 meetings meanwhile, 
-        * Collecting use cases https://​wiki.automotivelinux.org/​eg-v2c#​business_use_case_candidates 
-        * Feedback welcome 
-        * Overlap and differences to Connectivity EG  
- 
- 
-   * Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  
    
-   ​* ​Security Blueprint - SPEC-1454 ​ +   ​* ​ELISA updates 
-     ​* ​Security Expert Group discussed dropping ​the old blueprint from the doc site. +     ​* ​ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel ​the Thursday and Friday before FOSDEMRegistration information can be found [[https://elisa.tech/announcement/2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/​ | here]] ​ 
- +     ​ELISA groups.io page can be found [[https://lists.elisa.tech/g/devel | here ]] 
-   * Web app framework - Updates from LG/Igalia? +     ​* ​New ELISA development process subgroup has formed. See their [[ https://​lists.elisa.tech/g/devel/topic/​please_join/​61718502?​p=,,,20,0,0,0::​recentpostdate%2Fsticky,,,20,2,0,61718502 ​groups.io page]] for more information ​and to sign up. 
-     * 5/24 - Nothing to report. +
-     * 6/7 - Stephane will create a summary report of the findings from this weeks meetings including a list of action items to pursue. +
-     * 8/Stephane reports: +
-       * Jose pushed example html5 apps and a few fixes +
-       * meta-agl-lge: Status is that it works with EE, the FF branch is still WIP with master. Sebastien will take over when back. +
- +
-   Possibility that Suzuki could contribute new design for CES 2019 ​Tanikawa says they had proposal that was shown at local Japan meeting this week.  +
-     * 5/24 - Nothing to reportNext Japanese local meeting is next weekWill get an update for next SAT meeting.  +
-     * 6/7 - Nothing to report. Need to figure out if this is real by ALS or pursue getting an updated design elsewhere. ​ +
-     ​* ​8/2 - Nothing new. +
- +
-   * Dynamic library link usage. See SPEC-1454Added a comment to itAssigned to Jose.  +
- +
-New: +
-  * SPEC-1601 - discussion on pulse: +
-    * 4a pulse plugin makes pulse a client to 4a  +
-    * for FF:  +
-      * agl-demo be 4a+pulse (pulse active with plugin), option to build w/o pulse +
-        * additive agl-nopulse feature to aglsetup: removes the pulse DISTRO_FEATURE/BACKFILL +
-      * we can merge george patches +
-    * for GG:  +
-      * core should not ship pulse only by upper layer request +
-      * pulse to have minimal config by defaultand fragments add configuration bits in separate package +
-      * binary image can install lateron +
-  *  +
- +
-==== July 192018 ==== +
-Attendees: WaltJan-SimonStephaneKurokawaMitsunariMichaelSebastienTanikawaKusakabe +
- +
-   * Discussed Issues with FF RC2 +
-     * Fixing the black display issue requires reverting policy manager change (Jan-Simon will use gerrit 15461) due to bit bake failures. Once the revesion is finished Jan-Simon will merge change from Tanikawa'​s display fix.  +
-     * Race condition between home screen and launcher. If launcher wins the home screen is useless.  +
-     * Audio - discussed how to make 4a the default audio in aglsetup.sh so that pre-built binaries use 4a and users who do their own builds default to 4a unless they override the selection to use soundmanager or pulse.  +
-     * Schedule - revised FF schedule for RC2RC3, and final release ​  +
- +
-   * Reviewed and edited [[agl-distro:​release-notes#​funky_flounder|Funky Flounder release notes]] +
-     * Decision taken that 4a will be the default build option ​for 6.0.0 (and 5.1.0 the next eel release). ​  +
- +
-    * Window Manager and Homescreen Plan for 2018 +
-      * Need additional SAT oversight and open up of the work.  +
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposal. Tanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend.  +
-      * 4/26 - Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo.  Need to get something in writing from Toyota on their schedule of features for this year.  +
-      * 5/24 - Surface ID management proposal from Tanikawa-san is being updated for Monday'​s Graphics and UI EG call. Additional discussions on the plan for Window Manager and Homescreen will be discussed in Lorient in two weeks. Need to get ADIT's schedule for updating the ID agent to ensure that it will be available and working in FF.  +
-      * 6/7 - Tanikawa working on high level design for window manager and homescreen to be reviewed at the June 19 F2F SAT meeting in Tokyo. Will also need a plan for staffing and timing to be presented to the AB in Tokyo. ​ Plan from Toyota in SPEC-1467. ​ It looks like splitting App Launcher from Homescreen will happen by late June from Toyota. Rest of their work is planned for September or later, but they will not be working with us as a community+
    
-    * V2C EG 
-      * Kicks off July 16. Meetings planned every two weeks. ​ 
  
 +FOSSology/ License Review
 +   * So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work.  Will be brought up to AB at their next meeting.  ​
 +   * Open Chain reported that we have 320 different licenses. ​ How do we plan to collaborate with OpenChain?
 +   * Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year. 
  
-   * Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  
-  
  
-   * Web app framework - Updates from LG/​Igalia?​ +New Business:
-     * 5/24 - Nothing to report. +
-     * 6/7 - Stephane will create a summary report of the findings from this weeks meetings including a list of action items to pursue.  ​+
  
-   ​* ​Possibility that Suzuki could contribute new design ​for CES 2019.  Tanikawa says they had proposal that was shown at local Japan meeting this week.  +   ​* ​Walt to send out info on the CIP / EILSA webinar scheduled ​for tomorrow, ​ 
-     ​5/24 - Nothing ​to report. Next Japanese local meeting is next week. Will get an update ​for next SAT meeting +   ​Fujitsu wants to buy an i.MX8 board for testing, Scott recommended the [[ https://www.nxp.com/​design/development-boards/i.mx-evaluation-and-development-boards/​evaluation-kit-for-the-i.mx-8m-applications-processor:​MCIMX8M-EVK | NXP i.Mx8 EVKB]]
-     * 6/Nothing to reportNeed to figure out if this is real by ALS or pursue getting an updated design elsewhere+
  
-   * Dynamic library link usage. See SPEC-1454. Added a comment to it. Assigned to Jose.  
  
-New: 
-   * SPEC-1534 - In-tree builds fail with newer versions of app-templates 
-   * Feedback from ALS Demo 
  
 +==== February 13, 2020 ====
 +Attendees: Walt, Jan-Simon, Li, Scott, Jose, Sebastien, Kusakabe, Dr. Yamaguchi, Hosokawa, Michael, Jeremy, Kurokawa, Ronan, Sekine, Ohiwa, Guy
  
-==== July 5, 2018 ==== 
-Attendees: Walt, Jan-Simon, Michael, Daniel, George, Kurokawa, Guy, Tanikawa, Michele, Momiyama, Yamaguchi, Stephane, Sebastien, Tiejun 
  
-   ​* ​Reviewed and edited [[agl-distro:​release-notes#​funky_flounder|Funky Flounder release notes]] +   ​* ​2020 Roadmap Review ​ 
-     ​* ​Decision taken that 4a will be the default build option ​for 6.0.0 (and 5.1.0 the next eel release) +     ​* ​Create Jira tickets for components ​that may be moved to AGL core and post a request ​for comments on the mail list To be reviewed at SAT F2F at the AMM 
 +     * Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]].
  
-    * Window Manager and Homescreen Plan for 2018 
-      * Need additional SAT oversight and open up of the work.  
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposal. Tanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend. ​ 
-      * 4/26 - Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo.  Need to get something in writing from Toyota on their schedule of features for this year.  
-      * 5/24 - Surface ID management proposal from Tanikawa-san is being updated for Monday'​s Graphics and UI EG call. Additional discussions on the plan for Window Manager and Homescreen will be discussed in Lorient in two weeks. Need to get ADIT's schedule for updating the ID agent to ensure that it will be available and working in FF.  
-      * 6/7 - Tanikawa working on high level design for window manager and homescreen to be reviewed at the June 19 F2F SAT meeting in Tokyo. Will also need a plan for staffing and timing to be presented to the AB in Tokyo. ​ Plan from Toyota in SPEC-1467. ​ It looks like splitting App Launcher from Homescreen will happen by late June from Toyota. Rest of their work is planned for September or later, but they will not be working with us as a community. ​ 
-  
-    * V2C EG 
-      * Kicks off July 16. Meetings planned every two weeks. ​ 
  
 +[[ https://​jira.automotivelinux.org/​browse/​SPEC-2538 | SPEC-2538]] - Remove support for multiple versions of widgets to be installed simultaneously. ​
 +   * 2/13 - Sandbox tested out and will be included in JJ release. Build option will be available for keeping multiple versions, ​
  
-   ​* ​Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets ​for SAT]] +   ​* ​Icefish final release 
 +     * Being slowed down by issues ​with CI.  
 +     * Waiting ​for a fix from Igalia on the WAM issue reported by Scott on Tuesday (SPEC-3181). ​
    
 +   * SPEC-2927 - Window Manager for WAM
  
-   ​* ​Web app framework ​Updates from LG/​Igalia?​ +   ​* ​RHSA RFQ updated the RFQ document with commentsThe revised version is {{:eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}
-     * 5/24 - Nothing to report. +     ​* ​8/29 Panasonic ​is reviewing ​ 
-     * 6/7 Stephane will create a summary report of the findings from this weeks meetings including a list of action items to pursue  +     ​* ​9/12 Panasonic still in reviewSekine-san will check with Panasonic about EG review during the AMM in Monaco.  
- +     ​9/26 Still in review at PanasonicSekine-san expects ​reply soon.  
-   * Possibility that Suzuki could contribute new design for CES 2019 ​Tanikawa says they had proposal that was shown at local Japan meeting this week.  +     ​10/10 Sekine-san thinks Panasonic will release the RFQ in time to be reviewed ​in Monte CarloWalt will be in Yokohama in NovemberWe should plan a F2F meeting at that time with Panasonic ​and RHSA EG.  
-     ​* ​5/24 - Nothing to report. Next Japanese local meeting ​is next week. Will get an update for next SAT meeting. ​ +     ​* ​11/7 SC to meet next week and make recommendation to ABWe will make sure that Panasonic and Mazda RHSA team members are invited ​to that portion of the SC meeting next week.  
-     ​* ​6/Nothing to reportNeed to figure out if this is real by ALS or pursue getting an updated design elsewhere.  +     ​* ​11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is meeting next week in Tokyo to discuss furtherThere is a on-going discussion between Panasonic ​and Renesas about BSP Also will get quote for creating ​the BSP from Konsulko  
- +     ​* ​12/4 - Block diagram ​[[ https://wiki.automotivelinux.org/_media/eg-rhsa/r-car_h3_reference_hardware_blockdiagram_20191126.pdf | uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday.  
-   Dynamic library link usage. See SPEC-1454Added comment to itAssigned to Jose.  +     ​* ​12/19 - No updateWas reviewed by SC last week. Will forward ​and RFI to Konsulko ​for creating ​and maintaining the BSP.  
- +     ​Panasonic ​to get agreement with Qualcomm ​to release firmware ​for the BT/Wifi chipNo update ​on this topic.  
-New: +     ​1/16 Panasonic ​and Qualcomm are talking at the executive level about licensing ​the WiFi and Bluetooth chip firmware using click-thru license most likely
-   SPEC-1534 In-tree builds fail with newer versions of app-templates +
-   * Feedback from ALS Demo +
- +
- +
-==== June 21, 2018 ==== +
-Attendees:  +
- +
-See [[agl-distro:​jun2018-f2f|Face ​to Face Technical Meeting ​in TokyoJapan]] and {{:​agl-distro:​agl_sat_tokyo_june_19_2018.pdf|}} +
- +
- +
-==== June 72018 ==== +
-Attendees: Walt  +
- +
-   * Development processes ​and tool usage +
-     * Issue - Backlog of merge requests, speed up merging in meta repos. Bottleneck of merges if Jan-Simon goes on vacation.  +
-     ​* ​Issue More active reviews for source code repos +
-     * Broaden merge access ​to include more maintainersAllow maintainers ​to be nominated by the community to be approved by SAT+
-     ​* ​Each profile ​(IVI, telematics, corewould have set of maintainers  +
-     * Require reviews by changing merge criteria from +2 to an additive function (maybe +4) +
-     * Explore what other projects do +
-     * Jan-Simon - Will follow up with an email to the mail list asking for feedback ​and review the comments next SAT callThen put together ​more formal documentation of the process.  +
-     ​* ​Proposal ​[[https://docs.google.com/presentation/d/​1OOo6hyQEkOPoe-VMQNFB5uaM440pab7sieYx1MdF-WY/edit?​usp=sharing | as reviewed in Karlsruhe]] i +
-     * 5/24 Gatekeepers set up and wiki page created: [[subsystem:​gatekeepers|AGL Gatekeepers]] Still putting together ​the expert group reviewers and need to assign them to Git repos. +
- +
-   * Release Plan for 2018 +
-     ​* ​Funky Flounder will switch to rockoFocus on is on getting the BSP and the images correct for new features ​to be included in GG for CES and beyond.  +
-       * Beta versions of new features for CES will be permitted so we can start to try them out.  +
-     * Grumpy Guppy will stick with rocko. Focus for GG will be on feature development ​and maintaining ​a stable image. ​  +
-       * Need to manage new and complex feature more closely and ensure that the new features come in by September+
-       ​SAT will need to raise red flags earlier this year to get feature teams help when the features are critical ​for CES and falling behind.  +
- +
- +
-    * Window Manager and Homescreen Plan for 2018 +
-      * Need additional SAT oversight and open up of the work.  +
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposalTanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend.  +
-      * 4/26 - Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo.  Need to get something in writing from Toyota ​on their schedule of features for this year.  +
-      5/24 Surface ID management proposal from Tanikawa-san is being updated for Monday'​s Graphics ​and UI EG call. Additional discussions on the plan for Window Manager and Homescreen will be discussed in Lorient in two weeks. Need to get ADIT's schedule for updating ​the ID agent to ensure that it will be available ​and working in FF.  +
-      * 6/7 - Tanikawa working on high level design for window manager and homescreen to be reviewed at the June 19 F2F SAT meeting in Tokyo. Will also need plan for staffing and timing to be presented to the AB in Tokyo. ​ Plan from Toyota in SPEC-1467.  It looks like splitting App Launcher from Homescreen will happen by late June from Toyota. Rest of their work is planned for September or later, but they will not be working with us as a community+
    
-    * V2C EG +   * Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September.  
-      Received ​a proposal ​from Ashley ​for V2C EG +     * 9/12 - document is 60% translated to english. Kusakabe will present an update at the dev call next week.  
-      Panasonic may participate in the EGTanikawa will check internally.  +     ​9/26  
-      3/29 Kicked off at AMMWaiting ​for regular meeting schedule.  +       ​* ​ **Radio API review ** 
-      5/23 - No update. ​Have not seen any follow up meetings scheduledWill get in touch with Ashley to see if this is something he will continue to lead.  +       * Sample API of Denso Ten released in staging/​documents 
-      6/7/ - Email sent to Ashley and Lasse at ForgeRockWaiting on reply+       * Goal is to refine the radio api with additional functions found in the review of above 
 +       * focus on generic calls over hw specifics 
 +       * Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM 
 +       ​Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done 
 +     * 10/10 
 +       * Kusakabe posted the API to Gerrit https://git.automotivelinux.org/​staging/​documents/​log/?​h=sandbox/​kusakabe/​radio-api 
 +       ​Kusakabe to release additional APIs by the end of the month 
 +       * Scott needs to review. Need some additional Tier 1 or OEM reviewers.  
 +     * 11/Scott has been blocked on higher priority tasksWill bring this up to SC as an area for additional Tier One members to review the proposed API.  
 +     ​11/21 - No update. ​ 
 +     * 12/4 - No updateFurther translations from Denso Ten may be available at the end of December.  
 +     ​12/19 - No update 
 +     * 1/16 No update. Scott will start looking ​at it now that he is done with CES ​SPEC-1903 - IoT.bzh will provide a POC for the radio API.
  
-  +   * LTS   
-   ​SPEC-145 - Yocto Layer restructuringheadless device profile +     ​9/26 (Berlin F2F) 
-     ​Need to complete SPEC-219 Requirements for Telematics Device Profile + ​* ​AI: identify base services. What is in core-image-minimal that is available in all profiles. ​ 
-     ​Jan-Simon reviewed output from Vannes F2F meeting last week concerning device profiles and Yocto layer restructuringWe will have a follow up in two weeks during the SAT call. Assuming we agree to a plan in San Jose or within a week or afterwards, we will implement the changes after the update to the YP pyro branch ​on master. +  * lifecycle 
-     * 12/Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profile. Still being reviewed. +    * apps vs platform (which applications  
-     ​12/21 - Jan-Simon also started working on device profiles for FFShould get something pushed early in the new year +    ​ 
-     * 2/7 - Merging rocko onto master this week, then Jan-Simon will get the layer stuff onto master.  +  * API definition & documentation & Schema 
-     ​4/26 Sub-tasks continuing +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/browse/SPEC-1903 
-     ​5/24 - Part 3 in gerrit. Issues being looked at.  +    e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md 
-     ​6/7 - Part 3 has been merged! Current HTML5 demo is broken. Need to consider how to build this up in a manner that does not use Qt. Now we need a demo of a telematics unit! +    Follow-up on SAT 
 +  API versions 
 +    -> APPFW Jose
  
-   ​* ​Review ​[[https://jira.automotivelinux.org/issues/?​filter=11710 | Jira tickets for SAT]]  +  * '​core'​ LTS vs. IVI or Cluster LTS 
-  +    ​* ​depends on changes required e.g. by IC  
-   SPEC-1118 / SPEC-1036 - What to do about obsolete repos? +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.   
-     ​4/26 Tanikawa looking ​at resolving for FF.  +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects.  
-     ​5/24 Nothing to report +      * Stephane posted link for [[https://wiki.centos.org/Manuals/ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​ 
-     ​6/Nothing ​to report+      Will add to SC agenda for next week.  
 +    11/21 SC did not get to this topic, Will be addressed ​at December meeting.  
 +    12/Following up next week.  
 +    1/16 Added LTS to the SC agenda for February. ​
  
-   ​* ​Web app framework - Updates from LG/Igalia? +   ​* ​Toyota Code Drop 
-     ​* ​5/24 - Nothing ​to report+     ​* ​10/10  
-     ​* ​6/7 - Stephane ​will create a summary report of the findings ​from this weeks meetings including ​list of action items to pursue  +       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion 
- +       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community, 
-   ​Possibility that Suzuki could contribute new design ​for CES 2019 ​Tanikawa says they had proposal that was shown at local Japan meeting this week.  +     ​* ​11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san ​will be in Yokohama next week to discuss ​the next steps with the SC.  
-     ​* ​5/24 Nothing to reportNext Japanese local meeting ​is next weekWill get an update ​for next SAT meeting.  +     * 11/21 -  
-     ​* ​6/Nothing to reportNeed to figure out if this is real by ALS or pursue getting an updated design elsewhere.  +     * Notes from SC meeting  
- +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has lot of details about CAN messaging but it is difficult ​to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.  
-New:+     ​Ohiwa-san is working on providing the context ​for the API documentsFirst task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents.  
 +     ​* ​12/Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas  
 +       * Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended. 
 +       * Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash) 
 +       * Other requirements need to be documented that were discussed. Ohiwa-san will update ​and we will review further at the next SAT meeting. ​  
 +     ​* ​12/19 Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start upOhiwa-san will upload the document ​to the Toyota code drop Confluence pagehttps://​confluence.automotivelinux.org/​display/​TC/​Documents 
 +     * 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0. 
  
-   * Dynamic library link usage. See SPEC-1454. Added a comment to it. Assigned to Jose.  
  
- +   Navi EG met last week with Momiyama-san and they will present ​new architecture at the November ​SAT call.  
-==== May 24, 2018 ==== +     ​* ​11/More discussion needed before Navi EG is ready to present ​the new architecture.  
-Attendees: Walt, Jan-Simon, Michael, Sebastien, Kurokawa, Stephane, Kusakabe, Dominig +     * 11/21 Navi EG presented an update last week in Yokohama. Need to get the document ​from Micware
- +
-   Kick-off review of development processes ​and tool usage +
-     * Issue - Backlog of merge requests, speed up merging in meta repos. Bottleneck of merges if Jan-Simon goes on vacation.  +
-     * Issue - More active reviews for source code repos +
-     * Broaden merge access to include more maintainers. Allow maintainers to be nominated by the community to be approved by SAT. +
-     * Each profile (IVI, telematics, core) would have set of maintainers  +
-     * Require reviews by changing merge criteria from +2 to an additive function (maybe +4) +
-     * Explore what other projects do.  +
-     * Jan-Simon - Will follow up with an email to the mail list asking for feedback and review the comments next SAT call. Then put together a more formal documentation of the process.  +
-     ​* ​4/26 Proposal [[https://​docs.google.com/​presentation/​d/​1OOo6hyQEkOPoe-VMQNFB5uaM440pab7sieYx1MdF-WY/​edit?​usp=sharing | as reviewed in Karlsruhe]] ​is being implemented.  +
-     * 5/24 - Gatekeepers set up and wiki page created: [[subsystem:​gatekeepers|AGL Gatekeepers]] Still putting together the expert group reviewers and need to assign them to Git repos. +
- +
-   * Release Plan for 2018 +
-     * Funky Flounder will switch to rocko. Focus on is on getting ​the BSP and the images correct for new features to be included in GG for CES and beyond.  +
-       * Beta versions of new features for CES will be permitted so we can start to try them out.  +
-     * Grumpy Guppy will stick with rocko. Focus for GG will be on feature development and maintaining a stable image. ​  +
-       * Need to manage new and complex feature more closely and ensure that the new features come in by September. +
-       * SAT will need to raise red flags earlier this year to get feature teams help when the features are critical for CES and falling behind.  +
- +
-   * SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform. +
-     * 9/14 - See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment in Jira]] that summarizes the discussion and action items.  +
-     * 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884) +
-     * 10/12 - Action item 1 completed in SPEC 859. Need to create a subtask for AI 2. Probably defer action on it until after EE.  +
-     * 11/Action item 2 needs to be started +
-     * 4/26 - Action item 2 will be completed with the next (final) step in the layer/ profile restructuring ​ in the next week.  +
-     * 5/24 - Action item 2 on going. +
- +
-    * Window Manager and Homescreen Plan for 2018 +
-      * Need additional SAT oversight and open up of the work.  +
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposal. Tanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend +
-      * 4/26 - Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo.  ​Need to get something in writing ​from Toyota on their schedule of features for this year.  +
-      * 5/24 - Surface ID management proposal from Tanikawa-san is being updated for Monday'​s Graphics and UI EG call. Additional discussions on the plan for Window Manager and Homescreen will be discussed in Lorient in two weeks. Need to get ADIT's schedule for updating the ID agent to ensure that it will be available and working in FF+
    
-    ​V2C EG +   FOSDEM 
-      Received a proposal from Ashley for V2C EG +     ​FOSDEM stand acceptedEmbedded devroom talk schedule is now available.  
-      * Panasonic may participate in the EGTanikawa will check internally.  +     ​Sign up for staffing the stand at FOSDEM at https://​doodle.com/​poll/​z5wzgdpnsv3xgbkp
 
-      3/29 - Kicked off at AMM. Waiting for regular meeting schedule.  +     ​Deadline for AMM CFP is now Jan 17
-      5/23 - No update. Have not seen any follow up meetings scheduled. Will get in touch with Ashley to see if this is something he will continue to lead. +
  
-  +   ELISA updates 
-   SPEC-145 - Yocto Layer restructuring/​ headless device profile +     ​* ​ELISA and IC EG are recruiting AGL members ​to participate. The next F2F meeting ​for ELISA is in Brussel ​the Thursday and Friday before FOSDEMRegistration information can be found [[https://​elisa.tech/announcement/​2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/ | here]] ​ 
-     ​* ​Need to complete SPEC-219 - Requirements for Telematics Device Profile +     ​* ​ELISA groups.io page can be found [[https://lists.elisa.tech/​g/​devel | here ]] 
-     * Jan-Simon reviewed output from Vannes ​F2F meeting ​last week concerning device profiles and Yocto layer restructuring. We will have a follow up in two weeks during ​the SAT callAssuming we agree to a plan in San Jose or within a week or afterwards, we will implement the changes after the update to the YP pyro branch on master. +     ​* ​New ELISA development process subgroup has formed. See their [[ https://lists.elisa.tech/g/devel/​topic/​please_join/​61718502?​p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 | groups.io page]] for more information and to sign up
-     * 12/Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profile. Still being reviewed. +
-     ​* ​12/21 - Jan-Simon also started working on device profiles for FFShould get something pushed early in the new year.  +
-     ​* ​2/7 - Merging rocko onto master this week, then Jan-Simon will get the layer stuff onto master +
-     * 4/26 - Sub-tasks continuing +
-     * 5/24 - Part 3 in gerritIssues being looked at+
  
-   * Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  
-  
-   * SPEC-1118 / SPEC-1036 - What to do about obsolete repos? 
-     * 4/26 - Tanikawa looking at resolving for FF.  
-     * 5/24 - Nothing to report 
- 
-   * Web app framework - Updates from LG/Igalia? 
-     * 5/24 - Nothing to report. ​ 
- 
-   * Possibility that Suzuki could contribute new design for CES 2019.  Tanikawa says they had proposal that was shown at local Japan meeting this week.  
-     * 5/24 - Nothing to report. Next Japanese local meeting is next week. Will get an update for next SAT meeting. ​ 
- 
-New: 
-   * New board support for 2018.  
-     * Renesas H3 ULCB - board availability? ​ Does the Renesas BSP automatically support both M3 and H3? BSP update with Spectre and Meltdown targeted for FF RC3.  
-     * Intel Aeon Up-Square or Up-Core. See https://​up-shop.org/​4-up-boards ​ Probably will use the Up-Square Celeron 2GB or 4 GB. 
- 
-==== May 10, 2018 ==== 
-Attendees: //Upcoming Meeting// 
- 
-Review outcome from [[agl-distro:​apr2018-f2f|Karlsruhe F2F meeting]]. 
- 
-   * Kick-off review of development processes and tool usage 
-     * Issue - Backlog of merge requests, speed up merging in meta repos. Bottleneck of merges if Jan-Simon goes on vacation. ​ 
-     * Issue - More active reviews for source code repos 
-     * Broaden merge access to include more maintainers. Allow maintainers to be nominated by the community to be approved by SAT. 
-     * Each profile (IVI, telematics, core) would have a set of maintainers ​ 
-     * Require reviews by changing merge criteria from +2 to an additive function (maybe +4) 
-     * Explore what other projects do.  
-     * Jan-Simon - Will follow up with an email to the mail list asking for feedback and review the comments next SAT call. Then put together a more formal documentation of the process. ​ 
-     * 4/26 - Proposal [[https://​docs.google.com/​presentation/​d/​1OOo6hyQEkOPoe-VMQNFB5uaM440pab7sieYx1MdF-WY/​edit?​usp=sharing | as reviewed in Karlsruhe]] is being implemented. ​ 
  
-   * Release Plan for 2018 
-     * Funky Flounder will switch to rocko. Focus on is on getting the BSP and the images correct for new features to be included in GG for CES and beyond. ​ 
-       * Beta versions of new features for CES will be permitted so we can start to try them out.  
-     * Grumpy Guppy will stick with rocko. Focus for GG will be on feature development and maintaining a stable image.  ​ 
-       * Need to manage new and complex feature more closely and ensure that the new features come in by September. 
-       * SAT will need to raise red flags earlier this year to get feature teams help when the features are critical for CES and falling behind. ​ 
- 
-   * SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform. 
-     * 9/14 - See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment in Jira]] that summarizes the discussion and action items. ​ 
-     * 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884) 
-     * 10/12 - Action item 1 completed in SPEC 859. Need to create a subtask for AI 2. Probably defer action on it until after EE.  
-     * 11/9 - Action item 2 needs to be started 
-     * 4/26 - Action item 2 will be completed with the next (final) step in the layer/ profile restructuring ​ in the next week.  
- 
-    * Window Manager and Homescreen Plan for 2018 
-      * Need additional SAT oversight and open up of the work.  
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposal. Tanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend. ​ 
-      * 4/26 - Tanikawa spoke to Hoshina-san about Toyota schedule for 2018 and CES demo.  Need to get something in writing from Toyota on their schedule of features for this year.  
    
-    * V2C EG 
-      * Received a proposal from Ashley for V2C EG 
-      * Panasonic may participate in the EG. Tanikawa will check internally. ​ 
-      * 3/29 - Kicked off at AMM. Waiting for regular meeting schedule. ​ 
  
-  +FOSSology/ License Review 
-   ​* ​SPEC-145 - Yocto Layer restructuring/​ headless device profile +   ​* ​So far there has been no action taken on FOSSology reports. Dan brought up starting a new project ​to evaluate license file, conflicts etc. and funding someone to go do that work Will be brought ​up to AB at their next meeting  
-     * Need to complete SPEC-219 - Requirements for Telematics Device Profile +   * Open Chain reported that we have 320 different licenses. ​ How do we plan to collaborate with OpenChain? 
-     * Jan-Simon reviewed output from Vannes F2F meeting last week concerning device profiles ​and Yocto layer restructuringWe will have a follow ​up in two weeks during the SAT callAssuming ​we agree to a plan in San Jose or within a week or afterwards, we will implement the changes after the update ​to the YP pyro branch on master. +   ​Fujitsu has volunteered ​to do some work sorting out the licensing which will get started in the new year. 
-     ​12/7 - Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profile. Still being reviewed. +
-     * 12/21 - Jan-Simon also started ​working on device profiles for FF. Should get something pushed early in the new year.  +
-     * 2/7 - Merging rocko onto master this week, then Jan-Simon will get the layer stuff onto master.  +
-     * 4/26 - Sub-tasks continuing+
  
-   * Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  
-  
-   * SPEC-1118 / SPEC-1036 - What to do about obsolete repos? 
-     * 4/26 - Tanikawa looking at resolving for FF.  
  
-New +New Business:
-   * Updates from LG/​Igalia?​ +
-   * Possibility that Suzuki could contribute new design for CES 2019.  Tanikawa says they had proposal that was shown at local Japan meeting this week. +
  
-New:+   * SPEC-3097 - SOTA Issues (Ronan) 
 +     * Fixed, but SOTA is not built or tested in CI. Feature was broken for an unknown length of time. Ronan asked if we could set up periodic SOTA build. ​ Jan-Simon suggested adding patches to CI management scripts.
  
-==== April 26, 2018 ==== 
-Attendees: Walt, Jan-Simon, Kurokawa, Kusakabe, Tanikawa, Dominig, Steve L., Sebastien 
  
-Review outcome from [[agl-distro:​apr2018-f2f|Karlsruhe F2F meeting]]. 
  
-   * Kick-off review of development processes and tool usage 
-     * Issue - Backlog of merge requests, speed up merging in meta repos. Bottleneck of merges if Jan-Simon goes on vacation. ​ 
-     * Issue - More active reviews for source code repos 
-     * Broaden merge access to include more maintainers. Allow maintainers to be nominated by the community to be approved by SAT. 
-     * Each profile (IVI, telematics, core) would have a set of maintainers ​ 
-     * Require reviews by changing merge criteria from +2 to an additive function (maybe +4) 
-     * Explore what other projects do.  
-     * Jan-Simon - Will follow up with an email to the mail list asking for feedback and review the comments next SAT call. Then put together a more formal documentation of the process. ​ 
-     * 4/26 - Proposal [[https://​docs.google.com/​presentation/​d/​1OOo6hyQEkOPoe-VMQNFB5uaM440pab7sieYx1MdF-WY/​edit?​usp=sharing | as reviewed in Karlsruhe]] is being implemented. ​ 
  
-   * Release Plan for 2018 
-     * Funky Flounder will switch to rocko. Focus on is on getting the BSP and the images correct for new features to be included in GG for CES and beyond. ​ 
-       * Beta versions of new features for CES will be permitted so we can start to try them out.  
-     * Grumpy Guppy will stick with rocko. Focus for GG will be on feature development and maintaining a stable image.  ​ 
-       * Need to manage new and complex feature more closely and ensure that the new features come in by September. 
-       * SAT will need to raise red flags earlier this year to get feature teams help when the features are critical for CES and falling behind. ​ 
  
-   * SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform. +==== January 16, 2020 ==== 
-     * 9/14 - See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment in Jira]] that summarizes the discussion and action items. ​ +Attendees: Walt, DrYamaguchi, Kusakabe, Scott, Stephane, Michael ​
-     * 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884) +
-     * 10/12 - Action item 1 completed in SPEC 859. Need to create a subtask for AI 2. Probably defer action on it until after EE.  +
-     * 11/9 - Action item 2 needs to be started +
-     * 4/26 - Action item 2 will be completed with the next (final) step in the layer/ profile restructuring ​ in the next week+
  
-    * Window Manager and Homescreen Plan for 2018 +[[ https://jira.automotivelinux.org/browse/SPEC-2538 | SPEC-2538]] - Remove support ​for multiple versions of widgets ​to be installed simultaneously
-      * Need additional SAT oversight and open up of the work.  +
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposalTanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend +
-      * 4/26 Tanikawa spoke to Hoshina-san about Toyota schedule ​for 2018 and CES demo.  Need to get something in writing from Toyota on their schedule of features for this year.  +
-  +
-    * V2C EG +
-      * Received a proposal from Ashley for V2C EG +
-      * Panasonic may participate in the EG. Tanikawa will check internally.  +
-      * 3/29 - Kicked off at AMM. Waiting for regular meeting schedule+
  
 +   * Window manager update from Daniel
 +   * Icefish RC3 decisions
 +     * Will release this week. 
 +     * Waiting on the last changes from Daniel and Scott for window manager. Window manager is being rescheduled for January and will have to be in a point release of Itchy Icefish. ​
    
-   * SPEC-145 Yocto Layer restructuring/​ headless device profile +   * SPEC-2927 Window Manager ​for WAM
-     * Need to complete SPEC-219 - Requirements ​for Telematics Device Profile +
-     * Jan-Simon reviewed output from Vannes F2F meeting last week concerning device profiles and Yocto layer restructuring. We will have a follow up in two weeks during the SAT call. Assuming we agree to a plan in San Jose or within a week or afterwards, we will implement the changes after the update to the YP pyro branch on master. +
-     * 12/7 - Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profile. Still being reviewed. +
-     * 12/21 - Jan-Simon also started working on device profiles for FF. Should get something pushed early in the new year.  +
-     * 2/7 - Merging rocko onto master this week, then Jan-Simon will get the layer stuff onto master.  +
-     * 4/26 - Sub-tasks continuing+
  
-   ​* ​Review ​[[https://jira.automotivelinux.org/​issues/?​filter=11710 ​Jira tickets for SAT]] +   ​* ​RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}. 
 +     * 8/29 Panasonic is reviewing  
 +     * 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.  
 +     * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.  
 +     * 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.  
 +     * 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.  
 +     * 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP.  Also will get a quote for creating the BSP from Konsulko. ​  
 +     * 12/4 - Block diagram ​[[ https://wiki.automotivelinux.org/​_media/eg-rhsa/​r-car_h3_reference_hardware_blockdiagram_20191126.pdf ​uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday.  
 +     * 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.  
 +     * Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.  
 +     * 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely. ​
    
-   ​* ​SPEC-1118 SPEC-1036 - What to do about obsolete repos+   ​* ​Gap analysis ​Denso Ten will release documentation for radio and tuner functions by the end of September.  
-     * 4/26 Tanikawa ​looking at resolving ​for FF+     * 9/12 document is 60% translated ​to english. Kusakabe will present an update at the dev call next week.  
 +     * 9/26  
 +       ​* ​ **Radio API review ** 
 +       * Sample API of Denso Ten released in staging/​documents 
 +       * Goal is to refine the radio api with additional functions found in the review of above 
 +       * focus on generic calls over hw specifics 
 +       * Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM 
 +       * Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done 
 +     * 10/10 
 +       * Kusakabe posted the API to Gerrit https://​git.automotivelinux.org/​staging/​documents/​log/​?h=sandbox/​kusakabe/​radio-api 
 +       * Kusakabe to release additional APIs by the end of the month 
 +       * Scott needs to review. Need some additional Tier 1 or OEM reviewers. ​ 
 +     ​* ​11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API.  
 +     * 11/21 - No update.  
 +     * 12/- No update. Further translations from Denso Ten may be available at the end of December.  
 +     * 12/19 No update 
 +     * 1/16 - No update. Scott will start looking at it now that he is done with CES.  SPEC-1903 - IoT.bzh will provide a POC for the radio API.
  
-   ​* ​Review status of [[eg-speech|Speech EG]] kick off meetings. ​ BoF session planned for AMM next week.  +   ​* ​LTS   
-  +     * 9/26 (Berlin F2F) 
-   ​Review status [[eg-rhsa|RHSA EG]]Walt has an updated presentation from Goto-san and will share it with Goto-san's approval.   + ​* ​AI: identify base servicesWhat is in core-image-minimal that is available in all profiles 
-     ​Checking ​on updates for Karlsruhe F2F and whether Goto-san will attend in person+  * lifecycle 
 +    apps vs platform (which applications  
 +    *  
 +  * API definition & documentation & Schema 
 +    * AI: iot.bzh will follow-up ​on https://​jira.automotivelinux.org/​browse/​SPEC-1903 
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md 
 +    * Follow-up on SAT 
 +  * API versions 
 +    * -> APPFW / Jose
  
-New +  * '​core'​ LTS vs. IVI or Cluster LTS 
-   * Updates from LG/Igalia? +    depends on changes required e.g. by IC  
-   ​Possibility that Suzuki could contribute new design for CES 2019.  ​Tanikawa says they had proposal ​that was shown at local Japan meeting ​this week. +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.   
 +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects.  
 +      * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing.  
 +      * Will add to SC agenda for next week.  
 +    * 11/21 - SC did not get to this topic, Will be addressed ​at December ​meeting.  
 +    * 12/5 - Following up next week.  
 +    * 1/16 - Added LTS to the SC agenda for February
  
 +   * Toyota Code Drop
 +     * 10/10 
 +       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion. ​
 +       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
 +     * 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC. 
 +     * 11/21 - 
 +     * Notes from SC meeting ​
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure. ​
 +     * Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents. ​
 +     * 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.  ​
 +       * Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended.
 +       * Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash). ​
 +       * Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.  ​
 +     * 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://​confluence.automotivelinux.org/​display/​TC/​Documents
 +     * 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0. 
  
-==== April 12, 2018 ==== 
- 
-See notes from [[agl-distro:​apr2018-f2f|Karlsruhe F2F meeting]]. ​ 
- 
- 
-==== March 29 2018 ==== 
-Attendees: Walt, Tanikawa, Kurokawa, Stephane, Fulup, Sebastien 
- 
-   * Created [[agl-distro:​als-2018-demo|ALS Demo plan]] 
- 
-   * Reviewed agenda and topics for the [[agl-distro:​apr2018-f2f|Karlsruhe F2F meeting]] ​ 
- 
-   * Review [[agl-roadmap|2018 Roadmap]] 
  
-   ​* ​Kick-off review of development processes ​and tool usage +   ​* ​Navi EG met last week with Momiyama-san and they will present ​new architecture at the November ​SAT call.  
-     * Issue - Backlog of merge requests, speed up merging in meta repos. Bottleneck of merges if Jan-Simon goes on vacation.  +     ​* ​11/More discussion needed before Navi EG is ready to present ​the new architecture.  
-     * Issue - More active reviews for source code repos +     ​* ​11/21 Navi EG presented an update last week in Yokohama. Need to get the document from Micware
-     * Broaden merge access to include more maintainers. Allow maintainers to be nominated by the community to be approved by SAT. +
-     * Each profile (IVI, telematics, core) would have set of maintainers  +
-     * Require reviews by changing merge criteria from +2 to an additive function (maybe +4) +
-     * Explore what other projects do.  +
-     * Jan-Simon - Will follow up with an email to the mail list asking for feedback and review ​the comments next SAT call. Then put together a more formal documentation of the process.  +
-     ​* ​2/15 Discussed J +
- +
-   * Release Plan for 2018 +
-     * Funky Flounder will switch to rocko. Focus on is on getting the BSP and the images correct for new features ​to be included in GG for CES and beyond.  +
-       * Beta versions of new features for CES will be permitted so we can start to try them out.  +
-     * Grumpy Guppy will stick with rocko. Focus for GG will be on feature development and maintaining a stable image. ​  +
-       * Need to manage new and complex feature more closely and ensure that the new features come in by September. +
-       * SAT will need to raise red flags earlier this year to get feature teams help when the features are critical for CES and falling behind.  +
- +
-   * SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform+
-     ​* ​9/14 See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment ​in Jira]] that summarizes the discussion and action items.  +
-     * 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884) +
-     * 10/12 - Action item 1 completed in SPEC 859. Need to create a subtask for AI 2. Probably defer action on it until after EE.  +
-     * 11/9 - Action item 2 needs to be started +
- +
- +
-    * Window Manager and Homescreen Plan for 2018 +
-      * Need additional SAT oversight and open up of the work.  +
-      * 3/29 - Tanikawa meeting with Toyota next week about their proposal. Tanikawa will present the Toyota plan at the F2F in Karlsruhe since Toyota cannot attend+
    
-    ​V2C EG +   FOSDEM 
-      Received a proposal from Ashley for V2C EG +     ​FOSDEM stand acceptedEmbedded devroom talk schedule is now available.  
-      * Panasonic may participate in the EGTanikawa will check internally.  +     ​Sign up for staffing the stand at FOSDEM at https://​doodle.com/​poll/​z5wzgdpnsv3xgbkp
 
-      3/29 - Kicked off at AMMWaiting ​for regular meeting schedule. ​+     * Deadline ​for AMM CFP is now Jan 17
  
-  +   ELISA updates 
-   SPEC-145 - Yocto Layer restructuring/​ headless device profile +     ​* ​ELISA and IC EG are recruiting AGL members ​to participate. The next F2F meeting ​for ELISA is in Brussel ​the Thursday and Friday before FOSDEMRegistration information can be found [[https://​elisa.tech/​announcement/​2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/​ | here]] ​ 
-     ​* ​Need to complete SPEC-219 - Requirements for Telematics Device Profile +     ​* ​ELISA groups.io page can be found [[https://lists.elisa.tech/​g/​devel | here ]] 
-     * Jan-Simon reviewed output from Vannes ​F2F meeting ​last week concerning device profiles and Yocto layer restructuring. We will have a follow up in two weeks during ​the SAT callAssuming we agree to a plan in San Jose or within a week or afterwards, we will implement the changes after the update to the YP pyro branch on master+     ​* ​New ELISA development process subgroup has formed. See their [[ https://lists.elisa.tech/g/​devel/​topic/​please_join/​61718502?​p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 | groups.io page]] for more information and to sign up
-     ​* ​12/7 - Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profileStill being reviewed+
-     ​* ​12/21 - Jan-Simon also started working on device profiles for FFShould get something pushed early in the new year +
-     * 2/7 - Merging rocko onto master this weekthen Jan-Simon will get the layer stuff onto master+
  
-   * Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  
-  
-   * SPEC-1118 / SPEC-1036 - What to do about obsolete repos? 
  
-   * Review status of [[eg-speech|Speech EG]] kick off meetings. ​ BoF session planned for AMM next week.  
    
-   * Review status [[eg-rhsa|RHSA EG]]. Walt has an updated presentation from Goto-san and will share it with Goto-san'​s approval. ​  +New Business:
-     * Checking on updates for Karlsruhe F2F and whether Goto-san will attend in person. ​+
  
 +FOSSology/ License Review
 +   * So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work.  Will be brought up to AB at their next meeting.  ​
 +   * Open Chain reported that we have 320 different licenses. ​ How do we plan to collaborate with OpenChain?
 +   * Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year. 
  
-New 
  
 +   * Future meeting scheduling ​
 +     * Block scheduling of meetings to consolidate the schedule
 +     * Japanese members attending the call are ok with this meetings at this time. 
 +     * Might be better one or two hours earlier than currently (Hosokawa) ​
 +     * Will bring up at the SC meeting next week. Also post a question on the mail list (maybe create a poll)
  
-==== March 152018 ==== +Tanibata: Merge Graphics and UI with Instrument Cluster EG starting next year. Schedule for a more EU/Japan joint friendly time.  Would like feedback from Haraki-san on this proposal. Tanibata-san will meet with Haraki-san today to discuss. One idea is for meetings to be held at 5:00 pm JST (which is 9 am CET2 am Chicago time) 
-Attendees: Walt, Michael, Kurokawa, Stephane, Sebastien, Fulup+Developer call. Can try to hold two sessions per week.  One at the current time on Tuesday and a second session at 6 pm Chicago time/ 9 am JST. 
  
-   * Reviewed agenda and topics for the [[agl-distro:​apr2018-f2f|Karlsruhe F2F meeting]] ​ 
-   * only item looked at during the call.  ​ 
  
-   * Review [[agl-roadmap|2018 Roadmap]] 
  
-   * Kick-off review of development processes and tool usage 
-     * Issue - Backlog of merge requests, speed up merging in meta repos. Bottleneck of merges if Jan-Simon goes on vacation. ​ 
-     * Issue - More active reviews for source code repos 
-     * Broaden merge access to include more maintainers. Allow maintainers to be nominated by the community to be approved by SAT. 
-     * Each profile (IVI, telematics, core) would have a set of maintainers ​ 
-     * Require reviews by changing merge criteria from +2 to an additive function (maybe +4) 
-     * Explore what other projects do.  
-     * Jan-Simon - Will follow up with an email to the mail list asking for feedback and review the comments next SAT call. Then put together a more formal documentation of the process. ​ 
-     * 2/15 - Discussed J 
  
-   * Release Plan for 2018 +==== January 2, 2020 ==== 
-     * Funky Flounder will switch to rocko. Focus on is on getting the BSP and the images correct for new features to be included in GG for CES and beyond.  +Meeting Cancelled
-       * Beta versions of new features for CES will be permitted so we can start to try them out.  +
-     * Grumpy Guppy will stick with rocko. Focus for GG will be on feature development and maintaining a stable image. ​  +
-       * Need to manage new and complex feature more closely and ensure that the new features come in by September. +
-       * SAT will need to raise red flags earlier this year to get feature teams help when the features are critical for CES and falling behind. ​+
  
-   * SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform. 
-     * 9/14 - See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment in Jira]] that summarizes the discussion and action items. ​ 
-     * 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884) 
-     * 10/12 - Action item 1 completed in SPEC 859. Need to create a subtask for AI 2. Probably defer action on it until after EE.  
-     * 11/9 - Action item 2 needs to be started 
  
 +==== December 19, 2019 ====
 +Attendees: Walt, Jan-Simon, Scott, Stephane, Ohiwa, Kurokawa, Yamaguchi, Fulup, Guy, Li, Sekine, Takada, Nishiguchi, Haraki, Juhyun Doh, Cristoph Stoidner, Fulup, Vincent, George, Sebastien
  
-    * Window Manager and Homescreen Plan for 2018 
-      * Need additional SAT oversight and open up of the work.  
-  
-    * V2C EG 
-      * Received a proposal from Ashley for V2C EG 
-      * Panasonic may participate in the EG. Tanikawa will check internally. ​ 
-      * 9/28 - No update 
  
 +   * Window manager update from Daniel
 +   * Icefish RC3 decisions
 +     * Will release this week. 
 +     * Waiting on the last changes from Daniel and Scott for window manager. Window manager is being rescheduled for January and will have to be in a point release of Itchy Icefish. ​
    
-   * SPEC-145 Yocto Layer restructuring/​ headless device profile +   * SPEC-2927 Window Manager ​for WAM
-     * Need to complete SPEC-219 - Requirements ​for Telematics Device Profile +
-     * Jan-Simon reviewed output from Vannes F2F meeting last week concerning device profiles and Yocto layer restructuring. We will have a follow up in two weeks during the SAT call. Assuming we agree to a plan in San Jose or within a week or afterwards, we will implement the changes after the update to the YP pyro branch on master. +
-     * 12/7 - Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profile. Still being reviewed. +
-     * 12/21 - Jan-Simon also started working on device profiles for FF. Should get something pushed early in the new year.  +
-     * 2/7 - Merging rocko onto master this week, then Jan-Simon will get the layer stuff onto master. ​+
  
-   ​* ​Review ​[[https://jira.automotivelinux.org/​issues/?​filter=11710 ​Jira tickets for SAT]] +   ​* ​RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}. 
 +     * 8/29 Panasonic is reviewing  
 +     * 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.  
 +     * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.  
 +     * 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.  
 +     * 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.  
 +     * 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP.  Also will get a quote for creating the BSP from Konsulko. ​  
 +     * 12/4 - Block diagram ​[[ https://wiki.automotivelinux.org/​_media/eg-rhsa/​r-car_h3_reference_hardware_blockdiagram_20191126.pdf ​uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday.  
 +     * 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.  
 +     * Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic. ​
    
-   ​* ​SPEC-1118 SPEC-1036 - What to do about obsolete repos?+   ​* ​Gap analysis ​Denso Ten will release documentation for radio and tuner functions by the end of September.  
 +     * 9/12 document is 60% translated ​to english. Kusakabe will present an update at the dev call next week.  
 +     * 9/26  
 +       ​* ​ **Radio API review ** 
 +       * Sample API of Denso Ten released in staging/​documents 
 +       * Goal is to refine the radio api with additional functions found in the review of above 
 +       * focus on generic calls over hw specifics 
 +       * Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM 
 +       * Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done 
 +     * 10/10 
 +       * Kusakabe posted the API to Gerrit https://​git.automotivelinux.org/​staging/​documents/​log/​?h=sandbox/​kusakabe/​radio-api 
 +       * Kusakabe to release additional APIs by the end of the month 
 +       * Scott needs to review. Need some additional Tier 1 or OEM reviewers.  
 +     * 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API.  
 +     * 11/21 - No update.  
 +     * 12/4 - No update. Further translations from Denso Ten may be available at the end of December.  
 +     * 12/19 - No update
  
-   ​* ​Review status of [[eg-speech|Speech EG]] kick off meetings.  ​BoF session planned for AMM next week.  +   ​* ​LTS   
-  +     * 9/26 (Berlin F2F) 
-   ​Review status [[eg-rhsa|RHSA EG]]Walt has an updated presentation from Goto-san and will share it with Goto-san's approval.  ​+ * AI: identify base services. What is in core-image-minimal that is available in all profiles 
 +  * lifecycle 
 +    * apps vs platform (which applications ​ 
 +     
 +  * API definition & documentation & Schema 
 +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/​browse/​SPEC-1903 
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md 
 +    * Follow-up on SAT 
 +  * API versions 
 +    * -> APPFW / Jose
  
 +  * '​core'​ LTS vs. IVI or Cluster LTS
 +    * depends on changes required e.g. by IC 
 +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.  ​
 +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects. ​
 +      * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​
 +      * Will add to SC agenda for next week. 
 +    * 11/21 - SC did not get to this topic, Will be addressed at December meeting. ​
 +    * 12/5 - Following up next week. 
  
-New +   * Toyota Code Drop 
 +     * 10/10  
 +       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.  
 +       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,​ 
 +     * 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.  
 +     * 11/21 -  
 +     * Notes from SC meeting  
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.  
 +     * Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents.  
 +     * 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas. ​  
 +       * Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended. 
 +       * Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).  
 +       * Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting. ​  
 +     * 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://​confluence.automotivelinux.org/​display/​TC/​Documents
  
-==== March 1, 2018 ==== 
-Attendees: //Upcoming Meeting// 
  
-   ​* ​Review [[agl-roadmap|2018 Roadmap]] +   ​* ​Navi EG met last week with Momiyama-san and they will present ​new architecture at the November ​SAT call.  
- +     ​* ​11/More discussion needed before Navi EG is ready to present ​the new architecture.  
-   * Kick-off review of development processes ​and tool usage +     ​* ​11/21 Navi EG presented an update last week in Yokohama. Need to get the document from Micware
-     * Issue - Backlog of merge requests, speed up merging in meta repos. Bottleneck of merges if Jan-Simon goes on vacation.  +
-     * Issue - More active reviews for source code repos +
-     * Broaden merge access to include more maintainers. Allow maintainers to be nominated by the community to be approved by SAT. +
-     * Each profile (IVI, telematics, core) would have set of maintainers  +
-     * Require reviews by changing merge criteria from +2 to an additive function (maybe +4) +
-     * Explore what other projects do.  +
-     * Jan-Simon - Will follow up with an email to the mail list asking for feedback and review ​the comments next SAT call. Then put together a more formal documentation of the process.  +
-     ​* ​2/15 Discussed J +
- +
-   * Release Plan for 2018 +
-     * Funky Flounder will switch to rocko. Focus on is on getting the BSP and the images correct for new features ​to be included in GG for CES and beyond.  +
-       * Beta versions of new features for CES will be permitted so we can start to try them out.  +
-     * Grumpy Guppy will stick with rocko. Focus for GG will be on feature development and maintaining a stable image. ​  +
-       * Need to manage new and complex feature more closely and ensure that the new features come in by September. +
-       * SAT will need to raise red flags earlier this year to get feature teams help when the features are critical for CES and falling behind.  +
- +
-   * SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform+
-     ​* ​9/14 See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment in Jira]] that summarizes the discussion and action items.  +
-     * 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884) +
-     * 10/12 - Action item 1 completed ​in SPEC 859. Need to create a subtask for AI 2. Probably defer action on it until after EE.  +
-     * 11/9 - Action item 2 needs to be started +
- +
- +
-    * Window Manager and Homescreen Plan for 2018 +
-      * Need additional SAT oversight and open up of the work+
    
-    ​V2C EG +   FOSDEM 
-      Received a proposal from Ashley for V2C EG +     ​FOSDEM stand accepted. Embedded devroom talk schedule is now available. ​ 
-      Panasonic may participate in the EG. Tanikawa will check internally.  +     ​Sign up for staffing ​the stand at FOSDEM at https://​doodle.com/​poll/​z5wzgdpnsv3xgbkp
 
-      9/28 - No update+     ​Deadline for AMM CFP is now Jan 17
  
-  +   ELISA updates 
-   SPEC-145 - Yocto Layer restructuring/​ headless device profile +     ​* ​ELISA and IC EG are recruiting AGL members ​to participate. The next F2F meeting ​for ELISA is in Brussel ​the Thursday and Friday before FOSDEMRegistration information can be found [[https://​elisa.tech/​announcement/​2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/​ | here]] ​ 
-     ​* ​Need to complete SPEC-219 - Requirements for Telematics Device Profile +     ​* ​ELISA groups.io page can be found [[https://lists.elisa.tech/​g/​devel | here ]] 
-     * Jan-Simon reviewed output from Vannes ​F2F meeting ​last week concerning device profiles and Yocto layer restructuring. We will have a follow up in two weeks during ​the SAT callAssuming we agree to a plan in San Jose or within a week or afterwards, we will implement the changes after the update to the YP pyro branch on master+     ​* ​New ELISA development process subgroup has formed. See their [[ https://lists.elisa.tech/g/​devel/​topic/​please_join/​61718502?​p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 | groups.io page]] for more information and to sign up
-     ​* ​12/7 - Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profileStill being reviewed+
-     ​* ​12/21 - Jan-Simon also started working on device profiles for FFShould get something pushed early in the new year +
-     * 2/7 - Merging rocko onto master this weekthen Jan-Simon will get the layer stuff onto master+
  
-   * Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  
-  
-   * SPEC-1118 / SPEC-1036 - What to do about obsolete repos? 
  
-   * Review status of [[eg-speech|Speech EG]] kick off meetings. ​ BoF session planned for AMM next week.  
    
-   * Review status [[eg-rhsa|RHSA EG]]. Walt has an updated presentation from Goto-san and will share it with Goto-san'​s approval.  ​ 
- 
- 
-New 
- 
- 
-==== February 15 2018 ==== 
-Attendees: Walt, Jan-Simon, Michael, Sebastien, Dominig, Stephane, Fulup (2 computers - 1 for audio and 1 for video). ​ 
- 
-   * Review [[agl-roadmap|2018 Roadmap]] 
- 
-   * Kick-off review of development processes and tool usage 
-     * Issue - Backlog of merge requests, speed up merging in meta repos. Bottleneck of merges if Jan-Simon goes on vacation. ​ 
-     * Issue - More active reviews for source code repos 
-     * Broaden merge access to include more maintainers. Allow maintainers to be nominated by the community to be approved by SAT. 
-     * Each profile (IVI, telematics, core) would have a set of maintainers ​ 
-     * Require reviews by changing merge criteria from +2 to an additive function (maybe +4) 
-     * Explore what other projects do.  
-     * Jan-Simon - Will follow up with an email to the mail list asking for feedback and review the comments next SAT call. Then put together a more formal documentation of the process. ​ 
-     * 2/15 - Discussed [[https://​lists.linuxfoundation.org/​pipermail/​automotive-discussions/​2018-February/​005648.html | Jan-Simon'​s email]]. ​ Will hold a separate meeting to discuss changes to process. ​ 
- 
-   * Release Plan for 2018 
-     * Funky Flounder will switch to rocko. Focus on is on getting the BSP and the images correct for new features to be included in GG for CES and beyond. ​ 
-       * Beta versions of new features for CES will be permitted so we can start to try them out.  
-     * Grumpy Guppy will stick with rocko. Focus for GG will be on feature development and maintaining a stable image.  ​ 
-       * Need to manage new and complex feature more closely and ensure that the new features come in by September. 
-       * SAT will need to raise red flags earlier this year to get feature teams help when the features are critical for CES and falling behind. ​ 
- 
-   * SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform. 
-     * 9/14 - See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment in Jira]] that summarizes the discussion and action items. ​ 
-     * 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884) 
-     * 10/12 - Action item 1 completed in SPEC 859. Need to create a subtask for AI 2. Probably defer action on it until after EE.  
-     * 11/9 - Action item 2 needs to be started 
- 
- 
-    * Window Manager and Homescreen Plan for 2018 
-      * Need additional SAT oversight and open up of the work.  
-  
-    * V2C EG 
-      * Received a proposal from Ashley for V2C EG 
-      * Panasonic may participate in the EG. Tanikawa will check internally. ​ 
-      * 9/28 - No update 
- 
-  
-   * SPEC-145 - Yocto Layer restructuring/​ headless device profile 
-     * Need to complete SPEC-219 - Requirements for Telematics Device Profile 
-     * Jan-Simon reviewed output from Vannes F2F meeting last week concerning device profiles and Yocto layer restructuring. We will have a follow up in two weeks during the SAT call. Assuming we agree to a plan in San Jose or within a week or afterwards, we will implement the changes after the update to the YP pyro branch on master. 
-     * 12/7 - Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profile. Still being reviewed. 
-     * 12/21 - Jan-Simon also started working on device profiles for FF. Should get something pushed early in the new year.  
-     * 2/7 - Merging rocko onto master this week, then Jan-Simon will get the layer stuff onto master. ​ 
- 
-   * Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  
-  
-   * SPEC-1118 / SPEC-1036 - What to do about obsolete repos? 
- 
 New Business: New Business:
  
-   Reviewed status of [[eg-speech|Speech EG]] kick off meetings.  ​BoF session planned for AMM next week.  +FOSSology/ License Review 
-   ​* ​Reviewed status [[eg-rhsa|RHSA EG]]Walt has an updated presentation from Goto-san and will share it with Goto-san'​s approval +   So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work.  ​Will be brought up to AB at their next meeting  
 +   ​* ​Open Chain reported that we have 320 different licenses How do we plan to collaborate with OpenChain?​ 
 +   * Fujitsu ​has volunteered to do some work sorting out the licensing which will get started in the new year
  
  
-==== February 7, 2018 ==== +   * Future meeting scheduling ​ 
-Attendees: Walt, Jan-Simon, Oshri, Michael, Christian, Kusakabe ​+     * Block scheduling of meetings to consolidate the schedule 
 +     * Japanese members attending the call are ok with this meetings at this time.  
 +     * Might be better one or two hours earlier than currently (Hosokawa)  
 +     * Will bring up at the SC meeting next week. Also post a question on the mail list (maybe create a poll)
  
-   * Review [[agl-roadmap|2018 Roadmap]]+Tanibata: Merge Graphics and UI with Instrument Cluster EG starting next year. Schedule for a more EU/Japan joint friendly time.  Would like feedback from Haraki-san on this proposal. Tanibata-san will meet with Haraki-san today to discuss. One idea is for meetings to be held at 5:00 pm JST (which is 9 am CET, 2 am Chicago time) 
 +Developer call. Can try to hold two sessions per week.  One at the current time on Tuesday and a second session at 6 pm Chicago time/ 9 am JST. 
  
-   * Kick-off review of development processes and tool usage 
-     * Issue - Backlog of merge requests, speed up merging in meta repos. Bottleneck of merges if Jan-Simon goes on vacation. ​ 
-     * Issue - More active reviews for source code repos 
-     * Broaden merge access to include more maintainers. Allow maintainers to be nominated by the community to be approved by SAT. 
-     * Each profile (IVI, telematics, core) would have a set of maintainers ​ 
-     * Require reviews by changing merge criteria from +2 to an additive function (maybe +4) 
-     * Explore what other projects do.  
-     * Jan-Simon - Will follow up with an email to the mail list asking for feedback and review the comments next SAT call. Then put together a more formal documentation of the process. ​ 
  
-   * Release Plan for 2018 
-     * Funky Flounder will switch to rocko. Focus on is on getting the BSP and the images correct for new features to be included in GG for CES and beyond. ​ 
-       * Beta versions of new features for CES will be permitted so we can start to try them out.  
-     * Grumpy Guppy will stick with rocko. Focus for GG will be on feature development and maintaining a stable image.  ​ 
-       * Need to manage new and complex feature more closely and ensure that the new features come in by September. 
-       * SAT will need to raise red flags earlier this year to get feature teams help when the features are critical for CES and falling behind. ​ 
  
-   * SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform. +==== December 5, 2019 ==== 
-     * 9/14 - See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment in Jira]] that summarizes the discussion and action items. ​ +Attendees: Walt, Jan-Simon, Michael, Edi, Stephane, Sebastian, George, Nick, Jasim Quazi, Jeremy Puhlman, Guy, Julian, Ohiwa, DrYamaguchi, Kurokawa, Kusakabe, Nishiguchi, Scott, Sekine
-     * 9/28 Assigned action item to Romain (SPEC-883 and SPEC-884) +
-     * 10/12 - Action item 1 completed in SPEC 859Need to create a subtask for AI 2. Probably defer action on it until after EE.  +
-     * 11/9 - Action item 2 needs to be started+
  
- +   * Window ​manager update from Daniel 
-    * Window ​Manager ​and Homescreen Plan for 2018 +   * Icefish RC2 decisions 
-      Need additional SAT oversight ​and open up of the work+     * Token logic. Edi tested ​and no regressions noted. WE will include the token logic in the RC2 
 +     ​Waiting on one last patch from George. Will take Jacobo'​s changes ​and one liner from Scott for low CAN.  
 +     * Waiting on the last changes from Daniel and Scott for window manager. Really need to get this into RC2 today. Guy will check with Daniel
    
-    ​V2C EG +   SPEC-2927 - Window Manager ​for WAM
-      * Received a proposal from Ashley ​for V2C EG +
-      * Panasonic may participate in the EG. Tanikawa will check internally.  +
-      * 9/28 - No update+
  
 +   * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}.
 +     * 8/29 Panasonic is reviewing ​
 +     * 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco. ​
 +     * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon. 
 +     * 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG. 
 +     * 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week. 
 +     * 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP.  Also will get a quote for creating the BSP from Konsulko.  ​
 +     * 12/4 - Block diagram [[ https://​wiki.automotivelinux.org/​_media/​eg-rhsa/​r-car_h3_reference_hardware_blockdiagram_20191126.pdf | uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday. ​
    
-   ​* ​SPEC-145 - Yocto Layer restructuring/​ headless device profile +   ​* ​Gap analysis ​Denso Ten will release documentation ​for radio and tuner functions by the end of September. ​ 
-     * Need to complete SPEC-219 - Requirements ​for Telematics Device Profile +     ​* ​9/12 document is 60% translated to englishKusakabe ​will present an update at the dev call next week 
-     ​* ​Jan-Simon reviewed output from Vannes F2F meeting last week concerning device profiles and Yocto layer restructuringWe will have a follow up in two weeks during ​the SAT call. Assuming we agree to a plan in San Jose or within a week or afterwards, we will implement ​the changes after the update ​to the YP pyro branch on master. +     * 9/26  
-     ​* ​12/Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profileStill being reviewed+       ​* ​ **Radio API review ** 
-     ​* ​12/21 Jan-Simon also started working ​on device profiles for FFShould get something pushed early in the new year.  +       * Sample API of Denso Ten released in staging/​documents 
-     ​* ​2/Merging rocko onto master this week, then Jan-Simon will get the layer stuff onto master+       * Goal is to refine the radio api with additional functions found in the review of above 
 +       * focus on generic calls over hw specifics 
 +       * Scott Murray ​will review ​the documents and make a proposal for extending ​the radio api for review in the connectivity call and during AMM 
 +       * Lateron a definition is needed how the interface ​to the various implementations (hw+driver) can be done 
 +     ​* ​10/10 
 +       * Kusakabe posted the API to Gerrit https://​git.automotivelinux.org/​staging/​documents/​log/?​h=sandbox/​kusakabe/​radio-api 
 +       * Kusakabe ​to release additional APIs by the end of the month 
 +       * Scott needs to reviewNeed some additional Tier 1 or OEM reviewers.  
 +     ​* ​11/Scott has been blocked ​on higher priority tasksWill bring this up to SC as an area for additional Tier One members to review ​the proposed API.  
 +     ​* ​11/21 No update.  
 +     * 12/4 No update. Further translations from Denso Ten may be available at the end of December
  
-   ​* ​Review [[https://​jira.automotivelinux.org/​issues/?​filter=11710 | Jira tickets for SAT]]  +   ​* ​LTS   
-  +     * 9/26 (Berlin F2F) 
-   ​SPEC-1118 SPEC-1036 - What to do about obsolete repos?+ * AI: identify base services. What is in core-image-minimal that is available in all profiles.  
 +  * lifecycle 
 +    * apps vs platform (which applications  
 +    *  
 +  * API definition & documentation & Schema 
 +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/​browse/SPEC-1903 
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md 
 +    * Follow-up on SAT 
 +  * API versions 
 +    * -> APPFW Jose
  
 +  * '​core'​ LTS vs. IVI or Cluster LTS
 +    * depends on changes required e.g. by IC 
 +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.  ​
 +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects. ​
 +      * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​
 +      * Will add to SC agenda for next week. 
 +    * 11/21 - SC did not get to this topic, Will be addressed at December meeting. ​
 +    * 12/5 - Following up next week. 
  
 +   * Toyota Code Drop
 +     * 10/10 
 +       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion. ​
 +       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
 +     * 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC. 
 +     * 11/21 - 
 +     * Notes from SC meeting ​
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure. ​
 +     * Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents. ​
 +     * 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.  ​
 +       * Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended.
 +       * Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash). ​
 +       * Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.  ​
  
  
-==== January 18, 2018 ==== +   Navi EG met last week with Momiyama-san and they will present a new architecture at the November SAT call.  
-Attendees: Walt, Jan-Simon, Dominig, Stephane, Kurokawa, Evgeny, Michael, Michele. Sebastien +     ​* ​11/More discussion ​needed before Navi EG is ready to present ​the new architecture.  
- +     ​* 11/21 Navi EG presented an update last week in Yokohama. ​Need to get the document ​from Micware
-   Review [[agl-roadmap|2018 Roadmap]] +
- +
-   * SPEC-859 - Include ​and Ship libraries that applications need that are not part of the core platform+
-     ​* ​9/14 See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment in Jira]] that summarizes the discussion ​and action items.  +
-     * 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884) +
-     * 10/12 - Action item 1 completed in SPEC 859. Need to create a subtask for AI 2. Probably defer action on it until after EE.  +
-     * 11/9 - Action item 2 needs to be started +
- +
- +
-    * Window Manager and Homescreen Rework +
-      * 9/14 - First working version of the window manager based on Toyota requirements will be available tomorrow. Mentor team is switching from European team to a team in Japan starting tomorrow.  +
-      * 9/28 - Mentor currently debugging the code. Should be ready tomorrow. Will push source code to staging and recipe to meta-agl-devel so IoT.bzh can start to rebuild as well.  +
-      * 10/12 - RC2 drop on 27 Oct. Need to get the code building for RC1. There are instabilities reported by Toyota/ Mentor that need to be addressed, plus new features. Will work to get more transparency into the development process.  +
-      * 11/Latest in RC2. Homescreen and Window Manager work, but the HS may not launch automatically. Tanikawa using QEMU and it sometimes launches and most times does not.  +
-      * 11/23 - Discuss XDG, Window Manager, Homescreen, Chromium topic. +
-        * Notes captured in https://​docs.google.com/​document/​d/​1WKt2W4PjT6yqArvdNmFTwz1rMhajZN6q82-gjZ937GE/​edit +
-      * 12/7 - Tanikawa working on XDG proxy for next week in Yokohama. ​ +
-      * 12/21 - Tanikawa has the XDG proxy running. Will implement last required feature for tomorrow. IoT.bzh will test.  +
-        * Other issues: If an application crashes, the entire system needs to be rebooted. Root cause known and in progress (Mitsunari-san).  +
-        * Boot time slow due to interaction with IC. Root cause may be known and is being worked on by Toyota. +
- +
-    * V2C EG +
-      * Received a proposal ​from Ashley for V2C EG +
-      * Panasonic may participate in the EGTanikawa will check internally.  +
-      * 9/28 - No update +
    
-   ​* ​SPEC-145 - Yocto Layer restructuring/​ headless device profile +   ​* ​FOSDEM 
-     ​* ​Need to complete SPEC-219 - Requirements ​for Telematics Device Profile +     ​* ​FOSDEM stand accepted. Deadline ​for embedded devroom talk submissions is Dec 6.  
-     ​* ​Jan-Simon reviewed output from Vannes F2F meeting last week concerning device profiles and Yocto layer restructuring. We will have follow ​up in two weeks during ​the SAT call. Assuming we agree to a plan in San Jose or within a week or afterwards, we will implement the changes after the update to the YP pyro branch on master. +     ​* ​Will put together ​sign up for staffing ​the stand at FOSDEM 
-     ​* ​12/7 - Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profile. Still being reviewed. +     ​* ​Deadline ​for AMM CFP is Dec 6
-     * 12/21 - Jan-Simon also started working on device profiles ​for FF. Should get something pushed early in the new year. +
  
-   ​* ​Roadmap for EE and 2018 +   ​* ​ELISA updates 
- +     ​ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel ​the Thursday and Friday before FOSDEM. Registration information can be found [[https://​elisa.tech/​announcement/​2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/ ​here]]  
-   Need to define EE and 2018 roadmap at the [[agl-distro:jul2017-f2f|face to face meeting next month]] +     ​ELISA groups.io page can be found [[https://​lists.elisa.tech/​g/​devel ​here ]] 
-   ​Toyota (Hoshina-san) uploaded new App FW/ Window manager document to wikiSee [[windowmanager|Window Manager]] +     ​New ELISA development process subgroup has formed. See their [[ https://lists.elisa.tech/g/devel/​topic/​please_join/​61718502?p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 ​groups.io page]] for more information and to sign up. 
- +
-   Review ​[[https://jira.automotivelinux.org/issues/?filter=11710 Jira tickets for SAT]] +
    
-   * SPEC-1118 / SPEC-1036 - What to do about obsolete repos?+New Business:
  
 +   * Future meeting scheduling ​
 +     * Block scheduling of meetings to consolidate the schedule
 +     * Japanese members attending the call are ok with this meetings at this time. 
 +     * Might be better one or two hours earlier than currently (Hosokawa) ​
 +     * Will bring up at the SC meeting next week. Also post a question on the mail list (maybe create a poll)
  
-==== January 4, 2018 ==== 
-Attendees: Walt, Jan-Simon, Frederic, Michele, Stephane 
  
 +==== November 21, 2019 ====
 +Attendees: Walt, Jan-Simon, Sebastien, Guy, Michael, Stephane, Nick, Hosokawa, Haraki, Kurokawa, Sekine, Ohiwa, Kusakabe, Nishiguchi, Dr. Yamaguchi, ​
  
-   * SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform. 
-     * 9/14 - See [[https://​jira.automotivelinux.org/​browse/​SPEC-859?​focusedCommentId=13946&​page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#​comment-13946 | comment in Jira]] that summarizes the discussion and action items. ​ 
-     * 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884) 
-     * 10/12 - Action item 1 completed in SPEC 859. Need to create a subtask for AI 2. Probably defer action on it until after EE.  
-     * 11/9 - Action item 2 needs to be started 
  
 +   * Daniel getting window manager into Gerrit for Karlsruhe next week. 
 +   * SPEC-2927 - Window Manager for WAM
  
-    * Window Manager and Homescreen Rework +   * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}. 
-      * 9/14 First working version of the window manager based on Toyota requirements will be available tomorrow. Mentor team is switching from European team to a team in Japan starting tomorrow.  +     * 8/29 Panasonic is reviewing ​ 
-      * 9/28 Mentor currently debugging the codeShould be ready tomorrow. Will push source code to staging and recipe to meta-agl-devel so IoT.bzh can start to rebuild as well.  +     ​* 9/12 Panasonic still in review. Sekine-san will check with Panasonic about EG review during ​the AMM in Monaco.  
-      * 10/12 RC2 drop on 27 Oct. Need to get the code building for RC1. There are instabilities reported by Toyota/ Mentor that need to be addressedplus new features. Will work to get more transparency into the development process.  +     ​* 9/26 Still in review at PanasonicSekine-san expects a reply soon.  
-      * 11/Latest in RC2Homescreen ​and Window Manager work, but the HS may not launch automatically. Tanikawa using QEMU and it sometimes launches and most times does not.  +     ​* 10/10 Sekine-san thinks Panasonic will release ​the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in NovemberWe should plan a F2F meeting at that time with Panasonic and RHSA EG.  
-      * 11/23 Discuss XDG, Window Manager, Homescreen, Chromium topic. +     ​* 11/SC to meet next week and make recommendation to ABWe will make sure that Panasonic ​and Mazda RHSA team members are invited to that portion of the SC meeting next week.  
-        * Notes captured ​in https://​docs.google.com/​document/​d/​1WKt2W4PjT6yqArvdNmFTwz1rMhajZN6q82-gjZ937GE/​edit +     ​* 11/21 SC meeting last week in YokohamaWaiting ​on block diagram from Panasonic which was promised ​for two weeks (next week)There is a meeting next week in Tokyo to discuss furtherThere is on-going discussion between Panasonic and Renesas about BSP Also will get quote for creating ​the BSP from Konsulko 
-      * 12/7 - Tanikawa working ​on XDG proxy for next week in Yokohama +
-      * 12/21 - Tanikawa has the XDG proxy running. Will implement last required feature for tomorrow. IoT.bzh will test.  +
-        * Other issues: If an application crashes, the entire system needs to be rebooted. Root cause known and in progress (Mitsunari-san).  +
-        * Boot time slow due to interaction with ICRoot cause may be known and is being worked ​on by Toyota. +
- +
-    * V2C EG +
-      * Received ​proposal from Ashley ​for V2C EG +
-      * Panasonic may participate in the EGTanikawa will check internally.  +
-      * 9/28 - No update +
    
-   ​* ​SPEC-145 - Yocto Layer restructuring/​ headless device profile +   ​* ​Gap analysis ​Denso Ten will release documentation ​for radio and tuner functions by the end of September. ​ 
-     * Need to complete SPEC-219 - Requirements ​for Telematics Device Profile +     ​* ​9/12 document is 60% translated to englishKusakabe ​will present an update at the dev call next week 
-     ​* ​Jan-Simon reviewed output from Vannes F2F meeting last week concerning device profiles and Yocto layer restructuringWe will have a follow up in two weeks during ​the SAT call. Assuming we agree to a plan in San Jose or within a week or afterwards, we will implement ​the changes after the update ​to the YP pyro branch on master. +     * 9/26  
-     ​* ​12/Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profileStill being reviewed+       ​* ​ **Radio API review ** 
-     ​* ​12/21 Jan-Simon also started working ​on device profiles for FFShould get something pushed early in the new year+       * Sample API of Denso Ten released in staging/​documents 
 +       * Goal is to refine the radio api with additional functions found in the review of above 
 +       * focus on generic calls over hw specifics 
 +       * Scott Murray ​will review ​the documents and make a proposal for extending ​the radio api for review in the connectivity call and during AMM 
 +       * Lateron a definition is needed how the interface ​to the various implementations (hw+driver) can be done 
 +     ​* ​10/10 
 +       * Kusakabe posted the API to Gerrit https://​git.automotivelinux.org/​staging/​documents/​log/?​h=sandbox/​kusakabe/​radio-api 
 +       * Kusakabe ​to release additional APIs by the end of the month 
 +       * Scott needs to reviewNeed some additional Tier 1 or OEM reviewers.  
 +     ​* ​11/Scott has been blocked ​on higher priority tasksWill bring this up to SC as an area for additional Tier One members to review ​the proposed API.  
 +     * 11/21 - No update
  
-   ​* ​Roadmap for EE and 2018+   ​* ​LTS   
 +     * 9/26 (Berlin F2F) 
 + * AI: identify base services. What is in core-image-minimal that is available in all profiles.  
 +  * lifecycle 
 +    * apps vs platform (which applications  
 +    *  
 +  * API definition & documentation & Schema 
 +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/​browse/​SPEC-1903 
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md 
 +    * Follow-up on SAT 
 +  * API versions 
 +    * -> APPFW / Jose
  
-   ​* ​Need to define EE and 2018 roadmap at the [[agl-distro:jul2017-f2f|face to face meeting next month]].  +  * '​core'​ LTS vs. IVI or Cluster LTS 
-   ​Toyota (Hoshina-san) uploaded new App FWWindow manager document ​to wikiSee [[windowmanager|Window Manager]]+    ​* ​depends on changes required e.g. by IC  
 +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed ​to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.   
 +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects.  
 +      * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing.  
 +      Will add to SC agenda for next week.  
 +    * 11/21 - SC did not get to this topic, Will be addressed at December meeting
  
-   ​* ​Review ​[[https://jira.automotivelinux.org/​issues/?​filter=11710 ​Jira tickets for SAT]]  +   ​* ​Toyota Code Drop 
-  +     * 10/10  
-   * SPEC-1118 / SPEC-1036 - What to do about obsolete repos?+       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.  
 +       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,​ 
 +     * 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.  
 +     * 11/21 -  
 +     * Notes from SC meeting  
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.  
 +     * Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see [[https://confluence.automotivelinux.org/​display/TC/​Documents ​Confluence]] for more on the documents. ​
  
  
-   ​* ​**Roadmap/ Workplan for 2018** +   ​* ​Navi EG met last week with Momiyama-san and they will present a new architecture ​at the November SAT call.  
-     * Do we move some APIs from meta-agl-demo into meta-agl or meta-agl-extra?​ +     ​* ​11/7 - More discussion needed before Navi EG is ready to present ​the new architecture.  
-     * Revisit the development process ​and gerrit usage to make improvements based on lessons learned and expanded developer base.  +     ​* ​11/21 Navi EG presented an update last week in YokohamaNeed to get the document from Micware
-     * Review the scope of PulseAudio to minimize its usage to what is absolutely necessary. (SPEC-1220) +
-     * Review Reference Hardware System Architecture document and consider its implications for the software ​architecture.  +
-     * Move RHSA to doc site.  +
-     * Document ​the documentation workflow and documentation versioning +
-     * Propose a replacement for ask.automotivelinux.org. Probably stack overflow +
-     ​* ​Add additional simplified SOTA mechanism (A/B via rauc) +
-     * Add video support to mediaplayer binding +
- +
-   * **From App FW and Security ​EG** +
- +
-     * HTML5 apps/ home screen +
-       * Chromium  +
- +
-     * Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers ​to sign applications,​ load them. +
-     * Define ​the list of privileges we are going to enforce in the security model  ​ +
-     ​* ​Running apps not as rootmulti-user +
-     * Distinction between platform services (e.g., nfc, telephone) and user services that run inside a user context (e.g., media player and lightmedia scanner)  +
-     * Changes necessary at binder level for V2C +
-     * Application signing and installation mechanism +
-     * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system. +
-     * Improved Developer workflow for debugging apps including  +
-       * Round trip download/​debug/​fix/​download apps.  +
-       * Supervision daemon for apps and services for development mode. Allows a developers ​to have a central place monitor IPC in real time. Builds on the current monitor service that is available for binders. Extends its availability to startup and allows more general monitoring without requiring detailed knowledge of what is available in a specific binder. Current version only allows a single binder to be monitored. This would allow monitoring across binders.  +
- +
-     * Task manager app to allow developers to see what tasks/​process are running in an app. Allow for killing apps.   +
-       * Review AGL spec 1.0 to determine what requirements are there for managing home screen and apps. Something like iphone where a double-tap on home button allows swiping up of apps to kill them+
  
-     * Introduce resource widgets to share content/ resources across multiple apps.  +New Business: 
- +  
-   ​* ​**From Graphics EG** +   ​* ​FOSDEM stand acceptedDeadline ​for embedded devroom talk submissions is Dec 6
-     * Finish Window Manager and Homescreen work +
-       * Pop-up support +
-       * Focus management for out of focus apps +
-       * Improved secondary display suport  +
-     * Waltham protocol for internode display +
-     * Investigate replacement for Qt (e.g.. GTK+) +
-     * High Level audio API +
-     * AGL Advanced Audio Agent (AAAA) +
-     * Speech and Text to Speech Services +
- +
- +
-   * **From Connectivity EG** +
-     * Vehicle Signaling  +
-     * Bluetooth improvements +
-       * Bluetooth binding rewrite ​for stabililty and robustness  +
-       * PBAP/​Contacts binding +
-       * BT PAN binding +
-       * BLE binding  +
-     * WiFi improvements +
-       * WiFi binding rewrite for stability and robustness +
-       * AP mode +
-       * Additional Wifi dongle support +
-     * WWAN binding +
-       * Support current QMI  modems via either modemmanager or ofono +
-     * Telephony app improvements +
-       * Show missed call, last outgoing, last incoming call log info +
-       * Contacts integrated into dialing, caller ID, and call log info +
-     * NFC binder and NFC for user identification +
-     * Hardwired connection to telephone for Telematics use cases +
-     * Network management binding +
-       * General network connectivity above connman to manage connectivity including IPv4/v6 configuration,​ bridging, tethering, network QOS and switching +
-       * User profiles to allow authorized users to configure interfacing +
-       * Support multiple low-level interface binding backends including Ethernet, WiFi, BT PAN, and WWAN +
-     * For 2018 - evaluate usage of connman versus network manager/​modem manager for long-term especially for 4G and complex use cases. +
-     * Port Comtech'​s OSS nav app to demo HMI   +
- +
-   * **From V2X EG** +
-     * Kickoff EG +
- +
-   * **From Virtualization EG** +
-     * AGL virtualization architecture definition +
-     * EG Virtualization white paper +
-     * Extension of the virtualization-related yocto layers to support the defined architecture +
- +
-   * **From CIAT EG** +
-     * Lab in a box +
-       * Board management +
-       * Board on developer'​s desk +
-     * Improved publishing of test results +
-     * Additional tests +
-       * Applications +
-       * Platform +
-       * BSPs +
-     * Fuego integration +
- +
- +
-------+
  
-==== Meeting Archive (pre-2018) ==== 
-Minutes for meetings prior to 2014 - 2017 have been moved [[agl-sat-meetings:​archived-meetings |here]]. 
agl-sat-meetings.1573140923.txt.gz · Last modified: 2019/11/07 15:35 (external edit)