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-distro:jul2017-f2f [2017/07/17 21:05] waltminer [Attendees] |
agl-distro:jul2017-f2f [2017/07/20 13:12] waltminer |
||
---|---|---|---|
Line 87: | Line 87: | ||
* Currently only available via AGL gerrit. | * Currently only available via AGL gerrit. | ||
* Presentation for app users | * Presentation for app users | ||
+ | * Do we allow binary only apps or require source code? | ||
+ | * Do multiple (or all reference) platforms need to be supported to be accepted? | ||
+ | * Need to include a rating system for apps. | ||
+ | * In parallel we will create a wiki page for commercial vendors to let people know about their capabilities, since these may be service oriented or not related to a specific AGL Application. | ||
15:45 - 16:00 - Break\\ | 15:45 - 16:00 - Break\\ | ||
Line 97: | Line 101: | ||
* How do we collaborate with outside groups like W3C and Autosar that are working on topics of interest to AGL members? | * How do we collaborate with outside groups like W3C and Autosar that are working on topics of interest to AGL members? | ||
- | [[agl-distro:jul2017-f2f-tuesday-summary|Summary of day 1]] | + | * Propose a V2C Expert Group with Ashley Stevenson from ForgeRock to lead. |
+ | * Authentication | ||
+ | * V2C EG will make a proposal to the Steering Committee to propose use of OpenID Connect | ||
+ | * Nori will reach out to Nat from the [[http://openid.net/foundation/ | OpenID Foundation]] to speak at the October AMM. | ||
==== Evening Event ==== | ==== Evening Event ==== | ||
Line 116: | Line 123: | ||
08:30 - 09:00 - Check-in and Breakfast\\ | 08:30 - 09:00 - Check-in and Breakfast\\ | ||
09:00 - 10:00 - Toyota Window Manager API - Aurelian\\ | 09:00 - 10:00 - Toyota Window Manager API - Aurelian\\ | ||
+ | * Aurelian and Joel {{:eg-ui-graphics:170606_agl_hmi-fw_arch_0_2_3.docx|showed a presentation}} with the Toyota/Mentor proposed architecture and schedule | ||
+ | |||
+ | * Steve L - Security issues. Does Window Manager verify that surface changes are requested by the correct AppIO? How are AppIDs assigned so they cannot be spoofed? | ||
+ | * Fulup - SMACK level checking and verification should be performed by the Window Manager | ||
+ | * As proposed, Window Manager runs as its own process, does that introduce unacceptable latencies? | ||
+ | * The architecture is for a single display run by an single Window Manager. It was suggested that the APIs and Window Manager design should account for multiple displays and Window Manager instances. | ||
+ | |||
+ | * There was a schedule for Sound Manager changes included in the slides. Mentor and Toyota need to provide additional information about this activity. There are on-going Sound Manager activities that may conflict with this effort. Mentor was unable to identify who would be working on this activity. | ||
+ | |||
10:00 - 10:30 - LG Enact JavaScript Framework - Steve Winston\\ | 10:00 - 10:30 - LG Enact JavaScript Framework - Steve Winston\\ | ||
10:30 - 11:30 - Graphics EG \\ | 10:30 - 11:30 - Graphics EG \\ |