Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Development in 2024 is likely to be incremental.  Proposed tasks:

(Updated May 1September 4, 2024 with status

  1. 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) -  Repo name agl-grpc-protos. Debating whether this is needed yet since we only have two protobuf files at this time. If Decided against doing this for now.  If we expand the number of protobuf files later we will re-assess.  
  2. 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 - Not started
  3. 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. - Not started
  4. Investigate enabling SELinux enforcing mode in the demo builds. - Not started

...

  1. Keep following upstream KUKSA.val development and upgrading AGL to the latest releases. - Quillback updated to KUKSA 0.4.2
  2. Update recipes for the split of upstream KUKSA git repos for Ricefish and bump to latest KUKSA (0.4.5 or later) - Done
  3. VSS Proxy for V2C and gateway demo. - Done         
  4. VSS 5.0 is planned to be released in the fall of 2024. Will look to include it in Salmon.
  5. Push AGL signals (primarily audio) upstream to VSS