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

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

App FW EG Topics

• 10/2
  • Updated the 2024 Roadmap Confluence page

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.

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

• 10/2
  • Updated the 2024 Roadmap Confluence page

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:

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

• 10/2
  • Updated the 2024 Roadmap Confluence page

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:

Attendees: Walt, Jan-Simon, Scott

App FW EG Topics

• 10/2
  • Updated the 2024 Roadmap Confluence page

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:

Attendees: Walt, Jan-Simon, Scott

App FW EG Topics

• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page
• 5/1
  • Created the 2024 Roadmap Confluence page
• 9/4
  • Updated the 2024 Roadmap Confluence page

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:

Attendees: Walt, Scott, Marius

App FW EG Topics

• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page
• 5/1
  • Created the 2024 Roadmap Confluence page

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:

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page
• 5/1
  • Created the 2024 Roadmap Confluence page

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:

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page
• 5/1
  • Created the 2024 Roadmap Confluence page

Connectivity EG Topics

• CAN/ Vehicle Signaling

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

New:

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

App FW EG Topics

• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page
• 5/1
  • Created the 2024 Roadmap Confluence page

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:

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

App FW EG Topics

• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page
• 5/1
  • Created the 2024 Roadmap Confluence page

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:

Attendees: Walt, Scott, Marius

App FW EG Topics

• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page
• 5/1
  • Created the 2024 Roadmap Confluence page

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:

Attendees: Walt, Scott, Marius

App FW EG Topics

• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page
• 5/1
  • Created the 2024 Roadmap Confluence page

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:

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

App FW EG Topics

• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page

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:

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

• 9/20
  • Revisited and updated the 2023 Roadmap Confluence page
• 10/4
  • Scott started working on documentation
• 10/18
  • Scott uploaded a first batch of documentation changes:
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29283
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29284
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29285
  • Discussing options for mkdocs templating
    • https://squidfunk.github.io/mkdocs-material/ vs mkdocs + upstream rtd theme
• 11/29
  • All documentation done for now. Will look at doing some more updates before the Quillback release.
• 2/7
  • Revisited and updated the 2023 Roadmap Confluence page

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:

Attendees: Walt, Jan-Simon, Scott,

App FW EG Topics

• 9/20
  • Revisited and updated the 2023 Roadmap Confluence page
• 10/4
  • Scott started working on documentation
• 10/18
  • Scott uploaded a first batch of documentation changes:
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29283
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29284
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29285
  • Discussing options for mkdocs templating
    • https://squidfunk.github.io/mkdocs-material/ vs mkdocs + upstream rtd theme
• 11/29
  • All documentation done for now. Will look at doing some more updates before the Quillback release.

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:

Attendees: Walt, Jan-Simon, Scott, Marius

App FW EG Topics

• 9/20
  • Revisited and updated the 2023 Roadmap Confluence page
• 10/4
  • Scott started working on documentation
• 10/18
  • Scott uploaded a first batch of documentation changes:
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29283
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29284
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29285
  • Discussing options for mkdocs templating
    • https://squidfunk.github.io/mkdocs-material/ vs mkdocs + upstream rtd theme
• 11/29
  • All documentation done for now. Will look at doing some more updates before the Quillback release.

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:

Attendees: Jan-Simon, Scott, Denys, Marius

App FW EG Topics

• 9/20
  • Revisited and updated the 2023 Roadmap Confluence page
• 10/4
  • Scott started working on documenation
• 10/18
  • Scott uploaded a first batch of documentation changes:
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29283
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29284
    • https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29285
  • Discussing options for mkdocs templating
    • https://squidfunk.github.io/mkdocs-material/ vs mkdocs + upstream rtd theme

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:

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

App FW EG Topics

• 9/20
  • Revisited and updated the 2023 Roadmap Confluence page
• 10/4
  • Scott started working on documenation

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:

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

App FW EG Topics

• 9/20
  • Revisited and updated the 2023 Roadmap Confluence page

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:

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?

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?

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?

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

• 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
• 4/5
  • documentation WIP
  • Create link from https://docs.automotivelinux.org/en/master/#06_Component_Documentation/06_application_framework/ back to https://docs.automotivelinux.org/en/master/#04_Developer_Guides/01_Application_Framework/01_Introduction/
  • Debugging https://jira.automotivelinux.org/browse/SPEC-4199
• 4/19
  • Need update from Denys on documentation status.
    • Sandboxing documentation (Jira ticket)
    • Remove Dbus documentation once the WAM updates are done (Jira ticket)
• 5/3
  • Need update from Denys on documentation status.
    • Sandboxing documentation (Jira ticket)
    • Remove Dbus documentation once the WAM updates are done (Jira ticket)
• 5/17
  • Need update from Denys on documentation status.
    • Sandboxing documentation (Jira ticket)
    • Remove Dbus documentation once the WAM updates are done (Jira ticket)
• 5/31
  • Documentation for Pike is WIP

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

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

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
• 4/5
  • documentation WIP
  • Create link from https://docs.automotivelinux.org/en/master/#06_Component_Documentation/06_application_framework/ back to https://docs.automotivelinux.org/en/master/#04_Developer_Guides/01_Application_Framework/01_Introduction/
  • Debugging https://jira.automotivelinux.org/browse/SPEC-4199
• 4/19
  • Need update from Denys on documentation status.
    • Sandboxing documentation (Jira ticket)
    • Remove Dbus documentation once the WAM updates are done (Jira ticket)
• 5/3
  • Need update from Denys on documentation status.
    • Sandboxing documentation (Jira ticket)
    • Remove Dbus documentation once the WAM updates are done (Jira ticket)
• 5/17
  • Need update from Denys on documentation status.
    • Sandboxing documentation (Jira ticket)
    • Remove Dbus documentation once the WAM updates are done (Jira ticket)

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

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

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
• 4/5
  • documentation WIP
  • Create link from https://docs.automotivelinux.org/en/master/#06_Component_Documentation/06_application_framework/ back to https://docs.automotivelinux.org/en/master/#04_Developer_Guides/01_Application_Framework/01_Introduction/
  • Debugging https://jira.automotivelinux.org/browse/SPEC-4199
• 4/19
  • Need update from Denys on documentation status.
    • Sandboxing documentation (Jira ticket)
    • Remove Dbus documentation once the WAM updates are done (Jira ticket)
• 5/3
  • Need update from Denys on documentation status.
    • Sandboxing documentation (Jira ticket)
    • Remove Dbus documentation once the WAM updates are done (Jira ticket)

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

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

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
• 4/5
  • documentation WIP
  • Create link from https://docs.automotivelinux.org/en/master/#06_Component_Documentation/06_application_framework/ back to https://docs.automotivelinux.org/en/master/#04_Developer_Guides/01_Application_Framework/01_Introduction/
  • Debugging https://jira.automotivelinux.org/browse/SPEC-4199
• 4/19
  • Need update from Denys on documentation status.
    • Sandboxing documentation (Jira ticket)
    • Remove Dbus documentation once the WAM updates are done (Jira ticket)

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

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

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
• 4/5
  • documentation WIP
  • Create link from https://docs.automotivelinux.org/en/master/#06_Component_Documentation/06_application_framework/ back to https://docs.automotivelinux.org/en/master/#04_Developer_Guides/01_Application_Framework/01_Introduction/
  • Debugging https://jira.automotivelinux.org/browse/SPEC-4199

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

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.

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.

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.

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.

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

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:

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:

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:

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:

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:

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:

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:

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:

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

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

Application Framework Redesign

• 12/15
  • Applaunchd rewrite with glib feature-par with qt version. Debugging discovery. Will push initial version and discovery on-top.
  • Slides from ALS https://static.sched.com/hosted_files/ossalsjp21/e2/ALS2021-Arnaud.pdf
• 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 - - 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:

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

Application Framework Redesign

• 12/15
  • Applaunchd rewrite with glib feature-par with qt version. Debugging discovery. Will push initial version and discovery on-top.
  • Slides from ALS https://static.sched.com/hosted_files/ossalsjp21/e2/ALS2021-Arnaud.pdf
• 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 - - 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:

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

Special Meeting to to discuss App FW redesign.

Application Framework Redesign

• 12/15
  • Applaunchd rewrite with glib feature-par with qt version. Debugging discovery. Will push initial version and discovery on-top.
  • Slides from ALS https://static.sched.com/hosted_files/ossalsjp21/e2/ALS2021-Arnaud.pdf
• 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 - - 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:

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

Application Framework Redesign

• 12/15
  • Applaunchd rewrite with glib feature-par with qt version. Debugging discovery. Will push initial version and discovery on-top.
  • Slides from ALS https://static.sched.com/hosted_files/ossalsjp21/e2/ALS2021-Arnaud.pdf
• 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 - - 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:

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

Application Framework Redesign

• 12/15
  • Applaunchd rewrite with glib feature-par with qt version. Debugging discovery. Will push initial version and discovery on-top.
  • Slides from ALS https://static.sched.com/hosted_files/ossalsjp21/e2/ALS2021-Arnaud.pdf
• 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 - - 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:

Meeting Canceled

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

Application Framework Redesign

• 12/15
  • Applaunchd rewrite with glib feature-par with qt version. Debugging discovery. Will push initial version and discovery on-top.
  • Slides from ALS https://static.sched.com/hosted_files/ossalsjp21/e2/ALS2021-Arnaud.pdf
• 1/12
  • applaunchd patches should be submitted today.

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

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
    • Applaunchd rewrite with glib feature-par with qt version. Debugging discovery. Will push initial version and discovery on-top.
    • Slides from ALS https://static.sched.com/hosted_files/ossalsjp21/e2/ALS2021-Arnaud.pdf

• 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

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:

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:

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

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:

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:

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:

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:

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:

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:

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/4 - Reviewed the roadmap spreadsheet and added the tab “Copy of App FW and Security” to further refine and group the tasks.
  • Presentation on Web Apps and CEF by Lorenzo
  • Presentation from Daniel on App FW rework
• 5/19 - Lorenzo presented at the Webengines Hackfest Embedded Session link

• 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
  • Javier - updated the generic Yocto flatpak recipe and verified that it works. Will need to try building with AGL next.
• 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.

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/4 - Reviewed the roadmap spreadsheet and added the tab “Copy of App FW and Security” to further refine and group the tasks.
  • Presentation on Web Apps and CEF by Lorenzo
  • Presentation from Daniel on App FW rework
• 5/19 - Lorenzo presented at the Webengines Hackfest Embedded Session link

• 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
  • Javier - updated the generic Yocto flatpack recipe and verified that it works. Will need to try building with AGL next.

• New topics:

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

• 4/4 - Reviewed the roadmap spreadsheet and added the tab “Copy of App FW and Security” to further refine and group the tasks.
  • Presentation on Web Apps and CEF by Lorenzo
  • Presentation from Daniel on App FW rework
• 5/19 - Lorenzo presented at the Webengines Hackfest Embedded Session link

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

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

• 4/4 - Reviewed the roadmap spreadsheet and added the tab “Copy of App FW and Security” to further refine and group the tasks.
• Presentation on Web Apps and CEF by Lorenzo
• Presentation from Daniel on App FW rework

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

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

• Reviewed the roadmap spreadsheet and added the tab “Copy of App FW and Security” to further refine and group the tasks.
• Presentation on Web Apps and CEF by Lorenzo
• Presentation from Daniel on App FW rework

• New topics:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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
  • Links to Waltham documentation and RFC of Waltham backend

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

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
  • Links to Waltham documentation and RFC of Waltham backend

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

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:

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.

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.

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.

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.