This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
agl-roadmap [2018/02/16 16:32] waltminer |
agl-roadmap [2019/02/14 14:38] waltminer [2019 Roadmap/ Workplan from SAT] |
||
---|---|---|---|
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.org. Probably 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) | + | * Finish AGL spec 2.0 |
- | * **Add video support to mediaplayer binding | + | * 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. | ||
+ | |||
+ | |||
==== From App FW and Security EG ==== | ==== From App FW and Security EG ==== | ||
- | * **HTML5 apps/ home screen | + | * **HTML5 apps** |
- | * Chromium** | + | * HTML5 home screen |
+ | * Chromium | ||
* Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications, load them. | * Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications, load them. | ||
* Define the list of privileges we are going to enforce in the security model. | * Define the list of privileges we are going to enforce in the security model. | ||
- | * **Running apps not as root/ multi-user** | + | * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} **Running apps not as root/ multi-user** |
- | * Distinction between platform services (e.g., nfc, telephone) and user services that run inside a user context (e.g., media player and lightmedia scanner) | + | * {{: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 | + | * 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) | ||
* Improved Developer workflow for debugging apps including | * Improved Developer workflow for debugging apps including | ||
- | * Round trip download/debug/fix/download apps. | + | * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Round trip download/debug/fix/download apps. |
- | * **Supervision daemon for apps and services for development mode.** Allows a developers to have a central place monitor IPC in real time. Builds on the current monitor service that is available for binders. Extends its availability to startup and allows more general monitoring without requiring detailed knowledge of what is available in a specific binder. Current version only allows a single binder to be monitored. This would allow monitoring across binders. | + | * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} **Supervision daemon for apps and services for development mode.** Allows a developers to have a central place monitor IPC in real time. Builds on the current monitor service that is available for binders. Extends its availability to startup and allows more general monitoring without requiring detailed knowledge of what is available in a specific binder. |
* **Task manager app** to allow developers to see what tasks/process are running in an app. Allow for killing apps. | * **Task manager app** to allow developers to see what tasks/process are running in an app. Allow for killing apps. | ||
* Review AGL spec 1.0 to determine what requirements are there for managing home screen and apps. Something like iphone where a double-tap on home button allows swiping up of apps to kill them. | * Review AGL spec 1.0 to determine what requirements are there for managing home screen and apps. Something like iphone where a double-tap on home button allows swiping up of apps to kill them. | ||
+ | * Terminal app on home screen | ||
* Introduce resource widgets to share content/ resources across multiple apps. | * Introduce resource widgets to share content/ resources across multiple apps. | ||
Line 42: | Line 55: | ||
* Connection glitches in multi-ECU system shall be properly handled. | * Connection glitches in multi-ECU system shall be properly handled. | ||
* **XDS features** | * **XDS features** | ||
- | * v1.1.0 - targeted release date: AMM (2018 February 20th) | + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} v1.1.0 - targeted release date: AMM (2018 February 20th) |
* Board console/terminal integration within XDS dashboard | * Board console/terminal integration within XDS dashboard | ||
* Documentation improvement of debug section | * Documentation improvement of debug section | ||
- | * v2.0.0 - targeted release date: ALS (2018 June 20th) | + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} v6.0.0 - targeted release date: ALS (2018 June 20th) |
* Monitoring integration | * Monitoring integration | ||
+ | * v7.0.0 | ||
* 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 / service | ||
+ | * 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 | ||
- | * Improved secondary display suport | + | * Multi-resolution display support. |
+ | * Fix scaling issues across different display sizes | ||
+ | * Landscape vs. portrait | ||
+ | |||
+ | |||
+ | * Add new apps to home screen (not hardcoded) - SPEC-1734 | ||
+ | * Management of apps that overflow the screen - slider or multiple pages or folders | ||
+ | * 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 65: | Line 112: | ||
* Investigate replacement for Qt; HTML5, GTK+,,,, | * Investigate replacement for Qt; HTML5, GTK+,,,, | ||
* **Audio** | * **Audio** | ||
- | * High Level audio API | + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} High Level audio API |
- | * AGL Advanced Audio Agent (AAAA) | + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} AGL Advanced Audio Agent (4A) |
- | * Make PulseAudio optional | + | * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Make PulseAudio optional |
* Switch to Bluez / Alsa for Bluetooth audio | * Switch to Bluez / Alsa for Bluetooth audio | ||
* Speech and Text to Speech Services collaboration | * Speech and Text to Speech Services collaboration | ||
Line 73: | Line 120: | ||
* 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 81: | Line 129: | ||
==== From Connectivity EG ==== | ==== From Connectivity EG ==== | ||
* Vehicle Signaling | * Vehicle Signaling | ||
- | * **Signal composer stabilization an improvements** | + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **Signal composer stabilization an improvements** |
- | * API to define new virtual messages at run-time | + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} API to define new virtual messages at run-time |
- | * Extend low level binding to hardware other than CAN. Need to determine what the next target hardware should be. | + | * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Extend low level binding to hardware other than CAN. Need to determine what the next target hardware should be. |
* Factory programming of CAN message set based on final vehicle configuration. Requires multiple vehicle message dictionaries to be present in the code. | * Factory programming of CAN message set based on final vehicle configuration. Requires multiple vehicle message dictionaries to be present in the code. | ||
+ | * **Add GPS data to virtual signal composer** | ||
+ | * **Sensor data collection and include in signal composer** | ||
+ | * **V2C interface** | ||
+ | * **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 | ||
- | * **Bluetooth binding rewrite** for stability and robustness | + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **Bluetooth binding rewrite** for stability and robustness |
- | * **PBAP/Contacts binding** | + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **PBAP/Contacts binding** |
- | * BT PAN binding | + | |
* BLE binding | * BLE binding | ||
* WiFi improvements | * WiFi improvements | ||
- | * **WiFi binding rewrite** for stability and robustness | + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **WiFi binding rewrite** for stability and robustness |
* **AP mode** | * **AP mode** | ||
* **Additional Wifi dongle support** | * **Additional Wifi dongle support** | ||
Line 104: | Line 158: | ||
* Hardwired connection to telephone for **Telematics use cases** | * Hardwired connection to telephone for **Telematics use cases** | ||
* Network management binding | * Network management binding | ||
- | * General network connectivity above connman to manage connectivity including IPv4/v6 configuration, bridging, tethering, network QOS and switching | + | * GG priorities in bold |
+ | * General network connectivity above connman to manage connectivity including **IPv4/v6 configuration**, bridging, tethering, network QOS and switching | ||
+ | * **Add configuration support for networking into settings app** | ||
* User profiles to allow authorized users to configure interfacing | * User profiles to allow authorized users to configure interfacing | ||
- | * Support multiple low-level interface binding backends including Ethernet, WiFi, BT PAN, and WWAN | + | * Support multiple low-level interface binding backends including **Ethernet, WiFi**, BT PAN, and WWAN |
* For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. | * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. | ||
- | * Port Comtech's OSS nav app to demo HMI | + | |
==== From V2X EG ==== | ==== From V2X EG ==== | ||
Line 141: | Line 198: | ||
* Additional tests | * Additional tests | ||
* Applications | * Applications | ||
+ | * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} App Services | ||
* Platform | * Platform | ||
* BSPs | * BSPs |