Automotive Linux Wiki

User Tools

Site Tools

Trace: • meetings

Sidebar

Visit the AGL Web Site
AGL Projects
2018 CES Demonstrator

AGL Software

Schedule and Milestones
AGL Roadmap
AGL Software Distribution
AGL Confluence Site
AGL Documentation Site
AGL Jira
AGL Gerrit
Contributing to the AGL Code
Release Notes
Weekly Developer Call

Expert Groups

System Architecture Team
App Framework and Security
Connectivity
Continuous Integration and Test
Instrument Cluster
IVI Production Readiness
Reference Hardware System Architecture
Software Defined Vehicle
OSPO

About Us

Getting Started with AGL
AGL Meeting Calendar

eg-app-fw:meetings

Table of Contents

Meetings Notes for AGL Application Framework and Security Team

Meetings of the App Framework and Security EG are held every other Wednesday. The upcoming schedule can be found on the project calendar

Conference Information:

Topic: AGL App FW and Security BiWeekly Call

Join Zoom Meeting https://zoom.us/j/554912100?pwd=MkhsVllMR2pSdUlTVUhwRndTRzlvdz09

Meeting ID: 554 912 100
Passcode: 180916

Find your local number: https://zoom.us/u/ameRude4a

November 27, 2024

Attendees: Walt, Jan-Simon, Scott, Marius, Michael McKay

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 10/16
      • VSS 5.0 released.
      • KUKSA 2.0 changes are coming along. Once they are release Scott will look at incorporating them into Salmon.
    • 11/13
      • Scott just back from vacation so no update yet.
      • Will try VSS 5.0 then look at KUKSA.val 2.0 databroker for Salmon
    • 11/27
      • VSS 5.0 merged and will be available in Salmon M1
      • Scott waiting on the KUKSA.val 2.0 final release before pushing new databroker to master. Next status call is a week from tomorrow.
      • Scott created a Scarthgap Rust mixin layer for Yocto that will be pushed upstream later this. Will allow Rust 1.80.1 to be used with Scarthgap (current is 1.75)

New:

  • Michael introduced himself. Looking at AGL for UAV use cases.

November 13, 2024

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 10/16
      • VSS 5.0 released.
      • KUKSA 2.0 changes are coming along. Once they are release Scott will look at incorporating them into Salmon.
    • 11/13
      • Scott just back from vacation so no update yet.
      • Will try VSS 5.0 then look at KUKSA.val 2.0 databroker for Salmon

New:

October 16, 2024

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 7/10
      • Updates for databroker and KUKSA are in for Ricefish release.
    • 7/24
      • Latest databroker went into Ricefish.
    • 8/21
      • Discussed VSS standardization discussions that are taking place during the COVESA AMM next month.
      • VSS 5.0 is in review.
    • 10/02
      • VSS 5.0 expected for next week
    • 10/16
      • VSS 5.0 released.
      • KUKSA 2.0 changes are coming along. Once they are release Scott will look at incorporating them into Salmon.

New:

October 2, 2024

Attendees: Walt, Jan-Simon, Scott

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 7/10
      • Updates for databroker and KUKSA are in for Ricefish release.
    • 7/24
      • Latest databroker went into Ricefish.
    • 8/21
      • Discussed VSS standardization discussions that are taking place during the COVESA AMM next month.
      • VSS 5.0 is in review.
    • 10/02
      • VSS 5.0 expected for next week

New:

September 4, 2024

Attendees: Walt, Jan-Simon, Scott

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
  • 7/10
    • Updates for databroker and KUKSA are in for Ricefish release.
  • 7/24
    • Latest databroker went into Ricefish.
  • 8/21
    • Discussed VSS standardization discussions that are taking place during the COVESA AMM next month.
    • VSS 5.0 is in review.

New:

August 21, 2024

Attendees: Walt, Scott, Marius

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
  • 7/10
    • Updates for databroker and KUKSA are in for Ricefish release.
  • 7/24
    • Latest databroker went into Ricefish.
  • 8/21
    • Discussed VSS standardization discussions that are taking place during the COVESA AMM next month.
    • VSS 5.0 is in review.

New:

July 24, 2024

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
  • 7/10
    • Updates for databroker and KUKSA are in for Ricefish release.
  • 7/24
    • Latest databroker went into Ricefish.

New:

July 10, 2024

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
  • 7/10
    • Updates for databroker and KUKSA are in for Ricefish release.

New:

June 12, 2024

Attendees: Walt, Jan-Simon, Scott, Marius, Victor

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/15
      • VSS is gearing up to release version 4.2. Scott doesn't expect a big impact.
    • 5/29
      • Ricefish updates for latest KUKSA and VSS version will get into M2.
    • 6/12
      • Ricefish updates still planned for M2

New:

May 29, 2024

Attendees: Walt, Jan-Simon, Scott, Marius, Victor

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/15
      • VSS is gearing up to release version 4.2. Scott doesn't expect a big impact.
    • 5/29
      • Ricefish updates for latest KUKSA and VSS version will get into M2.

New:

May 15, 2024

Attendees: Walt, Scott, Marius

App FW EG Topics

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/15
      • VSS is gearing up to release version 4.2. Scott doesn't expect a big impact.

New:

May 1, 2024

Attendees: Walt, Scott, Marius

App FW EG Topics

Application Framework Redesign

  • IPC
    • 11/29
      • Full speed ahead with gRPC

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 12/13
      • KUKSA.val is now on 0.4.2
      • VSS is on 4.0
    • 2/7
      • Rust 1.70 mix-in is now merged which reduced the size of our patch for databroker.
  • Ref HW
    • No update
  • Networking/Bluetooth
    • No update
    • Possibly stubbed-out grpc api.
  • 5G/LTE module and Telephony
    • No update

New:

Feb 21, 2024

Attendees: Walt, Jan-Simon, Scott, Marius, Denys

App FW EG Topics

Application Framework Redesign

  • IPC
    • 11/29
      • Full speed ahead with gRPC

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 12/13
      • KUKSA.val is now on 0.4.2
      • VSS is on 4.0
    • 2/7
      • Rust 1.70 mix-in is now merged which reduced the size of our patch for databroker.
  • Ref HW
    • No update
  • Networking/Bluetooth
    • No update
    • Possibly stubbed-out grpc api.
  • 5G/LTE module and Telephony
    • No update

New:

Feb 7, 2024

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

Application Framework Redesign

  • IPC
    • 11/29
      • Full speed ahead with gRPC

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 12/13
      • KUKSA.val is now on 0.4.2
      • VSS is on 4.0
    • 2/7
      • Rust 1.70 mix-in is now merged which reduced the size of our patch for databroker.
  • Ref HW
    • No update
  • Networking/Bluetooth
    • No update
    • Possibly stubbed-out grpc api.
  • 5G/LTE module and Telephony
    • No update

New:

Dec 13, 2023

Attendees: Walt, Jan-Simon, Scott,

App FW EG Topics

Application Framework Redesign

  • IPC
    • 11/29
      • Full speed ahead with gRPC

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 12/13
      • KUKSA.val is now on 0.4.2
      • VSS is on 4.0
  • Ref HW
    • No update
  • Networking/Bluetooth
    • No update
    • Possibly stubbed-out grpc api.
  • 5G/LTE module and Telephony
    • No update

New:

Nov 29, 2023

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

Application Framework Redesign

  • IPC
    • 11/29
      • Full speed ahead with gRPC

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/31
      • 0.3.1 complete
      • databroker enablement uploaded to gerrit.
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.
  • Ref HW
    • No update
  • Networking/Bluetooth
    • No update
    • Possibly stubbed-out grpc api.
  • 5G/LTE module and Telephony
    • No update

New:

October 18, 2023

Attendees: Jan-Simon, Scott, Denys, Marius

App FW EG Topics

Application Framework Redesign

Documentation for Pike

  • 6/14
    • Scott will work on soon
  • 8/9
    • No update
  • 9/6
    • Denys passed his changes to Scott for the sandboxing and systemd changes. Waiting on Scott to complete the updates.
  • 9/20
    • Scott readying updates.
  • 10/18
    • see above, to be backported.
  • IPC
    • 5/17
      • WAM changes are done. Can try removing DBUS from applaunchd (SPEC-4801)
    • 5/31
      • SPEC-4801 - DBUS removal from applaunchd is complete
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.
    • 10/18
      • Databroker in use and old server removed.

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/31
      • 0.3.1 complete
      • databroker enablement uploaded to gerrit.
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.
  • Ref HW
    • No update
  • Networking/Bluetooth
    • No update
    • Possibly stubbed-out grpc api.
  • 5G/LTE module and Telephony
    • No update

New:

October 4, 2023

Attendees: Walt, Jan-Simon, Scott, Denys, Marius

App FW EG Topics

Application Framework Redesign

Documentation for Pike

  • 6/14
    • Scott will work on soon
  • 8/9
    • No update
  • 9/6
    • Denys passed his changes to Scott for the sandboxing and systemd changes. Waiting on Scott to complete the updates.
  • 9/20
    • Scott readying updates.
  • IPC
    • 5/17
      • WAM changes are done. Can try removing DBUS from applaunchd (SPEC-4801)
    • 5/31
      • SPEC-4801 - DBUS removal from applaunchd is complete
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/31
      • 0.3.1 complete
      • databroker enablement uploaded to gerrit.
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

September 20, 2023

Attendees: Walt, Jan-Simon, Scott, Yan, Denys, Marius

App FW EG Topics

Application Framework Redesign

Documentation for Pike

  • 6/14
    • Scott will work on soon
  • 8/9
    • No update
  • 9/6
    • Denys passed his changes to Scott for the sandboxing and systemd changes. Waiting on Scott to complete the updates.
  • 9/20
    • Scott readying updates.
  • IPC
    • 5/17
      • WAM changes are done. Can try removing DBUS from applaunchd (SPEC-4801)
    • 5/31
      • SPEC-4801 - DBUS removal from applaunchd is complete
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/31
      • 0.3.1 complete
      • databroker enablement uploaded to gerrit.
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

September 6, 2023

Attendees: Walt, Jan-Simon, Denys

App FW EG Topics

  • 5/31
    • Revisited and updated the 2023 Roadmap Confluence page
    • How do we improve the developer workflow for Qt and Webapps?
      • Start with documenting the process for deploying apps today.
      • We probably do not want to create and maintain a bunch of tools on our own.
      • Is there something upstream we could use? YP devtool is one possibility, but there is no upstream maintainer and we would need to document very well and expect problems with the tooling. Possibly write a script similar to what Joel has done for Flutter.
  • 6/14
    • Will add developer workflow to the F2F schedule in Tokyo
  • 8/9
    • test and link config for Joel's tooling, write section for doc site

Application Framework Redesign

Documentation for Pike

  • 6/14
    • Scott will work on soon
  • 8/9
    • No update
  • 9/6
    • Denys passed his changes to Scott for the sandboxing and systemd changes. Waiting on Scott to complete the updates.
  • IPC
    • 5/17
      • WAM changes are done. Can try removing DBUS from applaunchd (SPEC-4801)
    • 5/31
      • SPEC-4801 - DBUS removal from applaunchd is complete
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/31
      • 0.3.1 complete
      • databroker enablement uploaded to gerrit.
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

  • What to show at EOSS?

August 09, 2023

Attendees: Jan-Simon, Scott, Marius

App FW EG Topics

  • 5/31
    • Revisited and updated the 2023 Roadmap Confluence page
    • How do we improve the developer workflow for Qt and Webapps?
      • Start with documenting the process for deploying apps today.
      • We probably do not want to create and maintain a bunch of tools on our own.
      • Is there something upstream we could use? YP devtool is one possibility, but there is no upstream maintainer and we would need to document very well and expect problems with the tooling. Possibly write a script similar to what Joel has done for Flutter.
  • 6/14
    • Will add developer workflow to the F2F schedule in Tokyo
  • 8/9
    • test and link config for Joel's tooling, write section for doc site

Application Framework Redesign

Documentation for Pike

  • 6/14
    • Scott will work on soon
  • 8/9
    • No update
  • IPC
    • 5/17
      • WAM changes are done. Can try removing DBUS from applaunchd (SPEC-4801)
    • 5/31
      • SPEC-4801 - DBUS removal from applaunchd is complete
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/31
      • 0.3.1 complete
      • databroker enablement uploaded to gerrit.
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
    • 8/9
      • Databroker available in pike but not in use. QT apps will be converted in a point release of pike.
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

  • What to show at EOSS?

June 14, 2023

Attendees: Walt, Jan-Simon, Scott, Denys, Marius

App FW EG Topics

  • 5/31
    • Revisited and updated the 2023 Roadmap Confluence page
    • How do we improve the developer workflow for Qt and Webapps?
      • Start with documenting the process for deploying apps today.
      • We probably do not want to create and maintain a bunch of tools on our own.
      • Is there something upstream we could use? YP devtool is one possibility, but there is no upstream maintainer and we would need to document very well and expect problems with the tooling. Possibly write a script similar to what Joel has done for Flutter.
  • 6/14
    • Will add developer workflow to the F2F schedule in Tokyo

Application Framework Redesign

Documentation for Pike

  • 6/14
    • Scott will work on soon
  • IPC
    • 5/17
      • WAM changes are done. Can try removing DBUS from applaunchd (SPEC-4801)
    • 5/31
      • SPEC-4801 - DBUS removal from applaunchd is complete
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 5/31
      • 0.3.1 complete
      • databroker enablement uploaded to gerrit.
    • 6/14
      • Databroker gRPC for Qt apps in progress for Pike M2/M3
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

  • What to show at EOSS?

May 31, 2023

Attendees: Walt, Jan-Simon, Scott, Yan, Marius, Ishii, Kurokawa

App FW EG Topics

  • 5/31
    • Revisited and updated the 2023 Roadmap Confluence page
    • How do we improve the developer workflow for Qt and Webapps?
      • Start with documenting the process for deploying apps today.
      • We probably do not want to create and maintain a bunch of tools on our own.
      • Is there something upstream we could use? YP devtool is one possibility, but there is no upstream maintainer and we would need to document very well and expect problems with the tooling. Possibly write a script similar to what Joel has done for Flutter.

Application Framework Redesign

  • IPC
    • 5/17
      • WAM changes are done. Can try removing DBUS from applaunchd (SPEC-4801)
    • 5/31
      • SPEC-4801 - DBUS removal from applaunchd is complete

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 1/26
      • Kuksa.val running in the CES demo and is up to date in the Needlefish and Octopus releases.
    • 4/5
      • Working on Kuksa.val databroker (aka rust-based implementation, grpc only, preferred by upstream)
    • 4/19
      • Discussed Paul's work using with connecting steering wheel and standard VSS signals and KUKSA.val versus the overlay that Scott currently has implemented.
      • SPEC-4761 - Switch to KUKSA.val databroker
      • SPEC-4762 - Update to KUKSA.val to 0.3.1
    • 5/3
      • 0.3.1 upgrade in final stages. Client and feeder need more changes.
      • Added vss-tools recipe to generate the new json
      • mix-in layer ready this week, can add layer and submit databroker to gerrit
    • 5/17
      • 0.3.1 should be ready to go into master this week.
      • databroker in progress now that semi-latest Rust (1.6.8) is available with the mix-in layer.
    • 5/31
      • 0.3.1 complete
      • databroker enablement uploaded to gerrit.
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

May 17, 2023

Attendees: Walt, Scott, Marius, Deepansh Jain (Scooterson)

App FW EG Topics

Application Framework Redesign

  • IPC
    • 1/25
      • Radio tuner API converted to gRPC and the Qt app was updated to use the new API.
    • 3/22
      • Get an update from Scott next time.
    • 4/18
      • DBUS interface to Applaunchd can be removed once the WAM changes from Roger are merged.
    • 5/03
      • Changes to WAM are WIP
    • 5/17
      • WAM changes are done. Can try removing DBUS from applaunchd (SPEC-4801)

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 1/26
      • Kuksa.val running in the CES demo and is up to date in the Needlefish and Octopus releases.
    • 4/5
      • Working on Kuksa.val databroker (aka rust-based implementation, grpc only, preferred by upstream)
    • 4/19
      • Discussed Paul's work using with connecting steering wheel and standard VSS signals and KUKSA.val versus the overlay that Scott currently has implemented.
      • SPEC-4761 - Switch to KUKSA.val databroker
      • SPEC-4762 - Update to KUKSA.val to 0.3.1
    • 5/3
      • 0.3.1 upgrade in final stages. Client and feeder need more changes.
      • Added vss-tools recipe to generate the new json
      • mix-in layer ready this week, can add layer and submit databroker to gerrit
    • 5/17
      • 0.3.1 should be ready to go into master this week.
      • databroker in progress now that semi-latest Rust (1.6.8) is available with the mix-in layer.
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

May 3rd, 2023

Attendees: Walt, Jan-Simon, Scott, Marius, Denys, Dua Ha Quang

App FW EG Topics

Application Framework Redesign

  • IPC
    • 1/25
      • Radio tuner API converted to gRPC and the Qt app was updated to use the new API.
    • 3/22
      • Get an update from Scott next time.
    • 4/18
      • DBUS interface to Applaunchd can be removed once the WAM changes from Roger are merged.
    • 5/03
      • Changes to WAM are WIP

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 1/26
      • Kuksa.val running in the CES demo and is up to date in the Needlefish and Octopus releases.
    • 4/5
      • Working on Kuksa.val databroker (aka rust-based implementation, grpc only, preferred by upstream)
    • 4/19
      • Discussed Paul's work using with connecting steering wheel and standard VSS signals and KUKSA.val versus the overlay that Scott currently has implemented.
      • SPEC-4761 - Switch to KUKSA.val databroker
      • SPEC-4762 - Update to KUKSA.val to 0.3.1
    • 5/3
      • 0.3.1 upgrade in final stages. Client and feeder need more changes.
      • Added vss-tools recipe to generate the new json
      • mix-in layer ready this week, can add layer and submit databroker to gerrit
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

April 19, 2023

Attendees: Walt, Jan-Simon, Scott, Marius, Paul M, Du Ha

App FW EG Topics

Application Framework Redesign

  • IPC
    • 1/25
      • Radio tuner API converted to gRPC and the Qt app was updated to use the new API.
    • 3/22
      • Get an update from Scott next time.
    • 4/18
      • DBUS interface to Applaunchd can be removed once the WAM changes from Roger are merged.

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 1/26
      • Kuksa.val running in the CES demo and is up to date in the Needlefish and Octopus releases.
    • 4/5
      • Working on Kuksa.val databroker (aka rust-based implementation, grpc only, preferred by upstream)
    • 4/19
      • Discussed Paul's work using with connecting steering wheel and standard VSS signals and KUKSA.val versus the overlay that Scott currently has implemented.
      • SPEC-4761 - Switch to KUKSA.val databroker
      • SPEC-4762 - Update to KUKSA.val to 0.3.1
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

April 5, 2023

Attendees: Jan-Simon, Denys, Scott, Ishii-san, Marius

App FW EG Topics

Application Framework Redesign

  • IPC
    • 1/25
      • Radio tuner API converted to gRPC and the Qt app was updated to use the new API.
    • 3/22
      • Get an update from Scott next time.

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 1/26
      • Kuksa.val running in the CES demo and is up to date in the Needlefish and Octopus releases.
    • 4/5
      • Working on Kuksa.val databroker (aka rust-based implementation, grpc only, preferred by upstream)
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update

New:

March 22, 2023

Attendees: Walt, Jan-Simon, Kurokawa

App FW EG Topics

Application Framework Redesign

  • 2/22
    • Documentation update still in progress. Marius has some changes to the documentation as well.
  • 3/22
    • Marius documentation updates are in review in gerrit
    • Waiting on Denys for sandbox documentation updates
  • IPC
    • 1/25
      • Radio tuner API converted to gRPC and the Qt app was updated to use the new API.
    • 3/22
      • Get an update from Scott next time.

Connectivity EG Topics

  • CAN/ Vehicle Signaling
    • 1/26
      • Kuksa.val running in the CES demo and is up to date in the Needlefish and Octopus releases.
  • Bluetooth
    • No update
  • Ref HW
    • No update
  • 5G/LTE module and Telephony
    • No update
  • New topics:
    • Checked EG feature list for 2023. Scott will update the Confluence page to describe 2023 status and priorities.

February 22, 2023

Attendees: Walt, Scott, Denys, Marius, Kim Sung Won

Application Framework Redesign

  • 11/16
    • Denys to look at systemd units and the kernel config to enable better sandboxing and add that to the app templates.
  • 12/14
    • Looking into BPF to extend and enable the sandboxing.
    • Basic BPF support planned for Octopus M2
  • 1/25
    • SPEC-4627 - Basic BPF made it into Octopus. Need to check with Denys what type of testing has been done. Should we add to doc site?
      • Is there a simple example we can document such as limiting access to the root file system by the applications.
  • 2/8
    • Denys is going to update the documentation site with systemd and sandbox information.
  • 2/22
    • Documentation update still in progress. Marius has some changes to the documentation as well.
  • Flutter
    • 1/25
      • Nothing app FW related
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
    • 7/27 - permissive mode submitted in gerrit and should be in M2
    • 8/10 - permissive mode released in Needlefish
    • 8/24 - no update
    • 9/21 - no update
    • 10/5 - no update
    • 12/14 - no update
  • IPC
    • 1/25
      • Radio tuner API converted to gRPC and the Qt app was updated to use the new API.
  • New topics:
    • Checked EG feature list for 2023. Scott will update the Confluence page to describe 2023 status and priorities.

February 8, 2023

Attendees: Walt, Jan-Simon, Denys

Application Framework Redesign

  • 11/16
    • Denys to look at systemd units and the kernel config to enable better sandboxing and add that to the app templates.
  • 12/14
    • Looking into BPF to extend and enable the sandboxing.
    • Basic BPF support planned for Octopus M2
  • 1/25
    • SPEC-4627 - Basic BPF made it into Octopus. Need to check with Denys what type of testing has been done. Should we add to doc site?
      • Is there a simple example we can document such as limiting access to the root file system by the applications.
  • 2/8
    • Denys is going to update the documentation site with systemd and sandbox information.
  • Flutter
    • 1/25
      • Nothing app FW related
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
    • 7/27 - permissive mode submitted in gerrit and should be in M2
    • 8/10 - permissive mode released in Needlefish
    • 8/24 - no update
    • 9/21 - no update
    • 10/5 - no update
    • 12/14 - no update
  • IPC
    • 1/25
      • Radio tuner API converted to gRPC and the Qt app was updated to use the new API.
  • New topics:
    • Checked EG feature list for 2023. Scott will update the Confluence page to describe 2023 status and priorities.

January 25, 2023

Attendees: Walt, Jan-Simon, Scott, Marius, Andrea Pferscher (TU Graz)

Application Framework Redesign

  • 11/16
    • Denys to look at systemd units and the kernel config to enable better sandboxing and add that to the app templates.
  • 12/14
    • Looking into BPF to extend and enable the sandboxing.
    • Basic BPF support planned for Octopus M2
  • 1/25
    • SPEC-4627 - Basic BPF made it into Octopus. Need to check with Denys what type of testing has been done. Should we add to doc site?
      • Is there a simple example we can document such as limiting access to the root file system by the applications.
  • Flutter
    • 1/25
      • Nothing app FW related
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
    • 7/27 - permissive mode submitted in gerrit and should be in M2
    • 8/10 - permissive mode released in Needlefish
    • 8/24 - no update
    • 9/21 - no update
    • 10/5 - no update
    • 12/14 - no update
  • IPC
    • 1/25
      • Radio tuner API converted to gRPC and the Qt app was updated to use the new API.
  • New topics:
    • Andrea at TU Graz working with AVL on connectivity topics.
    • Checked EG feature list for 2023. Scott will update the Confluence page to describe 2023 status and priorities.

December 14, 2022

Attendees: Walt, Jan-Simon, Scott, Marius, Denys

Application Framework Redesign

  • 9/21
    • gRPC version of applaunchd in progress
      • just merged in master
    • looking at running applaunchd as a separate user
      • depends on grpc version of the deamon
    • Documentation of applaunchd and app templates to be completed by September F2F
      • will be ready for postponed F2F
  • 10/5
    • Roger working on converting WAM to use gRPC applaunchd interface over the next month.
    • Documentation of applaunchd and app templates to be completed by October F2F
  • 11/16
    • Denys to look at systemd units and the kernel config to enable better sandboxing and add that to the app templates.
  • 12/14
    • Looking into BPF to extend and enable the sandboxing.
    • Basic BPF support planned for Octopus M2
  • Flutter
  • 6/15 - got a few updates from Joel but no progress on the multiple app support yet.
  • 6/29 - Waiting for updates from Toyota. Due next week for M1.
  • 7/13 - Had separate call yesterday. Will get tag for needlefish, but need to enhance in a point release. Todos: try out multiple embedder instances e.g. under qt homescreen (→ Scott will try). Image for GSoC. (e.g.: https://github.com/aakash-s45/ic or https://github.com/hritik-chouhan/HVAC_dashboard)
  • 7/27
    • Flutter looking ok for M2. Scott working on app template (see above).
  • 8/10
    • Released for M3 and ready for final NN release
  • 8/24
    • Good progress being made. IVI PR call now every week in order to speed up progress.
    • Scott will move the Igalia home screen for flutter from the Igalia Github into an AGL repo and we will use that as a starting point for continued home screen work including the applaunchd work.
  • 9/21
    • 14.0.1 release pinned the Flutter SDK
    • Scott hacking on flutter-homescreen from Igalia, need to port to latest flutter
    • GSoC students finished or about to finish their apps.
    • Need code in embedder for window activation going forward
  • 10/5
    • Scott got to the point of being able to launch apps from the flutter home screen using applaunchd.
    • Discussed SPEC-4503 and how to proceed. Marius will do some prototyping and we will schedule a session during the F2F meeting to discuss.
  • 12/14
    • Scott has changes to enable observatory port to enable easier debugging
    • Discussing crash seen during ALS
      • pvr_sync_file: pvr_sync_create_fence: Failed to get fd

[10734.765629] pvr_sync_file: pvr_sync_create_fence: Failed to get fd [10734.771904] PVR_K:(Error): 808: SyncCheckpointCreateFence failed to create new fence<00000000d53eba0e> for timeline<20> using sync checkpoint context<000000005216f1c0>, psNewSyncCheckpoint=<00000000aea179b3>, eError=PVRSRV_ERROR_UNABLE_TO_ADD_HANDLE [700] [10734.794614] PVR_K:(Error): 808: PVRSRVRGXKickTA3DKM: SyncCheckpointCreateFence[3D] failed (PVRSRV_ERROR_UNABLE_TO_ADD_HANDLE) [4299]

  • Noticed an about 4h timeout on the websocket connection to kuksa .
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
    • 7/27 - permissive mode submitted in gerrit and should be in M2
    • 8/10 - permissive mode released in Needlefish
    • 8/24 - no update
    • 9/21 - no update
    • 10/5 - no update
    • 12/14 - no update
  • IPC
    • 6/15 - Kuksa using web sockets for Needlefish. Major gRPC update is planned in kuksa.val in the next month or so which will be a candidate for Octopus. Scott discover an HVAC interface in VSS that we re-use and will be hooking up the green machine demo to use that instead of rewriting the HVAC binder that we currently have.
    • 6/29
      • Jose started working on the APIs from WebApps for launching apps. Will probably use gRPC.
    • 7/13
      • Work going on upstream to enhance gRPC support.
    • 7/27
      • Jose looking at gRPC for web app interface. Kuksa.val gRPC work in progress upstream.
    • 8/10
      • Jose on vacation
    • 8/24
      • Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year.
    • 9/21
      • Update of Kuksa.val under investigation
    • 12/14
      • Kuksa.val updated
  • New topics:

Next call Jan 11th 2023

November 16, 2022

Attendees: Walt, Jan-Simon, Scott, Marius, Denys

Application Framework Redesign

  • 9/21
    • gRPC version of applaunchd in progress
      • just merged in master
    • looking at running applaunchd as a separate user
      • depends on grpc version of the deamon
    • Documentation of applaunchd and app templates to be completed by September F2F
      • will be ready for postponed F2F
  • 10/5
    • Roger working on converting WAM to use gRPC applaunchd interface over the next month.
    • Documentation of applaunchd and app templates to be completed by October F2F
  • 11/16
    • Denys to look at systemd units and the kernel config to enable better sandboxing and add that to the app templates.
  • Flutter
  • 6/15 - got a few updates from Joel but no progress on the multiple app support yet.
  • 6/29 - Waiting for updates from Toyota. Due next week for M1.
  • 7/13 - Had separate call yesterday. Will get tag for needlefish, but need to enhance in a point release. Todos: try out multiple embedder instances e.g. under qt homescreen (→ Scott will try). Image for GSoC. (e.g.: https://github.com/aakash-s45/ic or https://github.com/hritik-chouhan/HVAC_dashboard)
  • 7/27
    • Flutter looking ok for M2. Scott working on app template (see above).
  • 8/10
    • Released for M3 and ready for final NN release
  • 8/24
    • Good progress being made. IVI PR call now every week in order to speed up progress.
    • Scott will move the Igalia home screen for flutter from the Igalia Github into an AGL repo and we will use that as a starting point for continued home screen work including the applaunchd work.
  • 9/21
    • 14.0.1 release pinned the Flutter SDK
    • Scott hacking on flutter-homescreen from Igalia, need to port to latest flutter
    • GSoC students finished or about to finish their apps.
    • Need code in embedder for window activation going forward
  • 10/5
    • Scott got to the point of being able to launch apps from the flutter home screen using applaunchd.
    • Discussed SPEC-4503 and how to proceed. Marius will do some prototyping and we will schedule a session during the F2F meeting to discuss.
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
    • 7/27 - permissive mode submitted in gerrit and should be in M2
    • 8/10 - permissive mode released in Needlefish
    • 8/24 - no update
    • 9/21 - no update
    • 10/5 - no update
  • IPC
    • 6/15 - Kuksa using web sockets for Needlefish. Major gRPC update is planned in kuksa.val in the next month or so which will be a candidate for Octopus. Scott discover an HVAC interface in VSS that we re-use and will be hooking up the green machine demo to use that instead of rewriting the HVAC binder that we currently have.
    • 6/29
      • Jose started working on the APIs from WebApps for launching apps. Will probably use gRPC.
    • 7/13
      • Work going on upstream to enhance gRPC support.
    • 7/27
      • Jose looking at gRPC for web app interface. Kuksa.val gRPC work in progress upstream.
    • 8/10
      • Jose on vacation
    • 8/24
      • Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year.
    • 9/21
      • Update of Kuksa.val under investigation
  • New topics:

October 5, 2022

Attendees: Walt, Jan-Simon, Scott, Marius, Roger, Jose, Denys

Application Framework Redesign

  • 9/21
    • gRPC version of applaunchd in progress
      • just merged in master
    • looking at running applaunchd as a separate user
      • depends on grpc version of the deamon
    • Documentation of applaunchd and app templates to be completed by September F2F
      • will be ready for postponed F2F
  • 10/5
    • Roger working on converting WAM to use gRPC applaunchd interface over the next month.
    • Documentation of applaunchd and app templates to be completed by October F2F
  • Flutter
  • 6/15 - got a few updates from Joel but no progress on the multiple app support yet.
  • 6/29 - Waiting for updates from Toyota. Due next week for M1.
  • 7/13 - Had separate call yesterday. Will get tag for needlefish, but need to enhance in a point release. Todos: try out multiple embedder instances e.g. under qt homescreen (→ Scott will try). Image for GSoC. (e.g.: https://github.com/aakash-s45/ic or https://github.com/hritik-chouhan/HVAC_dashboard)
  • 7/27
    • Flutter looking ok for M2. Scott working on app template (see above).
  • 8/10
    • Released for M3 and ready for final NN release
  • 8/24
    • Good progress being made. IVI PR call now every week in order to speed up progress.
    • Scott will move the Igalia home screen for flutter from the Igalia Github into an AGL repo and we will use that as a starting point for continued home screen work including the applaunchd work.
  • 9/21
    • 14.0.1 release pinned the Flutter SDK
    • Scott hacking on flutter-homescreen from Igalia, need to port to latest flutter
    • GSoC students finished or about to finish their apps.
    • Need code in embedder for window activation going forward
  • 10/5
    • Scott got to the point of being able to launch apps from the flutter home screen using applaunchd.
    • Discussed SPEC-4503 and how to proceed. Marius will do some prototyping and we will schedule a session during the F2F meeting to discuss.
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
    • 7/27 - permissive mode submitted in gerrit and should be in M2
    • 8/10 - permissive mode released in Needlefish
    • 8/24 - no update
    • 9/21 - no update
    • 10/5 - no update
  • IPC
    • 6/15 - Kuksa using web sockets for Needlefish. Major gRPC update is planned in kuksa.val in the next month or so which will be a candidate for Octopus. Scott discover an HVAC interface in VSS that we re-use and will be hooking up the green machine demo to use that instead of rewriting the HVAC binder that we currently have.
    • 6/29
      • Jose started working on the APIs from WebApps for launching apps. Will probably use gRPC.
    • 7/13
      • Work going on upstream to enhance gRPC support.
    • 7/27
      • Jose looking at gRPC for web app interface. Kuksa.val gRPC work in progress upstream.
    • 8/10
      • Jose on vacation
    • 8/24
      • Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year.
    • 9/21
      • Update of Kuksa.val under investigation
  • New topics:

August 24, 2022

Attendees: Walt, Scott, Jan-Simon, Marius, Aman, Jose, Ishii, Lorenzo, Denys

Application Framework Redesign

  • 7/13
    • Code for reworked application start/stop is in gerrit for review
    • https://gerrit.automotivelinux.org/gerrit/q/SPEC-4466
    • This is scheduled to go into M1
    • Currently we still use .desktop files for enumeration.
      • Todo: work on enumeration
      • Todo: single app template might not be sufficient for all cases (e.g. Webapps)
      • agl-app(-html5/-flutter)-* templates ?
      • extra metadata in desktop files vs systemd units
        • DISPLAYNAME - maybe use 'Description' field
        • ICON PATH - well known fixed path (/usr/share/AGL/icons/appname.svg ?)
    • How to enable a sandboxing feature in a recipe ?
    • Need to document workflow for:
      • build with standard sdk/cross-compiler + how to deploy binary and other necessary files
  • 7/27
    • Denys applaunchd patches were released for M1
    • Currently we still use .desktop files for enumeration.
      • WIP: enumeration- In progress by Scott. Should be ready for M2.
      • WIP: templates - single app template might not be sufficient for all cases (e.g. Webapps)
    • Need to document workflow for:
      • build with standard sdk/cross-compiler + how to deploy binary and other necessary files]
  • 8/10
    • Denys looking at running applaunchd as a separate user.
    • gRPC version of applaunchd in progress
    • Documentation of applaunchd and app templates to be completed by September F2F
  • 8/24
    • Denys was on vacation last week so not much progress
    • looking at running applaunchd as a separate user.
    • gRPC version of applaunchd in progress
    • Documentation of applaunchd and app templates to be completed by September F2F
  • Flutter
  • 6/15 - got a few updates from Joel but no progress on the multiple app support yet.
  • 6/29 - Waiting for updates from Toyota. Due next week for M1.
  • 7/13 - Had separate call yesterday. Will get tag for needlefish, but need to enhance in a point release. Todos: try out multiple embedder instances e.g. under qt homescreen (→ Scott will try). Image for GSoC. (e.g.: https://github.com/aakash-s45/ic or https://github.com/hritik-chouhan/HVAC_dashboard)
  • 7/27
    • Flutter looking ok for M2. Scott working on app template (see above).
  • 8/10
    • Released for M3 and ready for final NN release
  • 8/24
    • Good progress being made. IVI PR call now every week in order to speed up progress.
    • Scott will move the Igalia home screen for flutter from the Igalia Github into an AGL repo and we will use that as a starting point for continued home screen work including the applaunchd work.
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
    • 7/27 - permissive mode submitted in gerrit and should be in M2
    • 8/10 - permissive mode released in Needlefish
    • 8/24 - no update
  • IPC
    • 6/15 - Kuksa using web sockets for Needlefish. Major gRPC update is planned in kuksa.val in the next month or so which will be a candidate for Octopus. Scott discover an HVAC interface in VSS that we re-use and will be hooking up the green machine demo to use that instead of rewriting the HVAC binder that we currently have.
    • 6/29
      • Jose started working on the APIs from WebApps for launching apps. Will probably use gRPC.
    • 7/13
      • Work going on upstream to enhance gRPC support.
    • 7/27
      • Jose looking at gRPC for web app interface. Kuksa.val gRPC work in progress upstream.
    • 8/10
      • Jose on vacation
    • 8/24
      • Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year.
  • New topics:

August 10, 2022

Attendees: Walt, Jan-Simon, Scott, Denys, Aakash, Aman, Marius, Hritik

Application Framework Redesign

  • 7/13
    • Code for reworked application start/stop is in gerrit for review
    • https://gerrit.automotivelinux.org/gerrit/q/SPEC-4466
    • This is scheduled to go into M1
    • Currently we still use .desktop files for enumeration.
      • Todo: work on enumeration
      • Todo: single app template might not be sufficient for all cases (e.g. Webapps)
      • agl-app(-html5/-flutter)-* templates ?
      • extra metadata in desktop files vs systemd units
        • DISPLAYNAME - maybe use 'Description' field
        • ICON PATH - well known fixed path (/usr/share/AGL/icons/appname.svg ?)
    • How to enable a sandboxing feature in a recipe ?
    • Need to document workflow for:
      • build with standard sdk/cross-compiler + how to deploy binary and other necessary files
  • 7/27
    • Denys applaunchd patches were released for M1
    • Currently we still use .desktop files for enumeration.
      • WIP: enumeration- In progress by Scott. Should be ready for M2.
      • WIP: templates - single app template might not be sufficient for all cases (e.g. Webapps)
    • Need to document workflow for:
      • build with standard sdk/cross-compiler + how to deploy binary and other necessary files]
  • 8/10
    • Denys looking at running applaunchd as a separate user.
    • gRPC version of applaunchd in progress
    • Documentation of applaunchd and app templates to be completed by September F2F
  • Flutter
  • 6/15 - got a few updates from Joel but no progress on the multiple app support yet.
  • 6/29 - Waiting for updates from Toyota. Due next week for M1.
  • 7/13 - Had separate call yesterday. Will get tag for needlefish, but need to enhance in a point release. Todos: try out multiple embedder instances e.g. under qt homescreen (→ Scott will try). Image for GSoC. (e.g.: https://github.com/aakash-s45/ic or https://github.com/hritik-chouhan/HVAC_dashboard)
  • 7/27
    • Flutter looking ok for M2. Scott working on app template (see above).
  • 8/10
    • Released for M3 and ready for final NN release
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
    • 7/27 - permissive mode submitted in gerrit and should be in M2
    • 8/10 - permissive mode released in Needlefish
  • IPC
    • 6/15 - Kuksa using web sockets for Needlefish. Major gRPC update is planned in kuksa.val in the next month or so which will be a candidate for Octopus. Scott discover an HVAC interface in VSS that we re-use and will be hooking up the green machine demo to use that instead of rewriting the HVAC binder that we currently have.
    • 6/29
      • Jose started working on the APIs from WebApps for launching apps. Will probably use gRPC.
    • 7/13
      • Work going on upstream to enhance gRPC support.
    • 7/27
      • Jose looking at gRPC for web app interface. Kuksa.val gRPC work in progress upstream.
    • 8/10
      • Jose on vacation
  • New topics:

July 27, 2022

Attendees: Walt, Jan-Simon, Scott, Marius, Jose

Application Framework Redesign

  • 7/13
    • Code for reworked application start/stop is in gerrit for review
    • https://gerrit.automotivelinux.org/gerrit/q/SPEC-4466
    • This is scheduled to go into M1
    • Currently we still use .desktop files for enumeration.
      • Todo: work on enumeration
      • Todo: single app template might not be sufficient for all cases (e.g. Webapps)
      • agl-app(-html5/-flutter)-* templates ?
      • extra metadata in desktop files vs systemd units
        • DISPLAYNAME - maybe use 'Description' field
        • ICON PATH - well known fixed path (/usr/share/AGL/icons/appname.svg ?)
    • How to enable a sandboxing feature in a recipe ?
    • Need to document workflow for:
      • build with standard sdk/cross-compiler + how to deploy binary and other necessary files
  • 7/27
    • Denys applaunchd patches were released for M1
    • Currently we still use .desktop files for enumeration.
      • WIP: enumeration- In progress by Scott. Should be ready for M2.
      • WIP: templates - single app template might not be sufficient for all cases (e.g. Webapps)
    • Need to document workflow for:
      • build with standard sdk/cross-compiler + how to deploy binary and other necessary files
  • Flutter
  • 6/15 - got a few updates from Joel but no progress on the multiple app support yet.
  • 6/29 - Waiting for updates from Toyota. Due next week for M1.
  • 7/13 - Had separate call yesterday. Will get tag for needlefish, but need to enhance in a point release. Todos: try out multiple embedder instances e.g. under qt homescreen (→ Scott will try). Image for GSoC. (e.g.: https://github.com/aakash-s45/ic or https://github.com/hritik-chouhan/HVAC_dashboard)
  • 7/27
    • Flutter looking ok for M2. Scott working on app template (see above).
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
    • 7/27 - permissive mode submitted in gerrit and should be in M2
  • IPC
    • 6/15 - Kuksa using web sockets for Needlefish. Major gRPC update is planned in kuksa.val in the next month or so which will be a candidate for Octopus. Scott discover an HVAC interface in VSS that we re-use and will be hooking up the green machine demo to use that instead of rewriting the HVAC binder that we currently have.
    • 6/29
      • Jose started working on the APIs from WebApps for launching apps. Will probably use gRPC.
    • 7/13
      • Work going on upstream to enhance gRPC support.
    • 7/27
      • Jose looking at gRPC for web app interface. Kuksa.val gRPC work in progress upstream.
  • New topics:

July 13, 2022

Attendees: Jan-Simon, Scott, Denys, Marius, Ishii-san

Application Framework Redesign

  • 4/20
    • Someone from Konsulko will be starting to work on this half-time starting in the next two weeks. Should get that person to Berlin for the F2F as well.
    • Marius opened SPEC-4236 to discuss the Flutter integration to AGL. Please review that conversation with Joel and provide feedback. Joel also added some comments to the Confluence requirements page.
  • 6/1
    • Applaunchd rework started by Denys. He received reference hardware and is getting it set up.
    • First thing to get done is to switch to systemd units. Asked Denys to provide an idea for a plan during the Tuesday dev call.
    • Marius asked if this will be a knife-switch. Will we deprecate the current spawning mechanism once this is added. Initial thought is that the new mechanism will be the only one available for the Needlefish release.
    • gRPC is seen as a follow-on effort, but will be available later in the Needlefish development cycle.
  • 6/15
    • Denis activities since last meeting
      • Going over the existing applaunchd source code, learning how it enumerates the apps, parses corresponding .desktop files, handles d-bus calls and signals and spawns the app
      • Experimented with converting sample apps into systemd units - found first limitation of systemd sandboxing only working on system-level services (i.e. root-owned), but not on user-level services
      • The workaround is for the system-level services to drop root privileges and run the apps under a regular “agl-driver” user by specifying User=agl-driver in the unit file
      • Another limitation of this approach is that agl-driver user normally won't have necessary permissions to start/stop those systemd services
      • Discussed with Scott and contemplated running applauchd as root,instead of a regular agl-driver user
      • For now came up with a PolKit rule that slightly elevates agl-driver permissions in order to start/stop specific services by name, e.g.those that start with “agl-app” prefix
      • Experimented with systemd templating and overriding mechanism
      • Came up with an approach that allows using a single generic template for all the apps, but also allows overriding individual settings for sandboxing purposes (e.g. disable network, protect directories, etc.) or completely override the entire unit, in case a custom oneis required for some apps
    • In-Meeting Discussion
    • Discussed adding a separate user for applaunchd that is not agl-driver and possibly run the compositor as a different user than the apps. Applaunchd should not run as root.
    • Authorization and policy management would need to be built in later but the initial sandboxing should provide us the framework for building it in later.
    • Plan for NN M1 is to have applaunchd converted to systemd, have the ability to start/stop apps, and have a preliminary version of the template available. Will review at the next EG meeting in two weeks.
  • 6/29
    • Denys gave a demo of the systemd sandboxing capabilities and start/stop of applications that is ready for M1.
    • Conversion of all of the existing apps will be completed for M2. Services will come later.
    • Denys will create a sandbox branch to help facilitate reviewing the code.
  • 7/13
    • Code for reworked application start/stop is in gerrit for review
    • https://gerrit.automotivelinux.org/gerrit/q/SPEC-4466
    • This is scheduled to go into M1
    • Currently we still use .desktop files for enumeration.
      • Todo: work on enumeration
      • Todo: single app template might not be sufficient for all cases (e.g. Webapps)
      • agl-app(-html5/-flutter)-* templates ?
      • extra metadata in desktop files vs systemd units
        • DISPLAYNAME - maybe use 'Description' field
        • ICON PATH - well known fixed path (/usr/share/AGL/icons/appname.svg ?)
    • How to enable a sandboxing feature in a recipe ?
    • Need to document workflow for:
      • build with standard sdk/cross-compiler + how to deploy binary and other necessary files
  • Flutter
  • 6/15 - got a few updates from Joel but no progress on the multiple app support yet.
  • 6/29 - Waiting for updates from Toyota. Due next week for M1.
  • 7/13 - Had separate call yesterday. Will get tag for needlefish, but need to enhance in a point release. Todos: try out multiple embedder instances e.g. under qt homescreen (→ Scott will try). Image for GSoC. (e.g.: https://github.com/aakash-s45/ic or https://github.com/hritik-chouhan/HVAC_dashboard)
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation.
    • 7/13 - Scott is starting today. Starting with permissive mode.
  • IPC
    • 6/15 - Kuksa using web sockets for Needlefish. Major gRPC update is planned in kuksa.val in the next month or so which will be a candidate for Octopus. Scott discover an HVAC interface in VSS that we re-use and will be hooking up the green machine demo to use that instead of rewriting the HVAC binder that we currently have.
    • 6/29
      • Jose started working on the APIs from WebApps for launching apps. Will probably use gRPC.
    • 7/13
      • Work going on upstream to enhance gRPC support.
  • New topics:

June 29, 2022

Attendees: Walt, Jan-Simon, Jose, Denys, Marius, Lorenzo

Application Framework Redesign

  • 4/20
    • Someone from Konsulko will be starting to work on this half-time starting in the next two weeks. Should get that person to Berlin for the F2F as well.
    • Marius opened SPEC-4236 to discuss the Flutter integration to AGL. Please review that conversation with Joel and provide feedback. Joel also added some comments to the Confluence requirements page.
  • 6/1
    • Applaunchd rework started by Denys. He received reference hardware and is getting it set up.
    • First thing to get done is to switch to systemd units. Asked Denys to provide an idea for a plan during the Tuesday dev call.
    • Marius asked if this will be a knife-switch. Will we deprecate the current spawning mechanism once this is added. Initial thought is that the new mechanism will be the only one available for the Needlefish release.
    • gRPC is seen as a follow-on effort, but will be available later in the Needlefish development cycle.
  • 6/15
    • Denis activities since last meeting
      • Going over the existing applaunchd source code, learning how it enumerates the apps, parses corresponding .desktop files, handles d-bus calls and signals and spawns the app
      • Experimented with converting sample apps into systemd units - found first limitation of systemd sandboxing only working on system-level services (i.e. root-owned), but not on user-level services
      • The workaround is for the system-level services to drop root privileges and run the apps under a regular “agl-driver” user by specifying User=agl-driver in the unit file
      • Another limitation of this approach is that agl-driver user normally won't have necessary permissions to start/stop those systemd services
      • Discussed with Scott and contemplated running applauchd as root,instead of a regular agl-driver user
      • For now came up with a PolKit rule that slightly elevates agl-driver permissions in order to start/stop specific services by name, e.g.those that start with “agl-app” prefix
      • Experimented with systemd templating and overriding mechanism
      • Came up with an approach that allows using a single generic template for all the apps, but also allows overriding individual settings for sandboxing purposes (e.g. disable network, protect directories, etc.) or completely override the entire unit, in case a custom oneis required for some apps
    • In-Meeting Discussion
    • Discussed adding a separate user for applaunchd that is not agl-driver and possibly run the compositor as a different user than the apps. Applaunchd should not run as root.
    • Authorization and policy management would need to be built in later but the initial sandboxing should provide us the framework for building it in later.
    • Plan for NN M1 is to have applaunchd converted to systemd, have the ability to start/stop apps, and have a preliminary version of the template available. Will review at the next EG meeting in two weeks.
  • 6/29
    • Denys gave a demo of the systemd sandboxing capabilities and start/stop of applications that is ready for M1.
    • Conversion of all of the existing apps will be completed for M2. Services will come later.
    • Denys will create a sandbox branch to help facilitate reviewing the code.
  • FLutter
  • 6/15 - got a few updates from Joel but no progress on the multiple app support yet.
  • 6/29 - Waiting for updates from Toyota. Due next week for M1.
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
    • 6/29 - Scott on vacation,
  • IPC
    • 6/15 - Kuksa using web sockets for Needlefish. Major gRPC update is planned in kuksa.val in the next month or so which will be a candidate for Octopus. Scott discover an HVAC interface in VSS that we re-use and will be hooking up the green machine demo to use that instead of rewriting the HVAC binder that we currently have.
    • 6/29
      • Jose started working on the APIs from WebApps for launching apps. Will probably use gRPC.
  • New topics:

June 15, 2022

Attendees: Walt, Jan-Simon, Scott, Jose, Denys, Marius

Application Framework Redesign

  • 4/20
    • Someone from Konsulko will be starting to work on this half-time starting in the next two weeks. Should get that person to Berlin for the F2F as well.
    • Marius opened SPEC-4236 to discuss the Flutter integration to AGL. Please review that conversation with Joel and provide feedback. Joel also added some comments to the Confluence requirements page.
  • 6/1
    • Applaunchd rework started by Denys. He received reference hardware and is getting it set up.
    • First thing to get done is to switch to systemd units. Asked Denys to provide an idea for a plan during the Tuesday dev call.
    • Marius asked if this will be a knife-switch. Will we deprecate the current spawning mechanism once this is added. Initial thought is that the new mechanism will be the only one available for the Needlefish release.
    • gRPC is seen as a follow-on effort, but will be available later in the Needlefish development cycle.
  • 6/15
    • Denis activities since last meeting
      • Going over the existing applaunchd source code, learning how it enumerates the apps, parses corresponding .desktop files, handles d-bus calls and signals and spawns the app
      • Experimented with converting sample apps into systemd units - found first limitation of systemd sandboxing only working on system-level services (i.e. root-owned), but not on user-level services
      • The workaround is for the system-level services to drop root privileges and run the apps under a regular “agl-driver” user by specifying User=agl-driver in the unit file
      • Another limitation of this approach is that agl-driver user normally won't have necessary permissions to start/stop those systemd services
      • Discussed with Scott and contemplated running applauchd as root,instead of a regular agl-driver user
      • For now came up with a PolKit rule that slightly elevates agl-driver permissions in order to start/stop specific services by name, e.g.those that start with “agl-app” prefix
      • Experimented with systemd templating and overriding mechanism
      • Came up with an approach that allows using a single generic template for all the apps, but also allows overriding individual settings for sandboxing purposes (e.g. disable network, protect directories, etc.) or completely override the entire unit, in case a custom oneis required for some apps
    • In-Meeting Discussion
    • Discussed adding a separate user for applaunchd that is not agl-driver and possibly run the compositor as a different user than the apps. Applaunchd should not run as root.
    • Authorization and policy management would need to be built in later but the initial sandboxing should provide us the framework for building it in later.
    • Plan for NN M1 is to have applaunchd converted to systemd, have the ability to start/stop apps, and have a preliminary version of the template available. Will review at the next EG meeting in two weeks.
  • FLutter
  • 6/15 - got a few updates from Joel but no progress on the multiple app support yet.
  • SELinux
    • 6/15 - SPEC-4332 SELinux not available for NN yet. Scott will look at after EW.
  • IPC
    • 6/15 - Kuksa using web sockets for Needlefish. Major gRPC update is planned in kuksa.val in the next month or so which will be a candidate for Octopus. Scott discover an HVAC interface in VSS that we re-use and will be hooking up the green machine demo to use that instead of rewriting the HVAC binder that we currently have.
  • New topics:

June 1, 2022

Attendees: Walt, Jan-Simon, Scott, Jose, Marius, Denys

Application Framework Redesign

  • 4/20
    • Someone from Konsulko will be starting to work on this half-time starting in the next two weeks. Should get that person to Berlin for the F2F as well.
    • Marius opened SPEC-4236 to discuss the Flutter integration to AGL. Please review that conversation with Joel and provide feedback. Joel also added some comments to the Confluence requirements page.
  • 6/1
    • Applaunchd rework started by Denys. He received reference hardware and is getting it set up.
    • First thing to get done is to switch to systemd units. Asked Denys to provide an idea for a plan during the Tuesday dev call.
    • Marius asked if this will be a knife-switch. Will we deprecate the current spawning mechanism once this is added. Initial thought is that the new mechanism will be the only one available for the Needlefish release.
    • gRPC is seen as a follow-on effort, but will be available later in the Needlefish development cycle.
  • FLutter
  • 2/9 - FIXME - add status from dev call yesterday. Plan for changing to AGL compositor is unknown.
  • 4/20 - See SPEC-4236 for discussion.
  • CIAT
    • 1/12 - HTML5 and flutter work is in progress. CI scripts are ready and uploaded. Waiting for something to be ready to build on master.
    • 2/9 - QEMU x86-64 is up and running for HTML5. Flutter needs to be added as part of M2.
    • 4/20 - Need to restore some mechanism to perform CIAT on the applications on master.
      • Need to rethink the mechanism for tagging apps since they currently float in git.
  • SELinux
    • 2/9 - Plan is to enable SELinux in permissive mode on master after Marlin branch is cut and we have updated to Kirkstone (YP 3.5). Walt to write a Jira ticket. Scott will test out turning on the layer on the AGL-next branch.
    • 4/20 - SPEC-4332 created for SELinux.
  • IPC
    • 2/9 - Need to deter
    • mine plan for Needlefish. Do we support gRPC? Websockets as default?
  • New topics:

March 23, 2022

Attendees: Walt, Jan-Simon, Scott, Du, Marius, Lorenzo

Application Framework Redesign

  • 12/15
  • 1/12
    • applaunchd patches should be submitted today.
  • 2/9
    • Documentation in progress for Marlin release. Arnaud expects to be ready to submit to gerrit by Friday. Documentation will appear here.
    • Toyota will review the documentation and suggest improvements to the implementation. Date-san can decide whether to post the improvements in Confluence or Jira depending on the scope of the changes.
  • 2/23
    • Documentation reviewed as part of gerrit 27166. Date-san said that IPC and notification mechanisms are in legal review at Toyota. Part of the IPC has been disclosed previously as part of base-system. Toyota will review document again and provide feedback in gerrit.
    • Meanwhile Toyota can provide requirements to the app FW effort as it evolves this year.
    • Discussed possible IPC mechanisms for WAM. Jose's proposal is to use javascript for a limited set of specific APIs. Scott brought up maintenance difficulties with having to update WAM every time a new API is added. Discussed gRPC as default mechanism and/or a proxy mechanism.
    • Flutter IPC is under development within Toyota.
  • 3/1
    • Scott added a write up of the current state and possible future roadmap to Confluence and gave an overview of the proposed roadmap.
      • Need additional app lifecycle requirements
      • Jose liked the idea of using the mixer as an initial implementation of gRPC that could be used by WAF.
      • Asking for people to review and comment in Confluence
      • Walt will take the roadmap as discussed in Confluence and add it to the roadmap spreadsheet.
      • Date-san asked for comments on base system and it's gaps with these requirements.
  • FLutter
  • 2/9 - FIXME - add status from dev call yesterday. Plan for changing to AGL compositor is unknown.
  • CIAT
    • 1/12 - HTML5 and flutter work is in progress. CI scripts are ready and uploaded. Waiting for something to be ready to build on master.
    • 2/9 - QEMU x86-64 is up and running for HTML5. Flutter needs to be added as part of M2.
  • SELinux
    • 2/9 - Plan is to enable SELinux in permissive mode on master after Marlin branch is cut and we have updated to Kirkstone (YP 3.5). Walt to write a Jira ticket. Scott will test out turning on the layer on the AGL-next branch.
  • IPC
    • 2/9 - Need to deter
    • mine plan for Needlefish. Do we support gRPC? Websockets as default?
  • New topics:

March 9, 2022

Attendees: Walt, Jan-Simon, Scott, Jose, Konagaya, Marius, Ishii, Lorenzo, Daniel

Application Framework Redesign

  • 12/15
  • 1/12
    • applaunchd patches should be submitted today.
  • 2/9
    • Documentation in progress for Marlin release. Arnaud expects to be ready to submit to gerrit by Friday. Documentation will appear here.
    • Toyota will review the documentation and suggest improvements to the implementation. Date-san can decide whether to post the improvements in Confluence or Jira depending on the scope of the changes.
  • 2/23
    • Documentation reviewed as part of gerrit 27166. Date-san said that IPC and notification mechanisms are in legal review at Toyota. Part of the IPC has been disclosed previously as part of base-system. Toyota will review document again and provide feedback in gerrit.
    • Meanwhile Toyota can provide requirements to the app FW effort as it evolves this year.
    • Discussed possible IPC mechanisms for WAM. Jose's proposal is to use javascript for a limited set of specific APIs. Scott brought up maintenance difficulties with having to update WAM every time a new API is added. Discussed gRPC as default mechanism and/or a proxy mechanism.
    • Flutter IPC is under development within Toyota.
  • 3/1
    • Scott added a write up of the current state and possible future roadmap to Confluence and gave an overview of the proposed roadmap.
      • Need additional app lifecycle requirements
      • Jose liked the idea of using the mixer as an initial implementation of gRPC that could be used by WAF.
      • Asking for people to review and comment in Confluence
      • Walt will take the roadmap as discussed in Confluence and add it to the roadmap spreadsheet.
      • Date-san asked for comments on base system and it's gaps with these requirements.
  • FLutter
  • 2/9 - FIXME - add status from dev call yesterday. Plan for changing to AGL compositor is unknown.
  • CIAT
    • 1/12 - HTML5 and flutter work is in progress. CI scripts are ready and uploaded. Waiting for something to be ready to build on master.
    • 2/9 - QEMU x86-64 is up and running for HTML5. Flutter needs to be added as part of M2.
  • SELinux
    • 2/9 - Plan is to enable SELinux in permissive mode on master after Marlin branch is cut and we have updated to Kirkstone (YP 3.5). Walt to write a Jira ticket. Scott will test out turning on the layer on the AGL-next branch.
  • IPC
    • 2/9 - Need to deter
    • mine plan for Needlefish. Do we support gRPC? Websockets as default?
  • New topics:

March 1, 2022

Attendees: Walt, Jan-Simon, Scott, Jose, Marius, Date, Arnaud, Kurokawa, Daniel

Special Meeting to to discuss App FW redesign.

Application Framework Redesign

  • 12/15
  • 1/12
    • applaunchd patches should be submitted today.
  • 2/9
    • Documentation in progress for Marlin release. Arnaud expects to be ready to submit to gerrit by Friday. Documentation will appear here.
    • Toyota will review the documentation and suggest improvements to the implementation. Date-san can decide whether to post the improvements in Confluence or Jira depending on the scope of the changes.
  • 2/23
    • Documentation reviewed as part of gerrit 27166. Date-san said that IPC and notification mechanisms are in legal review at Toyota. Part of the IPC has been disclosed previously as part of base-system. Toyota will review document again and provide feedback in gerrit.
    • Meanwhile Toyota can provide requirements to the app FW effort as it evolves this year.
    • Discussed possible IPC mechanisms for WAM. Jose's proposal is to use javascript for a limited set of specific APIs. Scott brought up maintenance difficulties with having to update WAM every time a new API is added. Discussed gRPC as default mechanism and/or a proxy mechanism.
    • Flutter IPC is under development within Toyota.
  • 3/1
    • Scott added a write up of the current state and possible future roadmap to Confluence and gave an overview of the proposed roadmap.
      • Need additional app lifecycle requirements
      • Jose liked the idea of using the mixer as an initial implementation of gRPC that could be used by WAF.
      • Asking for people to review and comment in Confluence
      • Walt will take the roadmap as discussed in Confluence and add it to the roadmap spreadsheet.
      • Date-san asked for comments on base system and it's gaps with these requirements.
  • FLutter
  • 2/9 - FIXME - add status from dev call yesterday. Plan for changing to AGL compositor is unknown.
  • CIAT
    • 1/12 - HTML5 and flutter work is in progress. CI scripts are ready and uploaded. Waiting for something to be ready to build on master.
    • 2/9 - QEMU x86-64 is up and running for HTML5. Flutter needs to be added as part of M2.
  • SELinux
    • 2/9 - Plan is to enable SELinux in permissive mode on master after Marlin branch is cut and we have updated to Kirkstone (YP 3.5). Walt to write a Jira ticket. Scott will test out turning on the layer on the AGL-next branch.
  • IPC
    • 2/9 - Need to deter
    • mine plan for Needlefish. Do we support gRPC? Websockets as default?
  • New topics:

February 23, 2022

Attendees: Walt, Jan-Simon, Scott, Lorenzo, Konagaya, Jose, Daniel, Marius, Date, Arnaud,

Application Framework Redesign

  • 12/15
  • 1/12
    • applaunchd patches should be submitted today.
  • 2/9
    • Documentation in progress for Marlin release. Arnaud expects to be ready to submit to gerrit by Friday. Documentation will appear here.
    • Toyota will review the documentation and suggest improvements to the implementation. Date-san can decide whether to post the improvements in Confluence or Jira depending on the scope of the changes.
  • 2/23
    • Documentation reviewed as part of gerrit 27166. Date-san said that IPC and notification mechanisms are in legal review at Toyota. Part of the IPC has been disclosed previously as part of base-system. Toyota will review document again and provide feedback in gerrit.
    • Meanwhile Toyota can provide requirements to the app FW effort as it evolves this year.
    • Discussed possible IPC mechanisms for WAM. Jose's proposal is to use javascript for a limited set of specific APIs. Scott brought up maintenance difficulties with having to update WAM every time a new API is added. Discussed gRPC as default mechanism and/or a proxy mechanism.
    • Flutter IPC is under development within Toyota.
  • FLutter
  • 2/9 - FIXME - add status from dev call yesterday. Plan for changing to AGL compositor is unknown.
  • CIAT
    • 1/12 - HTML5 and flutter work is in progress. CI scripts are ready and uploaded. Waiting for something to be ready to build on master.
    • 2/9 - QEMU x86-64 is up and running for HTML5. Flutter needs to be added as part of M2.
  • SELinux
    • 2/9 - Plan is to enable SELinux in permissive mode on master after Marlin branch is cut and we have updated to Kirkstone (YP 3.5). Walt to write a Jira ticket. Scott will test out turning on the layer on the AGL-next branch.
  • IPC
    • 2/9 - Need to deter
    • mine plan for Needlefish. Do we support gRPC? Websockets as default?
  • New topics:

February 9, 2022

Attendees: Walt, Jan-Simon, Scott, Marius, Arnaud, Takeuchi, Date, Konagaya

Application Framework Redesign

  • 12/15
  • 1/12
    • applaunchd patches should be submitted today.
  • 2/9
    • Documentation in progress for Marlin release. Arnaud expects to be ready to submit to gerrit by Friday. Documentation will appear here.
    • Toyota will review the documentation and suggest improvements to the implementation. Date-san can decide whether to post the improvements in Confluence or Jira depending on the scope of the changes.
  • FLutter
  • 2/9 - FIXME - add status from dev call yesterday. Plan for changing to AGL compositor is unknown.
  • CIAT
    • 1/12 - HTML5 and flutter work is in progress. CI scripts are ready and uploaded. Waiting for something to be ready to build on master.
    • 2/9 - QEMU x86-64 is up and running for HTML5. Flutter needs to be added as part of M2.
  • SELinux
    • 2/9 - Plan is to enable SELinux in permissive mode on master after Marlin branch is cut and we have updated to Kirkstone (YP 3.5). Walt to write a Jira ticket. Scott will test out turning on the layer on the AGL-next branch.
  • IPC
    • 2/9 - Need to determine plan for Needlefish. Do we support gRPC? Websockets as default?
  • New topics:

January 29, 2022

Meeting Canceled

January 12, 2022

Attendees: Walt, Jan-Simon, Scott, Marius, Ishii, Daniel, Arnaud

Application Framework Redesign

  • WAM and Flutter (SPEC-3876)
    • 12/1
      • Lorenzo working on getting Chromium and WAM working again. Should be able to make more progress once Arnaud's changes are merged in the next week or two.
    • 12/15
      • Reworking parts of WAM. Plan is to bring-back individual webapps, need to handle activation of apps for that in master.
  • CIAT
    • 1/12 - HTML5 and flutter work is in progress. CI scripts are ready and uploaded. Waiting for something to be ready to build on master.
  • New topics:

December 15, 2021

Attendees: Walt, Jan-Simon, Scott, Daniel, Lorenzo, Arnaud,

Application Framework Redesign

  • 7/28
    • Arnaud introduced himself as a new member of the team looking at Application Framework topics. Started looking at building flatpak and the work started by Codethink. The engineer working on this at Codethink moved on to another project. Javier is hoping to find someone else to look it.
    • Need to think about where the code will reside long-term. Is there an upstream project we can give this (YP, oe, meta-virtualization, RedHat).
  • 8/11
    • No update
  • 9/8
    • Arnaud back from vacation.
    • Sam showed a demo of AGL running on flatpak built from meta-flatpak.
    • Discussed replacing SMACK with SELinux/None option. Daniel needs to discuss with Simon.
    • Next steps for App FW
      • Need instructions for building with flatpak and how to build apps so people can start playing with QEMU as target.
      • Make sandbox available in the next two weeks
      • Daniel and Arnaud to work on documenting adding system level services.
    • 9/22
      • Sam will be transitioning to Richard Maw for their meta-flatpak work.
    • 10/6
      • Discussed the plan that Arnaud sent to Walt for next steps with the App FW. Arnaud will update the email and send it to the mail list later this week.
      • Discussed how to get the flatpak run-time into the AGL build. Scott to open Jira ticket to track.
      • Repo for meta-flatpack is in Github https://github.com/flatpak/meta-flatpak.
      • Initial work will be done with no LSM enabled. Scott suggested as an option that we start with SELinux in non-enforcing mode. Daniel will take a look at what can be done there.
    • 11/3
      • SPEC-4121 - removal of app FW from master will be merged later this week. Scott has a home screen hacked up that potentially could be added after the merge. Arnaud and Marius are working on the new launcher to be added in the next few weeks.
    • 11/17
      • Status update and discussion on next steps:
        • split lifecycle into separate daemon
        • rework homescreen and possibly merge launcher into homescreen
        • upload for review and discussion
        • milestone 1 can be delayed
    • 12/1
      • Arnaud's first patches are in review in gerrit (SPEC-4121). Discussed whether the patches should be in meta-agl-demo or a sub-layer under meta-agl. Arnaud will move the changes under meta-agl/…/app-fw. Jan-Simon will set up the stub for the layout and Arnaud will resubmit the changes.
      • Next set of changes will be for home screen and launcher daemon, then the launcher. Those will be uploaded in the next day or two.
      • Scott can upload changes for a number of apps within a day or two of the launcher being uploaded.
    • 12/15
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
    • 8/11 - Work ongoing on the launcher and UI part of hvac .
    • 11/3
      • WAM Upstream changes to remove Qt dependencies.
      • Chromium 84 to 87
      • Need to re-add Chromium and WAM after App FW removal.
    • 12/1
      • Lorenzo working on getting Chromium and WAM working again. Should be able to make more progress once Arnaud's changes are merged in the next week or two.
    • 12/15
      • Reworking parts of WAM. Plan is to bring-back individual webapps, need to handle activation of apps for that in master.
  • New topics:
    • html5 and flutter image being added to CI

Next call in 4 weeks

December 1, 2021

Attendees: Walt, Jan-Simon, Scott, Ishii, Marius, Lorenzo, Arnaud, Daniel

Application Framework Redesign

  • 7/28
    • Arnaud introduced himself as a new member of the team looking at Application Framework topics. Started looking at building flatpak and the work started by Codethink. The engineer working on this at Codethink moved on to another project. Javier is hoping to find someone else to look it.
    • Need to think about where the code will reside long-term. Is there an upstream project we can give this (YP, oe, meta-virtualization, RedHat).
  • 8/11
    • No update
  • 9/8
    • Arnaud back from vacation.
    • Sam showed a demo of AGL running on flatpak built from meta-flatpak.
    • Discussed replacing SMACK with SELinux/None option. Daniel needs to discuss with Simon.
    • Next steps for App FW
      • Need instructions for building with flatpak and how to build apps so people can start playing with QEMU as target.
      • Make sandbox available in the next two weeks
      • Daniel and Arnaud to work on documenting adding system level services.
    • 9/22
      • Sam will be transitioning to Richard Maw for their meta-flatpak work.
    • 10/6
      • Discussed the plan that Arnaud sent to Walt for next steps with the App FW. Arnaud will update the email and send it to the mail list later this week.
      • Discussed how to get the flatpak run-time into the AGL build. Scott to open Jira ticket to track.
      • Repo for meta-flatpack is in Github https://github.com/flatpak/meta-flatpak.
      • Initial work will be done with no LSM enabled. Scott suggested as an option that we start with SELinux in non-enforcing mode. Daniel will take a look at what can be done there.
    • 11/3
      • SPEC-4121 - removal of app FW from master will be merged later this week. Scott has a home screen hacked up that potentially could be added after the merge. Arnaud and Marius are working on the new launcher to be added in the next few weeks.
    • 11/17
      • Status update and discussion on next steps:
        • split lifecycle into separate daemon
        • rework homescreen and possibly merge launcher into homescreen
        • upload for review and discussion
        • milestone 1 can be delayed
    • 12/1
      • Arnaud's first patches are in review in gerrit (SPEC-4121). Discussed whether the patches should be in meta-agl-demo or a sub-layer under meta-agl. Arnaud will move the changes under meta-agl/…/app-fw. Jan-Simon will set up the stub for the layout and Arnaud will resubmit the changes.
      • Next set of changes will be for home screen and launcher daemon, then the launcher. Those will be uploaded in the next day or two.
      • Scott can upload changes for a number of apps within a day or two of the launcher being uploaded.
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
    • 8/11 - Work ongoing on the launcher and UI part of hvac .
    • 11/3
      • WAM Upstream changes to remove Qt dependencies.
      • Chromium 84 to 87
      • Need to re-add Chromium and WAM after App FW removal.
    • 12/1
      • Lorenzo working on getting Chromium and WAM working again. Should be able to make more progress once Arnaud's changes are merged in the next week or two.
  • New topics:

November 17, 2021

Attendees: Walt, Jan-Simon, Arnaud, Daniel, Ishii-san, Paul, Scott

Application Framework Redesign

  • 7/28
    • Arnaud introduced himself as a new member of the team looking at Application Framework topics. Started looking at building flatpak and the work started by Codethink. The engineer working on this at Codethink moved on to another project. Javier is hoping to find someone else to look it.
    • Need to think about where the code will reside long-term. Is there an upstream project we can give this (YP, oe, meta-virtualization, RedHat).
  • 8/11
    • No update
  • 9/8
    • Arnaud back from vacation.
    • Sam showed a demo of AGL running on flatpak built from meta-flatpak.
    • Discussed replacing SMACK with SELinux/None option. Daniel needs to discuss with Simon.
    • Next steps for App FW
      • Need instructions for building with flatpak and how to build apps so people can start playing with QEMU as target.
      • Make sandbox available in the next two weeks
      • Daniel and Arnaud to work on documenting adding system level services.
    • 9/22
      • Sam will be transitioning to Richard Maw for their meta-flatpak work.
    • 10/6
      • Discussed the plan that Arnaud sent to Walt for next steps with the App FW. Arnaud will update the email and send it to the mail list later this week.
      • Discussed how to get the flatpak run-time into the AGL build. Scott to open Jira ticket to track.
      • Repo for meta-flatpack is in Github https://github.com/flatpak/meta-flatpak.
      • Initial work will be done with no LSM enabled. Scott suggested as an option that we start with SELinux in non-enforcing mode. Daniel will take a look at what can be done there.
    • 11/3
      • SPEC-4121 - removal of app FW from master will be merged later this week. Scott has a home screen hacked up that potentially could be added after the merge. Arnaud and Marius are working on the new launcher to be added in the next few weeks.
    • 11/17
      • Status update and discussion on next steps:
        • split lifecycle into separate daemon
        • rework homescreen and possibly merge launcher into homescreen
        • upload for review and discussion
        • milestone 1 can be delayed
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
    • 8/11 - Work ongoing on the launcher and UI part of hvac .
    • 11/3
      • WAM Upstream changes to remove Qt dependencies.
      • Chromium 84 to 87
      • Need to re-add Chromium and WAM after App FW removal.
    • 11/17
  • New topics:

November 3, 2021

Attendees: Walt, Jan-Simon, Scott, Arnaud, Marius, Lorenzo, Sergio

Application Framework Redesign

  • 7/28
    • Arnaud introduced himself as a new member of the team looking at Application Framework topics. Started looking at building flatpak and the work started by Codethink. The engineer working on this at Codethink moved on to another project. Javier is hoping to find someone else to look it.
    • Need to think about where the code will reside long-term. Is there an upstream project we can give this (YP, oe, meta-virtualization, RedHat).
  • 8/11
    • No update
  • 9/8
    • Arnaud back from vacation.
    • Sam showed a demo of AGL running on flatpak built from meta-flatpak.
    • Discussed replacing SMACK with SELinux/None option. Daniel needs to discuss with Simon.
    • Next steps for App FW
      • Need instructions for building with flatpak and how to build apps so people can start playing with QEMU as target.
      • Make sandbox available in the next two weeks
      • Daniel and Arnaud to work on documenting adding system level services.
    • 9/22
      • Sam will be transitioning to Richard Maw for their meta-flatpak work.
    • 10/6
      • Discussed the plan that Arnaud sent to Walt for next steps with the App FW. Arnaud will update the email and send it to the mail list later this week.
      • Discussed how to get the flatpak run-time into the AGL build. Scott to open Jira ticket to track.
      • Repo for meta-flatpack is in Github https://github.com/flatpak/meta-flatpak.
      • Initial work will be done with no LSM enabled. Scott suggested as an option that we start with SELinux in non-enforcing mode. Daniel will take a look at what can be done there.
    • 11/3
      • SPEC-4121 - removal of app FW from master will be merged later this week. Scott has a home screen hacked up that potentially could be added after the merge. Arnaud and Marius are working on the new launcher to be added in the next few weeks.
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
    • 8/11 - Work ongoing on the launcher and UI part of hvac .
    • 11/3
      • WAM Upstream changes to remove Qt dependencies.
      • Chromium 84 to 87
      • Need to re-ad Chromium and WAM after App FW removal.
  • New topics:
  • Criteria for M1
    • Working home screen, laucncher, dashboard, and settings apps
  • Criteria for release
    • Bluetooth, media player (TBD exactly what and how) and Nav

October 6, 2021

Attendees: Walt, Scott, Guy, Arnaud, Daniel, Kurokawa, Javier, Marius, Sergio

Application Framework Redesign

  • 7/28
    • Arnaud introduced himself as a new member of the team looking at Application Framework topics. Started looking at building flatpak and the work started by Codethink. The engineer working on this at Codethink moved on to another project. Javier is hoping to find someone else to look it.
    • Need to think about where the code will reside long-term. Is there an upstream project we can give this (YP, oe, meta-virtualization, RedHat).
  • 8/11
    • No update
  • 9/8
    • Arnaud back from vacation.
    • Sam showed a demo of AGL running on flatpak built from meta-flatpak.
    • Discussed replacing SMACK with SELinux/None option. Daniel needs to discuss with Simon.
    • Next steps for App FW
      • Need instructions for building with flatpak and how to build apps so people can start playing with QEMU as target.
      • Make sandbox available in the next two weeks
      • Daniel and Arnaud to work on documenting adding system level services.
    • 9/22
      • Sam will be transitioning to Richard Maw for their meta-flatpak work.
    • 10/6
      • Discussed the plan that Arnaud sent to Walt for next steps with the App FW. Arnaud will update the email and send it to the mail list later this week.
      • Discussed how to get the flatpak run-time into the AGL build. Scott to open Jira ticket to track.
      • Repo for meta-flatpack is in Github https://github.com/flatpak/meta-flatpak.
      • Initial work will be done with no LSM enabled. Scott suggested as an option that we start with SELinux in non-enforcing mode. Daniel will take a look at what can be done there.
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
    • 8/11 - Work ongoing on the launcher and UI part of hvac .
  • New topics:

September 22, 2021

Attendees: Walt, Jan-Simon, Scott, Sam Thursfield (Codethink), Arnaud, Marius, Kelly (Codethink), Richard Maw (Codethink), James

Application Framework Redesign

  • 7/28
    • Arnaud introduced himself as a new member of the team looking at Application Framework topics. Started looking at building flatpak and the work started by Codethink. The engineer working on this at Codethink moved on to another project. Javier is hoping to find someone else to look it.
    • Need to think about where the code will reside long-term. Is there an upstream project we can give this (YP, oe, meta-virtualization, RedHat).
  • 8/11
    • No update
  • 9/8
    • Arnaud back from vacation.
    • Sam showed a demo of AGL running on flatpak built from meta-flatpak.
    • Discussed replacing SMACK with SELinux/None option. Daniel needs to discuss with Simon.
    • Next steps for App FW
      • Need instructions for building with flatpak and how to build apps so people can start playing with QEMU as target.
      • Make sandbox available in the next two weeks
      • Daniel and Arnaud to work on documenting adding system level services.
    • 9/22
      • Sam will be transitioning to Richard Maw for their meta-flatpak work.
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
    • 8/11 - Work ongoing on the launcher and UI part of hvac .
  • New topics:

September 8, 2021

Attendees: Walt, Jan-Simon, Scott, Javier, Sam Thursfield (Codethink), Arnaud, Marius, Daniel, Kelly (Codethink)

Application Framework Redesign

  • 6/2
    • Asked Daniel Stone to update his presentation on app FW changes for the June 15 workshop.
    • Flutter integration discussed. The thought is that we could do some app FW changes such as enable GRPC to make integration of Flutter simpler rather than creating a bunch of web socket code to enable flutter. We can use the lessons learned from Web Apps to determine the best course.
  • 6/30
    • Daniel and Simon made a presentation during the F2F meeting.
    • Collabora looking to free up someone to start on this.
  • 7/14
    • Daniel gave an update during AGL Tech Day! Collabora has someone starting in the next two weeks on the App FW effort.
    • For some more context here is a transcript of the meeting chat.

From Farshid Monhaseri to Everyone : Yes I meant, Is the “flatpack” with some other components are going to replace the “aplication frame work” (specificly in PR profile)?
From Scott Murray to Everyone : I'd say the answer in a general way is yes, but what goes into the PR profile is an open question, that's up to Toyota for the most part. They have their own in-house app framework
From Scott Murray to Everyone : This work is to replace the effectively custom AGL only app framework with components based on existing projects with bigger communities.
From Farshid Monhaseri to Everyone : Yes, I agree … I was hoping a slution without systemd but anyway … If it provide the automotive industry required functionalities It is Ok
From Farshid Monhaseri to Everyone : I know replacing systemd custom lots of resources … With this solution AGL will looks like a custom desktop distro (But I am agree it will have more functionalities and easy to develop)
From Javier Jardón to Everyone : To be more specific, we wrote a small doc about how to use the layer here: https://gitlab.com/CodethinkLabs/agl/meta-flatpak/-/blob/AGL/AGL.md
From Farshid Monhaseri to Everyone : Currently the AFB v4 is in “redpesk” repo, but the with different licences … I was planing to contribute to v4 and back port It to AGL … but I think It won't be possible when we consider licencing issue
From Farshid Monhaseri to Everyone : There are some lack of functionalities and policy managment issue in current application frame work … We wrote an additional service top on AFM to fulfill some requiremnts in real word Infotainment system.
From Farshid Monhaseri to Everyone : I was planing to push some features in current application frame work but with new situation, we have to re-learn AGL :))
From Javier Jardón to Everyone : https://docs.flatpak.org/en/latest/electron.html\\'

  • Javier said that they now have meta-flatpak building and running! Repo is available in Gitlab
  • 7/28
    • Arnaud introduced himself as a new member of the team looking at Application Framework topics. Started looking at building flatpak and the work started by Codethink. The engineer working on this at Codethink moved on to another project. Javier is hoping to find someone else to look it.
    • Need to think about where the code will reside long-term. Is there an upstream project we can give this (YP, oe, meta-virtualization, RedHat).
  • 8/11
    • No update
  • 9/8
    • Arnaud back from vacation.
    • Sam showed a demo of AGL running on flatpak built from meta-flatpak.
    • Discussed replacing SMACK with SELinux/None option. Daniel needs to discuss with Simon.
    • Next steps for App FW
      • Need instructions for building with flatpak and how to build apps so people can start playing with QEMU as target.
      • Make sandbox available in the next two weeks
      • Daniel and Arnaud to work on documenting adding system level services.
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
    • 8/11 - Work ongoing on the launcher and UI part of hvac .
  • New topics:

August 11, 2021

Attendees: Walt, Jan-Simon, Marius, Lorenzo, Javier

Application Framework Redesign

  • 6/2
    • Asked Daniel Stone to update his presentation on app FW changes for the June 15 workshop.
    • Flutter integration discussed. The thought is that we could do some app FW changes such as enable GRPC to make integration of Flutter simpler rather than creating a bunch of web socket code to enable flutter. We can use the lessons learned from Web Apps to determine the best course.
  • 6/30
    • Daniel and Simon made a presentation during the F2F meeting.
    • Collabora looking to free up someone to start on this.
  • 7/14
    • Daniel gave an update during AGL Tech Day! Collabora has someone starting in the next two weeks on the App FW effort.
    • For some more context here is a transcript of the meeting chat.

From Farshid Monhaseri to Everyone : Yes I meant, Is the “flatpack” with some other components are going to replace the “aplication frame work” (specificly in PR profile)?
From Scott Murray to Everyone : I'd say the answer in a general way is yes, but what goes into the PR profile is an open question, that's up to Toyota for the most part. They have their own in-house app framework
From Scott Murray to Everyone : This work is to replace the effectively custom AGL only app framework with components based on existing projects with bigger communities.
From Farshid Monhaseri to Everyone : Yes, I agree … I was hoping a slution without systemd but anyway … If it provide the automotive industry required functionalities It is Ok
From Farshid Monhaseri to Everyone : I know replacing systemd custom lots of resources … With this solution AGL will looks like a custom desktop distro (But I am agree it will have more functionalities and easy to develop)
From Javier Jardón to Everyone : To be more specific, we wrote a small doc about how to use the layer here: https://gitlab.com/CodethinkLabs/agl/meta-flatpak/-/blob/AGL/AGL.md
From Farshid Monhaseri to Everyone : Currently the AFB v4 is in “redpesk” repo, but the with different licences … I was planing to contribute to v4 and back port It to AGL … but I think It won't be possible when we consider licencing issue
From Farshid Monhaseri to Everyone : There are some lack of functionalities and policy managment issue in current application frame work … We wrote an additional service top on AFM to fulfill some requiremnts in real word Infotainment system.
From Farshid Monhaseri to Everyone : I was planing to push some features in current application frame work but with new situation, we have to re-learn AGL :))
From Javier Jardón to Everyone : https://docs.flatpak.org/en/latest/electron.html\\'

  • Javier said that they now have meta-flatpak building and running! Repo is available in Gitlab
  • 7/28
    • Arnaud introduced himself as a new member of the team looking at Application Framework topics. Started looking at building flatpak and the work started by Codethink. The engineer working on this at Codethink moved on to another project. Javier is hoping to find someone else to look it.
    • Need to think about where the code will reside long-term. Is there an upstream project we can give this (YP, oe, meta-virtualization, RedHat).
  • 8/11
    • No update
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
    • 8/11 - Work ongoing on the launcher and UI part of hvac .
  • New topics:

July 28, 2021

Attendees: Walt, Jan-Simon, Scott, Javier, Marius, Daniel, Arnaud (Collabora), Lorenzo

Application Framework Redesign

  • 6/2
    • Asked Daniel Stone to update his presentation on app FW changes for the June 15 workshop.
    • Flutter integration discussed. The thought is that we could do some app FW changes such as enable GRPC to make integration of Flutter simpler rather than creating a bunch of web socket code to enable flutter. We can use the lessons learned from Web Apps to determine the best course.
  • 6/30
    • Daniel and Simon made a presentation during the F2F meeting.
    • Collabora looking to free up someone to start on this.
  • 7/14
    • Daniel gave an update during AGL Tech Day! Collabora has someone starting in the next two weeks on the App FW effort.
    • For some more context here is a transcript of the meeting chat.

From Farshid Monhaseri to Everyone : Yes I meant, Is the “flatpack” with some other components are going to replace the “aplication frame work” (specificly in PR profile)?
From Scott Murray to Everyone : I'd say the answer in a general way is yes, but what goes into the PR profile is an open question, that's up to Toyota for the most part. They have their own in-house app framework
From Scott Murray to Everyone : This work is to replace the effectively custom AGL only app framework with components based on existing projects with bigger communities.
From Farshid Monhaseri to Everyone : Yes, I agree … I was hoping a slution without systemd but anyway … If it provide the automotive industry required functionalities It is Ok
From Farshid Monhaseri to Everyone : I know replacing systemd custom lots of resources … With this solution AGL will looks like a custom desktop distro (But I am agree it will have more functionalities and easy to develop)
From Javier Jardón to Everyone : To be more specific, we wrote a small doc about how to use the layer here: https://gitlab.com/CodethinkLabs/agl/meta-flatpak/-/blob/AGL/AGL.md
From Farshid Monhaseri to Everyone : Currently the AFB v4 is in “redpesk” repo, but the with different licences … I was planing to contribute to v4 and back port It to AGL … but I think It won't be possible when we consider licencing issue
From Farshid Monhaseri to Everyone : There are some lack of functionalities and policy managment issue in current application frame work … We wrote an additional service top on AFM to fulfill some requiremnts in real word Infotainment system.
From Farshid Monhaseri to Everyone : I was planing to push some features in current application frame work but with new situation, we have to re-learn AGL :))
From Javier Jardón to Everyone : https://docs.flatpak.org/en/latest/electron.html\\'

  • Javier said that they now have meta-flatpak building and running! Repo is available in Gitlab
  • 7/28
    • Arnaud introduced himself as a new member of the team looking at Application Framework topics. Started looking at building flatpak and the work started by Codethink. The engineer working on this at Codethink moved on to another project. Javier is hoping to find someone else to look it.
    • Need to think about where the code will reside long-term. Is there an upstream project we can give this (YP, oe, meta-virtualization, RedHat).
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
  • New topics:

July 14, 2021

Attendees: Walt, Jan-Simon, Scott, Marius, Daniel, Javier, Farshid, George

  • 6/2
    • Asked Daniel Stone to update his presentation on app FW changes for the June 15 workshop.
    • Flutter integration discussed. The thought is that we could do some app FW changes such as enable GRPC to make integration of Flutter simpler rather than creating a bunch of web socket code to enable flutter. We can use the lessons learned from Web Apps to determine the best course.
  • 6/30
    • Daniel and Simon made a presentation during the F2F meeting.
    • Collabora looking to free up someone to start on this.
  • 7/14
    • Daniel gave an update during AGL Tech Day! Collabora has someone starting in the next two weeks on the App FW effort.
    • For some more context here is a transcript of the meeting chat.

From Farshid Monhaseri to Everyone : Yes I meant, Is the “flatpack” with some other components are going to replace the “aplication frame work” (specificly in PR profile)?
From Scott Murray to Everyone : I'd say the answer in a general way is yes, but what goes into the PR profile is an open question, that's up to Toyota for the most part. They have their own in-house app framework
From Scott Murray to Everyone : This work is to replace the effectively custom AGL only app framework with components based on existing projects with bigger communities.
From Farshid Monhaseri to Everyone : Yes, I agree … I was hoping a slution without systemd but anyway … If it provide the automotive industry required functionalities It is Ok
From Farshid Monhaseri to Everyone : I know replacing systemd custom lots of resources … With this solution AGL will looks like a custom desktop distro (But I am agree it will have more functionalities and easy to develop)
From Javier Jardón to Everyone : To be more specific, we wrote a small doc about how to use the layer here: https://gitlab.com/CodethinkLabs/agl/meta-flatpak/-/blob/AGL/AGL.md
From Farshid Monhaseri to Everyone : Currently the AFB v4 is in “redpesk” repo, but the with different licences … I was planing to contribute to v4 and back port It to AGL … but I think It won't be possible when we consider licencing issue
From Farshid Monhaseri to Everyone : There are some lack of functionalities and policy managment issue in current application frame work … We wrote an additional service top on AFM to fulfill some requiremnts in real word Infotainment system.
From Farshid Monhaseri to Everyone : I was planing to push some features in current application frame work but with new situation, we have to re-learn AGL :))
From Javier Jardón to Everyone : https://docs.flatpak.org/en/latest/electron.html

  • Javier said that they now have meta-flatpak building and running! Repo is available in Gitlab
  • WAM and Flutter (SPEC-3876)
    • 6/30 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.
    • 7/14 - Confluence page was created by Lorenzo and Roger.
  • New topics:

June 30, 2021

Attendees: Walt, Jan-Simon, Hosokawa, Scott. Lorenzo, Marius

  • 6/2
    • Asked Daniel Stone to update his presentation on app FW changes for the June 15 workshop.
    • Flutter integration discussed. The thought is that we could do some app FW changes such as enable GRPC to make integration of Flutter simpler rather than creating a bunch of web socket code to enable flutter. We can use the lessons learned from Web Apps to determine the best course.
  • 6/30
    • Daniel and Simon made a presentation during the F2F meeting.
    • Collabora looking to free up someone to start on this.
  • 4/11 - CodeThink joined the called and they are interested in participating in flatpak development. Javier also commented that they are in favor of Daniel's proposal to more closely follow upstream for the App FW.
    • AWS main concern is security model using SMACK and the current AGL documentation makes it very difficult to develop new apps outside of the AGL demo apps. Would like the focus of new security model and App FW to be on the developer experience and making it easier to develop and deploy new apps.
    • Richard suggested that we build a tutorial on how to develop apps be created in parallel with the development effort.
    • Need to think about how we can use flatpak and SELinux can co-exist and create an easy developer experience.
  • 5/19 - Javier: waiting for appfw/Collabora progress. Meanwhile looking into core integration of flatpack into YP (updating support there)
  • 6/2
  • 6/30
    • No update on meta-flatpak other than it builds.
  • New topics:
    • SPEC-3876 - Lorenzo gave us an update on their work creating Flutter apps that run via WAM. Asked if he could provide a diagram in Confluence on what they are doing with an eye towards how we can resume the apps and other work once we move to Flutter embedder or other non-web based solution.

June 2, 2021

Attendees: Walt, Scott, Hosokawa, Marius, Bernard, Javier

  • 6/2
    • Asked Daniel Stone to update his presentation on app FW changes for the June 15 workshop.
    • Flutter integration discussed. The thought is that we could do some app FW changes such as enable GRPC to make integration of Flutter simpler rather than creating a bunch of web socket code to enable flutter. We can use the lessons learned from Web Apps to determine the best course.
  • 4/11 - CodeThink joined the called and they are interested in participating in flatpak development. Javier also commented that they are in favor of Daniel's proposal to more closely follow upstream for the App FW.
    • AWS main concern is security model using SMACK and the current AGL documentation makes it very difficult to develop new apps outside of the AGL demo apps. Would like the focus of new security model and App FW to be on the developer experience and making it easier to develop and deploy new apps.
    • Richard suggested that we build a tutorial on how to develop apps be created in parallel with the development effort.
    • Need to think about how we can use flatpak and SELinux can co-exist and create an easy developer experience.
  • 5/19 - Javier: waiting for appfw/Collabora progress. Meanwhile looking into core integration of flatpack into YP (updating support there)
  • 6/2
  • New topics:

May 19, 2021

Attendees: Jan-Simon, Scott, Javier, Lorenzo, Marius

  • 4/11 - CodeThink joined the called and they are interested in participating in flatpak development. Javier also commented that they are in favor of Daniel's proposal to more closely follow upstream for the App FW.
    • AWS main concern is security model using SMACK and the current AGL documentation makes it very difficult to develop new apps outside of the AGL demo apps. Would like the focus of new security model and App FW to be on the developer experience and making it easier to develop and deploy new apps.
    • Richard suggested that we build a tutorial on how to develop apps be created in parallel with the development effort.
    • Need to think about how we can use flatpak and SELinux can co-exist and create an easy developer experience.
  • 5/19 - Javier: waiting for appfw/Collabora progress. Meanwhile looking into core integration of flatpack into YP (updating support there)
  • New topics:
    • Marius: Development environment for application developer use-case is currently difficult to use. Need to reconsider with new appfw.

April 21, 2021

Attendees: Walt, Javier Jardon and Mark Green (Codethink), Hosokawa, Yamaguchi, Marius, Scott, Date, Kurokawa, Richard

  • 4/11 - CodeThink joined the called and they are interested in participating in flatpak development. Javier also commented that they are in favor of Daniel's proposal to more closely follow upstream for the App FW.
  • AWS main concern is security model using SMACK and the current AGL documentation makes it very difficult to develop new apps outside of the AGL demo apps. Would like the focus of new security model and App FW to be on the developer experience and making it easier to develop and deploy new apps.
  • Richard suggested that we build a tutorial on how to develop apps be created in parallel with the development effort.
  • Need to think about how we can use flatpak and SELinux can co-exist and create an easy developer experience.
  • New topics:

April 7, 2021

Attendees: Walt, Jan-Simon, Hosokawa, Scott, Date, Richard, Lorenzo,

  • New topics:

March 24, 2021

Attendees: Walt, Jan-Simon, Scott, Daniel, Hosokawa, Marius, Date, Stephane

Reviewed the roadmap spreadsheet and added the tab “Copy of App FW and Security” to further refine and group the tasks.

  • New topics:

March 10, 2021

Attendees: Walt, Jan-Simon, Marius, Scott, Li

  • RBA
  • 12/2
    • Anusha asked a question on the mail list. Discussed the responses to this.
    • Marius will look at dynamic loading of the policy engine at run time so that policies can be dynamic. An alternative solution that would not require dynamic loading of the policy is to incorporate RBA into the compositor itself. Hosokawa-san will was whether that is ok for Denso. It would avoid a lot of unnecessary complexity since there is probably no use case for having the policy dynamically loaded. Will continue the discussion on the mail list.
  • 12/16
    • RBA successfully connected to AGL compositor using M3 and QEMU and can run the demo apps. Code will be pushed by Hosokawa-san.
    • Discussed whether RBA will be enabled by default in the demo image. Plan will be to enable RBA by default. Need documentation on how to update the policies and create new policies in order to make this the default. Hosokawa said that there is no plan to create such documentation. If the documentation is created the proposal would be to have RBA be enabled by default with a mechanism to disable it and replace with a different policy engine.
  • 1/13
    • RBA now merged as a build time option and will run the existing AGL demo when enabled. Some open issues remain. RBA is not enabled in CI or in any build images as an option.
    • Documentation and example are in progress.
    • Walt suggested that Hosokawa submit a talk for AMM that shows the demo running with RBA enabled.
  • 1/27
    • No update
  • 2/10
    • No update
  • 2/24
    • ADIT preparing documentation for RBA.
  • Waltham - Discussed SPEC-3647. Waltham currently requires a private fork that is not maintained to be usable. ADIT currently has no customer or budget to continue the Waltham work. Need to decide the long-term future of Waltham with the Steering Committee. Do we work to upstream this and have AGL maintain it or go with what is it there and potentially let it bit rot over the next few years?

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
    • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • New topics:

February 24, 2021

Attendees: Walt, Jan-Simon, Marius, Scott, Farshid, Hosokawa, Anusha

  • RBA
  • 12/2
    • Anusha asked a question on the mail list. Discussed the responses to this.
    • Marius will look at dynamic loading of the policy engine at run time so that policies can be dynamic. An alternative solution that would not require dynamic loading of the policy is to incorporate RBA into the compositor itself. Hosokawa-san will was whether that is ok for Denso. It would avoid a lot of unnecessary complexity since there is probably no use case for having the policy dynamically loaded. Will continue the discussion on the mail list.
  • 12/16
    • RBA successfully connected to AGL compositor using M3 and QEMU and can run the demo apps. Code will be pushed by Hosokawa-san.
    • Discussed whether RBA will be enabled by default in the demo image. Plan will be to enable RBA by default. Need documentation on how to update the policies and create new policies in order to make this the default. Hosokawa said that there is no plan to create such documentation. If the documentation is created the proposal would be to have RBA be enabled by default with a mechanism to disable it and replace with a different policy engine.
  • 1/13
    • RBA now merged as a build time option and will run the existing AGL demo when enabled. Some open issues remain. RBA is not enabled in CI or in any build images as an option.
    • Documentation and example are in progress.
    • Walt suggested that Hosokawa submit a talk for AMM that shows the demo running with RBA enabled.
  • 1/27
    • No update
  • 2/10
    • No update
  • 2/24
    • ADIT preparing documentation for RBA.
  • Waltham - Discussed SPEC-3647. Waltham currently requires a private fork that is not maintained to be usable. ADIT currently has no customer or budget to continue the Waltham work. Need to decide the long-term future of Waltham with the Steering Committee. Do we work to upstream this and have AGL maintain it or go with what is it there and potentially let it bit rot over the next few years?

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
    • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • New topics:

February 10, 2021

Attendees: Walt, Jan-Simon, Marius

  • RBA
  • 12/2
    • Anusha asked a question on the mail list. Discussed the responses to this.
    • Marius will look at dynamic loading of the policy engine at run time so that policies can be dynamic. An alternative solution that would not require dynamic loading of the policy is to incorporate RBA into the compositor itself. Hosokawa-san will was whether that is ok for Denso. It would avoid a lot of unnecessary complexity since there is probably no use case for having the policy dynamically loaded. Will continue the discussion on the mail list.
  • 12/16
    • RBA successfully connected to AGL compositor using M3 and QEMU and can run the demo apps. Code will be pushed by Hosokawa-san.
    • Discussed whether RBA will be enabled by default in the demo image. Plan will be to enable RBA by default. Need documentation on how to update the policies and create new policies in order to make this the default. Hosokawa said that there is no plan to create such documentation. If the documentation is created the proposal would be to have RBA be enabled by default with a mechanism to disable it and replace with a different policy engine.
  • 1/13
    • RBA now merged as a build time option and will run the existing AGL demo when enabled. Some open issues remain. RBA is not enabled in CI or in any build images as an option.
    • Documentation and example are in progress.
    • Walt suggested that Hosokawa submit a talk for AMM that shows the demo running with RBA enabled.
  • 1/27
    • No update
  • 2/10
    • No update
  • Waltham - Discussed SPEC-3647. Waltham currently requires a private fork that is not maintained to be usable. ADIT currently has no customer or budget to continue the Waltham work. Need to decide the long-term future of Waltham with the Steering Committee. Do we work to upstream this and have AGL maintain it or go with what is it there and potentially let it bit rot over the next few years?

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • New topics:

January 27, 2021

Attendees: Walt, Jan-Simon, Tanikawa, Scott, Marius

  • RBA
  • 12/2
    • Anusha asked a question on the mail list. Discussed the responses to this.
    • Marius will look at dynamic loading of the policy engine at run time so that policies can be dynamic. An alternative solution that would not require dynamic loading of the policy is to incorporate RBA into the compositor itself. Hosokawa-san will was whether that is ok for Denso. It would avoid a lot of unnecessary complexity since there is probably no use case for having the policy dynamically loaded. Will continue the discussion on the mail list.
  • 12/16
    • RBA successfully connected to AGL compositor using M3 and QEMU and can run the demo apps. Code will be pushed by Hosokawa-san.
    • Discussed whether RBA will be enabled by default in the demo image. Plan will be to enable RBA by default. Need documentation on how to update the policies and create new policies in order to make this the default. Hosokawa said that there is no plan to create such documentation. If the documentation is created the proposal would be to have RBA be enabled by default with a mechanism to disable it and replace with a different policy engine.
  • 1/13
    • RBA now merged as a build time option and will run the existing AGL demo when enabled. Some open issues remain. RBA is not enabled in CI or in any build images as an option.
    • Documentation and example are in progress.
    • Walt suggested that Hosokawa submit a talk for AMM that shows the demo running with RBA enabled.
  • 1/27
    • No update
  • Waltham - Discussed SPEC-3647. Waltham currently requires a private fork that is not maintained to be usable. ADIT currently has no customer or budget to continue the Waltham work. Need to decide the long-term future of Waltham with the Steering Committee. Do we work to upstream this and have AGL maintain it or go with what is it there and potentially let it bit rot over the next few years?

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • New topics:

January 13, 2021

Attendees: Walt, Jan-Simon, Tanikawa, Scott, Marius, Hosokawa,

  • RBA
  • 12/2
    • Anusha asked a question on the mail list. Discussed the responses to this.
    • Marius will look at dynamic loading of the policy engine at run time so that policies can be dynamic. An alternative solution that would not require dynamic loading of the policy is to incorporate RBA into the compositor itself. Hosokawa-san will was whether that is ok for Denso. It would avoid a lot of unnecessary complexity since there is probably no use case for having the policy dynamically loaded. Will continue the discussion on the mail list.
  • 12/16
    • RBA successfully connected to AGL compositor using M3 and QEMU and can run the demo apps. Code will be pushed by Hosokawa-san.
    • Discussed whether RBA will be enabled by default in the demo image. Plan will be to enable RBA by default. Need documentation on how to update the policies and create new policies in order to make this the default. Hosokawa said that there is no plan to create such documentation. If the documentation is created the proposal would be to have RBA be enabled by default with a mechanism to disable it and replace with a different policy engine.
  • 1/13
    • RBA now merged as a build time option and will run the existing AGL demo when enabled. Some open issues remain. RBA is not enabled in CI or in any build images as an option.
    • Documentation and example are in progress.
    • Walt suggested that Hosokawa submit a talk for AMM that shows the demo running with RBA enabled.
  • Waltham - Discussed SPEC-3647. Waltham currently requires a private fork that is not maintained to be usable. ADIT currently has no customer or budget to continue the Waltham work. Need to decide the long-term future of Waltham with the Steering Committee. Do we work to upstream this and have AGL maintain it or go with what is it there and potentially let it bit rot over the next few years?

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • New topics:

December 16, 2020

Attendees: Walt, Jan-Simon, Hosokawa, Kurokawa, Marius, Scott, Tanikawa

  • RBA
  • 12/2
    • Anusha asked a question on the mail list. Discussed the responses to this.
    • Marius will look at dynamic loading of the policy engine at run time so that policies can be dynamic. An alternative solution that would not require dynamic loading of the policy is to incorporate RBA into the compositor itself. Hosokawa-san will was whether that is ok for Denso. It would avoid a lot of unnecessary complexity since there is probably no use case for having the policy dynamically loaded. Will continue the discussion on the mail list.
  • 12/16
    • RBA successfully connected to AGL compositor using M3 and QEMU and can run the demo apps. Code will be pushed by Hosokawa-san.
    • Discussed whether RBA will be enabled by default in the demo image. Plan will be to enable RBA by default. Need documentation on how to update the policies and create new policies in order to make this the default. Hosokawa said that there is no plan to create such documentation. If the documentation is created the proposal would be to have RBA be enabled by default with a mechanism to disable it and replace with a different policy engine.
  • Waltham - Discussed SPEC-3647. Waltham currently requires a private fork that is not maintained to be usable. ADIT currently has no customer or budget to continue the Waltham work. Need to decide the long-term future of Waltham with the Steering Committee. Do we work to upstream this and have AGL maintain it or go with what is it there and potentially let it bit rot over the next few years?

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • New topics:

December 2, 2020

Attendees: Walt, Jan-Simon, Tanikawa, Anusha, Marius, Hosokawa, Scott, Li

  • RBA
    • Anusha asked a question on the mail list. Discussed the responses to this.
    • Marius will look at dynamic loading of the policy engine at run time so that policies can be dynamic. An alternative solution that would not require dynamic loading of the policy is to incorporate RBA into the compositor itself. Hosokawa-san will was whether that is ok for Denso. It would avoid a lot of unnecessary complexity since there is probably no use case for having the policy dynamically loaded. Will continue the discussion on the mail list.
  • Waltham - Discussed SPEC-3647. Waltham currently requires a private fork that is not maintained to be usable. ADIT currently has no customer or budget to continue the Waltham work. Need to decide the long-term future of Waltham with the Steering Committee. Do we work to upstream this and have AGL maintain it or go with what is it there and potentially let it bit rot over the next few years?

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

November 18, 2020

Attendees: Walt, Jan-Simon, Tanikawa, Nomoto, Marius

  • Waltham - Discussed SPEC-3647. Waltham currently requires a private fork that is not maintained to be usable. ADIT currently has no customer or budget to continue the Waltham work. Need to decide the long-term future of Waltham with the Steering Committee. Do we work to upstream this and have AGL maintain it or go with what is it there and potentially let it bit rot over the next few years?

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

November 4, 2020

Attendees: Walt, Scott, Tanikawa, Hosokawa, Anusha, Marius

  • Waltham - Discussed SPEC-3647. Waltham currently requires a private fork that is not maintained to be usable. ADIT currently has no customer or budget to continue the Waltham work. Need to decide the long-term future of Waltham with the Steering Committee. Do we work to upstream this and have AGL maintain it or go with what is it there and potentially let it bit rot over the next few years?

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

October 21, 2020

Attendees: Walt, Jan-Simon, Scott, Tanikawa, Marius

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

September 23, 2020

Attendees: Walt, Jan-Simon, Scott, Tanikawa, Marius

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

August 26, 2020

Attendees: Walt, Jan-Simon, Scott, Marius, Li, Tanikawa, Kurokawa

AGL Roadmap

  • Product readiness effort
    • No one from Toyota dialed in, Need to discuss the future of the app framework with respect to the PR effort.
    • Tanikawa: Current app framework is targeting a modern mobile environment for app installation and management. PR effort is thinking more along the lines of a re-using an older vision of app framework.
      • Need to separate app management functions from a common platform service implementation.
    • Scott: Would like a definition of what Toyota says they will drop to AGL for a new application framework after 2021.
      • Current state of PR effort effectively freezes the project while people wait for Toyota to make decisions.
    • Jan-Simon: There are impacts to other parts of the project.
    • All: Toyota's Base System attempts to replace systemd. This takes the project in a very different and not open source friendly direction. Need to understand what Toyota's intentions are with respect to their Base System and whether they think systemd will be used long-term. EG does not think the Base System is sustainable.
      • Suggestion is that we let Toyota own and do the work for the “trial version” and only provide advice and training since this seems to be throw-away long term and have the EG develop the long-term solution.
      • Tanikawa: Need to investigate replacing SMACK with SELinux (or something else). SMACK does not seem to be up to the needs of a production system.

Topics for EG for PR

  • Continued use of systemd
  • Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution.
  • Package management and deployment solution
  • API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another)
  • Long-term use of Qt
  • IPC should be defined and selected.
  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

July 29, 2020

Attendees: Walt, Scott, Marius, Li, Tanikawa

AGL Roadmap

  • Current status
    • Window Manager and Compositor are functionally equivalent to CES 2020 demo for Qt Apps.
    • WAM implementation is being worked on by Igalia and should be ready for JJ RC3
    • Marius has a number of Jira tickets to resolve but will quickly run out of work if new requirements are not defined and agreed upon by the IVI Product Readiness effort.
  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

July 1, 2020

Attendees: Walt, Jan-Simon, Scott, Marius, Li

AGL Roadmap

  • Discussion about architecture of window-manager and compositor work done by Marius
  • Marius to create a Jira ticket for the layout manager functionality.
  • Hosokawa-san asked that we review the Waltham documentation and RFC backend put out by Tanibata-san
  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

June 17, 2020

Attendees: Walt, Jan-Simon, Yamaguchi-san, Hosokawa-san, Li, Scott, Tanikawa-san, Veeresh, Marius

AGL Roadmap

  • Discussion about architecture of window-manager and compositor work done by Marius
  • Marius to create a Jira ticket for the layout manager functionality.
  • Hosokawa-san asked that we review the Waltham documentation and RFC backend put out by Tanibata-san
  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

June 3, 2020

Attendees: Walt, Jan-Simon, Scott, Marius, Kurokawa

AGL Roadmap

  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • New topics:

May 20, 2020

Attendees: Walt, Jan-Simon, Tanikawa, Marius, Guy

AGL Roadmap

  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • 2/12 - Fixed the breakage from RC2. Scott reported an issue with launcher and home screen that Igalia has reproduced and will be fixed for the final release.
    • 3/11 - All apps that have been migrated have been pushed to gerrit and Edi has run the test suite against them. Issues identified and being worked on by Igalia.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 2/12 - Jose implemented build option to keep multiple versions as a build option. Testing out the main option which is to keep a single version. Will be targeted to JJ once we get agreement from SAT/SC.
  • New topics:
  • What high priority bugs/issues need to be addressed in App Framework?
    • Issue from the fall with running too many threads on.
    • Cannot run Weston with memfd turned on due to SMACK issues.

May 6, 2020

Attendees: Walt, Jan-Simon, Scott, Marius

AGL Roadmap - Reviewed updates made by Walt.

  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?
    • 5/6 - Sounds like we will get these requirements in June timeframe based on the schedule presented during the IC EG call on Monday.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.
    • 5/6 - Long discussion on libwindowmanager

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • 2/12 - Fixed the breakage from RC2. Scott reported an issue with launcher and home screen that Igalia has reproduced and will be fixed for the final release.
    • 3/11 - All apps that have been migrated have been pushed to gerrit and Edi has run the test suite against them. Issues identified and being worked on by Igalia.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 2/12 - Jose implemented build option to keep multiple versions as a build option. Testing out the main option which is to keep a single version. Will be targeted to JJ once we get agreement from SAT/SC.
  • New topics:
  • What high priority bugs/issues need to be addressed in App Framework?
    • Issue from the fall with running too many threads on.
    • Cannot run Weston with memfd turned on due to SMACK issues.

April 22, 2020

Attendees: Walt, Jan-Simon, Scott, Marius, Tanikawa

AGL Roadmap - Reviewed updates made by Walt.

  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 4/22 - Marius submitted a number of patches to gerrit that are in process of being reviewed.
      • SPEC-3293, SPEC-3287, SPEC-3286 need to be fixed by Igalia to get WAM working correctly
      • Scott asked if Igalia has signed off on WAM/ Chromium on Zeus, Need to check on that.

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • 2/12 - Fixed the breakage from RC2. Scott reported an issue with launcher and home screen that Igalia has reproduced and will be fixed for the final release.
    • 3/11 - All apps that have been migrated have been pushed to gerrit and Edi has run the test suite against them. Issues identified and being worked on by Igalia.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 2/12 - Jose implemented build option to keep multiple versions as a build option. Testing out the main option which is to keep a single version. Will be targeted to JJ once we get agreement from SAT/SC.
  • New topics:
  • What high priority bugs/issues need to be addressed in App Framework?
    • Issue from the fall with running too many threads on.
    • Cannot run Weston with memfd turned on due to SMACK issues.

April 8, 2020

Attendees: Walt, Jan-Simon, Scott, Antia, Lorenzo, Parth

AGL Roadmap - Reviewed updates made by Walt.

  • Discussed IVI container solution for IC EG. Would like some more input from IC EG about what compositor will be used, security (SMACK vs. token logic), and use cases to be enabled. Will App FW be used? Will WAM be present or will Qt apps be used?

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 3/11 - Review of Marius documentation continued last week. Next call scheduled for one week.

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • 2/12 - Fixed the breakage from RC2. Scott reported an issue with launcher and home screen that Igalia has reproduced and will be fixed for the final release.
    • 3/11 - All apps that have been migrated have been pushed to gerrit and Edi has run the test suite against them. Issues identified and being worked on by Igalia.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 2/12 - Jose implemented build option to keep multiple versions as a build option. Testing out the main option which is to keep a single version. Will be targeted to JJ once we get agreement from SAT/SC.
  • New topics:

March 25, 2020

Attendees: Walt, Jan-Simon, Li, Scott

AGL Roadmap - Reviewed updates made by Walt.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.
    • 3/11 - Review of Marius documentation continued last week. Next call scheduled for one week.

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • 2/12 - Fixed the breakage from RC2. Scott reported an issue with launcher and home screen that Igalia has reproduced and will be fixed for the final release.
    • 3/11 - All apps that have been migrated have been pushed to gerrit and Edi has run the test suite against them. Issues identified and being worked on by Igalia.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 2/12 - Jose implemented build option to keep multiple versions as a build option. Testing out the main option which is to keep a single version. Will be targeted to JJ once we get agreement from SAT/SC.
  • New topics:

March 11, 2020

Attendees: Walt, Jan-Simon, Scott, Stephane, Lorenzo, Antia, Teddy Zhai (Green Hills)

AGL Roadmap - Walt will update based on the input received from Igalia separately and remove the completed tasks from the roadmap.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,
    • 3/11 - Review of Marius documentation started. Next call scheduled for one week.

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 2/12 - Merged for Icefish and WAM has been adapted to use it.
    • 3/11 - Completed.
  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
    • 3/11 - Still on-hold
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
    • 3/11 - Still need Jose or someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish
    • 2/12 - Ready for Icefish. Documentation is reasonable.
    • 3/11 - Nothing published on documentation site yet.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • 2/12 - Fixed the breakage from RC2. Scott reported an issue with launcher and home screen that Igalia has reproduced and will be fixed for the final release.
    • 3/11 - All apps that have been migrated have been pushed to gerrit and Edi has run the test suite against them. Issues identified and being worked on by Igalia.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 2/12 - Jose implemented build option to keep multiple versions as a build option. Testing out the main option which is to keep a single version. Will be targeted to JJ once we get agreement from SAT/SC.
  • New topics:

February 12, 2020

Attendees: Walt, Jan-Simon, Scott, Stephane, Jose, Lorenzo, Li, Laurent, Guy

AGL Roadmap will be updated by IoT.bzh and Igalia by Monday in preparation for the next SC meeting.

* Window Manager and Compositor consolidation

  • Activity Manager
    • 2/12 - Marius completing a document to update the design and code work he has completed and we will hold a separate review next week,

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 2/12 - Merged for Icefish and WAM has been adapted to use it.
  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 2/12 - User creation and management needs to be developed.
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
    • 2/12 - Documentation needs to be backfilled for the App FW work done for the Icefish release. Need to assign someone at IoT.bzh to complete the documentation.
  • Cyanara replacement (Cynanagora) Icefish

. * 2/12 - Ready for Icefish. Documentation is reasonable.

  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 2/12 - On hold until after Icefish. Need to determine priority for this work.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 2/12 - No update. On hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • 2/12 - Fixed the breakage from RC2. Scott reported an issue with launcher and home screen that Igalia has reproduced and will be fixed for the final release.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 2/12 - On priority list for 2020.
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 2/12 - Jose implemented build option to keep multiple versions as a build option. Testing out the main option which is to keep a single version. Will be targeted to JJ once we get agreement from SAT/SC.
  • Scott asked if we will have to carry the Cynara DBus patches when we do the upgrade to zeus. Jose to clarify.
    • 11/20 - Some adaptation will be necessary. Jose will take a look at it.
    • 12/4 - On hold until Jose is free to look at the forward port. Probably mid-January after CES.
    • 2/12 - Done
  • New topics:

January 29, 2020

Attendees: Walt, Jan-Simon, Scott, Matt P

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update
  • 7/31 - Daniel not on call. At the F2F meeting in Tokyo the latest architecture and design were presented and documented on Confluence.
  • 8/28 - No update
  • 9/11 - Daniel attending plumbers this week in Lisbon.
  • 11/6 - Daniel not attending
  • 1/15 - Got Marius unblocked on running as root issue. Working on some policy management as well as home screen/ app launcher.

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 7/31 - Loic and Jose working on this for Icefish
    • 8/28
    • 9/11
      • Jose added topic to meeting in Berlin. Jose will present what is left to be implemented on the App FW side and get advice on what needs to be done for apps and app developers.
    • 10/9
      • A lot of good discussion about token logic at the Berlin F2F. Things are almost clear to Jose about what needs to be done. Will be able to get this into Icefish with a draft available in November.
    • 11/6 - Loic on vacation last week. Will probably wait until Jose merges to merge Loic's.
    • 11/20 - Jose will have a draft next week and a WIP the week after. Collaborating with Lorenzo on the work in progress as risk mitigation. Target is first integration to master for RC2. Some archtecture and design documentation is in progress and will be placed in Confluence.
    • 12/4 - Initial version will be merged later today. Will need Edi to do some testing to make sure there is no breakage. There will be transition period where apps (binders) will not be required to use tokens, Eventually we will transition to require tokens for all apps and binders. Will need to update the doc site on how to create binders and widgets to reflect this.
    • Plan - Source (app-framework-main and app-framework-binder) will be merged today. Jose will submit the recipe change so Edi can test for tomorrow's SAT call. Assuming this goes ok we will merge the recipe change and release it for RC2.
  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 8/28 - Most parts fixed, services and apps work, few messages in the audit log left to do
      • For existing testplans, grep the systemd log at the end for “kernel: audit:” SPEC-2777
    • 9/11 - Lower priority than token logic. Added topic to Berlin meeting since we will have many of the OEMs present to ask about requirements.
    • 10/9 - User creation and management needs to be developed. Lower priority than token logic. Will probably be next year.
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
  • Cyanara replacement (Cynanagora) Icefish
    • 8/28 - Jose has a ready sandbox for this, but not JIRA, yet.
    • 9/11
      • Still in development, but Jose thinks it can be pushed for review and merge to master. Will add topic to SAT call for tomorrow to make a decision. He has been using the sandbox in his workflow.
    • 10/9
      • Repo created. Jose still preparing the Gerrit reviews and documentation. Will be tested along with the token logic change so the initial push to Gerrit will be in November.
    • 11/6 - Jose will finish the reviews and merge the changes to master this week so Edi can test in next week's master test cycle.
    • 11/20 - Cyanagora now merged and included in the latest test cycle that Edi performed. Looks good.
    • 12/4 - Some issues with dbus that may be attributable to Cynagora (see SPEC-3002). Jose will be able to look at this once the dust settles with token logic changes.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 8/28 - Can keep going for now.
    • 9/11 - Will not replace for now. Keep using the Tizen Security manager for Icefish.
    • 10/3 - On hold until after Icefish
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 8/28 - waiting for WM refactoring
  • Activity Manager for Icefish and who will do the work? Confluence link.
    • 8/28 - no update
    • 9/11 - no update
    • 10/9 - on hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Working with Igalia on a plan to do this throughout the year.
  • 8/28
    • Fixing issues with GPU on m3 (youtube)
    • single brower process issues on m3
    • keyboard / focus issues fixed
    • created jira for SDK integration for webapps
    • integration of sockets w/ new user model
    • work on homescreen
    • Chromium 72 not yet released
  • 9/11
    • Web apps performance issues are being investigated.
    • Meeting between Igalia and LG to discuss additional app porting work.
  • 10/9
    • Working continuing. Igalia now has an H3 board to test on.
  • 11/6 - See dev call notes from yesterday.
  • 1/15 - Working on fixes to security model that broke in RC2. May have to postpone RC5 since WAM is broken and only displays a white screen.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 8/28
      • No update
    • 9/11
      • No Update
    • 10/9
      • In Berlin we talked about how to use a widget directory. Jan-Simon will start a Jira Epic to document requirements.
    • 11/6
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 8/28 - No update
    • 9/3 - Briefly discussed and added to Berlin agenda. Please comment on ticket in the meanwhile.
    • 10/9 - No real update in Berlin, Was briefly discussed, but there was no progress.
    • 11/6 - No update
  • Scott asked if we will have to carry the Cynara DBus patches when we do the upgrade to zeus. Jose to clarify.
    • 11/20 - Some adaptation will be necessary. Jose will take a look at it.
    • 12/4 - On hold until Jose is free to look at the forward port. Probably mid-January after CES.
  • SPEC-3010 - Settings app sometimes not starting in crowded Wifi environments.
  • New topics:

January 15, 2020

Attendees: Walt, Scott, Marius, Stephane, Li, Lorenzo, Loic,

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update
  • 7/31 - Daniel not on call. At the F2F meeting in Tokyo the latest architecture and design were presented and documented on Confluence.
  • 8/28 - No update
  • 9/11 - Daniel attending plumbers this week in Lisbon.
  • 11/6 - Daniel not attending
  • 1/15 - Got Marius unblocked on running as root issue. Working on some policy management as well as home screen/ app launcher.

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 7/31 - Loic and Jose working on this for Icefish
    • 8/28
    • 9/11
      • Jose added topic to meeting in Berlin. Jose will present what is left to be implemented on the App FW side and get advice on what needs to be done for apps and app developers.
    • 10/9
      • A lot of good discussion about token logic at the Berlin F2F. Things are almost clear to Jose about what needs to be done. Will be able to get this into Icefish with a draft available in November.
    • 11/6 - Loic on vacation last week. Will probably wait until Jose merges to merge Loic's.
    • 11/20 - Jose will have a draft next week and a WIP the week after. Collaborating with Lorenzo on the work in progress as risk mitigation. Target is first integration to master for RC2. Some archtecture and design documentation is in progress and will be placed in Confluence.
    • 12/4 - Initial version will be merged later today. Will need Edi to do some testing to make sure there is no breakage. There will be transition period where apps (binders) will not be required to use tokens, Eventually we will transition to require tokens for all apps and binders. Will need to update the doc site on how to create binders and widgets to reflect this.
    • Plan - Source (app-framework-main and app-framework-binder) will be merged today. Jose will submit the recipe change so Edi can test for tomorrow's SAT call. Assuming this goes ok we will merge the recipe change and release it for RC2.
  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 8/28 - Most parts fixed, services and apps work, few messages in the audit log left to do
      • For existing testplans, grep the systemd log at the end for “kernel: audit:” SPEC-2777
    • 9/11 - Lower priority than token logic. Added topic to Berlin meeting since we will have many of the OEMs present to ask about requirements.
    • 10/9 - User creation and management needs to be developed. Lower priority than token logic. Will probably be next year.
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
  • Cyanara replacement (Cynanagora) Icefish
    • 8/28 - Jose has a ready sandbox for this, but not JIRA, yet.
    • 9/11
      • Still in development, but Jose thinks it can be pushed for review and merge to master. Will add topic to SAT call for tomorrow to make a decision. He has been using the sandbox in his workflow.
    • 10/9
      • Repo created. Jose still preparing the Gerrit reviews and documentation. Will be tested along with the token logic change so the initial push to Gerrit will be in November.
    • 11/6 - Jose will finish the reviews and merge the changes to master this week so Edi can test in next week's master test cycle.
    • 11/20 - Cyanagora now merged and included in the latest test cycle that Edi performed. Looks good.
    • 12/4 - Some issues with dbus that may be attributable to Cynagora (see SPEC-3002). Jose will be able to look at this once the dust settles with token logic changes.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 8/28 - Can keep going for now.
    • 9/11 - Will not replace for now. Keep using the Tizen Security manager for Icefish.
    • 10/3 - On hold until after Icefish
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 8/28 - waiting for WM refactoring
  • Activity Manager for Icefish and who will do the work? Confluence link.
    • 8/28 - no update
    • 9/11 - no update
    • 10/9 - on hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Working with Igalia on a plan to do this throughout the year.
  • 8/28
    • Fixing issues with GPU on m3 (youtube)
    • single brower process issues on m3
    • keyboard / focus issues fixed
    • created jira for SDK integration for webapps
    • integration of sockets w/ new user model
    • work on homescreen
    • Chromium 72 not yet released
  • 9/11
    • Web apps performance issues are being investigated.
    • Meeting between Igalia and LG to discuss additional app porting work.
  • 10/9
    • Working continuing. Igalia now has an H3 board to test on.
  • 11/6 - See dev call notes from yesterday.
  • 1/15 - Working on fixes to security model that broke in RC2. May have to postpone RC5 since WAM is broken and only displays a white screen.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 8/28
      • No update
    • 9/11
      • No Update
    • 10/9
      • In Berlin we talked about how to use a widget directory. Jan-Simon will start a Jira Epic to document requirements.
    • 11/6
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 8/28 - No update
    • 9/3 - Briefly discussed and added to Berlin agenda. Please comment on ticket in the meanwhile.
    • 10/9 - No real update in Berlin, Was briefly discussed, but there was no progress.
    • 11/6 - No update
  • Scott asked if we will have to carry the Cynara DBus patches when we do the upgrade to zeus. Jose to clarify.
    • 11/20 - Some adaptation will be necessary. Jose will take a look at it.
    • 12/4 - On hold until Jose is free to look at the forward port. Probably mid-January after CES.
  • SPEC-2998 - Data persistence is not persistent. Issue on both Halibut and master. Needed for CES demos. - Closed
  • SPEC-3010 - Settings app sometimes not starting in crowded Wifi environments.
  • New topics:

December 4, 2019

Attendees: Walt, Jose, Scott, Jan-Simon

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update
  • 7/31 - Daniel not on call. At the F2F meeting in Tokyo the latest architecture and design were presented and documented on Confluence.
  • 8/28 - No update
  • 9/11 - Daniel attending plumbers this week in Lisbon.
  • 11/6 - Daniel not attending

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 7/31 - Loic and Jose working on this for Icefish
    • 8/28
    • 9/11
      • Jose added topic to meeting in Berlin. Jose will present what is left to be implemented on the App FW side and get advice on what needs to be done for apps and app developers.
    • 10/9
      • A lot of good discussion about token logic at the Berlin F2F. Things are almost clear to Jose about what needs to be done. Will be able to get this into Icefish with a draft available in November.
    • 11/6 - Loic on vacation last week. Will probably wait until Jose merges to merge Loic's.
    • 11/20 - Jose will have a draft next week and a WIP the week after. Collaborating with Lorenzo on the work in progress as risk mitigation. Target is first integration to master for RC2. Some archtecture and design documentation is in progress and will be placed in Confluence.
    • 12/4 - Initial version will be merged later today. Will need Edi to do some testing to make sure there is no breakage. There will be transition period where apps (binders) will not be required to use tokens, Eventually we will transition to require tokens for all apps and binders. Will need to update the doc site on how to create binders and widgets to reflect this.
    • Plan - Source (app-framework-main and app-framework-binder) will be merged today. Jose will submit the recipe change so Edi can test for tomorrow's SAT call. Assuming this goes ok we will merge the recipe change and release it for RC2.
  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 8/28 - Most parts fixed, services and apps work, few messages in the audit log left to do
      • For existing testplans, grep the systemd log at the end for “kernel: audit:” SPEC-2777
    • 9/11 - Lower priority than token logic. Added topic to Berlin meeting since we will have many of the OEMs present to ask about requirements.
    • 10/9 - User creation and management needs to be developed. Lower priority than token logic. Will probably be next year.
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
  • Cyanara replacement (Cynanagora) Icefish
    • 8/28 - Jose has a ready sandbox for this, but not JIRA, yet.
    • 9/11
      • Still in development, but Jose thinks it can be pushed for review and merge to master. Will add topic to SAT call for tomorrow to make a decision. He has been using the sandbox in his workflow.
    • 10/9
      • Repo created. Jose still preparing the Gerrit reviews and documentation. Will be tested along with the token logic change so the initial push to Gerrit will be in November.
    • 11/6 - Jose will finish the reviews and merge the changes to master this week so Edi can test in next week's master test cycle.
    • 11/20 - Cyanagora now merged and included in the latest test cycle that Edi performed. Looks good.
    • 12/4 - Some issues with dbus that may be attributable to Cynagora (see SPEC-3002). Jose will be able to look at this once the dust settles with token logic changes.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 8/28 - Can keep going for now.
    • 9/11 - Will not replace for now. Keep using the Tizen Security manager for Icefish.
    • 10/3 - On hold until after Icefish
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 8/28 - waiting for WM refactoring
  • Activity Manager for Icefish and who will do the work? Confluence link.
    • 8/28 - no update
    • 9/11 - no update
    • 10/9 - on hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Working with Igalia on a plan to do this throughout the year.
  • 8/28
    • Fixing issues with GPU on m3 (youtube)
    • single brower process issues on m3
    • keyboard / focus issues fixed
    • created jira for SDK integration for webapps
    • integration of sockets w/ new user model
    • work on homescreen
    • Chromium 72 not yet released
  • 9/11
    • Web apps performance issues are being investigated.
    • Meeting between Igalia and LG to discuss additional app porting work.
  • 10/9
    • Working continuing. Igalia now has an H3 board to test on.
  • 11/6 - See dev call notes from yesterday.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 8/28
      • No update
    • 9/11
      • No Update
    • 10/9
      • In Berlin we talked about how to use a widget directory. Jan-Simon will start a Jira Epic to document requirements.
    • 11/6
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 8/28 - No update
    • 9/3 - Briefly discussed and added to Berlin agenda. Please comment on ticket in the meanwhile.
    • 10/9 - No real update in Berlin, Was briefly discussed, but there was no progress.
    • 11/6 - No update
  • Scott asked if we will have to carry the Cynara DBus patches when we do the upgrade to zeus. Jose to clarify.
    • 11/20 - Some adaptation will be necessary. Jose will take a look at it.
    • 12/4 - On hold until Jose is free to look at the forward port. Probably mid-January after CES.
  • New topics:
  • SPEC-2998 - Data persistence is not persistent. Issue on both Halibut and master. Needed for CES demos.
  • SPEC-3010 - Settings app sometimes not starting in crowded Wifi environments.

November 20, 2019

Attendees: Walt, Jose, Vincent, Loic, Kurokawa, Jan-Simon, Laurent

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update
  • 7/31 - Daniel not on call. At the F2F meeting in Tokyo the latest architecture and design were presented and documented on Confluence.
  • 8/28 - No update
  • 9/11 - Daniel attending plumbers this week in Lisbon.
  • 11/6 - Daniel not attending

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 7/31 - Loic and Jose working on this for Icefish
    • 8/28
    • 9/11
      • Jose added topic to meeting in Berlin. Jose will present what is left to be implemented on the App FW side and get advice on what needs to be done for apps and app developers.
    • 10/9
      • A lot of good discussion about token logic at the Berlin F2F. Things are almost clear to Jose about what needs to be done. Will be able to get this into Icefish with a draft available in November.
    • 11/6 - Loic on vacation last week. Will probably wait until Jose merges to merge Loic's.
    • 11/20 - Jose will have a draft next week and a WIP the week after. Collaborating with Lorenzo on the work in progress as risk mitigation. Target is first integration to master for RC2. Some archtecture and design documentation is in progress and will be placed in Confluence.
  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 8/28 - Most parts fixed, services and apps work, few messages in the audit log left to do
      • For existing testplans, grep the systemd log at the end for “kernel: audit:” SPEC-2777
    • 9/11 - Lower priority than token logic. Added topic to Berlin meeting since we will have many of the OEMs present to ask about requirements.
    • 10/9 - User creation and management needs to be developed. Lower priority than token logic. Will probably be next year.
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
  • Cyanara replacement (Cynanagora) Icefish
    • 8/28 - Jose has a ready sandbox for this, but not JIRA, yet.
    • 9/11
      • Still in development, but Jose thinks it can be pushed for review and merge to master. Will add topic to SAT call for tomorrow to make a decision. He has been using the sandbox in his workflow.
    • 10/9
      • Repo created. Jose still preparing the Gerrit reviews and documentation. Will be tested along with the token logic change so the initial push to Gerrit will be in November.
    • 11/6 - Jose will finish the reviews and merge the changes to master this week so Edi can test in next week's master test cycle.
    • 11/20 - Cyanagora now merged and included in the latest test cycle that Edi performed. Looks good.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 8/28 - Can keep going for now.
    • 9/11 - Will not replace for now. Keep using the Tizen Security manager for Icefish.
    • 10/3 - On hold until after Icefish
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 8/28 - waiting for WM refactoring
  • Activity Manager for Icefish and who will do the work? Confluence link.
    • 8/28 - no update
    • 9/11 - no update
    • 10/9 - on hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Working with Igalia on a plan to do this throughout the year.
  • 8/28
    • Fixing issues with GPU on m3 (youtube)
    • single brower process issues on m3
    • keyboard / focus issues fixed
    • created jira for SDK integration for webapps
    • integration of sockets w/ new user model
    • work on homescreen
    • Chromium 72 not yet released
  • 9/11
    • Web apps performance issues are being investigated.
    • Meeting between Igalia and LG to discuss additional app porting work.
  • 10/9
    • Working continuing. Igalia now has an H3 board to test on.
  • 11/6 - See dev call notes from yesterday.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 8/28
      • No update
    • 9/11
      • No Update
    • 10/9
      • In Berlin we talked about how to use a widget directory. Jan-Simon will start a Jira Epic to document requirements.
    • 11/6
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 8/28 - No update
    • 9/3 - Briefly discussed and added to Berlin agenda. Please comment on ticket in the meanwhile.
    • 10/9 - No real update in Berlin, Was briefly discussed, but there was no progress.
    • 11/6 - No update
  • Scott asked if we will have to carry the Cynara DBus patches when we do the upgrade to zeus. Jose to clarify.
    • 11/20 - Some adaptation will be necessary. Jose will take a look at it.
  • New topics:
  • SPEC-2972 - Container issues uncovered in the course of Kurokawa-san's work. He is now unblocked, but Jose can fix these issues pretty quickly as well.

November 6, 2019

Attendees: Walt, Jan-Simon, Scott, Hosokawa, Stephane

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update
  • 7/31 - Daniel not on call. At the F2F meeting in Tokyo the latest architecture and design were presented and documented on Confluence.
  • 8/28 - No update
  • 9/11 - Daniel attending plumbers this week in Lisbon.
  • 11/6 - Daniel not attending

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 7/31 - Loic and Jose working on this for Icefish
    • 8/28
    • 9/11
      • Jose added topic to meeting in Berlin. Jose will present what is left to be implemented on the App FW side and get advice on what needs to be done for apps and app developers.
    • 10/9
      • A lot of good discussion about token logic at the Berlin F2F. Things are almost clear to Jose about what needs to be done. Will be able to get this into Icefish with a draft available in November.
    • 11/6 - Loic on vacation last week. Will probably wait until Jose merges to merge Loic's.
  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 8/28 - Most parts fixed, services and apps work, few messages in the audit log left to do
      • For existing testplans, grep the systemd log at the end for “kernel: audit:” SPEC-2777
    • 9/11 - Lower priority than token logic. Added topic to Berlin meeting since we will have many of the OEMs present to ask about requirements.
    • 10/9 - User creation and management needs to be developed. Lower priority than token logic. Will probably be next year.
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
  • Cyanara replacement (Cynanagora) Icefish
    • 8/28 - Jose has a ready sandbox for this, but not JIRA, yet.
    • 9/11
      • Still in development, but Jose thinks it can be pushed for review and merge to master. Will add topic to SAT call for tomorrow to make a decision. He has been using the sandbox in his workflow.
    • 10/9
      • Repo created. Jose still preparing the Gerrit reviews and documentation. Will be tested along with the token logic change so the initial push to Gerrit will be in November.
    • 11/6 - Jose will finish the reviews and merge the changes to master this week so Edi can test in next week's master test cycle.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 8/28 - Can keep going for now.
    • 9/11 - Will not replace for now. Keep using the Tizen Security manager for Icefish.
    • 10/3 - On hold until after Icefish
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 8/28 - waiting for WM refactoring
  • Activity Manager for Icefish and who will do the work? Confluence link.
    • 8/28 - no update
    • 9/11 - no update
    • 10/9 - on hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Working with Igalia on a plan to do this throughout the year.
  • 8/28
    • Fixing issues with GPU on m3 (youtube)
    • single brower process issues on m3
    • keyboard / focus issues fixed
    • created jira for SDK integration for webapps
    • integration of sockets w/ new user model
    • work on homescreen
    • Chromium 72 not yet released
  • 9/11
    • Web apps performance issues are being investigated.
    • Meeting between Igalia and LG to discuss additional app porting work.
  • 10/9
    • Working continuing. Igalia now has an H3 board to test on.
  • 11/6 - See dev call notes from yesterday.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 8/28
      • No update
    • 9/11
      • No Update
    • 10/9
      • In Berlin we talked about how to use a widget directory. Jan-Simon will start a Jira Epic to document requirements.
    • 11/6
      • SPEC-2938 - Widget directory - need comments
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 8/28 - No update
    • 9/3 - Briefly discussed and added to Berlin agenda. Please comment on ticket in the meanwhile.
    • 10/9 - No real update in Berlin, Was briefly discussed, but there was no progress.
    • 11/6 - No update
  • New topics:
  • Scott asked if we will have to carry the Cynara patches when we do the upgrade to zeus. Jose to clarify.

October 23, 2019

Meeting canceled.

October 9, 2019

Attendees: Walt, Jan-Simon, Scott, Lorenzo, Hosokawa, Kurokawa, Vincent, Jose

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update
  • 7/31 - Daniel not on call. At the F2F meeting in Tokyo the latest architecture and design were presented and documented on Confluence.
  • 8/28 - No update
  • 9/11 - Daniel attending plumbers this week in Lisbon.

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 7/31 - Loic and Jose working on this for Icefish
    • 8/28
    • 9/11
      • Jose added topic to meeting in Berlin. Jose will present what is left to be implemented on the App FW side and get advice on what needs to be done for apps and app developers.
    • 10/9
      • A lot of good discussion about token logic at the Berlin F2F. Things are almost clear to Jose about what needs to be done. Will be able to get this into Icefish with a draft available in November.
  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 8/28 - Most parts fixed, services and apps work, few messages in the audit log left to do
      • For existing testplans, grep the systemd log at the end for “kernel: audit:” SPEC-2777
    • 9/11 - Lower priority than token logic. Added topic to Berlin meeting since we will have many of the OEMs present to ask about requirements.
    • 10/9 - User creation and management needs to be developed. Lower priority than token logic. Will probably be next year.
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
  • Cyanara replacement (Cynanagora) Icefish
    • 8/28 - Jose has a ready sandbox for this, but not JIRA, yet.
    • 9/11
      • Still in development, but Jose thinks it can be pushed for review and merge to master. Will add topic to SAT call for tomorrow to make a decision. He has been using the sandbox in his workflow.
    • 10/9
      • Repo created. Jose still preparing the Gerrit reviews and documentation. Will be tested along with the token logic change so the initial push to Gerrit will be in November.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 8/28 - Can keep going for now.
    • 9/11 - Will not replace for now. Keep using the Tizen Security manager for Icefish.
    • 10/3 - On hold.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 8/28 - waiting for WM refactoring
  • Activity Manager for Icefish and who will do the work? Confluence link.
    • 8/28 - no update
    • 9/11 - no update
    • 10/9 - on hold until after Icefish. Looking for volunteers to take this on as well.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Working with Igalia on a plan to do this throughout the year.
  • 8/28
    • Fixing issues with GPU on m3 (youtube)
    • single brower process issues on m3
    • keyboard / focus issues fixed
    • created jira for SDK integration for webapps
    • integration of sockets w/ new user model
    • work on homescreen
    • Chromium 72 not yet released
  • 9/11
    • Web apps performance issues are being investigated.
    • Meeting between Igalia and LG to discuss additional app porting work.
  • 10/9
    • Working continuing. Igalia now has an H3 board to test on.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 8/28
      • No update
    • 9/11
      • No Update
    • 10/9
      • In Berlin we talked about how to use a widget directory. Jan-Simon will start a Jira Epic to document requirements.
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 8/28 - No update
    • 9/3 - Briefly discussed and added to Berlin agenda. Please comment on ticket in the meanwhile.
    • 10/9 - No real update in Berlin, Was briefly discussed, but there was no progress.
  • New topics:
  • gerrit 22590 - Add the ability to discover existing exported APIs within a binder dynamically without it appearing in the config file at build time. Could also include external bindings within an existing binder. Will add a permission to enable this so it is not enabled by default for security reasons.

September 25, 2019

Attendees: Upcoming Meeting

September 11, 2019

Attendees: Walt, Jan-Simon, Sebastien, Jose, Scott, Loic, Lorenzo, Hosokawa, Li

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update
  • 7/31 - Daniel not on call. At the F2F meeting in Tokyo the latest architecture and design were presented and documented on Confluence.
  • 8/28 - No update
  • 9/11 - Daniel attending plumbers this week in Lisbon.

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 8/28 - Most parts fixed, services and apps work, few messages in the audit log left to do
      • For existing testplans, grep the systemd log at the end for “kernel: audit:” SPEC-2777
    • 9/11 - Lower priority than token logic. Added topic to Berlin meeting since we will have many of the OEMs present to ask about requirements.
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
  • Cyanara replacement Icefish
    • 8/28 - Jose has a ready sandbox for this, but not JIRA, yet.
    • 9/11
      • Still in development, but Jose thinks it can be pushed for review and merge to master. Will add topic to SAT call for tomorrow to make a decision. He has been using the sandbox in his workflow.
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 8/28 - Can keep going for now.
    • 9/11 - Will not replace for now. Keep using the Tizen Security manager for Icefish.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 8/28 - waiting for WM refactoring
  • Activity Manager for Icefish and who will do the work? Confluence link.
    • 8/28 - no update
    • 9/11 - no update
  • Web App Manager and Migration of Qt Apps to HTML5
    • Working with Igalia on a plan to do this throughout the year.
  • 8/28
    • Fixing issues with GPU on m3 (youtube)
    • single brower process issues on m3
    • keyboard / focus issues fixed
    • created jira for SDK integration for webapps
    • integration of sockets w/ new user model
    • work on homescreen
    • Chromium 72 not yet released
  • 9/11
    • Web apps performance issues are being investigated.
    • Meeting between Igalia and LG to discuss additional app porting work.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 8/28
      • No update
    • 9/11
      • No Update
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 8/28 - No update
    • 9/3 - Briefly discussed and added to Berlin agenda. Please comment on ticket in the meanwhile.
  • New topics:

August 28, 2019

Attendees: Jan-Simon, Hosokawa-san, Laurent, Scott, Loic, Stephane, Dennis, Lorenzo, Jose

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update
  • 7/31 - Daniel not on call. At the F2F meeting in Tokyo the latest architecture and design were presented and documented on Confluence.
  • 8/28 - No update

* AppFW

  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
    • 8/28 - Most parts fixed, services and apps work, few messages in the audit log left to do
    • For existing testplans, grep the systemd log at the end for “kernel: audit:” SPEC-2777
  • Security workflow for Device and App developers
    • 8/28 - Documentation todo
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
    • 8/28 - Can keep going for now.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
    • 8/28 - waiting for WM refactoring
  • Activity Manager for Icefish and who will do the work? Confluence link.
    • 8/28 - no update
  • Web App Manager and Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.
    • Update 04/10: no update today.
    • 4/24 - Working on rebase of latest upstream WebOS OSE changes to guppy for the 7.0.2 (just a recipe change is needed).
    • Working to get some changes upstreamed to LG for WebOS OSE.
    • SPEC-2342 to fix master dependency issue.
  • 6/5
  • Pull requests to upgrade chromium and Web App Manager for Guppy
  • Launcher is in progress. Needs a proper UI which Igalia is working on.
  • 6/19
    • Working on the issues listed yesterday in dev call.
    • SPEC-2401 - New launcher in progress.
  • 7/3
    • Lorenzo updated us yesterday on developer call.
    • SPEC-2586 WAM Causing homescreen crash. Working on HTML5 home screen and interfacing directly to Pipewire for audio (SPEC-2343).
  • 7/31
    • Working on some remaining open issues for Halibut
    • Working on infrastructure improvements with Jan-Simon to get the web apps into gerrit and building them in CI.
    • Will be starting the upgrade to Chromium 72
  • 8/28
    • Fixing issues with GPU on m3 (youtube)
    • single brower process issues on m3
    • keyboard / focus issues fixed
    • created jira for SDK integration for webapps
    • integration of sockets w/ new user model
    • work on homescreen
    • Chromium 72 not yet released
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
    • 8/28
      • No update
  • SPEC-2538 - Jose brought up question about versioning the binders and keeping the version number in the name.
    • Multiple API versions vs multiple versions of a wgt
    • 8/28 - No update

August 14, 2019

Meeting canceled due to vacations.

July 31, 2019

Attendees: Walt, Scott, Loic, Hosokawa, Jose, Lorenzo, George

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update
  • 7/31 - Daniel not on call. At the F2F meeting in Tokyo the latest architecture and design were presented and documented on Confluence.

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 7/31 - Loic and Jose working on this for Icefish.
  • Enable multi-user across the reference platform. - Icefish availability depends on priorities
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
  • Security workflow for Device and App developers
  • Cyanara replacement Icefish
  • Replace obsolete Tizen Security Manager Icefish
    • Requirements for sharing files between applications will updates to security manager.
    • Not a large component. No candidate replacement in mind. Need to search for a candidate replacement with current AGL requirements in mind.
    • Work with Jose and Sebastien on priority and estimates.
  • Consent manager and user interface for consent of app installation. Need to discuss whether this is a priority for Icefish.
  • Activity Manager for Icefish and who will do the work? Confluence link.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.
    • Update 04/10: no update today.
    • 4/24 - Working on rebase of latest upstream WebOS OSE changes to guppy for the 7.0.2 (just a recipe change is needed).
    • Working to get some changes upstreamed to LG for WebOS OSE.
    • SPEC-2342 to fix master dependency issue.
  • 6/5
  • Pull requests to upgrade chromium and Web App Manager for Guppy
  • Launcher is in progress. Needs a proper UI which Igalia is working on.
  • 6/19
    • Working on the issues listed yesterday in dev call.
    • SPEC-2401 - New launcher in progress.
  • 7/3
    • Lorenzo updated us yesterday on developer call.
    • SPEC-2586 WAM Causing homescreen crash. Working on HTML5 home screen and interfacing directly to Pipewire for audio (SPEC-2343).
  • 7/31
    • Working on some remaining open issues for Halibut
    • Working on infrastructure improvements with Jan-Simon to get the web apps into gerrit and building them in CI.
    • Will be starting the upgrade to Chromium 72
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
  • SPEC-2358 - Jose brought up question about versioning the binders and keeping the version number in the name.
  • New topics:

July 17, 2019

Canceled due to ALS

July 3, 2019

Attendees: Walt, Jan-Simon, Scott, Sebastien, Loic, Lorenzo

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.
  • 7/3 - No update

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 5/8 - Jose worked out an agreement with Jose P. on how to go about this.
    • 5/22 - No progress since Spain due to higher priorities.
    • 6/19 - On hold. Jose on vacation next two weeks. Loic will take over this work in the meantime. End of July is a likely target to complete. Lorenzo will create a ticket to track the work that both Igalia and IoT.bzh are doing in this area to gain agreement on what needs to be done. Will target the 8.0.1 release in early September to get this into the build.
  • Enable multi-user across the reference platform.
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
  • Security workflow for Device and App developers
  • Replace obsolete Tizen Security Manager
  • Jose
    • Working on change to not run as root. Was waiting for thud migration to hit master. sandbox/jobol/wip-mu
      • Update 04/10: multi-user patches planned after Jose's vacation (~ in 2 weeks)
      • 4/24 - Jose getting multi-user patches ready for Halibut. Apps that are displayed such as home screen abd others will run as agl-driver
      • Services still need to be looked at as well. Jose will come up with a migration guide for what needs to be done to update the services to be shared at the F2F meeting in Spain.
      • Jose will prepare a sandbox for Edi and Stoyan to test prior to the merge.
      • 5/22 - Some progress, but not ready to merge to master.
      • 6/19 - Jose submitted all of the changes. Jan-Simon did a manual build to test out which went ok. Edi and Stoyan tested the sandbox ok as well. Changes were just merge to master.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.
    • Update 04/10: no update today.
    • 4/24 - Working on rebase of latest upstream WebOS OSE changes to guppy for the 7.0.2 (just a recipe change is needed).
    • Working to get some changes upstreamed to LG for WebOS OSE.
    • SPEC-2342 to fix master dependency issue.
  • 6/5
  • Pull requests to upgrade chromium and Web App Manager for Guppy
  • Launcher is in progress. Needs a proper UI which Igalia is working on.
  • 6/19
    • Working on the issues listed yesterday in dev call.
    • SPEC-2401 - New launcher in progress.
  • 7/3
    • Lorenzo updated us yesterday on developer call.
    • SPEC-2586 WAM Causing homescreen crash. Working on HTML5 home screen and interfacing directly to Pipewire for audio (SPEC-2343).
  • Jose: thud-upgrade / dbus testing - in-progress
    • 5/22 - Still in progress
    • 6/19 - complete. Changes included in the not running as root patches. One minor issue remaining. Jose will write a Jira ticket.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
  • SPEC-2358 - Jose brought up question about versioning the binders and keeping the version number in the name.
  • New topics:

June 19, 2019

Attendees: Walt, Jan-Simon, Sebastien, Lorenzo, Guy, Daniel, George, Stephane

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.
  • 6/19 - Daniel - No sure on homescreen progress. Weston 6 merged to master for HH. May bump up to 6.0.1 by the end of the month in time for HH release.

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 5/8 - Jose worked out an agreement with Jose P. on how to go about this.
    • 5/22 - No progress since Spain due to higher priorities.
    • 6/19 - On hold. Jose on vacation next two weeks. Loic will take over this work in the meantime. End of July is a likely target to complete. Lorenzo will create a ticket to track the work that both Igalia and IoT.bzh are doing in this area to gain agreement on what needs to be done. Will target the 8.0.1 release in early September to get this into the build.
  • Enable multi-user across the reference platform.
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
  • Security workflow for Device and App developers
  • Replace obsolete Tizen Security Manager
  • Jose
    • Working on change to not run as root. Was waiting for thud migration to hit master. sandbox/jobol/wip-mu
      • Update 04/10: multi-user patches planned after Jose's vacation (~ in 2 weeks)
      • 4/24 - Jose getting multi-user patches ready for Halibut. Apps that are displayed such as home screen abd others will run as agl-driver
      • Services still need to be looked at as well. Jose will come up with a migration guide for what needs to be done to update the services to be shared at the F2F meeting in Spain.
      • Jose will prepare a sandbox for Edi and Stoyan to test prior to the merge.
      • 5/22 - Some progress, but not ready to merge to master.
      • 6/19 - Jose submitted all of the changes. Jan-Simon did a manual build to test out which went ok. Edi and Stoyan tested the sandbox ok as well. Changes were just merge to master.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.
    • Update 04/10: no update today.
    • 4/24 - Working on rebase of latest upstream WebOS OSE changes to guppy for the 7.0.2 (just a recipe change is needed).
    • Working to get some changes upstreamed to LG for WebOS OSE.
    • SPEC-2342 to fix master dependency issue.
  • 6/5
  • Pull requests to upgrade chromium and Web App Manager for Guppy
  • Launcher is in progress. Needs a proper UI which Igalia is working on.
  • 6/19
    • Working on the issues listed yesterday in dev call.
    • SPEC-2401 - New launcher in progress.
  • Jose: thud-upgrade / dbus testing - in-progress
    • 5/22 - Still in progress
    • 6/19 - complete. Changes included in the not running as root patches. One minor issue remaining. Jose will write a Jira ticket.
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
  • New topics:
    • Jose brought up question about versioning the binders and keeping the version number in the name. He will create a Jira ticket to be reviewed during SAT. (SPEC-2538)

June 5, 2019

Attendees: Walt, Jan-Simon, Kurokawa, Sebastien, Stephane, Lorenzo, George, Antia,

Jose out sick today.

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 5/8 - Jose worked out an agreement with Jose P. on how to go about this.
    • 5/22 - No progress since Spain due to higher priorities.
  • Enable multi-user across the reference platform.
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
  • Security workflow for Device and App developers
  • Replace obsolete Tizen Security Manager
  • Jose
    • Change to allow listing of all installed binders - Done
    • Working on change to not run as root. Was waiting for thud migration to hit master. sandbox/jobol/wip-mu
      • Update 04/10: multi-user patches planned after Jose's vacation (~ in 2 weeks)
      • 4/24 - Jose getting multi-user patches ready for Halibut. Apps that are displayed such as home screen abd others will run as agl-driver
      • Services still need to be looked at as well. Jose will come up with a migration guide for what needs to be done to update the services to be shared at the F2F meeting in Spain.
      • Jose will prepare a sandbox for Edi and Stoyan to test prior to the merge.
      • 5/22 - Some progress, but not ready to merge to master.
  • Web App Manager and Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.
    • Update 04/10: no update today.
    • 4/24 - Working on rebase of latest upstream WebOS OSE changes to guppy for the 7.0.2 (just a recipe change is needed).
    • Working to get some changes upstreamed to LG for WebOS OSE.
    • SPEC-2342 to fix master dependency issue.
  • 6/5
  • Pull requests to upgrade chromium and Web App Manager for Guppy
  • Launcher is in progress. Needs a proper UI which Igalia is working on.
  • Jose: thud-upgrade / dbus testing - in-progress
    • 5/22 - Still in progress
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
  • New topics:

May 22, 2019

Attendees: Walt, Jan-Simon, Jose, Guy, Kurokawa, Daniel, Sebastien

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
    • 5/22 - Need to identify the lead person for this and update documentation in Confluence.
  • Input manager
    • 5/22 - Daniel - Scott (NZ) working on getting homescreen to come up with the new compositor.

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 5/8 - Jose worked out an agreement with Jose P. on how to go about this.
    • 5/22 - No progress since Spain due to higher priorities.
  • Enable multi-user across the reference platform.
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
  • Security workflow for Device and App developers
  • Replace obsolete Tizen Security Manager
  • Jose
    • Change to allow listing of all installed binders - Done
    • Working on change to not run as root. Was waiting for thud migration to hit master. sandbox/jobol/wip-mu
      • Update 04/10: multi-user patches planned after Jose's vacation (~ in 2 weeks)
      • 4/24 - Jose getting multi-user patches ready for Halibut. Apps that are displayed such as home screen abd others will run as agl-driver
      • Services still need to be looked at as well. Jose will come up with a migration guide for what needs to be done to update the services to be shared at the F2F meeting in Spain.
      • Jose will prepare a sandbox for Edi and Stoyan to test prior to the merge.
      • 5/22 - Some progress, but not ready to merge to master.
  • Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.
    • Update 04/10: no update today.
    • 4/24 - Working on rebase of latest upstream WebOS OSE changes to guppy for the 7.0.2 (just a recipe change is needed).
    • Working to get some changes upstreamed to LG for WebOS OSE.
    • SPEC-2342 to fix master dependency issue.
  • Jose: thud-upgrade / dbus testing - in-progress
    • 5/22 - Still in progress
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
  • New topics:

May 8, 2019

Held in conjunction with F2F Meeting in Spain

Attendees:

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
  • Input manager
    • Update from Daniel on the window manager and compositor effort expected tomorrow during the SAT call.
    • Update 04/10:

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
    • 5/8 - Jose worked out an agreement with Jose P. on how to go about this.
  • Enable multi-user across the reference platform.
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
  • Security workflow for Device and App developers
  • Replace obsolete Tizen Security Manager
  • Jose
    • Change to allow listing of all installed binders - Done
    • Working on change to not run as root. Was waiting for thud migration to hit master. sandbox/jobol/wip-mu
      • Update 04/10: multi-user patches planned after Jose's vacation (~ in 2 weeks)
      • 4/24 - Jose getting multi-user patches ready for Halibut. Apps that are displayed such as home screen abd others will run as agl-driver
      • Services still need to be looked at as well. Jose will come up with a migration guide for what needs to be done to update the services to be shared at the F2F meeting in Spain.
      • Jose will prepare a sandbox for Edi and Stoyan to test prior to the merge.
  • Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.
    • Update 04/10: no update today.
    • 4/24 - Working on rebase of latest upstream WebOS OSE changes to guppy for the 7.0.2 (just a recipe change is needed).
    • Working to get some changes upstreamed to LG for WebOS OSE.
    • SPEC-2342 to fix master dependency issue.
  • Jose: thud-upgrade / dbus testing - in-progress
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
  • New topics:

April 24, 2019

Attendees: Walt, Tom, Thomas, Jose, Loic, Jan-Simon, Stephane, Lorenzo, Kurokawa,

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
  • Input manager
    • Update from Daniel on the window manager and compositor effort expected tomorrow during the SAT call.
    • Update 04/10:

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
  • Enable multi-user across the reference platform.
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
  • Security workflow for Device and App developers
  • Replace obsolete Tizen Security Manager
  • Jose
    • Change to allow listing of all installed binders - Done
    • Working on change to not run as root. Was waiting for thud migration to hit master. sandbox/jobol/wip-mu
      • Update 04/10: multi-user patches planned after Jose's vacation (~ in 2 weeks)
      • 4/24 - Jose getting multi-user patches ready for Halibut. Apps that are displayed such as home screen abd others will run as agl-driver
      • Services still need to be looked at as well. Jose will come up with a migration guide for what needs to be done to update the services to be shared at the F2F meeting in Spain.
      • Jose will prepare a sandbox for Edi and Stoyan to test prior to the merge.
  • Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.
    • Update 04/10: no update today.
    • 4/24 - Working on rebase of latest upstream WebOS OSE changes to guppy for the 7.0.2 (just a recipe change is needed).
    • Working to get some changes upstreamed to LG for WebOS OSE.
    • SPEC-2342 to fix master dependency issue.
  • Jose: thud-upgrade / dbus testing - in-progress
  • AGL appstore discussion
    • necessary infra needs to be added in appfw (signatures)
  • New topics:

April 10, 2019

Attendees: Jan-Simon, Jose, Loic, Ohiwa-san, Tom, Lorenzo, Stephane, George, Edi, Antia, Stoyan

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
  • Input manager
    • Update from Daniel on the window manager and compositor effort expected tomorrow during the SAT call.
    • Update 04/10:

* AppFW

  • Enable Token logic required for HTML5 apps and remote clients/apps
  • Enable multi-user across the reference platform.
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
  • Security workflow for Device and App developers
  • Replace obsolete Tizen Security Manager
  • Jose
    • Change to allow listing of all installed binders
    • Working on change to not run as root. Was waiting for thud migration to hit master. sandbox/jobol/wip-mu
    • Update 04/10: multi-user patches planned after Jose's vacation (~ in 2 weeks)
  • Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.
    • Update 04/10: no update today.

March 27, 2019

Attendees: Walt, Jan-Simon, Michael, Sebastien, Jose, Lorenzo, George, Kusakabe,

Priorities for 2019 * Window Manager and Compositor consolidation

  • Activity Manager
  • Input manager
  • Enable Token logic required for HTML5 apps and remote clients/apps
  • Enable multi-user across the reference platform.
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app or service will be installed on the system. Note that a service widget itself may choose to internally support multiple versions of its own API within a single widget, but that is up to the service provide to maintain.
  • Security workflow for Device and App developers
  • Replace obsolete Tizen Security Manager
  • Update from Daniel on the window manager and compositor effort expected tomorrow during the SAT call.
  • Jose
    • Change to allow listing of all installed binders
    • Working on change to not run as root. Was waiting for thud migration to hit master. sandbox/jobol/wip-mu
  • Migration of Qt Apps to HTML5
    • Will work with Igalia on a plan to do this throughout the year. Will announce the plan around the time of the F2F Meeting in May.

March 13, 2019

Attendees: Walt, Tom, Kurokawa, Ohiwa, Stephane, Pierre, Jose

Roadmap priorities for 2019

  • Window Manager and Compositor consolidation
  • Activity Manager
  • Input manager
  • Enable Token logic required for HTML5 apps and remote clients/apps
  • Enable multi-user across the reference platform.
    • Widget installation per user - When a given application is installed on the system it can be made available to all or to specific users.
    • Teen driver or senior citizen use cases for example
    • Only one version of a given app will be installed on the system
  • Security workflow for Device and App developers
  • Replace obsolete Tizen Security Manager

Pointed out meeting notes from last week's F2F meeting for those who were not there. Especially for Window Manager updates. See Confluence for details.

February 27, 2019

Cancelled due to AMM. See F2F meeting minutes.

February 13, 2019

Attendees: Walt, Jan-Simon, Guy, Jose, Kusakabe, Tanikawa, Tom

  • Window Manager and Home Screen services

January 30, 2019

Attendees: Walt, Ohiwa, Stephane, Guy, Daniel, Lorenzo, Kurokawa

  • Window Manager and Home Screen services
  • Update from Ohiwa-san:
    • Status slide
    • CES demo being updated for AMM. Getting permission to show at the AMM
    • Will merge the latest patches into master after guppy branch is created.
  • Refactor libwindowmanger and libhomescreen (Lorenzo and Abhijeet) and adding Application Lifecycle
  • SPEC-1920 closed after discussion last week and started Confluence page for redesign.
  • SPEC-1871 - mostly complete.
  • Started Confluence page for HMI Framework redesign
    • Igalia
      • Working on a flounder/chromium 68 branch in meta-agl-lge.
      • Should have working for CES on Renesas, Intel, Raspberry Pi
    • SPEC-2120 - Need to get Igalia and/or Collabora reviewing the proposed Window Manager changes in gerrit. Will get names to add to default reviewers.

* Roadmap for 2019 can be found here.

  • 1/16 - Updates to roadmap for 2019 to be presented to AB at the AMM are necessary. IoT.bzh has a list they are working on. Walt also discussing with Igalia and Collabora.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK/Monitoring/ Dev Tools
    • 1/17 - Roadmap update to plan 2019 for next meeting
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
    • 9/26 - Jose will add to GG as a build option so others can start debugging their services. Sebastien and Jose will put together a plan for getting this done by RC1. They will also send out a description of what App FW features will be added in the GG build.
    • 11/21 - Not ready for GG due to competing priorities.
    • 12/5 - Email from George on this topic. Jose has mic problems. Will discuss during SAT call.
    • 12/19 - Jose posted a number of patches and George is working on testing them. See dev call minutes from yesterday for more details.
    • 1/16 - No progress due to holidays/ CES
    • 1/30 - No further progress

New:

  • Will switch to zoom for next call to see how things work out.

January 16, 2019

Attendees: Walt, Jan-Simon, Loic, Sebastien, Xiaoming, Kusakabe

  • Window Manager and Home Screen services
  • Update from Ohiwa-san:
    • See latest status in SPEC-1932
    • CES Demo #3 shipped to Las Vegas
    • Walt purchased a Logitech 920 steering wheel to bring to CES.
  • Refactor libwindowmanger and libhomescreen (Lorenzo and Abhijeet) and adding Application Lifecycle
  • SPEC-1920 closed after discussion last week and started Confluence page for redesign.
  • SPEC-1871 - mostly complete.
  • Started Confluence page for HMI Framework redesign
    • Igalia
      • Working on a flounder/chromium 68 branch in meta-agl-lge.
      • Should have working for CES on Renesas, Intel, Raspberry Pi
    • SPEC-2120 - Need to get Igalia and/or Collabora reviewing the proposed Window Manager changes in gerrit. Will get names to add to default reviewers.

* Roadmap for 2019 can be found here.

  • 1/16 - Updates to roadmap for 2019 to be presented to AB at the AMM are necessary. IoT.bzh has a list they are working on. Walt also discussing with Igalia and Collabora.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK/Monitoring/ Dev Tools
    • 1/17 - Roadmap update to plan 2019 for next meeting
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
    • 9/26 - Jose will add to GG as a build option so others can start debugging their services. Sebastien and Jose will put together a plan for getting this done by RC1. They will also send out a description of what App FW features will be added in the GG build.
    • 11/21 - Not ready for GG due to competing priorities.
    • 12/5 - Email from George on this topic. Jose has mic problems. Will discuss during SAT call.
    • 12/19 - Jose posted a number of patches and George is working on testing them. See dev call minutes from yesterday for more details.
    • 1/16 - No progress due to holidays/ CES

New:

  • Will switch to zoom for next call to see how things work out.

January 2, 2019

Attendees: Upcoming Meeting Cancelled no one called in.

  • Window Manager and Home Screen services
  • Update from Ohiwa-san:
    • See latest status in SPEC-1932
    • CES Demo #3 shipped to Las Vegas
    • Walt purchased a Logitech 920 steering wheel to bring to CES.
  • Refactor libwindowmanger and libhomescreen (Lorenzo and Abhijeet) and adding Application Lifecycle
  • SPEC-1920 closed after discussion last week and started Confluence page for redesign.
  • SPEC-1871 - mostly complete.
  • Started Confluence page for HMI Framework redesign
    • Igalia
      • Working on a flounder/chromium 68 branch in meta-agl-lge.
      • Should have working for CES on Renesas, Intel, Raspberry Pi *

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
      • 8/29 - SDK basically ready for FF except release branch builds
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
    • 9/26 - Jose will add to GG as a build option so others can start debugging their services. Sebastien and Jose will put together a plan for getting this done by RC1. They will also send out a description of what App FW features will be added in the GG build.
    • 11/21 - Not ready for GG due to competing priorities.
    • 12/5 - Email from George on this topic. Jose has mic problems. Will discuss during SAT call.
    • 12/19 - Jose posted a number of patches and George is working on testing them. See dev call minutes from yesterday for more details.

New:

December 19, 2018

Attendees: Walt, Jose, Kusakabe, Kurokawa, Lorenzo

  • Window Manager and Home Screen services
  • Update from Ohiwa-san:
    • See latest status in SPEC-1932
    • CES Demo #3 shipped to Las Vegas
    • Walt purchased a Logitech 920 steering wheel to bring to CES.
  • Refactor libwindowmanger and libhomescreen (Lorenzo and Abhijeet) and adding Application Lifecycle
  • SPEC-1920 closed after discussion last week and started Confluence page for redesign.
  • SPEC-1871 - mostly complete.
  • Started Confluence page for HMI Framework redesign
    • Igalia
      • Working on a flounder/chromium 68 branch in meta-agl-lge.
      • Should have working for CES on Renesas, Intel, Raspberry Pi *

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
      • 8/29 - SDK basically ready for FF except release branch builds
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
    • 9/26 - Jose will add to GG as a build option so others can start debugging their services. Sebastien and Jose will put together a plan for getting this done by RC1. They will also send out a description of what App FW features will be added in the GG build.
    • 11/21 - Not ready for GG due to competing priorities.
    • 12/5 - Email from George on this topic. Jose has mic problems. Will discuss during SAT call.
    • 12/19 - Jose posted a number of patches and George is working on testing them. See dev call minutes from yesterday for more details.

New:

December 5, 2018

Attendees: Walt, Jan-Simon, Ohiwa, Sebastien, Kusakabe, Lorenzo, Dominig, Jose

  • Adding Window Manager and Home Screen services to App FW EG. The F2F meeting in Yokohama is addressing these topics this week.
    • Update from Ohiwa-san:
      • See latest status in SPEC-1932
      • Waltham in progress being debugged with ADIT. May use a workaround for CES.
      • Good progress being made on the split screen apps
      • CES Demo #3 integration will continue next week in Yokohama
      • Confirmed shipping arrangements for demo to Las Vegas. Walt will order steering wheel.
  • Refactor libwindowmanger and libhomescreen (Lorenzo and Abhijeet)
    • SPEC-1871 and SPEC-1920 - progressing. Need to discuss comments in SPEC-1920 with Mitsunari-san. Will send an email to him to attend the SAT call tomorrow.

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
      • 8/29 - SDK basically ready for FF except release branch builds
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
    • 9/26 - Jose will add to GG as a build option so others can start debugging their services. Sebastien and Jose will put together a plan for getting this done by RC1. They will also send out a description of what App FW features will be added in the GG build.
    • 11/21 - Not ready for GG due to competing priorities.
    • 12/5 - Email from George on this topic. Jose has mic problems. Will discuss during SAT call.
  • Other topics
    • Application Life Cycle
      • 8/1 - there's a jira on OOM (new facebook oomd), there's lifecycle discussion for apps (see gfx thread, Tanikawa-san), put on list to check for GG, needs agreement of events/states for app lifecycle.
      • 8/28 - Becoming more apparent that this is needed for GG. Tanikawa working on this. Will add to the F2F meeting agenda for discussion.

New:

November 21, 2018

Attendees: Walt, Sebastien, Abhijeet, Loic, Lorenzo, Stephane, Supriya, Ohiwa, Kurokawa

  • Adding Window Manager and Home Screen services to App FW EG. The F2F meeting in Yokohama is addressing these topics this week.
    • Update from Ohiwa-san:
      • Waltham in progress, being debugged. May be ready at the end of November
      • Currently split screen on display is the same size. They are making a change to allow the split window sizing to change via swipe. Challenging task! Being developed by Toyota
      • CES Demo #3 integration continuing at Toyota office and they will provide a weekly update
      • Will get a complete readout after the Yokohama F2F meeting
  • Refactor libwindowmanger and libhomescreen (Lorenzo and Abhijeet)
    • SPEC-1871 and SPEC-1920 - progressing. Probably another two weeks of work.

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
      • 8/29 - SDK basically ready for FF except release branch builds
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
    • 9/26 - Jose will add to GG as a build option so others can start debugging their services. Sebastien and Jose will put together a plan for getting this done by RC1. They will also send out a description of what App FW features will be added in the GG build.
    • 11/21 - Not ready for GG due to competing priorities.
  • Other topics
    • Application Life Cycle
      • 8/1 - there's a jira on OOM (new facebook oomd), there's lifecycle discussion for apps (see gfx thread, Tanikawa-san), put on list to check for GG, needs agreement of events/states for app lifecycle.
      • 8/28 - Becoming more apparent that this is needed for GG. Tanikawa working on this. Will add to the F2F meeting agenda for discussion.

New:

November 7, 2018

Attendees: Walt, Sebastien, Stephane, Loic, Ohiwa, Jose

  • Adding Window Manager and Home Screen services to App FW EG. The F2F meeting in Yokohama is addressing these topics this week.
    • Update from Ohiwa-san:
      • Waltham in progress, being debugged. May be ready at the end of November
      • Currently split screen on display is the same size. They are making a change to allow the split window sizing to change via swipe. Challenging task! Being developed by Toyota
      • CES Demo #3 integration continuing at Toyota office and they will provide a weekly update
      • Will get a complete readout after the Yokohama F2F meeting

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
    • 6/6 - Nothing to report.
    • 7/4 - Nothing to report
    • 7/18 - Nothing to report
    • 8/1 - Nothing new to report
    • 8/29 - No update
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
      • 8/29 - SDK basically ready for FF except release branch builds
  • Chromium and Web App Runtime from LG and Igalia
    • 7/4 - F2F meeting Santa Clara in Sep. Engaging Igalia to support.
    • 8/1 - meta-agl-lg still needs some fixes/adaptations
    • 8/29 - Sebastien has demo running on eel/ M3. FF not working due to current home screen issues in FF.
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
    • 9/26 - Jose will add to GG as a build option so others can start debugging their services. Sebastien and Jose will put together a plan for getting this done by RC1. They will also send out a description of what App FW features will be added in the GG build.
  • Other topics
    • Application Life Cycle
      • 8/1 - there's a jira on OOM (new facebook oomd), there's lifecycle discussion for apps (see gfx thread, Tanikawa-san), put on list to check for GG, needs agreement of events/states for app lifecycle.
      • 8/28 - Becoming more apparent that this is needed for GG. Tanikawa working on this. Will add to the F2F meeting agenda for discussion.
  • App FW vs. HMI FW split
  • Surface management
    • Making surfaces available to services such as navigation so that map is service available to native and HTML5 apps.
      • 8/1: runxdg working again
      • 8/28 - Zhang made some patches that ended up getting reverted for FF. Need a major revisit of this topic for GG.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
    • 7/4 - SPEC-1018 (restructure of folders) on hold
    • 8/1 - no update
    • 8/28 - no update

New:

October 10, 2018

Attendees: Walt

Meeting canceled due to lack of attendance.

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
    • 6/6 - Nothing to report.
    • 7/4 - Nothing to report
    • 7/18 - Nothing to report
    • 8/1 - Nothing new to report
    • 8/29 - No update
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
      • 8/29 - SDK basically ready for FF except release branch builds
  • Chromium and Web App Runtime from LG and Igalia
    • 7/4 - F2F meeting Santa Clara in Sep. Engaging Igalia to support.
    • 8/1 - meta-agl-lg still needs some fixes/adaptations
    • 8/29 - Sebastien has demo running on eel/ M3. FF not working due to current home screen issues in FF.
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
    • 9/26 - Jose will add to GG as a build option so others can start debugging their services. Sebastien and Jose will put together a plan for getting this done by RC1. They will also send out a description of what App FW features will be added in the GG build.
  • Other topics
    • Application Life Cycle
      • 8/1 - there's a jira on OOM (new facebook oomd), there's lifecycle discussion for apps (see gfx thread, Tanikawa-san), put on list to check for GG, needs agreement of events/states for app lifecycle.
      • 8/28 - Becoming more apparent that this is needed for GG. Tanikawa working on this. Will add to the F2F meeting agenda for discussion.
  • App FW vs. HMI FW split
  • Surface management
    • Making surfaces available to services such as navigation so that map is service available to native and HTML5 apps.
      • 8/1: runxdg working again
      • 8/28 - Zhang made some patches that ended up getting reverted for FF. Need a major revisit of this topic for GG.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
    • 7/4 - SPEC-1018 (restructure of folders) on hold
    • 8/1 - no update
    • 8/28 - no update

New:

September 26, 2018

Attendees: Walt, Stephane, Jose

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
    • 6/6 - Nothing to report.
    • 7/4 - Nothing to report
    • 7/18 - Nothing to report
    • 8/1 - Nothing new to report
    • 8/29 - No update
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
      • 8/29 - SDK basically ready for FF except release branch builds
  • Chromium and Web App Runtime from LG and Igalia
    • 7/4 - F2F meeting Santa Clara in Sep. Engaging Igalia to support.
    • 8/1 - meta-agl-lg still needs some fixes/adaptations
    • 8/29 - Sebastien has demo running on eel/ M3. FF not working due to current home screen issues in FF.
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
    • 9/26 - Jose will add to GG as a build option so others can start debugging their services. Sebastien and Jose will put together a plan for getting this done by RC1. They will also send out a description of what App FW features will be added in the GG build.
  • Other topics
    • Application Life Cycle
      • 8/1 - there's a jira on OOM (new facebook oomd), there's lifecycle discussion for apps (see gfx thread, Tanikawa-san), put on list to check for GG, needs agreement of events/states for app lifecycle.
      • 8/28 - Becoming more apparent that this is needed for GG. Tanikawa working on this. Will add to the F2F meeting agenda for discussion.
  • App FW vs. HMI FW split
  • Surface management
    • Making surfaces available to services such as navigation so that map is service available to native and HTML5 apps.
      • 8/1: runxdg working again
      • 8/28 - Zhang made some patches that ended up getting reverted for FF. Need a major revisit of this topic for GG.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
    • 7/4 - SPEC-1018 (restructure of folders) on hold
    • 8/1 - no update
    • 8/28 - no update

New:

September 12, 2018

See Santa Clara F2F Meeting for details.

August 29, 2018

Attendees: Walt, Jan-Simon, Sebastien, Stephane, Jose

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
    • 6/6 - Nothing to report.
    • 7/4 - Nothing to report
    • 7/18 - Nothing to report
    • 8/1 - Nothing new to report
    • 8/29 - No update
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
      • 8/29 - SDK basically ready for FF except release branch builds
  • Chromium and Web App Runtime from LG and Igalia
    • 7/4 - F2F meeting Santa Clara in Sep. Engaging Igalia to support.
    • 8/1 - meta-agl-lg still needs some fixes/adaptations
    • 8/29 - Sebastien has demo running on eel/ M3. FF not working due to current home screen issues in FF.
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
    • 8/28 - Jose has three patches that can be built to get the system running as a non-root user. Need guidelines for how to configure users, which services can run with root privileges, etc. Set a goal of having draft guidelines and a summary of what is done in other systems for the September 26 meeting of the EG.
  • Other topics
    • Application Life Cycle
      • 8/1 - there's a jira on OOM (new facebook oomd), there's lifecycle discussion for apps (see gfx thread, Tanikawa-san), put on list to check for GG, needs agreement of events/states for app lifecycle.
      • 8/28 - Becoming more apparent that this is needed for GG. Tanikawa working on this. Will add to the F2F meeting agenda for discussion.
  • App FW vs. HMI FW split
  • Surface management
    • Making surfaces available to services such as navigation so that map is service available to native and HTML5 apps.
      • 8/1: runxdg working again
      • 8/28 - Zhang made some patches that ended up getting reverted for FF. Need a major revisit of this topic for GG.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
    • 7/4 - SPEC-1018 (restructure of folders) on hold
    • 8/1 - no update
    • 8/28 - no update
  • Code reviewers for EG: Jose, ask Dominig, Need someone focused on security, Tanikawa or someone else from Japan, Thierry

New:

  • SPEC-1230 reopened - re-install app does not update cynara privileges.
    • Jose investigating. Trying to get a fix for RC5

August 16, 2018

Attendees: Walt, Jan-Simon, Scott, Sebastien, Fulup, Romain

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
    • 6/6 - Nothing to report.
    • 7/4 - Nothing to report
    • 7/18 - Nothing to report
    • 8/1 - Nothing new to report
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
  • API v3.0 - planned for FF
    • 7/4 - API v3.0 went into RC1. Some bugs to be fixed by Jose.
    • 8/1 - doc update pending (migration guide v2→v3)
  • Chromium and Web App Runtime from LG and Igalia
    • 7/4 - F2F meeting Santa Clara in Sep. Engaging Igalia to support.
    • 8/1 - meta-agl-lg still needs some fixes/adaptations
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
  • Other topics
    • Application Life Cycle
      • 8/1 - there's a jira on OOM (new facebook oomd), there's lifecycle discussion for apps (see gfx thread, Tanikawa-san), put on list to check for GG, needs aggreement of events/states for app lifecycle.
    • App FW vs. HMI FW split
    • Surface management
      • Making surfaces available to services such as navigation so that map is service available to native and HTML5 apps.
        • 8/1: runxdg working again
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
    • 7/4 - SPEC-1018 (restructure of folders) on hold
    • 8/1 - no update
  • Code reviewers for EG: Jose, ask Dominig, Need someone focused on security, Tanikawa or someone else from Japan, Thierry

New:

Aug 1, 2018

Attendees: Jan-Simon, Stephane, Momiyama-san

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
    • 6/6 - Nothing to report.
    • 7/4 - Nothing to report
    • 7/18 - Nothing to report
    • 8/1 - Nothing new to report
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • 8/1 No update
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report
  • 8/1 - No update. Walt to ping Denso.

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
      • 8/1 - gerrit part solved, ci builds solved, release branch builds not yet done
  • API v3.0 - planned for FF
    • 7/4 - API v3.0 went into RC1. Some bugs to be fixed by Jose.
    • 8/1 - doc update pending (migration guide v2→v3)
  • Chromium and Web App Runtime from LG and Igalia
    • 7/4 - F2F meeting Santa Clara in Sep. Engaging Igalia to support.
    • 8/1 - meta-agl-lg still needs some fixes/adaptations
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
    • 8/1 - Working towards it.
  • Other topics
    • Application Life Cycle
      • 8/1 - there's a jira on OOM (new facebook oomd), there's lifecycle discussion for apps (see gfx thread, Tanikawa-san), put on list to check for GG, needs aggreement of events/states for app lifecycle.
    • App FW vs. HMI FW split
    • Surface management
      • Making surfaces available to services such as navigation so that map is service available to native and HTML5 apps.
        • 8/1: runxdg working again
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
    • 7/4 - SPEC-1018 (restructure of folders) on hold
    • 8/1 - no update
  • Code reviewers for EG: Jose, ask Dominig, Need someone focused on security, Tanikawa or someone else from Japan, Thierry

New:

July 18, 2018

Attendees: Walt, Jan-Simon, Sebastien, Stephane, Jose

* Roadmap for 2018 can be found here.

  • Continued roadmap review. Added GG priority list.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
    • 6/6 - Nothing to report.
    • 7/4 - Nothing to report
    • 7/18 - Nothing to report
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
      • 7/18 - Working on adding XDS client to gerrit/ CI
  • API v3.0 - planned for FF
    • 7/4 - API v3.0 went into RC1. Some bugs to be fixed by Jose.
  • Chromium and Web App Runtime from LG and Igalia
    • 7/4 - F2F meeting Santa Clara in Sep. Engaging Igalia to support.
  • Not running as root.
    • 7/4 - On hold. Need to review whether we can get this into GG.
  • Other topics
    • Application Life Cycle
    • App FW vs. HMI FW split
    • Surface management
      • Making surfaces available to services such as navigation so that map is service available to native and HTML5 apps.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
    • 7/4 - SPEC-1018 (restructure of folders) on hold
  • Code reviewers for EG: Jose, ask Dominig, Need someone focused on security, Tanikawa or someone else from Japan, Thierry

New:

July 4, 2018

Attendees: Walt, Jan-Simon, Tanikawa, Stephane, Jose, Sebastien

  • Roadmap for 2018 can be found here.
    • Starting to review for features that were completed in FF, what will be done in GG, and any features for 2019.
  • Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/docs/sec-blueprint)
    • 11/22
      • Eli sending comments on the system hardening section to the mail list or on github directly.
      • IoT.bzh reviewing the document and has a proposal for some restructuring. The Application Security section is need of an update.
      • Jan-Simon found some inconsistencies between the hardening guide and the current kernel configuration. See comments in https://github.com/automotive-grade-linux/docs-agl/pull/28
    • 12/6
      • Eli still working on his comments
      • Sebastien and Vincent completed a rework of the Security Blueprint based on the latest code. They published a pdf to the mail list. Will add to github in a new directory later today. Walt will reply to their email with a request to review the document and add comments to github before the next EG meeting (Dec 20).
    • 12/21
      • Only a few comments received on the document so we will postpone the review until the new year. Will send an email reminding people to review the document.
    • 1/3
      • No update
    • 1/17
      • No comments received. Most likely due to CES.
    • 1/31
    • 2/14 - No comments received.
    • 3/28 - Eli's comments were sent to the mail list for review.
    • 4/25 - In progress. Pull request was done by Vincent. Some open issues remain. See https://github.com/automotive-grade-linux/docs-agl/issues/112
    • 5/23 - Pull request merged. Old version still appears on the doc site. Sebastien will send an email to the mail proposing to remove it. Will remove it after next meeting if there is no dissent. Will request the Virtualization EG to update section 3. A list of updates needed are in the TODO Notes section.
    • 6/6 - Since there was no dissent about removing the old version we will remove it ASAP. SPEC-1502. Jira tickets created for the rest of the ToDo list in the document.
    • 7/4 - Old version needs to be removed. ToDo list is progressing.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
    • 6/6 - Nothing to report.
    • 7/4 - Nothing to report
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
  • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)
  • 5/23 - Need to get this moving.
  • 6/6 - Nothing to report
  • 7/4 - Nothing to report

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 3/28 - Sebastien working on monitoring and supervision for Karlsruhe meeting.
      • 4/25 - In progress
      • ptest(-wrapper) for CI, developer local run, diagnostics in production5/23 - XDS 1.1.1 released. SPEC-1361 in progress for publishing XDS packages. Next step is Sebastien's. XDS 2.0.0 still on target for ALS.
      • 6/6 - XDS 2.0.0 - Stephane will present a video with a demo use case at ALS. Software be published in time for ALS (consider it an alpha release, not bug free, but can be tried out).
      • 7/4 - Stephane's demo of the monitoring at ALS went well. Sebastien and Jan-Simon worked on aligning the versioning of XDS with the rest of AGL. XDS 2.0.0 is now 6.0.0.
  • API v3.0 - planned for FF
    • Dynamic API, binder/API discovery
    • 3/28 - Features will be discussed in Karlsruhe in detail. What is the plan to deprecate API v2.0 once 3.0 is available? Thought is that one year of overlap will be sufficient. To be discussed further in Karlsruhe.
    • 4/25 - In progress. Should see something pushed to gerrit by the next meeting of EG.
    • 5/23 - In progress and under test by Jose. API v3.0 should be ready for RC1.
    • 6/6 - Jose will be ready to push in time for RC1 with documentation and stabilization updates to follow.
    • 7/4 - API v3.0 went into RC1. Some bugs to be fixed by Jose.
  • Chromium and Web App Runtime from LG and Igalia
    • 2/14 - Silvia will be at the AMM next week to discuss schedule and roadmap from Igalia. Need to discuss
      • Chromium for HTML5 apps and how to get that integrated into AGL.
      • Chromium browser and app support for all reference boards
    • 3/28 - Need to work out a plan with Igalia and LG for web apps based on their discussions at the AMM.
    • 4/25 - Steve L. - LG SVL porting web app runtime (WAM) and Chromium from WebOS OSE to AGL this week. WebOS OSE + Daring Dab + Chromium 53. Goal is to have web app up and running on AGL this week. Background: WebOS has been running web apps LG TVs since 2013, and was first created in 2008 for WebOS phones and tablets from HP/Palm. WebOS was first open-sourced by HP in 2012; LG released WebOS OSE just after the AMM in February.
      • Stephane showed Chromium Embedded Framework (CEF), but to avoid confusion: CEF is not relevant to the current WebOS OSE AGL effort.
      • Steve ran across an email thread from Dominig email and another email from Tizen days regarding Crosswalk, Web App, security and process model issues that were being looked at by Tizen. WebOS already addresses many of these concerns in televisions.
      • Follow up technical meeting at 10 am PDT/ 7 pm CET.
    • 5/23 - LG will be at the F2F in Lorient in two weeks.
    • 6/6 - LG will arrive in Lorient tomorrow.
    • 7/4 - F2F meeting Santa Clara in Sep. Engaging Igalia to support.
  • Not running as root.
    • 3/28 - Work in progress. Kernel patches from Tizen BSPs are needed and Jose and is trying to get those upstream in a single place in the kernel.
    • 4/25 - Work is on standby. Patch merged in gerrit to enable this. Jose needs to test.
    • 5/23 - Still on standby. Probably not ready for FF. Still a lot of testing to do and we do not want to risk breaking FF with this change.
    • 6/6 - On hold.
    • 7/4 - On hold. Need to review whether we can get this into GG.
  • Other topics
    • Application Life Cycle
    • App FW vs. HMI FW split
    • Surface management
      • Making surfaces available to services such as navigation so that map is service available to native and HTML5 apps.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
    • 7/4 - SPEC-1018 (restructure of folders) on hold
  • Code reviewers for EG: Jose, ask Dominig, Need someone focused on security, Tanikawa or someone else from Japan, Thierry

New:

June 20, 2018

Canceled due to Automotive Linux Summit.

June 6, 2018

Attendees: Walt, Jan-Simon, Sebastien, Stephane, Jose

  • Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/docs/sec-blueprint)
    • 11/22
      • Eli sending comments on the system hardening section to the mail list or on github directly.
      • IoT.bzh reviewing the document and has a proposal for some restructuring. The Application Security section is need of an update.
      • Jan-Simon found some inconsistencies between the hardening guide and the current kernel configuration. See comments in https://github.com/automotive-grade-linux/docs-agl/pull/28
    • 12/6
      • Eli still working on his comments
      • Sebastien and Vincent completed a rework of the Security Blueprint based on the latest code. They published a pdf to the mail list. Will add to github in a new directory later today. Walt will reply to their email with a request to review the document and add comments to github before the next EG meeting (Dec 20).
    • 12/21
      • Only a few comments received on the document so we will postpone the review until the new year. Will send an email reminding people to review the document.
    • 1/3
      • No update
    • 1/17
      • No comments received. Most likely due to CES.
    • 1/31
    • 2/14 - No comments received.
    • 3/28 - Eli's comments were sent to the mail list for review.
    • 4/25 - In progress. Pull request was done by Vincent. Some open issues remain. See https://github.com/automotive-grade-linux/docs-agl/issues/112
    • 5/23 - Pull request merged. Old version still appears on the doc site. Sebastien will send an email to the mail proposing to remove it. Will remove it after next meeting if there is no dissent. Will request the Virtualization EG to update section 3. A list of updates needed are in the TODO Notes section.
    • 6/6 - Since there was no dissent about removing the old version we will remove it ASAP. SPEC-1502. Jira tickets created for the rest of the ToDo list in the document.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
    • 6/6 - Nothing to report.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 3/28 - Sebastien working on monitoring and supervision for Karlsruhe meeting.
      • 4/25 - In progress
      • 5/23 - XDS 1.1.1 released. SPEC-1361 in progress for publishing XDS packages. Next step is Sebastien's. XDS 2.0.0 still on target for ALS.
      • 6/6 - XDS 2.0.0 - Stephane will present a video with a demo use case at ALS. Software be published in time for ALS (consider it an alpha release, not bug free, but can be tried out).
  • API v3.0 - planned for FF
    • Dynamic API, binder/API discovery
    • 3/28 - Features will be discussed in Karlsruhe in detail. What is the plan to deprecate API v2.0 once 3.0 is available? Thought is that one year of overlap will be sufficient. To be discussed further in Karlsruhe.
    • 4/25 - In progress. Should see something pushed to gerrit by the next meeting of EG.
    • 5/23 - In progress and under test by Jose. API v3.0 should be ready for RC1.
    • 6/6 - Jose will be ready to push in time for RC1 with documentation and stabilization updates to follow.
  • Chromium and Web App Runtime from LG and Igalia
    • 2/14 - Silvia will be at the AMM next week to discuss schedule and roadmap from Igalia. Need to discuss
      • Chromium for HTML5 apps and how to get that integrated into AGL.
      • Chromium browser and app support for all reference boards
    • 3/28 - Need to work out a plan with Igalia and LG for web apps based on their discussions at the AMM.
    • 4/25 - Steve L. - LG SVL porting web app runtime (WAM) and Chromium from WebOS OSE to AGL this week. WebOS OSE + Daring Dab + Chromium 53. Goal is to have web app up and running on AGL this week. Background: WebOS has been running web apps LG TVs since 2013, and was first created in 2008 for WebOS phones and tablets from HP/Palm. WebOS was first open-sourced by HP in 2012; LG released WebOS OSE just after the AMM in February.
      • Stephane showed Chromium Embedded Framework (CEF), but to avoid confusion: CEF is not relevant to the current WebOS OSE AGL effort.
      • Steve ran across an email thread from Dominig email and another email from Tizen days regarding Crosswalk, Web App, security and process model issues that were being looked at by Tizen. WebOS already addresses many of these concerns in televisions.
      • Follow up technical meeting at 10 am PDT/ 7 pm CET.
    • 5/23 - LG will be at the F2F in Lorient in two weeks.
    • 6/6 - LG will arrive in Lorient tomorrow.
  • Not running as root.
    • 3/28 - Work in progress. Kernel patches from Tizen BSPs are needed and Jose and is trying to get those upstream in a single place in the kernel.
    • 4/25 - Work is on standby. Patch merged in gerrit to enable this. Jose needs to test.
    • 5/23 - Still on standby. Probably not ready for FF. Still a lot of testing to do and we do not want to risk breaking FF with this change.
    • 6/6 - On hold.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
  • From Stephane:
    • How to handle services/apps packages (widgets) until we have an app store (at least for developers). Typical example: CAN low level service which is ready to be shipped into AGL as a reference implementation for CAN
    • Immediate solution (DD): build packages during platform build (bitbake recipe) then embed into image, install at first boot. This is what we have currently for agl-demo. Typically, CAN-signaling should enter in that category
    • After DD: setup AGL profiles and determine in which profile a given app/service should be preinstalled (still using platform builds+firstboot)
    • EE-rc1: setup a separate build for apps/services then tell developers how to grab those packages and install by hand (wget … ; afm-util install …) depending on their needs
    • Later (EE?): have an appfw store (kinda repository) and a client to download and install apps/services from a store
    • Update 9/27 - Working on app branches for master and dab. We should shortly have the download folder ready.
    • Update 10/11 - 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.
    • Update 11/1 - SPEC-1018 created to figure out the dab and master overwrite issue.
    • 11/8 - No update
    • 11/22 - No update. Need to add Eel folder as well.
    • 12/6 - Need to check with Jan-Simon
    • 12/21 Folders now work SPEC-1018). Waiting on a full build for all apps for Eel. Need to populate the dab folder with the dab apps on the dab branch. SPEC-1019.
      • Comment from Stephane to reorganize the folder structure to allow for easier download by branch or by boards, etc. Will add a suggested folder structure to SPEC-1018.
      • 1/3 - SPEC-1018 in progress. Would be nice to have the ability to download via a package manager from the target as well. Need to be able to verify the certificates and signatures of the apps being downloaded.
      • 1/31 - Settled on restructure of the folders for the repository (SPEC-1018).
      • 2/14 - SPEC-1018 in progress
      • 4/25 - SPEC-1018 on hold.
      • 5/23 - SPEC-1018 on hold.
      • 6/6 - SPEC-1018 on hold.
  • Code reviewers for EG: Jose, ask Dominig, Need someone focused on security, Tanikawa or someone else from Japan, New guy from IoT.bzh (Thierry)

New:

May 23, 2018

Attendees: Walt, Jan-Simon, Tanikawa, Kurokawa, Sebastien, Jose

  • Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/docs/sec-blueprint)
    • 11/22
      • Eli sending comments on the system hardening section to the mail list or on github directly.
      • IoT.bzh reviewing the document and has a proposal for some restructuring. The Application Security section is need of an update.
      • Jan-Simon found some inconsistencies between the hardening guide and the current kernel configuration. See comments in https://github.com/automotive-grade-linux/docs-agl/pull/28
    • 12/6
      • Eli still working on his comments
      • Sebastien and Vincent completed a rework of the Security Blueprint based on the latest code. They published a pdf to the mail list. Will add to github in a new directory later today. Walt will reply to their email with a request to review the document and add comments to github before the next EG meeting (Dec 20).
    • 12/21
      • Only a few comments received on the document so we will postpone the review until the new year. Will send an email reminding people to review the document.
    • 1/3
      • No update
    • 1/17
      • No comments received. Most likely due to CES.
    • 1/31
    • 2/14 - No comments received.
    • 3/28 - Eli's comments were sent to the mail list for review.
    • 4/25 - In progress. Pull request was done by Vincent. Some open issues remain. See https://github.com/automotive-grade-linux/docs-agl/issues/112
    • 5/23 - Pull request merged. Old version still appears on the doc site. Sebastien will send an email to the mail proposing to remove it. Will remove it after next meeting if there is no dissent. Will request the Virtualization EG to update section 3. A list of updates needed are in the TODO Notes section.

SafeRide proposal

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
    • 5/23 - Nothing to report.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting

Application Framework

  • SDK
    • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
      • Monitoring integration
      • Improved development cycle (based on partial Widget installation) (Update 5/25 - May be deferred past ALS)
      • First step to support package manager for SDKs (Yomo) (Update 5/25 - May be deferred past ALS)
      • Bug fixes
      • 3/28 - Sebastien working on monitoring and supervision for Karlsruhe meeting.
      • 4/25 - In progress
      • 5/23 - XDS 1.1.1 released. SPEC-1361 in progress for publishing XDS packages. Next step is Sebastien's. XDS 2.0.0 still on target for ALS.
  • API v3.0 - planned for FF
    • Dynamic API, binder/API discovery
    • 3/28 - Features will be discussed in Karlsruhe in detail. What is the plan to deprecate API v2.0 once 3.0 is available? Thought is that one year of overlap will be sufficient. To be discussed further in Karlsruhe.
    • 4/25 - In progress. Should see something pushed to gerrit by the next meeting of EG.
    • 5/23 - In progress and under test by Jose. API v3.0 should be ready for RC1.
  • Chromium and Web App Runtime from LG and Igalia
    • 2/14 - Silvia will be at the AMM next week to discuss schedule and roadmap from Igalia. Need to discuss
      • Chromium for HTML5 apps and how to get that integrated into AGL.
      • Chromium browser and app support for all reference boards
    • 3/28 - Need to work out a plan with Igalia and LG for web apps based on their discussions at the AMM.
    • 4/25 - Steve L. - LG SVL porting web app runtime (WAM) and Chromium from WebOS OSE to AGL this week. WebOS OSE + Daring Dab + Chromium 53. Goal is to have web app up and running on AGL this week. Background: WebOS has been running web apps LG TVs since 2013, and was first created in 2008 for WebOS phones and tablets from HP/Palm. WebOS was first open-sourced by HP in 2012; LG released WebOS OSE just after the AMM in February.
      • Stephane showed Chromium Embedded Framework (CEF), but to avoid confusion: CEF is not relevant to the current WebOS OSE AGL effort.
      • Steve ran across an email thread from Dominig email and another email from Tizen days regarding Crosswalk, Web App, security and process model issues that were being looked at by Tizen. WebOS already addresses many of these concerns in televisions.
      • Follow up technical meeting at 10 am PDT/ 7 pm CET.
    • 5/23 - LG will be at the F2F in Lorient in two weeks.
  • Not running as root.
    • 3/28 - Work in progress. Kernel patches from Tizen BSPs are needed and Jose and is trying to get those upstream in a single place in the kernel.
    • 4/25 - Work is on standby. Patch merged in gerrit to enable this. Jose needs to test.
    • 5/23 - Still on standby. Probably not ready for FF. Still a lot of testing to do and we do not want to risk breaking FF with this change.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
  • From Stephane:
    • How to handle services/apps packages (widgets) until we have an app store (at least for developers). Typical example: CAN low level service which is ready to be shipped into AGL as a reference implementation for CAN
    • Immediate solution (DD): build packages during platform build (bitbake recipe) then embed into image, install at first boot. This is what we have currently for agl-demo. Typically, CAN-signaling should enter in that category
    • After DD: setup AGL profiles and determine in which profile a given app/service should be preinstalled (still using platform builds+firstboot)
    • EE-rc1: setup a separate build for apps/services then tell developers how to grab those packages and install by hand (wget … ; afm-util install …) depending on their needs
    • Later (EE?): have an appfw store (kinda repository) and a client to download and install apps/services from a store
    • Update 9/27 - Working on app branches for master and dab. We should shortly have the download folder ready.
    • Update 10/11 - 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.
    • Update 11/1 - SPEC-1018 created to figure out the dab and master overwrite issue.
    • 11/8 - No update
    • 11/22 - No update. Need to add Eel folder as well.
    • 12/6 - Need to check with Jan-Simon
    • 12/21 Folders now work SPEC-1018). Waiting on a full build for all apps for Eel. Need to populate the dab folder with the dab apps on the dab branch. SPEC-1019.
      • Comment from Stephane to reorganize the folder structure to allow for easier download by branch or by boards, etc. Will add a suggested folder structure to SPEC-1018.
      • 1/3 - SPEC-1018 in progress. Would be nice to have the ability to download via a package manager from the target as well. Need to be able to verify the certificates and signatures of the apps being downloaded.
      • 1/31 - Settled on restructure of the folders for the repository (SPEC-1018).
      • 2/14 - SPEC-1018 in progress
      • 4/25 - SPEC-1018 on hold.
      • 5/23 - SPEC-1018 on hold.
  • Code reviewers for EG: Jose, ask Dominig, Need someone focused on security, Tanikawa or someone else from Japan, New guy from IoT.bzh (Thierry)

New:

May 9, 2018

Attendees:Upcoming Meeting

Notes from Dresden Meeting.

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting

Application Framework

  • SDK
    • XDS v1.1.0 in progress - targeted release date: AMM (2018 February 20th)
      • Board console/terminal integration within XDS dashboard
      • Documentation improvement of debug section
      • Bug fixes
    • 2/14 - On track to be available next week.
    • 3/28 - Now available. Action item for Jan-Simon (SPEC-1361) to make XDS source packages available on the download server.
    • 4/25 - SPEC-1361 in progress.
  • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
    • Monitoring integration
    • Improved development cycle (based on partial Widget installation)
    • First step to support package manager for SDKs (Yomo)
    • Bug fixes
    • 3/28 - Sebastien working on monitoring and supervision for Karlsruhe meeting.
    • 4/25 - In progress
  • API v3.0 - planned for FF
    • Dynamic API, binder/API discovery
    • 3/28 - Features will be discussed in Karlsruhe in detail. What is the plan to deprecate API v2.0 once 3.0 is available? Thought is that one year of overlap will be sufficient. To be discussed further in Karlsruhe.
    • 4/25 - In progress. Should see something pushed to gerrit by the next meeting of EG.
  • Chromium and Web App Runtime from LG and Igalia
    • 2/14 - Silvia will be at the AMM next week to discuss schedule and roadmap from Igalia. Need to discuss
      • Chromium for HTML5 apps and how to get that integrated into AGL.
      • Chromium browser and app support for all reference boards
    • 3/28 - Need to work out a plan with Igalia and LG for web apps based on their discussions at the AMM.
    • 4/25 - Steve L. - LG SVL porting web app runtime (WAM) and Chromium from WebOS OSE to AGL this week. WebOS OSE + Daring Dab + Chromium 53. Goal is to have web app up and running on AGL this week. Background: WebOS has been running web apps LG TVs since 2013, and was first created in 2008 for WebOS phones and tablets from HP/Palm. WebOS was first open-sourced by HP in 2012; LG released WebOS OSE just after the AMM in February.
      • Stephane showed Chromium Embedded Framework (CEF), but to avoid confusion: CEF is not relevant to the current WebOS OSE AGL effort.
      • Steve ran across an email thread from Dominig email and another email from Tizen days regarding Crosswalk, Web App, security and process model issues that were being looked at by Tizen. WebOS already addresses many of these concerns in televisions.
      • Follow up technical meeting at 10 am PDT/ 7 pm CET.
  • Not running as root.
    • 3/28 - Work in progress. Kernel patches from Tizen BSPs are needed and Jose and is trying to get those upstream in a single place in the kernel.
    • 4/25 - Work is on standby. Patch merged in gerrit to enable this. Jose needs to test.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
  • From Stephane:
    • How to handle services/apps packages (widgets) until we have an app store (at least for developers). Typical example: CAN low level service which is ready to be shipped into AGL as a reference implementation for CAN
    • Immediate solution (DD): build packages during platform build (bitbake recipe) then embed into image, install at first boot. This is what we have currently for agl-demo. Typically, CAN-signaling should enter in that category
    • After DD: setup AGL profiles and determine in which profile a given app/service should be preinstalled (still using platform builds+firstboot)
    • EE-rc1: setup a separate build for apps/services then tell developers how to grab those packages and install by hand (wget … ; afm-util install …) depending on their needs
    • Later (EE?): have an appfw store (kinda repository) and a client to download and install apps/services from a store
    • Update 9/27 - Working on app branches for master and dab. We should shortly have the download folder ready.
    • Update 10/11 - 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.
    • Update 11/1 - SPEC-1018 created to figure out the dab and master overwrite issue.
    • 11/8 - No update
    • 11/22 - No update. Need to add Eel folder as well.
    • 12/6 - Need to check with Jan-Simon
    • 12/21 Folders now work SPEC-1018). Waiting on a full build for all apps for Eel. Need to populate the dab folder with the dab apps on the dab branch. SPEC-1019.
      • Comment from Stephane to reorganize the folder structure to allow for easier download by branch or by boards, etc. Will add a suggested folder structure to SPEC-1018.
      • 1/3 - SPEC-1018 in progress. Would be nice to have the ability to download via a package manager from the target as well. Need to be able to verify the certificates and signatures of the apps being downloaded.
      • 1/31 - Settled on restructure of the folders for the repository (SPEC-1018).
      • 2/14 - SPEC-1018 in progress
      • 4/25 - SPEC-1018 on hold.

New:

  • Code reviewers for EG: Jose, ask Dominig, Need someone focused on security, Tanikawa or someone else from Japan, New guy from IoT.bzh (Thierry)

April 25, 2018

Attendees: Walt, Jan-Simon, Steve L., Sebastien, Stephane, Sebastien, Tanikawa, Michael, Jose

Notes from Dresden Meeting.

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopp about getting them accepted.
    • 4/25 - Discussions in progress between Oliver and Oshri.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • Update 11/1 - Walt to get this done this week.
    • Update 11/8 - No update
    • Update 11/22 - No update
    • 12/6 - No update
    • 1/3 - No update
    • 1/17 - No update
    • 1/31 - No update
    • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)

Application Framework

  • SDK
    • XDS v1.1.0 in progress - targeted release date: AMM (2018 February 20th)
      • Board console/terminal integration within XDS dashboard
      • Documentation improvement of debug section
      • Bug fixes
    • 2/14 - On track to be available next week.
    • 3/28 - Now available. Action item for Jan-Simon (SPEC-1361) to make XDS source packages available on the download server.
    • 4/25 - SPEC-1361 in progress.
  • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
    • Monitoring integration
    • Improved development cycle (based on partial Widget installation)
    • First step to support package manager for SDKs (Yomo)
    • Bug fixes
    • 3/28 - Sebastien working on monitoring and supervision for Karlsruhe meeting.
    • 4/25 - In progress
  • API v3.0 - planned for FF
    • Dynamic API, binder/API discovery
    • 3/28 - Features will be discussed in Karlsruhe in detail. What is the plan to deprecate API v2.0 once 3.0 is available? Thought is that one year of overlap will be sufficient. To be discussed further in Karlsruhe.
    • 4/25 - In progress. Should see something pushed to gerrit by the next meeting of EG.
  • Chromium and Web App Runtime from LG and Igalia
    • 2/14 - Silvia will be at the AMM next week to discuss schedule and roadmap from Igalia. Need to discuss
      • Chromium for HTML5 apps and how to get that integrated into AGL.
      • Chromium browser and app support for all reference boards
    • 3/28 - Need to work out a plan with Igalia and LG for web apps based on their discussions at the AMM.
    • 4/25 - Steve L. - LG SVL porting web app runtime (WAM) and Chromium from WebOS OSE to AGL this week. WebOS OSE + Daring Dab + Chromium 53. Goal is to have web app up and running on AGL this week. Background: WebOS has been running web apps LG TVs since 2013, and was first created in 2008 for WebOS phones and tablets from HP/Palm. WebOS was first open-sourced by HP in 2012; LG released WebOS OSE just after the AMM in February.
      • Stephane showed Chromium Embedded Framework (CEF), but to avoid confusion: CEF is not relevant to the current WebOS OSE AGL effort.
      • Steve ran across an email thread from Dominig email and another email from Tizen days regarding Crosswalk, Web App, security and process model issues that were being looked at by Tizen. WebOS already addresses many of these concerns in televisions.
      • Follow up technical meeting at 10 am PDT/ 7 pm CET.
  • Dominig - will need to define a strategy to maintain iot security layer since ostro moved in a different direction. Ostro removed cynara. Need Jira issue to track.
    • 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
    • Jose to evaluate Tizen 4.0 security to see what they have done (SPEC-763)
    • Update 12/6 - On hold
    • 12/21 - On hold
    • 1/3 - Jose working on evaluation. Maybe done by end of January.
    • 1/31 - Jose is working on security layer updates as part of the uprev to rocko. Middle of next week per dev call yesterday. Also evaluation of Tizen 4.0 (SPEC-763) was completed. See Jira for results. Summary is that there is nothing much we can use from Tizen 4.0 since we have diverged a bit from their approach. Possibly can use Integrated Network Enforcement from Tizen 4.0.
    • 2/14 - Jose has the new security layer building for rocko. Testing in progress.
    • 3/28 - New security layer (meta-security) is merged as part of the update to rocko, but there is an issue with ptest.
    • 4/25 - ptest issue resolved. Can close this issue.
  • Not running as root.
    • 3/28 - Work in progress. Kernel patches from Tizen BSPs are needed and Jose and is trying to get those upstream in a single place in the kernel.
    • 4/25 - Work is on standby. Patch merged in gerrit to enable this. Jose needs to test.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
  • From Stephane:
    • How to handle services/apps packages (widgets) until we have an app store (at least for developers). Typical example: CAN low level service which is ready to be shipped into AGL as a reference implementation for CAN
    • Immediate solution (DD): build packages during platform build (bitbake recipe) then embed into image, install at first boot. This is what we have currently for agl-demo. Typically, CAN-signaling should enter in that category
    • After DD: setup AGL profiles and determine in which profile a given app/service should be preinstalled (still using platform builds+firstboot)
    • EE-rc1: setup a separate build for apps/services then tell developers how to grab those packages and install by hand (wget … ; afm-util install …) depending on their needs
    • Later (EE?): have an appfw store (kinda repository) and a client to download and install apps/services from a store
    • Update 9/27 - Working on app branches for master and dab. We should shortly have the download folder ready.
    • Update 10/11 - 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.
    • Update 11/1 - SPEC-1018 created to figure out the dab and master overwrite issue.
    • 11/8 - No update
    • 11/22 - No update. Need to add Eel folder as well.
    • 12/6 - Need to check with Jan-Simon
    • 12/21 Folders now work SPEC-1018). Waiting on a full build for all apps for Eel. Need to populate the dab folder with the dab apps on the dab branch. SPEC-1019.
      • Comment from Stephane to reorganize the folder structure to allow for easier download by branch or by boards, etc. Will add a suggested folder structure to SPEC-1018.
      • 1/3 - SPEC-1018 in progress. Would be nice to have the ability to download via a package manager from the target as well. Need to be able to verify the certificates and signatures of the apps being downloaded.
      • 1/31 - Settled on restructure of the folders for the repository (SPEC-1018).
      • 2/14 - SPEC-1018 in progress
      • 4/25 - SPEC-1018 on hold.

New:

  • Code reviewers for EG: Jose, ask Dominig, Need someone focused on security, Tanikawa or someone else from Japan, New guy from IoT.bzh (Thierry)

March 28, 2018

Attendees: Walt, Stephane, Dominig, Jose, Sebastien, Eli

  • Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/docs/sec-blueprint)
    • 11/22
      • Eli sending comments on the system hardening section to the mail list or on github directly.
      • IoT.bzh reviewing the document and has a proposal for some restructuring. The Application Security section is need of an update.
      • Jan-Simon found some inconsistencies between the hardening guide and the current kernel configuration. See comments in https://github.com/automotive-grade-linux/docs-agl/pull/28
    • 12/6
      • Eli still working on his comments
      • Sebastien and Vincent completed a rework of the Security Blueprint based on the latest code. They published a pdf to the mail list. Will add to github in a new directory later today. Walt will reply to their email with a request to review the document and add comments to github before the next EG meeting (Dec 20).
    • 12/21
      • Only a few comments received on the document so we will postpone the review until the new year. Will send an email reminding people to review the document.
    • 1/3
      • No update
    • 1/17
      • No comments received. Most likely due to CES.
    • 1/31
    • 2/14 - No comments received.
    • 3/28 - Eli's comments were sent to the mail list for review.

Notes from Dresden Meeting.

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
    • 3/28 - Oshri pushed the patches to gerrit. Need to get them accepted upstream in the kernel. He has been communicating with Oliver Hartkopf about getting them accepted.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • Update 11/1 - Walt to get this done this week.
    • Update 11/8 - No update
    • Update 11/22 - No update
    • 12/6 - No update
    • 1/3 - No update
    • 1/17 - No update
    • 1/31 - No update
    • 3/28 - Need to get a copy of the Denso presentation from the AMM so we can review it. Also should take a look at FASTR ( Future of Automotive Security Technology Research)

Application Framework

  • SDK
    • XDS v1.1.0 in progress - targeted release date: AMM (2018 February 20th)
      • Board console/terminal integration within XDS dashboard
      • Documentation improvement of debug section
      • Bug fixes
    • 2/14 - On track to be available next week.
    • 3/28 - Now available. Action item for Jan-Simon to make XDS source packages available on the download server.
  • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
    • Monitoring integration
    • Improved development cycle (based on partial Widget installation)
    • First step to support package manager for SDKs (Yomo)
    • Bug fixes
    • 3/28 - Sebastien working on monitoring and supervision for Karlsruhe meeting.
  • API v3.0 - planned for FF
    • Dynamic API, binder/API discovery
    • 3/28 - Features will be discussed in Karlsruhe in detail. What is the plan to deprecate API v2.0 once 3.0 is available? Thought is that one year of overlap will be sufficient. To be discussed further in Karlsruhe.
  • Chromium from Igalia
    • 2/14 - Silvia will be at the AMM next week to discuss schedule and roadmap from Igalia. Need to discuss
      • Chromium for HTML5 apps and how to get that integrated into AGL.
      • Chromium browser and app support for all reference boards
    • 3/28 - Need to work out a plan with Igalia and LG for web apps based on their discussions at the AMM.
  • Dominig - will need to define a strategy to maintain iot security layer since ostro moved in a different direction. Ostro removed cynara. Need Jira issue to track.
    • 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
    • Jose to evaluate Tizen 4.0 security to see what they have done (SPEC-763)
    • Update 12/6 - On hold
    • 12/21 - On hold
    • 1/3 - Jose working on evaluation. Maybe done by end of January.
    • 1/31 - Jose is working on security layer updates as part of the uprev to rocko. Middle of next week per dev call yesterday. Also evaluation of Tizen 4.0 (SPEC-763) was completed. See Jira for results. Summary is that there is nothing much we can use from Tizen 4.0 since we have diverged a bit from their approach. Possibly can use Integrated Network Enforcement from Tizen 4.0.
    • 2/14 - Jose has the new security layer building for rocko. Testing in progress.
    • 3/28 - New security layer (meta-security) is merged as part of the update to rocko, but there is an issue with ptest.
  • Not running as root.
    • 3/28 - Work in progress. Kernel patches from Tizen BSPs are needed and Jose and is trying to get those upstream in a single place in the kernel.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
  • From Stephane:
    • How to handle services/apps packages (widgets) until we have an app store (at least for developers). Typical example: CAN low level service which is ready to be shipped into AGL as a reference implementation for CAN
    • Immediate solution (DD): build packages during platform build (bitbake recipe) then embed into image, install at first boot. This is what we have currently for agl-demo. Typically, CAN-signaling should enter in that category
    • After DD: setup AGL profiles and determine in which profile a given app/service should be preinstalled (still using platform builds+firstboot)
    • EE-rc1: setup a separate build for apps/services then tell developers how to grab those packages and install by hand (wget … ; afm-util install …) depending on their needs
    • Later (EE?): have an appfw store (kinda repository) and a client to download and install apps/services from a store
    • Update 9/27 - Working on app branches for master and dab. We should shortly have the download folder ready.
    • Update 10/11 - 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.
    • Update 11/1 - SPEC-1018 created to figure out the dab and master overwrite issue.
    • 11/8 - No update
    • 11/22 - No update. Need to add Eel folder as well.
    • 12/6 - Need to check with Jan-Simon
    • 12/21 Folders now work SPEC-1018). Waiting on a full build for all apps for Eel. Need to populate the dab folder with the dab apps on the dab branch. SPEC-1019.
      • Comment from Stephane to reorganize the folder structure to allow for easier download by branch or by boards, etc. Will add a suggested folder structure to SPEC-1018.
      • 1/3 - SPEC-1018 in progress. Would be nice to have the ability to download via a package manager from the target as well. Need to be able to verify the certificates and signatures of the apps being downloaded.
      • 1/31 - Settled on restructure of the folders for the repository (SPEC-1018).
      • 2/14 - SPEC-1018 in progress

New:

February 14, 2018

Attendees: Walt, Sebastien, Oshri, Stephane, Evgeniy

  • Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/docs/sec-blueprint)
    • 11/22
      • Eli sending comments on the system hardening section to the mail list or on github directly.
      • IoT.bzh reviewing the document and has a proposal for some restructuring. The Application Security section is need of an update.
      • Jan-Simon found some inconsistencies between the hardening guide and the current kernel configuration. See comments in https://github.com/automotive-grade-linux/docs-agl/pull/28
    • 12/6
      • Eli still working on his comments
      • Sebastien and Vincent completed a rework of the Security Blueprint based on the latest code. They published a pdf to the mail list. Will add to github in a new directory later today. Walt will reply to their email with a request to review the document and add comments to github before the next EG meeting (Dec 20).
    • 12/21
      • Only a few comments received on the document so we will postpone the review until the new year. Will send an email reminding people to review the document.
    • 1/3
      • No update
    • 1/17
      • No comments received. Most likely due to CES.
    • 1/31
    • 2/14 - No comments received.

Notes from Dresden Meeting.

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • 2/14 - Oshri started discussing how to add his code to the AGL baseline with Jan-Simon. Oshri plans to push the first patch by the end of the week.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • Update 11/1 - Walt to get this done this week.
    • Update 11/8 - No update
    • Update 11/22 - No update
    • 12/6 - No update
    • 1/3 - No update
    • 1/17 - No update
    • 1/31 - No update

Application Framework

  • SDK
    • XDS v1.1.0 in progress - targeted release date: AMM (2018 February 20th)
      • Board console/terminal integration within XDS dashboard
      • Documentation improvement of debug section
      • Bug fixes
    • 2/14 - On track to be available next week.
  • XDS v2.0.0 - targeted release date: ALS (2018 June 20th)
    • Monitoring integration
    • Improved development cycle (based on partial Widget installation)
    • First step to support package manager for SDKs (Yomo)
    • Bug fixes
  • Chromium from Igalia
    • 2/14 - Silvia will be at the AMM next week to discuss schedule and roadmap from Igalia. Need to discuss
      • Chromium for HTML5 apps and how to get that integrated into AGL.
      • Chromium browser and app support for all reference boards
  • Dominig - will need to define a strategy to maintain iot security layer since ostro moved in a different direction. Ostro removed cynara. Need Jira issue to track.
    • 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
    • Jose to evaluate Tizen 4.0 security to see what they have done (SPEC-763)
    • Update 12/6 - On hold
    • 12/21 - On hold
    • 1/3 - Jose working on evaluation. Maybe done by end of January.
    • 1/31 - Jose is working on security layer updates as part of the uprev to rocko. Middle of next week per dev call yesterday. Also evaluation of Tizen 4.0 (SPEC-763) was completed. See Jira for results. Summary is that there is nothing much we can use from Tizen 4.0 since we have diverged a bit from their approach. Possibly can use Integrated Network Enforcement from Tizen 4.0.
    • 2/14 - Jose has the new security layer building for rocko. Testing in progress.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
  • From Stephane:
    • How to handle services/apps packages (widgets) until we have an app store (at least for developers). Typical example: CAN low level service which is ready to be shipped into AGL as a reference implementation for CAN
    • Immediate solution (DD): build packages during platform build (bitbake recipe) then embed into image, install at first boot. This is what we have currently for agl-demo. Typically, CAN-signaling should enter in that category
    • After DD: setup AGL profiles and determine in which profile a given app/service should be preinstalled (still using platform builds+firstboot)
    • EE-rc1: setup a separate build for apps/services then tell developers how to grab those packages and install by hand (wget … ; afm-util install …) depending on their needs
    • Later (EE?): have an appfw store (kinda repository) and a client to download and install apps/services from a store
    • Update 9/27 - Working on app branches for master and dab. We should shortly have the download folder ready.
    • Update 10/11 - 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.
    • Update 11/1 - SPEC-1018 created to figure out the dab and master overwrite issue.
    • 11/8 - No update
    • 11/22 - No update. Need to add Eel folder as well.
    • 12/6 - Need to check with Jan-Simon
    • 12/21 Folders now work SPEC-1018). Waiting on a full build for all apps for Eel. Need to populate the dab folder with the dab apps on the dab branch. SPEC-1019.
      • Comment from Stephane to reorganize the folder structure to allow for easier download by branch or by boards, etc. Will add a suggested folder structure to SPEC-1018.
      • 1/3 - SPEC-1018 in progress. Would be nice to have the ability to download via a package manager from the target as well. Need to be able to verify the certificates and signatures of the apps being downloaded.
      • 1/31 - Settled on restructure of the folders for the repository (SPEC-1018).
      • 2/14 - SPEC-1018 in progress

New:

January 31, 2018

Attendees: Walt, Jan-Simon, Sebastien, Eli

  • Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/docs/sec-blueprint)
    • 11/22
      • Eli sending comments on the system hardening section to the mail list or on github directly.
      • IoT.bzh reviewing the document and has a proposal for some restructuring. The Application Security section is need of an update.
      • Jan-Simon found some inconsistencies between the hardening guide and the current kernel configuration. See comments in https://github.com/automotive-grade-linux/docs-agl/pull/28
    • 12/6
      • Eli still working on his comments
      • Sebastien and Vincent completed a rework of the Security Blueprint based on the latest code. They published a pdf to the mail list. Will add to github in a new directory later today. Walt will reply to their email with a request to review the document and add comments to github before the next EG meeting (Dec 20).
    • 12/21
      • Only a few comments received on the document so we will postpone the review until the new year. Will send an email reminding people to review the document.
    • 1/3
      • No update
    • 1/17
      • No comments received. Most likely due to CES.
    • 1/31

Notes from Dresden Meeting.

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • Update 11/1 - Discussed how Oshri can make the code available in gerrit for AGL. Will take about one month to have the code available. Source will be in github.
    • 11/8 - No update
    • 11/22 - No update
    • 12/6 - No update
    • 12/21 - No update
    • 1/3 - Nothing to report. SafeRide will be at CES next week.
    • 1/17 - Oshri was at CES and said that they will be upstreaming their code soon.
    • 1/31 - No update
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • Update 11/1 - Walt to get this done this week.
    • Update 11/8 - No update
    • Update 11/22 - No update
    • 12/6 - No update
    • 1/3 - No update
    • 1/17 - No update
    • 1/31 - No update

Application Framework

  • SDK
    • SDK for EE
      • Ready for RC2
      • XDS - will be released by the end of the year
        • SPEC-1132 - Move the code from IoT.bzh github to AGL gerrit
          • 12/6 - In progress
          • 1/3 - New repos created. Migration in progress. Discussed SPEC-1147 and release of XDS for Eel. Sebastien to reply to Walt's latest comment and create a new task for the final XDS release.
          • 1/31 - XDS source code is now in Gerrit. Sebastien working with Jan-Simon to build XDS in Jenkins. Sebastien will send an email with high level XDS features planned for 2018 to be added to the roadmap.
  • Chromium from Igalia
    • 9/27 - Stephane has tested for Gen 3. It is expected to work on any wayland target not just Renesas. Stephane trying out for QEMU and Intel. No support for IVI shell extensions.
    • 10/11 - New version pushed by Igalia. Stephane having issue building for Intel. Stephane can build Chromium with the SDK and create a wgt but it takes a long time. (see https://github.com/iotbzh/chromium-agl-app) and SPEC-942
    • 11/8 - No update
    • 11/22 - Reviewed email from Maksim about Igalia's plans for Chromium. Goals for Chromium
      • Build and run Chromium as an app available for Intel, Renesas, and other platforms
      • Build and run web engine in platform or as an app depending on the profile/device need for multiple platforms
      • Enable Qt-WebEngine for EE?
    • 12/6 - Waiting for some feedback from Igalia (Maksim) on how they want to proceed. They are envisioning everything as part of the platform built in Yocto, but that is not the current proposal that AGL would like to pursue.
    • 12/21 - No update. Waiting for latest updates on XDG launcher from Tanikawa-san
    • 1/3 - Chromium running on full surface of the screen. Some issues with XDG launcher.
    • 1/31 - XDG launcher works ok on the eel branch. Need to check if this got ported to master.
  • Window Manager interface for App Framework Discussion
    • 12/6 - Tanikawa working on XDG proxy for EE/ CES. Hopefully ready for next week's integration session. Stephane asked about user management to switch home screen look and feel based on the current user and whether that is included in the EE homescreen. Need to check next week in Yokohama.
    • 1/3 - SPEC-1086 needs to be addressed. Surface is not released in the window manager when the app dies.
    • 1/31 - SPEC-1086 closed. Merged for eel and master.
  • Dominig - will need to define a strategy to maintain iot security layer since ostro moved in a different direction. Ostro removed cynara. Need Jira issue to track.
    • 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
    • Jose to evaluate Tizen 4.0 security to see what they have done (SPEC-763)
    • Update 12/6 - On hold
    • 12/21 - On hold
    • 1/3 - Jose working on evaluation. Maybe done by end of January.
    • 1/31 - Jose is working on security layer updates as part of the uprev to rocko. Middle of next week per dev call yesterday. Also evaluation of Tizen 4.0 (SPEC-763) was completed. See Jira for results. Summary is that there is nothing much we can use from Tizen 4.0 since we have diverged a bit from their approach. Possibly can use Integrated Network Enforcement from Tizen 4.0.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
  • From Stephane:
    • How to handle services/apps packages (widgets) until we have an app store (at least for developers). Typical example: CAN low level service which is ready to be shipped into AGL as a reference implementation for CAN
    • Immediate solution (DD): build packages during platform build (bitbake recipe) then embed into image, install at first boot. This is what we have currently for agl-demo. Typically, CAN-signaling should enter in that category
    • After DD: setup AGL profiles and determine in which profile a given app/service should be preinstalled (still using platform builds+firstboot)
    • EE-rc1: setup a separate build for apps/services then tell developers how to grab those packages and install by hand (wget … ; afm-util install …) depending on their needs
    • Later (EE?): have an appfw store (kinda repository) and a client to download and install apps/services from a store
    • Update 9/27 - Working on app branches for master and dab. We should shortly have the download folder ready.
    • Update 10/11 - 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.
    • Update 11/1 - SPEC-1018 created to figure out the dab and master overwrite issue.
    • 11/8 - No update
    • 11/22 - No update. Need to add Eel folder as well.
    • 12/6 - Need to check with Jan-Simon
    • 12/21 Folders now work SPEC-1018). Waiting on a full build for all apps for Eel. Need to populate the dab folder with the dab apps on the dab branch. SPEC-1019.
      • Comment from Stephane to reorganize the folder structure to allow for easier download by branch or by boards, etc. Will add a suggested folder structure to SPEC-1018.
      • 1/3 - SPEC-1018 in progress. Would be nice to have the ability to download via a package manager from the target as well. Need to be able to verify the certificates and signatures of the apps being downloaded.
      • 1/31 - Settled on restructure of the folders for the repository (SPEC-1018).

New:

January 17, 2018

Attendees: Walt, Jan-Simon, Sebastien, Ronan, Dominig, Jose

  • Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/docs/sec-blueprint)
    • 11/22
      • Eli sending comments on the system hardening section to the mail list or on github directly.
      • IoT.bzh reviewing the document and has a proposal for some restructuring. The Application Security section is need of an update.
      • Jan-Simon found some inconsistencies between the hardening guide and the current kernel configuration. See comments in https://github.com/automotive-grade-linux/docs-agl/pull/28
    • 12/6
      • Eli still working on his comments
      • Sebastien and Vincent completed a rework of the Security Blueprint based on the latest code. They published a pdf to the mail list. Will add to github in a new directory later today. Walt will reply to their email with a request to review the document and add comments to github before the next EG meeting (Dec 20).
    • 12/21
      • Only a few comments received on the document so we will postpone the review until the new year. Will send an email reminding people to review the document.
    • 1/3
      • No update
    • 1/17
      • No comments received. Most likely due to CES.

Notes from Dresden Meeting.

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • Update 11/1 - Discussed how Oshri can make the code available in gerrit for AGL. Will take about one month to have the code available. Source will be in github.
    • 11/8 - No update
    • 11/22 - No update
    • 12/6 - No update
    • 12/21 - No update
    • 1/3 - Nothing to report. SafeRide will be at CES next week.
    • 1/17 - Oshri was at CES and said that they will be upstreaming their code soon.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • Update 11/1 - Walt to get this done this week.
    • Update 11/8 - No update
    • Update 11/22 - No update
    • 12/6 - No update
    • 1/3 - No update
    • 1/17 - No update

Application Framework

  • SDK
    • SDK for EE
      • Ready for RC2
      • XDS - will be released by the end of the year
        • SPEC-1132 - Move the code from IoT.bzh github to AGL gerrit
          • 12/6 - In progress
          • 1/3 - New repos created. Migration in progress. Discussed SPEC-1147 and release of XDS for Eel. Sebastien to reply to Walt's latest comment and create a new task for the final XDS release.
  • Chromium from Igalia
    • 9/27 - Stephane has tested for Gen 3. It is expected to work on any wayland target not just Renesas. Stephane trying out for QEMU and Intel. No support for IVI shell extensions.
    • 10/11 - New version pushed by Igalia. Stephane having issue building for Intel. Stephane can build Chromium with the SDK and create a wgt but it takes a long time. (see https://github.com/iotbzh/chromium-agl-app) and SPEC-942
    • 11/8 - No update
    • 11/22 - Reviewed email from Maksim about Igalia's plans for Chromium. Goals for Chromium
      • Build and run Chromium as an app available for Intel, Renesas, and other platforms
      • Build and run web engine in platform or as an app depending on the profile/device need for multiple platforms
      • Enable Qt-WebEngine for EE?
    • 12/6 - Waiting for some feedback from Igalia (Maksim) on how they want to proceed. They are envisioning everything as part of the platform built in Yocto, but that is not the current proposal that AGL would like to pursue.
    • 12/21 - No update. Waiting for latest updates on XDG launcher from Tanikawa-san
    • 1/3 - Chromium running on full surface of the screen. Some issues with XDG launcher.
  • Window Manager interface for App Framework Discussion
    • 12/6 - Tanikawa working on XDG proxy for EE/ CES. Hopefully ready for next week's integration session. Stephane asked about user management to switch home screen look and feel based on the current user and whether that is included in the EE homescreen. Need to check next week in Yokohama.
    • 1/3 - SPEC-1086 needs to be addressed. Surface is not released in the window manager when the app dies.
  • Dominig - will need to define a strategy to maintain iot security layer since ostro moved in a different direction. Ostro removed cynara. Need Jira issue to track.
    • 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
    • Jose to evaluate Tizen 4.0 security to see what they have done (SPEC-763)
    • Update 12/6 - On hold
    • 12/21 - On hold
    • 1/3 - Jose working on evaluation. Maybe done by end of January.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
  • From Stephane:
    • How to handle services/apps packages (widgets) until we have an app store (at least for developers). Typical example: CAN low level service which is ready to be shipped into AGL as a reference implementation for CAN
    • Immediate solution (DD): build packages during platform build (bitbake recipe) then embed into image, install at first boot. This is what we have currently for agl-demo. Typically, CAN-signaling should enter in that category
    • After DD: setup AGL profiles and determine in which profile a given app/service should be preinstalled (still using platform builds+firstboot)
    • EE-rc1: setup a separate build for apps/services then tell developers how to grab those packages and install by hand (wget … ; afm-util install …) depending on their needs
    • Later (EE?): have an appfw store (kinda repository) and a client to download and install apps/services from a store
    • Update 9/27 - Working on app branches for master and dab. We should shortly have the download folder ready.
    • Update 10/11 - 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.
    • Update 11/1 - SPEC-1018 created to figure out the dab and master overwrite issue.
    • 11/8 - No update
    • 11/22 - No update. Need to add Eel folder as well.
    • 12/6 - Need to check with Jan-Simon
    • 12/21 Folders now work SPEC-1018). Waiting on a full build for all apps for Eel. Need to populate the dab folder with the dab apps on the dab branch. SPEC-1019.
      • Comment from Stephane to reorganize the folder structure to allow for easier download by branch or by boards, etc. Will add a suggested folder structure to SPEC-1018.
      • 1/3 - SPEC-1018 in progress. Would be nice to have the ability to download via a package manager from the target as well. Need to be able to verify the certificates and signatures of the apps being downloaded.
  • API instances (was namespaces). API names are hardcoded in the JSON description at the moment and there is no way to have multiple instances of the same binding. This is a limitation being run into in the audio area and vehicle signaling where there can be multiple physical devices that need to be supported via the same API.
  • Enable APIs in languages other than C/Cplus plus. Use case is from Daimler to use Rust. Probably FF or later in the roadmap.
    • 10/11 - Need Jira issue to track this.
    • 11/1 - SPEC-1020 created to track this issue.
    • 11/8 - No update
    • 11/22 - SPEC-1020 - 4A is using a version of dynamic APIs already (dynapi). Will be available globally, Jose needs to update the documentation.
    • 12/6 - No update
    • 12/21 - No update. Should be API “instances” instead of a traditional namespace problem since we resolved using a dynamic API model.
    • 1/2 - No update.
  • Systemd v235 - introduced dynamic users (see http://0pointer.net/blog/dynamic-users-with-systemd.html)
    • Propose testing the dynamic users using Arch Linux to see if the expected benefits are seen and whether we should backport to AGL before we see it in poky which may take another version or two.
    • Created SPEC-940
    • Plan to get a readout before the Feb AMM to determine if we should do this for FF or wait for Yocto to do the uprev.
    • 11/22 - Jose did a little investigation and this creates a dynamic user that is intended to be disposable which is not our requirement. He submitted a patch to systemd which was accepted for a future version of systemd. Will need to do some backporting for FF when we change to multi-user.
    • 12/6 - On hold
    • 12/21 - On hold for FF. Jose's patch was merged upstream in systemd.
    • 1/3 - Issue (SPEC-940) Closed.

New:

  • Roadmap for 2018
    • Need to come to next meeting with FF and GG plans
    • 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.
  • App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5
  • App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly?
  • App Framework binder communications shall be able to manage return from sleep mode.
  • Connection glitches in multi-ECU system shall be properly handled.

January 3, 2018

Attendees: Walt, Stephane, Sebastien, Vincent, Dominig, Jose

  • Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/docs/sec-blueprint)
    • 11/22
      • Eli sending comments on the system hardening section to the mail list or on github directly.
      • IoT.bzh reviewing the document and has a proposal for some restructuring. The Application Security section is need of an update.
      • Jan-Simon found some inconsistencies between the hardening guide and the current kernel configuration. See comments in https://github.com/automotive-grade-linux/docs-agl/pull/28
    • 12/6
      • Eli still working on his comments
      • Sebastien and Vincent completed a rework of the Security Blueprint based on the latest code. They published a pdf to the mail list. Will add to github in a new directory later today. Walt will reply to their email with a request to review the document and add comments to github before the next EG meeting (Dec 20).
    • 12/21
      • Only a few comments received on the document so we will postpone the review until the new year. Will send an email reminding people to review the document.
    • 1/3
      • No update

Notes from Dresden Meeting.

  • Oshri Yahav of Saferide.io made a proposal about security. saferide_open_source_project.pdf
    • Update 11/1 - Discussed how Oshri can make the code available in gerrit for AGL. Will take about one month to have the code available. Source will be in github.
    • 11/8 - No update
    • 11/22 - No update
    • 12/6 - No update
    • 12/21 - No update
    • 1/3 - Nothing to report. SafeRide will be at CES next week.
  • Discussed the process for security issues in AGL code
    • Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism.
    • Create a new Jira project for security issues visible to members of the EG.
    • Create a process for accepting applications to and vetting access to the mail list and Jira.
    • Review at next EG meeting
    • Update 11/1 - Walt to get this done this week.
    • Update 11/8 - No update
    • Update 11/22 - No update
    • 12/6 - No update
    • 1/3 - No update

Application Framework

  • SDK
    • SDK for EE
      • Ready for RC2
      • XDS - will be released by the end of the year
        • SPEC-1132 - Move the code from IoT.bzh github to AGL gerrit
          • 12/6 - In progress
          • 1/3 - New repos created. Migration in progress. Discussed SPEC-1147 and release of XDS for Eel. Sebastien to reply to Walt's latest comment and create a new task for the final XDS release.
  • Chromium from Igalia
    • 9/27 - Stephane has tested for Gen 3. It is expected to work on any wayland target not just Renesas. Stephane trying out for QEMU and Intel. No support for IVI shell extensions.
    • 10/11 - New version pushed by Igalia. Stephane having issue building for Intel. Stephane can build Chromium with the SDK and create a wgt but it takes a long time. (see https://github.com/iotbzh/chromium-agl-app) and SPEC-942
    • 11/8 - No update
    • 11/22 - Reviewed email from Maksim about Igalia's plans for Chromium. Goals for Chromium
      • Build and run Chromium as an app available for Intel, Renesas, and other platforms
      • Build and run web engine in platform or as an app depending on the profile/device need for multiple platforms
      • Enable Qt-WebEngine for EE?
    • 12/6 - Waiting for some feedback from Igalia (Maksim) on how they want to proceed. They are envisioning everything as part of the platform built in Yocto, but that is not the current proposal that AGL would like to pursue.
    • 12/21 - No update. Waiting for latest updates on XDG launcher from Tanikawa-san
    • 1/3 - Chromium running on full surface of the screen. Some issues with XDG launcher.
  • Window Manager interface for App Framework Discussion
    • 12/6 - Tanikawa working on XDG proxy for EE/ CES. Hopefully ready for next week's integration session. Stephane asked about user management to switch home screen look and feel based on the current user and whether that is included in the EE homescreen. Need to check next week in Yokohama.
    • 1/3 - SPEC-1086 needs to be addressed. Surface is not released in the window manager when the app dies.
  • Dominig - will need to define a strategy to maintain iot security layer since ostro moved in a different direction. Ostro removed cynara. Need Jira issue to track.
    • 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
    • Jose to evaluate Tizen 4.0 security to see what they have done (SPEC-763)
    • Update 12/6 - On hold
    • 12/21 - On hold
    • 1/3 - Jose working on evaluation. Maybe done by end of January.
  • Matsuzawa asked about having a developer repository (store) for AGL apps so that developers can exchange apps.
  • From Stephane:
    • How to handle services/apps packages (widgets) until we have an app store (at least for developers). Typical example: CAN low level service which is ready to be shipped into AGL as a reference implementation for CAN
    • Immediate solution (DD): build packages during platform build (bitbake recipe) then embed into image, install at first boot. This is what we have currently for agl-demo. Typically, CAN-signaling should enter in that category
    • After DD: setup AGL profiles and determine in which profile a given app/service should be preinstalled (still using platform builds+firstboot)
    • EE-rc1: setup a separate build for apps/services then tell developers how to grab those packages and install by hand (wget … ; afm-util install …) depending on their needs
    • Later (EE?): have an appfw store (kinda repository) and a client to download and install apps/services from a store
    • Update 9/27 - Working on app branches for master and dab. We should shortly have the download folder ready.
    • Update 10/11 - 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.
    • Update 11/1 - SPEC-1018 created to figure out the dab and master overwrite issue.
    • 11/8 - No update
    • 11/22 - No update. Need to add Eel folder as well.
    • 12/6 - Need to check with Jan-Simon
    • 12/21 Folders now work SPEC-1018). Waiting on a full build for all apps for Eel. Need to populate the dab folder with the dab apps on the dab branch. SPEC-1019.
      • Comment from Stephane to reorganize the folder structure to allow for easier download by branch or by boards, etc. Will add a suggested folder structure to SPEC-1018.
      • 1/3 - SPEC-1018 in progress. Would be nice to have the ability to download via a package manager from the target as well. Need to be able to verify the certificates and signatures of the apps being downloaded.
  • API instances (was namespaces). API names are hardcoded in the JSON description at the moment and there is no way to have multiple instances of the same binding. This is a limitation being run into in the audio area and vehicle signaling where there can be multiple physical devices that need to be supported via the same API.
  • Enable APIs in languages other than C/Cplus plus. Use case is from Daimler to use Rust. Probably FF or later in the roadmap.
    • 10/11 - Need Jira issue to track this.
    • 11/1 - SPEC-1020 created to track this issue.
    • 11/8 - No update
    • 11/22 - SPEC-1020 - 4A is using a version of dynamic APIs already (dynapi). Will be available globally, Jose needs to update the documentation.
    • 12/6 - No update
    • 12/21 - No update. Should be API “instances” instead of a traditional namespace problem since we resolved using a dynamic API model.
    • 1/2 - No update.
  • Systemd v235 - introduced dynamic users (see http://0pointer.net/blog/dynamic-users-with-systemd.html)
    • Propose testing the dynamic users using Arch Linux to see if the expected benefits are seen and whether we should backport to AGL before we see it in poky which may take another version or two.
    • Created SPEC-940
    • Plan to get a readout before the Feb AMM to determine if we should do this for FF or wait for Yocto to do the uprev.
    • 11/22 - Jose did a little investigation and this creates a dynamic user that is intended to be disposable which is not our requirement. He submitted a patch to systemd which was accepted for a future version of systemd. Will need to do some backporting for FF when we change to multi-user.
    • 12/6 - On hold
    • 12/21 - On hold for FF. Jose's patch was merged upstream in systemd.
    • 1/3 - Issue (SPEC-940) Closed.

New:

  • Roadmap for 2018
    • Need to come to next meeting with FF and GG plans
    • 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.

Pre-2018 Meeting Minutes

Minutes from meetings held prior to 2018 have been archived here.

eg-app-fw/meetings.txt · Last modified: 2024/11/27 14:24 by wminer

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki