...
- Create a repository to hold the shared AGL gRPC API definitions so that server and client implementations can source them from a common location. Some investigation will be required with respect to the most straightforward way of integrating this with the server and client implementations already in hand (e.g. integration with Meson).
- Finish converting the HTML5 demo homescreen and launcher to using the applaunchd gRPC API and removing the D-Bus API from the applaunchd codebase.
- Finish investigation into a minimal set of advanced systemd sandbox features to turn on by default in the application templates.
- Define a gRPC version of the legacy application framework's agl-server-audiomixer API, extend the new agl-server-audiomixer daemon to implement it, and update the Qt demo mixer application to use it.
- Keep following upstream KUKSA.val development and upgrading AGL to the latest releases .- Connectivity EG
- Convert all existing KUKSA.val VIS WebSocket usage to the gRPC API .- Connectivity EG
- Investigate potentially switching from the original KUKSA.val server to the Rust-based reimplementation (known as the KUKSA.val "databroker"). There are signs that the upstream community is starting to switch focus to the databroker, and the use of Rust is a potentially interesting technology demo to provide to AGL members .- Connectivity EG
- Investigate the effort required to define and implement gRPC APIs for the previous agl-service-bluetooth and agl-service-network bindings, with an eye to following through with implementing them if the effort seems reasonable. The end goal of this would be to enable development of a Flutter demo settings application and potentially enhancing the HTML5 demo settings application.
- Investigate solutions for managing authorization tokens and potentially SSL certificates for VIS and/or gRPC. One option that needs to be considered is integrating use of systemd-auth to pass things to daemons and applications.
- Investigate enabling SELinux enforcing mode in the demo builds.