User Tools

Site Tools


agl-sat-meetings

AGL System Architecture Team (SAT) Meetings

Meetings of the System Architecture Team are held every other Thursday at 13:00 UTC. The upcoming schedule can be found below.

Conference Information:

AGL-SAT Biweekly Meeting

Please join my meeting from your computer, tablet or smartphone. https://global.gotomeeting.com/join/796425741

You can also dial in using your phone. United States (Toll Free): 1 877 309 2070 United States: +1 (312) 757-3119

Access Code: 796-425-741

More phone numbers:

Australia: +61 2 8355 1034 Austria: +43 7 2088 0716
Belgium: +32 28 93 7002 Canada (Toll Free): 1 877 777 3281
Canada: +1 (647) 497-9372 Denmark: +45 69 91 84 58
Finland: +358 923 17 0556 France: +33 170 950 590
Germany: +49 692 5736 7206 India (Toll Free): 18002669775
Ireland: +353 19 030 053 Italy: +39 0 699 26 68 65
Japan (Toll Free): 0 120 242 200 Korea, Republic of (Toll Free): 0806180880
Netherlands: +31 208 080 759 New Zealand: +64 9 974 9579
Norway: +47 21 04 30 59 Spain: +34 931 76 1534
Sweden: +46 852 500 691 Switzerland: +41 435 0026 89
United Kingdom: +44 20 3713 5011

Joining from a video-conferencing room or system? Dial: 67.217.95.2##796425741 Cisco devices: 796425741@67.217.95.2

First GoToMeeting? Let's do a quick system check: https://link.gotomeeting.com/system-check |


December 20, 2018

Attendees: Upcoming Meeting

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 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 here.
    • Dominig brought up non-technical issues that were 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 time. Jose 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.
  • API documentation proposals and update on documentation effort
    • 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 resolved Jira issues
    • Reviewed SPEC-1885 - Moving WAM into AGL
    • Review SPEC-1920 - Refactor libhomescreen and libwindowmanager
  • API documentation proposals and update on documentation effort
    • 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
    • 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

Attendees: Walt, 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 address. Also 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 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.
  • Web app framework - Updates from LG/Igalia?
    • 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/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.
    • 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-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
    • 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-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.

September 27, 2018

Attendees: Walt, Jan-Simon, Kusakabe, Stephane, Sebastien, Fulup, Kurokawa

  • 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.
  • 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 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.
  • Web app framework - Updates from LG/Igalia?
    • 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/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.
    • 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-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
    • 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.
  • 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 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.
  • Web app framework - Updates from LG/Igalia?
    • 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/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.
    • 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-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

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.

August 30, 2018

Attendees: Walt, Jan-Simon, Kurokawa, Kusakabe-san, Fulup, George, Sebastien, Yamaguchi, Stephane, Michael, Guy, Mitsunari, Momiyama

  • Discussed Issues with FF RC4
  • 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
  • Security Blueprint - SPEC-1454
    • Security Expert Group discussed dropping the old blueprint from the doc site.
  • Web app framework - Updates from LG/Igalia?
    • 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/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.
  • 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.

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 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)
  • 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
  • Security Blueprint - SPEC-1454
    • Security Expert Group discussed dropping the old blueprint from the doc site.
  • Web app framework - Updates from LG/Igalia?
    • 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/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.
  • 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.

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 default, and fragments add configuration bits in separate package
      • binary image can install lateron

July 19, 2018

Attendees: Walt, Jan-Simon, Stephane, Kurokawa, Mitsunari, Michael, Sebastien, Tanikawa, Kusakabe

  • 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
  • Reviewed and edited 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.
  • Web app framework - Updates from LG/Igalia?
    • 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.
    • 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.
  • 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

July 5, 2018

Attendees: Walt, Jan-Simon, Michael, Daniel, George, Kurokawa, Guy, Tanikawa, Michele, Momiyama, Yamaguchi, Stephane, Sebastien, Tiejun

  • Reviewed and edited 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.
  • Web app framework - Updates from LG/Igalia?
    • 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.
    • 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.
  • 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

June 21, 2018

June 7, 2018

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 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.
    • 5/24 - Gatekeepers set up and wiki page created: 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.
  • 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
    • 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.
    • 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.
    • 6/7/ - Email sent to Ashley and Lasse at ForgeRock. Waiting on reply.
  • 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.
    • 4/26 - Sub-tasks continuing
    • 5/24 - Part 3 in gerrit. Issues being looked at.
    • 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!
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?
    • 4/26 - Tanikawa looking at resolving for FF.
    • 5/24 - Nothing to report
    • 6/7 - Nothing to report
  • Web app framework - Updates from LG/Igalia?
    • 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.
    • 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.

New:

  • Dynamic library link usage. See SPEC-1454. Added a comment to it. Assigned to Jose.

May 24, 2018

Attendees: Walt, Jan-Simon, Michael, Sebastien, Kurokawa, Stephane, Kusakabe, Dominig

  • 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 as reviewed in Karlsruhe is being implemented.
    • 5/24 - Gatekeepers set up and wiki page created: 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 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.
    • 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
    • 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.
    • 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.
  • 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.
    • 4/26 - Sub-tasks continuing
    • 5/24 - Part 3 in gerrit. Issues being looked at.
  • 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 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 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 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.
  • 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.
    • 4/26 - Sub-tasks continuing
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?
    • 4/26 - Tanikawa looking at resolving for FF.

New

  • 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:

April 26, 2018

Attendees: Walt, Jan-Simon, Kurokawa, Kusakabe, Tanikawa, Dominig, Steve L., Sebastien

Review outcome from 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 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 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.
  • 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.
    • 4/26 - Sub-tasks continuing
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?
    • 4/26 - Tanikawa looking at resolving for FF.
  • Review status of Speech EG kick off meetings. BoF session planned for AMM next week.
  • Review status RHSA EG. Walt has an updated presentation from Goto-san and will share it with Goto-san's approval.
    • Checking on updates for Karlsruhe F2F and whether Goto-san will attend in person.

New

  • 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.

April 12, 2018

See notes from Karlsruhe F2F meeting.

March 29 2018

Attendees: Walt, Tanikawa, Kurokawa, Stephane, Fulup, Sebastien

  • 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
    • 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 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
    • 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.
  • 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.
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?
  • Review status of Speech EG kick off meetings. BoF session planned for AMM next week.
  • Review status RHSA EG. Walt has an updated presentation from Goto-san and will share it with Goto-san's approval.
    • Checking on updates for Karlsruhe F2F and whether Goto-san will attend in person.

New

March 15, 2018

Attendees: Walt, Michael, Kurokawa, Stephane, Sebastien, Fulup

  • 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
    • 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 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.
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?
  • Review status of Speech EG kick off meetings. BoF session planned for AMM next week.
  • Review status RHSA EG. Walt has an updated presentation from Goto-san and will share it with Goto-san's approval.

New

March 1, 2018

Attendees: Upcoming 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.
    • 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 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.
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?
  • Review status of Speech EG kick off meetings. BoF session planned for AMM next week.
  • Review status 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).

  • 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 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 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.
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?

New Business:

  • Reviewed status of Speech EG kick off meetings. BoF session planned for AMM next week.
  • Reviewed status RHSA EG. Walt has an updated presentation from Goto-san and will share it with Goto-san's approval.

February 7, 2018

Attendees: Walt, Jan-Simon, Oshri, Michael, Christian, Kusakabe

  • 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.
    • 9/14 - See 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.
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?

January 18, 2018

Attendees: Walt, Jan-Simon, Dominig, Stephane, Kurokawa, Evgeny, Michael, Michele. Sebastien

  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
    • 9/14 - See 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/9 - 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.
    • 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 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.
  • Roadmap for EE and 2018
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?

January 4, 2018

Attendees: Walt, Jan-Simon, Frederic, Michele, Stephane

  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
    • 9/14 - See 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/9 - 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.
    • 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 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.
  • Roadmap for EE and 2018
  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?
  • Roadmap/ Workplan for 2018
    • Do we move some APIs from meta-agl-demo into meta-agl or meta-agl-extra?
    • Revisit the development process and gerrit usage to make improvements based on lessons learned and expanded developer base.
    • 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 root/ multi-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.
  • From Graphics EG
    • 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

December 21, 2017

Attendees: Walt, Jan-Simon, Stephane, Michael, Tanikawa, Fulup, Dominig, Loic,

  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
    • 9/14 - See 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/9 - 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.
    • 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 EG. Tanikawa will check internally.
    • 9/28 - No update
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
    • 8/3 - Need Jira ticket created.
    • 9/12 - No ticket created yet.
    • 9/24 - No ticket
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
    • Update 8/3 - No update. Plan is to add this to master after update to pyro is complete.
    • Update 9/14 - subtasks created for EE work to split out using binaries after EE
    • Update 9/28 - subtask SPEC-876, SPEC-921 in progress. SDK needs to be built for the three machine types (ARM 64, ARM 32, Intel) and the app developer will choose the SDK version to download.
    • 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.
  • Roadmap for EE and 2018
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
    • 8/2 - Tanikawa reviewed and thinks it is ok as is, but we probably need a different view of which services belong to the application framework and which ones are not available to the applications. Probably need different views of the architecture for audio, video, window system, and other major subsystems to indicate the which parts are included as application framework bindings and which areas systemd covers (OS layer).
    • 9/24 - No work yet. Want to revisit before AMM, ELCE. Set up meeting for next Wednesday. Start a new diagram on draw.io.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?
    • 8/2 - Need Jira ticket.
    • 9/14 - no ticket
    • 9/28 - Dominig to create ticket.
  • SPEC-391 - Document Map Creation Process. Review latest comment. What should SAT recommend?

New:

  • SPEC-1118 / SPEC-1036 - What to do about obsolete repos?
  • After New Year
    • Do we move some APIs from meta-agl-demo into meta-agl or meta-agl-extra?
    • Revisit the development process and gerrit usage to make improvements based on lessons learned and expanded developer base.
    • 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

December 7, 2017

Attendees: Walt, Michael, Matt

  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
    • 9/14 - See 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/9 - 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.
    • 12/7 - Tanikawa working on XDG proxy for next week in Yokohama.
  • V2C EG
    • Received a proposal from Ashley for V2C EG
    • Panasonic may participate in the EG. Tanikawa will check internally.
    • 9/28 - No update
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
    • 8/3 - Need Jira ticket created.
    • 9/12 - No ticket created yet.
    • 9/24 - No ticket
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
    • Update 8/3 - No update. Plan is to add this to master after update to pyro is complete.
    • Update 9/14 - subtasks created for EE work to split out using binaries after EE
    • Update 9/28 - subtask SPEC-876, SPEC-921 in progress. SDK needs to be built for the three machine types (ARM 64, ARM 32, Intel) and the app developer will choose the SDK version to download.
    • 12/7 - Alex Bidnichenko (EPAM) submitted 12303 to create a telematics profile. Still being reviewed.
  • Roadmap for EE and 2018
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
    • 8/2 - Tanikawa reviewed and thinks it is ok as is, but we probably need a different view of which services belong to the application framework and which ones are not available to the applications. Probably need different views of the architecture for audio, video, window system, and other major subsystems to indicate the which parts are included as application framework bindings and which areas systemd covers (OS layer).
    • 9/24 - No work yet. Want to revisit before AMM, ELCE. Set up meeting for next Wednesday. Start a new diagram on draw.io.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?
    • 8/2 - Need Jira ticket.
    • 9/14 - no ticket
    • 9/28 - Dominig to create ticket.
  • SPEC-391 - Document Map Creation Process. Review latest comment. What should SAT recommend?

New:

November 23, 2017

Attendees: Upcoming Meeting

  • Only topic discussed.
  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
    • 9/14 - See 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/9 - 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.
  • V2C EG
    • Received a proposal from Ashley for V2C EG
    • Panasonic may participate in the EG. Tanikawa will check internally.
    • 9/28 - No update
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
    • 8/3 - Need Jira ticket created.
    • 9/12 - No ticket created yet.
    • 9/24 - No ticket
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
    • Update 8/3 - No update. Plan is to add this to master after update to pyro is complete.
    • Update 9/14 - subtasks created for EE work to split out using binaries after EE
    • Update 9/28 - subtask SPEC-876, SPEC-921 in progress. SDK needs to be built for the three machine types (ARM 64, ARM 32, Intel) and the app developer will choose the SDK version to download.
  • Roadmap for EE and 2018
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
    • Update 9/14 - Need to get an update on this. Would like to resolve for EE.
    • Update 9/28 - Jose is looking at moving to meta-security. Fulup will be meeting with Samsung at the GENIVI AMM to talk about the future of Tizen security. Future of SMACK, is Casey still working on it?
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
    • 8/2 - Tanikawa reviewed and thinks it is ok as is, but we probably need a different view of which services belong to the application framework and which ones are not available to the applications. Probably need different views of the architecture for audio, video, window system, and other major subsystems to indicate the which parts are included as application framework bindings and which areas systemd covers (OS layer).
    • 9/24 - No work yet. Want to revisit before AMM, ELCE. Set up meeting for next Wednesday. Start a new diagram on draw.io.
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
    • 8/2 - Rewriting App builder CI jobs to run for dab and master. Will add the apps to a directory on the download server after that is complete.
    • 9/14 - Apps are currently being built. Need to differentiate between master and Dab then we can make them available publicly on the download server.
    • 9/28 - Apps now have a dab branch. Jenkins jobs now build both master and dab branch for apps. Apps now placed on download server after a change is merged (agl/apps/…)
    • 10/12 - Results are now being synched to https://download.automotivelinux.org/AGL/apps/ Not seeing apps for both master and dab, seems to be one or the other. Apps are populated into the directory when they are patched/built. Jan-Simon to check to see if dab and master are overwriting each other.
    • 11/9 - No update
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?
    • 8/2 - Need Jira ticket.
    • 9/14 - no ticket
    • 9/28 - Dominig to create ticket.
  • SPEC-391 - Document Map Creation Process. Review latest comment. What should SAT recommend?

New:


November 9, 2017

Attendees: Walt, Jan-Simon, Michael, Tanikawa

  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
    • 9/14 - See 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/9 - 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.
  • V2C EG
    • Received a proposal from Ashley for V2C EG
    • Panasonic may participate in the EG. Tanikawa will check internally.
    • 9/28 - No update
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
    • 8/3 - Need Jira ticket created.
    • 9/12 - No ticket created yet.
    • 9/24 - No ticket
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
    • Update 8/3 - No update. Plan is to add this to master after update to pyro is complete.
    • Update 9/14 - subtasks created for EE work to split out using binaries after EE
    • Update 9/28 - subtask SPEC-876, SPEC-921 in progress. SDK needs to be built for the three machine types (ARM 64, ARM 32, Intel) and the app developer will choose the SDK version to download.
  • Roadmap for EE and 2018
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
    • Update 9/14 - Need to get an update on this. Would like to resolve for EE.
    • Update 9/28 - Jose is looking at moving to meta-security. Fulup will be meeting with Samsung at the GENIVI AMM to talk about the future of Tizen security. Future of SMACK, is Casey still working on it?
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
    • 8/2 - Tanikawa reviewed and thinks it is ok as is, but we probably need a different view of which services belong to the application framework and which ones are not available to the applications. Probably need different views of the architecture for audio, video, window system, and other major subsystems to indicate the which parts are included as application framework bindings and which areas systemd covers (OS layer).
    • 9/24 - No work yet. Want to revisit before AMM, ELCE. Set up meeting for next Wednesday. Start a new diagram on draw.io.
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
    • 8/2 - Rewriting App builder CI jobs to run for dab and master. Will add the apps to a directory on the download server after that is complete.
    • 9/14 - Apps are currently being built. Need to differentiate between master and Dab then we can make them available publicly on the download server.
    • 9/28 - Apps now have a dab branch. Jenkins jobs now build both master and dab branch for apps. Apps now placed on download server after a change is merged (agl/apps/…)
    • 10/12 - Results are now being synched to https://download.automotivelinux.org/AGL/apps/ Not seeing apps for both master and dab, seems to be one or the other. Apps are populated into the directory when they are patched/built. Jan-Simon to check to see if dab and master are overwriting each other.
    • 11/9 - No update
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?
    • 8/2 - Need Jira ticket.
    • 9/14 - no ticket
    • 9/28 - Dominig to create ticket.
  • SPEC-391 - Document Map Creation Process. Review latest comment. What should SAT recommend?

New:

  • Walt will get the new color scheme to Tanikawa-san.

—–

November 3, 2017

Attendees: Walt, Jan-Simon, Fulup, Stephane, Matt

  • Had difficulties starting the call with Gotomeeting and sent out a cancelation after ten minutes. Got the call started and there were only the four of us on the call.
    • Used the opportunity to discuss the current status of the audio for EE RC2
    • Fulup got Mentor/Toyota to agree to remove their sound-manager in favor of the work being done by Konsulko to create a proper glue layer to the high level audio API.
    • Konsulko code is work in progress
    • Will not include sound-manager in RC2
    • Possible RC3 at the end of next week prior to Yokohama F2F if we get the audio issue sorted out.
    • Reviewed the IoT.bzh repo requests in Jira to sort out what is a binder and where things should go.
  • End of call for 11/3
  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
    • 9/14 - See 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.
  • 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.
  • V2C EG
    • Received a proposal from Ashley for V2C EG
    • Panasonic may participate in the EG. Tanikawa will check internally.
    • 9/28 - No update
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
    • 8/3 - Need Jira ticket created.
    • 9/12 - No ticket created yet.
    • 9/24 - No ticket
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
    • Update 8/3 - No update. Plan is to add this to master after update to pyro is complete.
    • Update 9/14 - subtasks created for EE work to split out using binaries after EE
    • Update 9/28 - subtask SPEC-876, SPEC-921 in progress. SDK needs to be built for the three machine types (ARM 64, ARM 32, Intel) and the app developer will choose the SDK version to download.
  • Roadmap for EE and 2018
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
    • Update 9/14 - Need to get an update on this. Would like to resolve for EE.
    • Update 9/28 - Jose is looking at moving to meta-security. Fulup will be meeting with Samsung at the GENIVI AMM to talk about the future of Tizen security. Future of SMACK, is Casey still working on it?
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
    • 8/2 - Tanikawa reviewed and thinks it is ok as is, but we probably need a different view of which services belong to the application framework and which ones are not available to the applications. Probably need different views of the architecture for audio, video, window system, and other major subsystems to indicate the which parts are included as application framework bindings and which areas systemd covers (OS layer).
    • 9/24 - No work yet. Want to revisit before AMM, ELCE. Set up meeting for next Wednesday. Start a new diagram on draw.io.
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
    • 8/2 - Rewriting App builder CI jobs to run for dab and master. Will add the apps to a directory on the download server after that is complete.
    • 9/14 - Apps are currently being built. Need to differentiate between master and Dab then we can make them available publicly on the download server.
    • 9/28 - Apps now have a dab branch. Jenkins jobs now build both master and dab branch for apps. Apps now placed on download server after a change is merged (agl/apps/…)
    • 10/12 - Results are now being synched to https://download.automotivelinux.org/AGL/apps/ Not seeing apps for both master and dab, seems to be one or the other. Apps are populated into the directory when they are patched/built. Jan-Simon to check to see if dab and master are overwriting each other.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?
    • 8/2 - Need Jira ticket.
    • 9/14 - no ticket
    • 9/28 - Dominig to create ticket.

New Business: * SPEC-391 - Document Map Creation Process. Review latest comment. What should SAT recommend?

October 12, 2017

Attendees: Walt, Jan-Simon, Kojima, Michael, Stephane, Kurokawa, Eugeny

  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
    • 9/14 - See 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.
  • 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.
  • V2C EG
    • Received a proposal from Ashley for V2C EG
    • Panasonic may participate in the EG. Tanikawa will check internally.
    • 9/28 - No update
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
    • 8/3 - Need Jira ticket created.
    • 9/12 - No ticket created yet.
    • 9/24 - No ticket
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
    • Update 8/3 - No update. Plan is to add this to master after update to pyro is complete.
    • Update 9/14 - subtasks created for EE work to split out using binaries after EE
    • Update 9/28 - subtask SPEC-876, SPEC-921 in progress. SDK needs to be built for the three machine types (ARM 64, ARM 32, Intel) and the app developer will choose the SDK version to download.
  • Roadmap for EE and 2018
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
    • Update 9/14 - Need to get an update on this. Would like to resolve for EE.
    • Update 9/28 - Jose is looking at moving to meta-security. Fulup will be meeting with Samsung at the GENIVI AMM to talk about the future of Tizen security. Future of SMACK, is Casey still working on it?
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
    • 8/2 - Tanikawa reviewed and thinks it is ok as is, but we probably need a different view of which services belong to the application framework and which ones are not available to the applications. Probably need different views of the architecture for audio, video, window system, and other major subsystems to indicate the which parts are included as application framework bindings and which areas systemd covers (OS layer).
    • 9/24 - No work yet. Want to revisit before AMM, ELCE. Set up meeting for next Wednesday. Start a new diagram on draw.io.
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
    • 8/2 - Rewriting App builder CI jobs to run for dab and master. Will add the apps to a directory on the download server after that is complete.
    • 9/14 - Apps are currently being built. Need to differentiate between master and Dab then we can make them available publicly on the download server.
    • 9/28 - Apps now have a dab branch. Jenkins jobs now build both master and dab branch for apps. Apps now placed on download server after a change is merged (agl/apps/…)
    • 10/12 - Results are now being synched to https://download.automotivelinux.org/AGL/apps/ Not seeing apps for both master and dab, seems to be one or the other. Apps are populated into the directory when they are patched/built. Jan-Simon to check to see if dab and master are overwriting each other.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?
    • 8/2 - Need Jira ticket.
    • 9/14 - no ticket
    • 9/28 - Dominig to create ticket.

New Business: * ELCE and FOSDEM


September 28, 2017

Attendees: Walt, Jan-Simon, Stephane, Christian, Dominig, Kojima, Fulup, Frederic,

Agenda:

  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
    • 9/14 - See comment in Jira that summarizes the discussion and action items.
    • 9/28 - Assigned action item to Romain (SPEC-883 and SPEC-884)
  • 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.
  • V2C EG
    • Received a proposal from Ashley for V2C EG
    • Panasonic may participate in the EG. Tanikawa will check internally.
    • 9/28 - No update
  • Mechanism for keeping track of backports - Email topic started by Martin Kelly.
    • Do all backports go into one repo or one one per architecture
    • Documentation for keeping tracking of backports
    • Move the discussion to a Jira ticket.
    • Incorporate into the layer re-organization
    • 8/3 - SPEC-802 created
    • 9/14 - SPEC-802 discussion resulted in SPEC-879 to gather backports and implement as part of SPEC-145
    • 9/28 - Plan in motion. Can close for SAT
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
    • 8/3 - Need Jira ticket created.
    • 9/12 - No ticket created yet.
    • 9/24 - No ticket
  • Graphics EG - Weston version for EE upgrades to 2.0 which is part of pyro (YP 2.3).
    • Renesas Gen 3 board
      • Officially supports Yocto 2.1 (korgoth).
      • IoT.bzh ported the the BSP to morty (Weston 1.11) for DD.
      • Expect that the next official Renesas BSP will be for morty.
      • IoT.bzh expects to take that version and provide pyro (Weston 2.0) support for Gen 3.
    • Porter probably will not be supported for EE.
    • Update 9/14
      • Pyro branched merged to master
      • Intel ok.
      • TI video output needs to be checked
      • RPI video output needs to be checked
      • Renesas Gen 3 in progress
      • Renesas Gen 2 failing gstreamer.
    • Update 9/24
      • Everything is good except Porter. Waiting for response from Renesas on their plan for the Porter. Can close this for SAT.
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
    • Update 8/3 - No update. Plan is to add this to master after update to pyro is complete.
    • Update 9/14 - subtasks created for EE work to split out using binaries after EE
    • Update 9/28 - subtask SPEC-876, SPEC-921 in progress. SDK needs to be built for the three machine types (ARM 64, ARM 32, Intel) and the app developer will choose the SDK version to download.
  • Roadmap for EE and 2018
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
    • Update 9/14 - Need to get an update on this. Would like to resolve for EE.
    • Update 9/28 - Jose is looking at moving to meta-security. Fulup will be meeting with Samsung at the GENIVI AMM to talk about the future of Tizen security. Future of SMACK, is Casey still working on it?
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
    • 8/2 - Tanikawa reviewed and thinks it is ok as is, but we probably need a different view of which services belong to the application framework and which ones are not available to the applications. Probably need different views of the architecture for audio, video, window system, and other major subsystems to indicate the which parts are included as application framework bindings and which areas systemd covers (OS layer).
    • 9/24 - No work yet. Want to revisit before AMM, ELCE. Set up meeting for next Wednesday. Start a new diagram on draw.io.
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
    • 8/2 - Rewriting App builder CI jobs to run for dab and master. Will add the apps to a directory on the download server after that is complete.
    • 9/14 - Apps are currently being built. Need to differentiate between master and Dab then we can make them available publicly on the download server.
    • 9/28 - Apps now have a dab branch. Jenkins jobs now build both master and dab branch for apps. Apps now placed on download server after a change is merged (agl/apps/…)
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?
    • 8/2 - Need Jira ticket.
    • 9/14 - no ticket
    • 9/28 - Dominig to create ticket.

New Business: * ELCE and FOSDEM

September 14, 2017

Attendees: Walt, Jan-Simon, Stephane, Aurelian, Kurokawa

Agenda:

  • SPEC-859 - Include and Ship libraries that applications need that are not part of the core platform.
  • 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.
  • V2C EG
    • Received a proposal from Ashley for V2C EG
    • Panasonic may participate in the EG. Tanikawa will check internally.
  • Mechanism for keeping track of backports - Email topic started by Martin Kelly.
    • Do all backports go into one repo or one one per architecture
    • Documentation for keeping tracking of backports
    • Move the discussion to a Jira ticket.
    • Incorporate into the layer re-organization
    • 8/3 - SPEC-802 created
    • 9/14 - SPEC-802 discussion resulted in SPEC-879 to gather backports and implement as part of SPEC-145
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
    • 8/3 - Need Jira ticket created.
    • 9/12 - No ticket created yet.
  • Graphics EG - Weston version for EE upgrades to 2.0 which is part of pyro (YP 2.3).
    • Renesas Gen 3 board
      • Officially supports Yocto 2.1 (korgoth).
      • IoT.bzh ported the the BSP to morty (Weston 1.11) for DD.
      • Expect that the next official Renesas BSP will be for morty.
      • IoT.bzh expects to take that version and provide pyro (Weston 2.0) support for Gen 3.
    • Porter probably will not be supported for EE.
    • Update 9/14
      • Pyro branched merged to master
      • Intel ok.
      • TI video output needs to be checked
      • RPI video output needs to be checked
      • Renesas Gen 3 in progress
      • Renesas Gen 2 failing gstreamer.
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
    • Update 8/3 - No update. Plan is to add this to master after update to pyro is complete.
    • Update 9/14 - subtasks created for EE work to split out using binaries after EE
  • Roadmap for EE and 2018
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
    • Update 9/14 - Need to get an update on this. Would like to resolve for EE.
  • SPEC-538 - Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 6/8 - Ronan posted the App FW bindings for SUSE,Fedora, and Ubuntu (see Jira comment for link). Need to request a high level public project rather than hosting it in Ronan's home.
    • Update 9/14 - Issue closed.
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
    • 8/2 - Tanikawa reviewed and thinks it is ok as is, but we probably need a different view of which services belong to the application framework and which ones are not available to the applications. Probably need different views of the architecture for audio, video, window system, and other major subsystems to indicate the which parts are included as application framework bindings and which areas systemd covers (OS layer).
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
    • 8/2 - Rewriting App builder CI jobs to run for dab and master. Will add the apps to a directory on the download server after that is complete.
    • 9/14 - Apps are currently being built. Need to differentiate between master and Dab then we can make them available publicly on the download server.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?
    • 8/2 - Need Jira ticket.
    • 9/14 - no ticket

New Business:

August 31 , 2017

Attendees: Upcoming Meeting

August 24 , 2017

Attendees: Walt, Michael F, Michael T, Tanibata, Fulup, Stephane, Eugen Friedrich, Sebastien, Tanikawa, Mizuno, Tiejun Chen

Agenda:

  • XDG-Shell and ivi-application-shell architecture review. (Michael T)
    • Need to get slides with strict copyright notice removed

August 17 , 2017

Attendees: Canceled

August 3, 2017

Attendees: Walt, Jan-Simon, Aurelian, Tanikawa, Kusakabe,

Agenda:

  • Window Manager
    • Document updated to version 2.4 on the wiki page by Hoshina-san but no one knows what the updates were. Walt will send an email to the mail list asking.
  • V2C EG
    • Received a proposal from Ashley for V2C EG
    • Panasonic may participate in the EG. Tanikawa will check internally.
  • Mechanism for keeping track of backports - Email topic started by Martin Kelly.
    • Do all backports go into one repo or one one per architecture
    • Documentation for keeping tracking of backports
    • Move the discussion to a Jira ticket.
    • Incorporate into the layer re-organization
    • 8/3 - SPEC-802 created
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
    • 8/3 - Need Jira ticket created.
  • Graphics EG - Weston version for EE upgrades to 2.0 which is part of pyro (YP 2.3).
    • Renesas Gen 3 board
      • Officially supports Yocto 2.1 (korgoth).
      • IoT.bzh ported the the BSP to morty (Weston 1.11) for DD.
      • Expect that the next official Renesas BSP will be for morty.
      • IoT.bzh expects to take that version and provide pyro (Weston 2.0) support for Gen 3.
    • Porter probably will not be supported for EE.
    • Dominig to confirm for Intel boards.
    • Jan-Simon will check with Karthik and TI - no pyro branch yet, but they will add one
    • Need information on other BSPs?
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
    • Update 8/3 - No update. Plan is to add this to master after update to pyro is complete.
  • Roadmap for EE and 2018
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
  • SPEC-538 - Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 6/8 - Ronan posted the App FW bindings for SUSE,Fedora, and Ubuntu (see Jira comment for link). Need to request a high level public project rather than hosting it in Ronan's home.
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
    • 8/2 - Tanikawa reviewed and thinks it is ok as is, but we probably need a different view of which services belong to the application framework and which ones are not available to the applications. Probably need different views of the architecture for audio, video, window system, and other major subsystems to indicate the which parts are included as application framework bindings and which areas systemd covers (OS layer).
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
    • 8/2 - Rewriting App builder CI jobs to run for dab and master. Will add the apps to a directory on the download server after that is complete.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?
    • 8/2 - Need Jira ticket.

New Business:

  • Tanikawa asked about current (DD) homescreen and window manager maintenance. Tanikawa offered to help / take over maintenance existing home screen window manager.

July 20, 2017

Attendees: Walt, Michael, Aurelian, Martin, Tanikawa, Kusakabe, Kurokawa, Dennis,

  • Mechanism for keeping track of backports - Email topic started by Martin Kelly.
    • Do all backports go into one repo or one one per architecture
    • Documentation for keeping tracking of backports
    • Move the discussion to a Jira ticket.
    • Incorporate into the layer re-organization
  • Dennis had a question about what steps are required to create a product from AGL. Is there some documentation on the steps that a company would need to take to create a head unit product from AGL. Add this doc site. Create Jira ticket.
  • Graphics EG - Weston version for EE upgrades to 2.0 which is part of pyro (YP 2.3).
    • Renesas Gen 3 board
      • Officially supports Yocto 2.1 (korgoth).
      • IoT.bzh ported the the BSP to morty (Weston 1.11) for DD.
      • Expect that the next official Renesas BSP will be for morty.
      • IoT.bzh expects to take that version and provide pyro (Weston 2.0) support for Gen 3.
    • Porter probably will not be supported for EE.
    • Dominig to confirm for Intel boards.
    • Jan-Simon will check with Karthik and TI
    • Need information on other BSPs?
  • 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.
    • Update 7/6 - Jan-Simon started a POC on github. https://github.com/dl9pf/layer-reorg and invited participation from members.
    • Update 7/20 - Update on POC from Jan-Simon
  • Roadmap for EE and 2018
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
  • SPEC-538 - Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 6/8 - Ronan posted the App FW bindings for SUSE,Fedora, and Ubuntu (see Jira comment for link). Need to request a high level public project rather than hosting it in Ronan's home.
  • Need to define EE and 2018 roadmap at the face to face meeting next month.
  • Toyota (Hoshina-san) uploaded new App FW/ Window manager document to wiki. See Window Manager
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?

New Business:


July 6, 2017

Attendees: Walt, Jan-Simon, Isogai, Dennis, Kurokawa, Michael F, Stephane, Sebastien, Tanikawa,

  • Graphics EG - Weston version for EE upgrades to 2.0 which is part of pyro (YP 2.3).
    • Renesas Gen 3 board
      • Officially supports Yocto 2.1 (korgoth).
      • IoT.bzh ported the the BSP to morty (Weston 1.11) for DD.
      • Expect that the next official Renesas BSP will be for morty.
      • IoT.bzh expects to take that version and provide pyro (Weston 2.0) support for Gen 3.
    • Porter probably will not be supported for EE.
    • Dominig to confirm for Intel boards.
    • Jan-Simon will check with Karthik and TI
    • Need information on other BSPs?
  • Release management question - CC 3.0.4 pulled in the tip of the poky branch rather than an official release. Should we limit upstream code to official releases plus cherry picked backported fixes or continue with the current policy?
    • SAT agrees to match point releases from upstream repos rather than picking up random patches from upstream that may not be tested as working.
  • 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.
  • Roadmap for EE and 2018
  • Agenda for San Jose F2F
    • Yocto Layers and Device Profiles
    • Audio architecture for EE and beyond (App FW Binding or GENIVI audio manager path)
      • Fulup to detail progress on App FW Binding and UNICENS progress since the Karlsruhe F2F
      • Isogai
    • Roadmap for EE and 2018
    • V2C
    • User Identity
    • Application persistent data (per identity and security considerations)
    • Toyota to present the window manager API via video conference
    • CES 2018
  • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project. SPEC-588 is the primary task in the Epic.
    • Update 6/8 - For DD we want to incorporate the reference low level binding for OBD II along with a reference app, and documentation that describes what needs to be done to create your own binding. Discussed a mechanism to provide a “preview” of code that is proposed to eventually become part of the platform as it matures in a later release. Candidate include ViWi, UNICENS 2 audio, and low-level audio.
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SPEC-145 - Yocto Layer restructuring/ headless device profile
    • Need to complete SPEC-219 - Requirements for Telematics Device Profile
    • Stephane: Need for headless profile to support Telematics and Renesas use cases where we cannot redistribute graphics drivers so that we can enable app development.
    • SPEC-537 - Yocto Layer reorganization - Need to complete requirements first.
    • DEFAULTTUNE (SPEC-491)- Update 4/27 - Jan-Simon has a sandbox in gerrit that can be looked at.
    • Update 4/27 - Setting up a meeting for next Wednesday to discuss. Added notes to SPEC-219 for requirements.
    • Update 5/11 - See SPEC-145 for updates on latest meetings. Next meeting planned for 22 May.
    • Update 6/8 - BoF held last week during ALS. Results documented in Jira. F2F meeting planned in Vannes for next week.
    • Update 6/22 -
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
  • SPEC-538 - Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 6/8 - Ronan posted the App FW bindings for SUSE,Fedora, and Ubuntu (see Jira comment for link). Need to request a high level public project rather than hosting it in Ronan's home.
  • Need to define EE and 2018 roadmap at the face to face meeting next month.
  • Toyota (Hoshina-san) uploaded new App FW/ Window manager document to wiki. See Window Manager
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?

New Business:


June 22, 2017

Attendees: Walt, Jan-Simon, Aurelian, Fulup, Sebastien, Tanikawa, Stephane, Dominig, Kusakabe, Michael F, Dennis

  • 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.
  • Roadmap for EE and 2018
  • Agenda for San Jose F2F
    • Yocto Layers and Device Profiles
    • Audio architecture for EE and beyond (App FW Binding or GENIVI audio manager path)
      • Fulup to detail progress on App FW Binding and UNICENS progress since the Karlsruhe F2F
      • Isogai
    • Roadmap for EE and 2018
    • V2C
    • User Identity
    • Application persistent data (per identity and security considerations)
    • Toyota to present the window manager API via video conference
    • CES 2018
  • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project. SPEC-588 is the primary task in the Epic.
    • Update 6/8 - For DD we want to incorporate the reference low level binding for OBD II along with a reference app, and documentation that describes what needs to be done to create your own binding. Discussed a mechanism to provide a “preview” of code that is proposed to eventually become part of the platform as it matures in a later release. Candidate include ViWi, UNICENS 2 audio, and low-level audio.
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SPEC-145 - Yocto Layer restructuring/ headless device profile
    • Need to complete SPEC-219 - Requirements for Telematics Device Profile
    • Stephane: Need for headless profile to support Telematics and Renesas use cases where we cannot redistribute graphics drivers so that we can enable app development.
    • SPEC-537 - Yocto Layer reorganization - Need to complete requirements first.
    • DEFAULTTUNE (SPEC-491)- Update 4/27 - Jan-Simon has a sandbox in gerrit that can be looked at.
    • Update 4/27 - Setting up a meeting for next Wednesday to discuss. Added notes to SPEC-219 for requirements.
    • Update 5/11 - See SPEC-145 for updates on latest meetings. Next meeting planned for 22 May.
    • Update 6/8 - BoF held last week during ALS. Results documented in Jira. F2F meeting planned in Vannes for next week.
    • Update 6/22 -
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
  • SPEC-538 - Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 6/8 - Ronan posted the App FW bindings for SUSE,Fedora, and Ubuntu (see Jira comment for link). Need to request a high level public project rather than hosting it in Ronan's home.
  • Need to define EE and 2018 roadmap at the face to face meeting next month.
  • Toyota (Hoshina-san) uploaded new App FW/ Window manager document to wiki. See Window Manager
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE (or later). Jira issue?

New Business:

June 8, 2017

Attendees: Walt, Jan-Simon, Fulup, Stephane, Sebastien, Kusakabe, Dominig

  • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project.
    • Update 4/27 - Create a primary epic called “Enable CAN messaging in AGL Platform”. Make SPEC-428 a subtask and should make SPEC-137 a subtask. Also may need to update Jira for AGL
    • Update 5/11 - Created Epic - SPEC-588 and linked to SPEC-428 and SPEC-137
    • Update 5/25 - No update. No more issues have been added to the epic.
    • Update 6/8 - For DD we want to incorporate the reference low level binding for OBD II along with a reference app, and documentation that describes what needs to be done to create your own binding. Discussed a mechanism to provide a “preview” of code that is proposed to eventually become part of the platform as it matures in a later release. Candidate include ViWi, UNICENS 2 audio, and low-level audio.
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SPEC-145 - Yocto Layer restructuring/ headless device profile
    • Need to complete SPEC-219 - Requirements for Telematics Device Profile
    • Stephane: Need for headless profile to support Telematics and Renesas use cases where we cannot redistribute graphics drivers so that we can enable app development.
    • SPEC-537 - Yocto Layer reorganization - Need to complete requirements first.
    • DEFAULTTUNE (SPEC-491)- Update 4/27 - Jan-Simon has a sandbox in gerrit that can be looked at.
    • Update 4/27 - Setting up a meeting for next Wednesday to discuss. Added notes to SPEC-219 for requirements.
    • Update 5/11 - See SPEC-145 for updates on latest meetings. Next meeting planned for 22 May.
    • Update 6/8 - BoF held last week during ALS. Results documented in Jira. F2F meeting planned in Vannes for next week.
  • SPEC-511 - replace 01org/meta-intel-iot-security layer:
    • Update 6/7 from App FW meeting- Dominig has spoken to the maintainer of Yocto meta-security (Armin Kuster) which has SELinux and TPM and we may have home there. We could possibly move the recipes that we use from meta-iot-security
  • SPEC-538 - Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 6/8 - Ronan posted the App FW bindings for SUSE,Fedora, and Ubuntu (see Jira comment for link). Need to request a high level public project rather than hosting it in Ronan's home.

New Business:

  • Need to define EE and 2018 roadmap at the face to face meeting next month.
  • Toyota (Hoshina-san) uploaded new App FW/ Window manager document to wiki. See Window Manager
  • Need a new/revised public architecture diagram. See https://www.draw.io/#G0ByWQ8KVvCEUrMUQ1OFBWcm9EV1E for version from Spec 1.0
  • Jan-Simon: We are now building Apps in CI. Should we make these publicly available? Will be put in a folder, but not advertise it until we get a handle on how well it works. Can they pre-built demo apps be made available in DD? Revisit this in two weeks.
  • Dominig: Requirements for deep sleep, shutdown, and suspend/resume. Roadmap item for EE++. Jira issue?

May 25, 2017

Attendees: Walt, Jan-Simon, Tanikawa, Aurelian

  • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project.
    • Update 4/27 - Create a primary epic called “Enable CAN messaging in AGL Platform”. Make SPEC-428 a subtask and should make SPEC-137 a subtask. Also may need to update Jira for AGL
    • Update 5/11 - Created Epic - SPEC-588 and linked to SPEC-428 and SPEC-137
    • Update 5/25 - No update. No more issues have been added to the epic.
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SPEC-145 - Yocto Layer restructuring/ headless device profile
    • Need to complete SPEC-219 - Requirements for Telematics Device Profile
    • Stephane: Need for headless profile to support Telematics and Renesas use cases where we cannot redistribute graphics drivers so that we can enable app development.
    • SPEC-537 - Yocto Layer reorganization - Need to complete requirements first.
    • DEFAULTTUNE (SPEC-491)- Update 4/27 - Jan-Simon has a sandbox in gerrit that can be looked at.
    • Update 4/27 - Setting up a meeting for next Wednesday to discuss. Added notes to SPEC-219 for requirements.
    • Update 5/11 - See SPEC-145 for updates on latest meetings. Next meeting planned for 22 May
  • SPEC-511 - 01org/meta-intel-iot-security: upstream removed cynara support in 3936bc3 -import recipe locally ? fork repo ? maintainer ?
  • SPEC-538 - Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 5/11 - Nothing to report

New Business:


May 11, 2017

Attendees: Walt, Michael, Aurelian, Stephane

Agenda:

  • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project.
    • Update 4/27 - Create a primary epic called “Enable CAN messaging in AGL Platform”. Make SPEC-428 a subtask and should make SPEC-137 a subtask. Also may need to update Jira for AGL
    • Update 5/11 - Created Epic - SPEC-588 and linked to SPEC-428 and SPEC-137
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SPEC-145 - Yocto Layer restructuring/ headless device profile
    • Need to complete SPEC-219 - Requirements for Telematics Device Profile
    • Stephane: Need for headless profile to support Telematics and Renesas use cases where we cannot redistribute graphics drivers so that we can enable app development.
    • SPEC-537 - Yocto Layer reorganization - Need to complete requirements first.
    • DEFAULTTUNE (SPEC-491)- Update 4/27 - Jan-Simon has a sandbox in gerrit that can be looked at.
    • Update 4/27 - Setting up a meeting for next Wednesday to discuss. Added notes to SPEC-219 for requirements.
    • Update 5/11 - See SPEC-145 for updates on latest meetings. Next meeting planned for 22 May
  • SPEC-511 - 01org/meta-intel-iot-security: upstream removed cynara support in 3936bc3 -import recipe locally ? fork repo ? maintainer ?
  • SPEC-538 - Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 5/11 - Nothing to report

New Business:


April 27, 2017

Attendees: Walt, Jan-Simon, Sebastien, Tanikawa, Michael, Jens, Mikko, Kusakabe Agenda:

  • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project.
    • Update 4/27 - Create a primary epic called “Enable CAN messaging in AGL Platform”. Make SPEC-428 a subtask and should make SPEC-137 a subtask. Also may need to update Jira for AGL
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SDL integration. Layer proposed by this week which bypasses security in App FW. Need to follow up with Ford and EB
  • SPEC-145 - Yocto Layer restructuring/ headless device profile
    • Need to complete SPEC-219 - Requirements for Telematics Device Profile
    • Stephane: Need for headless profile to support Telematics and Renesas use cases where we cannot redistribute graphics drivers so that we can enable app development.
    • SPEC-537 - Yocto Layer reorganization - Need to complete requirements first.
    • DEFAULTTUNE (SPEC-491)- Update 4/27 - Jan-Simon has a sandbox in gerrit that can be looked at.
    • Update 4/27 - Setting up a meeting for next Wednesday to discuss. Added notes to SPEC-219 for requirements.
  • SPEC-511 - 01org/meta-intel-iot-security: upstream removed cynara support in 3936bc3 -import recipe locally ? fork repo ? maintainer ?
  • Fulup: Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 3/30 - Need Jira issue. Stephane filled us in on some progress they have made.
    • Update 4/27 - Nothing to report.

New Business:


April 13, 2017

Attendees: Walt, Jens, Jan-Simon, Tanikawa

Agenda:

  • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project.
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SDL integration. Layer proposed by this week which bypasses security in App FW. Need to follow up with Ford and EB
  • SPEC-459: Move community board support files and recipes to meta-agl-devel.
    • AI for Jan-Simon and Stephane to work out the best structure for this.
    • Update 3/22 - Now that SPEC-411 has been merged we can move forward with this.
    • Update 3/29 - Work will start next month.
    • Update 4/13 - Made a subtask of SPEC-145 to be completed as part of layer restructuring.
  • SPEC-458 -01org/meta-security-isafw: upstream broken on morty
  • SPEC-511 - 01org/meta-intel-iot-security: upstream removed cynara support in 3936bc3 -import recipe locally ? fork repo ? maintainer ?
  • SPEC-145 - Stephane: Need for headless profile to support Telematics and Renesas use cases where we cannot redistribute graphics drivers so that we can enable app development. (SPEC-145)
  • Fulup: Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 3/30 - Need Jira issue. Stephane filled us in on some progress they have made.

New Business: * Reworking of Yocto layers for EE to accommodate device profiles (SPEC-537). Made a subtask of SPEC-145 to be completed as part of layer restructuring. * DEFAULTTUNE (SPEC-491), see email on ML. Made a subtask of SPEC-145 to be completed as part of layer restructuring.


March 30, 2017

Attendees: Walt, Jan-Simon, Dominig, Jens, Kusakabe, Stephane

Agenda:

  • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project.
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SDL integration. Layer proposed by this week which bypasses security in App FW. Need to follow up with Ford and EB
  • SPEC-459: Move community board support files and recipes to meta-agl-devel.
    • AI for Jan-Simon and Stephane to work out the best structure for this.
    • Update 3/22 - Now that SPEC-411 has been merged we can move forward with this.
    • Update 3/29 - Work will start next month.
  • SPEC-511 - 01org/meta-intel-iot-security: upstream removed cynara support in 3936bc3 -import recipe locally ? fork repo ? maintainer ?
  • SPEC-145 - Stephane: Need for headless profile to support Telematics and Renesas use cases where we cannot redistribute graphics drivers so that we can enable app development. (SPEC-145)
  • Fulup: Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.
    • Update 3/30 - Need Jira issue. Stephane filled us in on some progress they have made.

New Business:

March 22, 2017

Attendees: Walt, Michael, Stephane, Jens, Tanikawa, Gabriel

Agenda:

  • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project.
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SDL integration. Layer proposed by this week which bypasses security in App FW. Need to follow up with Ford and EB
  • SPEC-448: Move App FW to meta-agl from meta-agl-extra. Decision by SC by 22 Mar. Approved without comment from SC.
  • SPEC-459: Move community board support files and recipes to meta-agl-devel.
    • AI for Jan-Simon and Stephane to work out the best structure for this.
    • Update 3/22 - Now that SPEC-411 has been merged we can move forward with this.
  • SPEC-458 -01org/meta-security-isafw: upstream broken on morty

(breaks isafw reports in snapshots, had to revert to old revision) –> needs someone with cycles to fix/push patch upstream

  • 01org/meta-intel-iot-security: upstream removed cynara support in 3936bc3 -

import recipe locally ? fork repo ? maintainer ? –> mid/long term support issue!

New Business:

  • SPEC-474 - Add iotivity-node to distro
  • Agenda for F2F
  • Stephane: Need for headless profile to support Telematics and Renesas use cases where we cannot redistribute graphics drivers so that we can enable app development. (SPEC-145)
  • Fulup: Need for developers to be able to develop AGL applications for a native Linux environment rather than running QEMU.

March, 2 2017

Attendees: Walt, Jan-Simon, Jens, Stephane, Fulup (The Fab Five)

Agenda:

  • Release Schedule Now posted on Wiki
    • Reviewed schedule and made some updates to be posted
    • Need to review the Jira Epics and make sure we them up to date. Will use Vehicle Signaling as a test case for multi-release project.
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
    • Fulup is an invited guest to W3C meetings but has no standing. W3C is looking to settle on the JLR standard (VSS) in the April time-frame. Initiate was started from GENIVI.
    • AGL should investigate which standards body to use for normalizing vehicle to cloud communications. W3C, Oasis, OpenID are possibilities.
    • Current effort at IoT.bzh is focused on OpenXC for inside vehicle, VIWI for web interface, and OpenID Connect for authentication on the cloud.
    • Kick up to Steering Committee as well.
  • SDL integration. Layer proposed by this week which bypasses security in App FW. Need to follow up with Ford and EB

New Business:

  • Move App FW to meta-agl from meta-agl-extra
  • SPEC-459: Move community board support files and recipes to meta-agl-devel.
    • AI for Jan-Simon and Stephane to work out the best structure for this.
  • SPEC-458 -01org/meta-security-isafw: upstream broken on morty

(breaks isafw reports in snapshots, had to revert to old revision) –> needs someone with cycles to fix/push patch upstream

  • 01org/meta-intel-iot-security: upstream removed cynara support in 3936bc3 -

import recipe locally ? fork repo ? maintainer ? –> mid/long term support issue!


February 16, 2017

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

Agenda:

  • Framework Updates for 2017
    • Message Signaling - Wiki page to document the changes. Plan is to go ahead with this architecture.
    • Upcoming Improvements to App Framework
      • Reworking the App FW to use systemd for control of apps (Complete for CC)
      • Introduce cgroups (Will be included in CC. Additional work will be needed for DD)
      • Namespace (Will be included in Daring Dab)
      • Basically containerizing applications (LXC) (Requires namespace so DD or later)
      • Notification service (Dominig presenting at AMM a proposal)
      • I18 mechanism to broadcast events and manage resource files across applications.
      • Sharing resources (bindings, libraries, etc) between applications needs a larger discussion
      • Identity and user management
      • Key management for app installation and the manifest that gives the rights within cynara.
      • First boot app installation mechanism (SPEC-317)
      • Building apps in CI and providing snapshot builds.
      • Consistent templates and documentation for creation of apps and widgets
      • Documentation of how to convert legacy apps to AGL Apps.
      • Updating skins across applications (more Graphics and UI EG than App FW)
      • Consent management for managing resources and applications. Examples include payments, enabling LBS. Should be done securely per application and user
  • Other 2017 Roadmap
    • CIAT
      • Merge our fork of JTA back into Fuego to get continuous support.
      • New reference boards added to Lava and CI system
      • Publish and evaluate test results
      • Ensure that CI system builds and checks patches for optional features. Example of recent patches to Iotivity that did not get built by the CI system because the feature was not enabled.
      • Static analysis of code
    • Architecture for vehicle signaling. Getting CAN reference data from OEMs.
    • Define success for 2017 in terms of AGL being ready for production and what that looks like.
      • Quality improvements - “We don't have to have everything, but what we have needs to work.”
      • Documentation
      • Testing and published test results
    • Virtualization / Containers
      • New ARMv8 platforms are powerful enough to benefit from virtualization
      • New Virtualization Expert Group
        • a new webpage will be created on the wiki. A number of conference calls and face to face meetings will be set to define a possible roadmap for this EG.
        • a set of meeting slots will be proposed (the idea is to start after CES2017). Walt will prepare the needed meeting infrastructure when everything will be set.
        • Virtual Open Systems, plans to develop a specific PoC on this matter in 2017 (KVM hypervisor and TrustZone).
    • API tools and common description of APIs along with documentation
    • Expand binder API capability to an RTOS to prove interoperability of AGL
    • Device profiles
    • Homescreen improvements with secure APIs
    • Speech Services API and service binder

Expert Groups:

  • AGL Compositor - possible donation from Wind River (Ned) Same status per Kaz.
    • IP Scan in progress inside Wind River
    • Some cleanup of the code is required internal to Wind River
    • Will be presented to the Graphics and UI EG prior to SAT
    • Could be hosted in the agl staging area for review - Ned's guess is this about a month away (say Nov 1).
    • Features
      • Qt Waylon dependencies - elimination of Qt dependencies would need to be community effort
      • Window manager
      • Surface sharing
      • Multiple display support
  • Navigation EG Update - see EG Navi Wiki page for more information. Need to get more interaction with SAT from this EG. We would like to see instructions on how to integrate a new map with the App. Code is well written according to Fulup but comments are all in Japanese and there is no documentation. EG is planning to add some new features for the CES demo.
  • Speech Services - possible donation from Conti for TTS No Update.
    • 3 - 6 months until Conti legal and technical review can be completed.
    • The feature set you would get is basically a TTS with an API to put out “Speak” requests.
    • The API is used in our products and allows for
    • Different sources (Speech Dialog, Navigation, “Apps”…) to speak
    • Priority handling / arbitration of Applications using the TTS
    • Interruption of “Speak” requests
  • Connectivity
    • Bluetooth and Wifi Connectivity
      • Looking a common commercial BT/Wifi dongle to be used as part of a standard set up. IoT.bzh will do some testing and make a recommendation. Done. Recommendation on CES demo wiki page.
    • Vehicle messaging and signaling
      • Looking for some characterization of IVI system message rates from CAN bus in order to drive the design. Getting trace data from CAN buses is impossible on the internet. Walt will bring to Steering Committee to ask for date.
      • See https://github.com/iotbzh/txc-demo/blob/master/bench/result-bench-porter for some bench marks done by IoT.bzh for one vehicle trace from Ford (openxc) that was found on the internet.
  • Release Schedule
  • FIXME Update for DD and EE as well CC patch releases
  • Telematics (Proposed EG)
    • Dead for now based on BoF. Device manufacturers not really interested. Service providers seem more interested.

Miscellaneous:

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

New Business:

  • Can we collect usage information by including a “First Boot” application that requests the user to collect anonymous information about how the system is being used.
  • Need to review W3C proposals from VW and JLR. Setting up another call to make a decision on which one to pursue.
  • SDL integration. Layer proposed by this week which bypasses security in App FW. Need to follow up with Ford and EB.

January 19, 2017

Attendees: Walt, Jan-Simon, Jens, Dominig

Agenda:

  • Framework Updates for 2017
    • Message Signaling - Wiki page to document the changes. Plan is to go ahead with this architecture.
    • Upcoming Improvements to App Framework
      • Reworking the App FW to use systemd for control of apps (Complete for CC)
      • Introduce cgroups (Will be included in CC. Additional work will be needed for DD)
      • Namespace (Will be included in Daring Dab)
      • Basically containerizing applications (LXC) (Requires namespace so DD or later)
      • Notification service (Dominig presenting at AMM a proposal)
      • I18 mechanism to broadcast events and manage resource files across applications.
      • Sharing resources (bindings, libraries, etc) between applications needs a larger discussion
      • Identity and user management
      • Key management for app installation and the manifest that gives the rights within cynara.
      • First boot app installation mechanism (SPEC-317)
      • Building apps in CI and providing snapshot builds.
      • Consistent templates and documentation for creation of apps and widgets
      • Documentation of how to convert legacy apps to AGL Apps.
      • Updating skins across applications (more Graphics and UI EG than App FW)
      • Consent management for managing resources and applications. Examples include payments, enabling LBS. Should be done securely per application and user
  • Other 2017 Roadmap
    • CIAT
      • Merge our fork of JTA back into Fuego to get continuous support.
      • New reference boards added to Lava and CI system
      • Publish and evaluate test results
      • Ensure that CI system builds and checks patches for optional features. Example of recent patches to Iotivity that did not get built by the CI system because the feature was not enabled.
      • Static analysis of code
    • Architecture for vehicle signaling. Getting CAN reference data from OEMs.
    • Define success for 2017 in terms of AGL being ready for production and what that looks like.
      • Quality improvements - “We don't have to have everything, but what we have needs to work.”
      • Documentation
      • Testing and published test results
    • Virtualization / Containers
      • New ARMv8 platforms are powerful enough to benefit from virtualization
      • New Virtualization Expert Group
        • a new webpage will be created on the wiki. A number of conference calls and face to face meetings will be set to define a possible roadmap for this EG.
        • a set of meeting slots will be proposed (the idea is to start after CES2017). Walt will prepare the needed meeting infrastructure when everything will be set.
        • Virtual Open Systems, plans to develop a specific PoC on this matter in 2017 (KVM hypervisor and TrustZone).
    • API tools and common description of APIs along with documentation
    • Expand binder API capability to an RTOS to prove interoperability of AGL
    • Device profiles
    • Homescreen improvements with secure APIs
    • Walt will start an email thread to collect ideas for 2017 roadmap. Need to complete the roadmap update by the end of January for the AMM.
    • Speech Services API and service binder

Expert Groups:

  • AGL Compositor - possible donation from Wind River (Ned) Same status per Kaz.
    • IP Scan in progress inside Wind River
    • Some cleanup of the code is required internal to Wind River
    • Will be presented to the Graphics and UI EG prior to SAT
    • Could be hosted in the agl staging area for review - Ned's guess is this about a month away (say Nov 1).
    • Features
      • Qt Waylon dependencies - elimination of Qt dependencies would need to be community effort
      • Window manager
      • Surface sharing
      • Multiple display support
  • Navigation EG Update - see EG Navi Wiki page for more information. Need to get more interaction with SAT from this EG. We would like to see instructions on how to integrate a new map with the App. Code is well written according to Fulup but comments are all in Japanese and there is no documentation. EG is planning to add some new features for the CES demo.
  • Speech Services - possible donation from Conti for TTS No Update.
    • 3 - 6 months until Conti legal and technical review can be completed.
    • The feature set you would get is basically a TTS with an API to put out “Speak” requests.
    • The API is used in our products and allows for
    • Different sources (Speech Dialog, Navigation, “Apps”…) to speak
    • Priority handling / arbitration of Applications using the TTS
    • Interruption of “Speak” requests
  • Connectivity
    • Bluetooth and Wifi Connectivity
      • Looking a common commercial BT/Wifi dongle to be used as part of a standard set up. IoT.bzh will do some testing and make a recommendation. Done. Recommendation on CES demo wiki page.
    • Vehicle messaging and signaling
      • Looking for some characterization of IVI system message rates from CAN bus in order to drive the design. Getting trace data from CAN buses is impossible on the internet. Walt will bring to Steering Committee to ask for date.
      • See https://github.com/iotbzh/txc-demo/blob/master/bench/result-bench-porter for some bench marks done by IoT.bzh for one vehicle trace from Ford (openxc) that was found on the internet.
  • CIAT
    • Blowfish 2.0.4 released. Blowfish 2.0.5 in January should be final Blowfish update
    • CC schedule announced
      • RC 1 - At the conclusion of the integration session we need all updates to be submitted by the end of the day Sunday December 18. We will use the December 18 snapshot build as the basis for our RC1. Development will continue on the master branch.
      • RC 2 - We will create RC 2 on or about December 28. Depending on how settled the code is, we may create the Charming Chinook release branch at this point or continue to work on Master. That decision will be made by Jan-Simon and Walt.
      • CC Release - Scheduled for January 6. Charming Chinook release branch will be tagged and released. New work on master will be for the Daring Dab release.
    • Lava up and running for Porter.
    • For 2017 can we combine API and platform level testing in one front end UI? graphana.org or similar?
  • Telematics (Proposed EG)
    • No news

Miscellaneous:

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

New Business:

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

January 5, 2017

Canceled - CES

Meeting Archive (pre-2017)

Minutes for meetings prior to 2014 - 2016 have been moved here.

agl-sat-meetings.txt · Last modified: 2018/12/12 02:25 by waltminer