User Tools

Site Tools


agl-roadmap

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
agl-roadmap [2018/07/12 13:59]
waltminer [From Connectivity EG]
agl-roadmap [2019/02/14 14:58] (current)
waltminer
Line 3: Line 3:
 The official AGL Roadmap is maintained in Jira. [[https://​jira.automotivelinux.org/​issues/?​filter=10401 |This link]] will show the latest project list in Jira. More information on how AGL uses Jira for project management can be found [[start:​using-jira|here]]. ​ The official AGL Roadmap is maintained in Jira. [[https://​jira.automotivelinux.org/​issues/?​filter=10401 |This link]] will show the latest project list in Jira. More information on how AGL uses Jira for project management can be found [[start:​using-jira|here]]. ​
  
-===== 2018 Roadmap/ Workplan from SAT =====+===== 2019 Roadmap/ Workplan from SAT =====
  
-    * **Funky Flounder ​on YP rocko**, Grumpy Guppy <​del>​on YP sumo</​del>​ +    * **Happy Halibut and Itchy Icefish ​on Yocto 2.6 (thud)** 
-    * Do we move some APIs from meta-agl-demo into meta-agl or meta-agl-extra? +    * Components to move from agl-devel to agl-extras 
-     ​**Revisit the development process and gerrit usage to make improvements based on lessons learned and expanded developer base.**  +      4a
-     * **Review the scope of PulseAudio to minimize its usage to what is absolutely necessary.** (SPEC-1220)+
      * Review Reference Hardware System Architecture document and consider its implications for the software architecture. ​      * Review Reference Hardware System Architecture document and consider its implications for the software architecture. ​
      * Move RHSA to doc site.       * Move RHSA to doc site. 
-     ​* ​Document ​the documentation ​workflow ​and documentation ​versioning +     ​* ​Finish ​the documentation ​site improvements ​and increase the amount of documentation ​by 100% 
-     ​* ​Propose a replacement for ask.automotivelinux.orgProbably stack overflow +     ​* ​Move to groups.io  
-       ​ask has been deprecated. Need someone ​to create a label in stack overflow for us.  +     ​**Add video support ​to mediaplayer binding.** 
-     ​* ​Add additional simplified SOTA mechanism ​(A/B via rauc+     ​* ​Video player and in-vehicle video architecture that allow third-party plug-ins, rear view camera, Autonomous vehicles, encrypted data such as widevine ​(from Googlefor Netflix, Hulu, Android, etc. 
-     * **Add video support to mediaplayer binding +     ​* ​Finish AGL spec 2.0 
-**+     Web App Manager maturity  
 +     Speech API maturity 
 +     ​Home Screen and Window Manager re-architecture  
 +     Instrument Cluster reference device improvements and maturity 
 +     * Create Telematics reference device 
 +     * New reference board for 2019? CES 2020 board should be M3 again or move to H3?  Need information from RHSA. 
 +     * Smartphone connectivity - no OS solution that allows integration of proprietary solutions such as CarPlay or Android Auto.  We do not have all of the components (video and audio especially) that are required for these integrations. What do we need to add? 
 + 
 + 
 ==== From App FW and Security EG ==== ==== From App FW and Security EG ====
  
Line 28: Line 36:
      * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Distinction between platform services (e.g., nfc, telephone) and user services that run inside a user context (e.g., media player and lightmedia scanner) ​      * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Distinction between platform services (e.g., nfc, telephone) and user services that run inside a user context (e.g., media player and lightmedia scanner) ​
      * Changes necessary at binder level for V2C (SSL transport)      * Changes necessary at binder level for V2C (SSL transport)
-     * Application signing and installation mechanism+     ​* ​{{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} ​Application signing and installation mechanism 
 +       * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} Mechanism for checking signature is in place.  
 +       * Require all apps to be signed in GG 
 +       * Developer workflow is needed for managing keys 
 +       * Development mode and Production mode for app management ​
      * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system.      * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system.
      * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} Binder APIv3 (enable dynamic APIs)      * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} Binder APIv3 (enable dynamic APIs)
Line 53: Line 65:
          * Improved development cycle (based on partial Widget installation)          * Improved development cycle (based on partial Widget installation)
          * First step to support package manager for SDKs (Yomo)          * First step to support package manager for SDKs (Yomo)
 +
 +     * **GG Priorities for App FW**
 +       * Complete application lifecycle definition to prepare for all apps moving to new app lifecycle in HH
 +         * Background app awareness on the home screen - (e.g. Current song on media player, phone call in progress, # messages unread)
 +         * Kill apps individually from life cycle manager
 +         * Need to define state diagram for app life cycle
 +
 +       * **HTML5 app support as necessary**
 +       * Multi-user use case
 +       * API for abstraction of hardware mechanism for signing apps, packages, etc. 
 +       * Headless/ Telematics use case
 +       * Unit testing for app framework
 +       * Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms. ​
 +         * Split off the keys from the App FW. Currently are [[https://​git.automotivelinux.org/​src/​app-framework-main/​tree/​certs | here]]
 +         * Allow keys to be changed by the device developers - git repo and recipe for keys
 +         * Library (or binding) to plug in key management to the app FW. 
 +         * Reference implementation will use the file system as the key store. Can be swapped for a trusted environment by a device creator at a later time. 
 +         * Sign at build time in AGL CI system with a check at run time 
  
 ==== From Graphics EG ==== ==== From Graphics EG ====
      * Graphic      * Graphic
        * **Finish Window Manager and Homescreen work**        * **Finish Window Manager and Homescreen work**
-         * Home Screen API  +         * Home Screen API / service 
-         ​* ​Home Screen keyboard ​for english and Japanese+           * UI for Qt 
 +           * UI for HTML5 
 +         ​* ​High level API for virtual keyboard in english and Japanese
          * Pop-up support          * Pop-up support
 +           * Virtual keyboard placement and removal
 +           * Alerts
          * Focus management for out of focus apps          * Focus management for out of focus apps
-         ​* ​Background app awareness on the homescreen ​(e.gCurrent song on media player, # messages unread) +         ​* ​Multi-resolution display support 
-         * Add new apps to home screen (not hardcoded)+           * Fix scaling issues across different display sizes  
 +           * Landscape vsportrait  
 + 
 +  
 +         * Add new apps to home screen (not hardcoded) ​- SPEC-1734
          * Management of apps that overflow the screen - slider or multiple pages or folders          * Management of apps that overflow the screen - slider or multiple pages or folders
-         * Improved secondary display ​suport ​+         * Improved secondary display ​support ​
          * Transition Animation          * Transition Animation
-         * Hardware plane management; Rear veiw camera, smart phone connection,,,​+           * Need to define use cases and requirements 
 +           * Handled by Qt Compositor if we continue to use it for demos.  
 +           * Will need to rethink if we switch compositors 
 +         * Hardware plane management; Rear view camera, smart phone connection,,,​
          * User interactive response; vibration of screen, beep,,,          * User interactive response; vibration of screen, beep,,,
        * Upstream to Wayland/​Weston        * Upstream to Wayland/​Weston
Line 81: Line 122:
  
    * Questions for EG from SAT:    * Questions for EG from SAT:
-     * Do we remove support for IVI protocol is favor of XDG?   +     * Do we remove support for IVI protocol is favor of XDG? 
-     ​How do we get LG involved in this group?+       ​Answer: No. Cannot deprecate IVI protocol unless extensions to XDG are made.   
      * What is the roadmap for Wayland/​Weston versions for 2018?      * What is the roadmap for Wayland/​Weston versions for 2018?
        * SAT recommends following Yocto. ​        * SAT recommends following Yocto. ​
Line 97: Line 139:
        * **V2C interface**        * **V2C interface**
        * **Improved performance using Denso Ten baseline as presented at ALS 2018**        * **Improved performance using Denso Ten baseline as presented at ALS 2018**
 +       * Content encryption within vehicle for streaming services or Blue Ray content. ​
 +       * Telematics reference device profile with built in modem
  
      * Bluetooth improvements      * Bluetooth improvements
agl-roadmap.1531403978.txt.gz · Last modified: 2018/07/12 13:59 by waltminer