This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
agl-distro:oct2016-f2f [2016/10/25 12:42] waltminer Updated meeting minutes with summaries from EG notes |
agl-distro:oct2016-f2f [2016/10/25 12:43] waltminer [System Architecture Team] |
||
---|---|---|---|
Line 68: | Line 68: | ||
==== System Architecture Team ==== | ==== System Architecture Team ==== | ||
* Full meeting notes are [[https://wiki.automotivelinux.org/agl-sat-meetings#october_14_2016 | here]]. | * Full meeting notes are [[https://wiki.automotivelinux.org/agl-sat-meetings#october_14_2016 | here]]. | ||
+ | |||
+ | **Summary:** | ||
* Yocto 2.1 Update - Discussion of whether we should move to Yocto 2.2 (not released yet but is on the master branch of Yocto). SAT was split on whether this is a good idea. Walt will check with CES vendors to see if the switch to Yocto 2.2 will break compatibility in the short term (pre-CES). | * Yocto 2.1 Update - Discussion of whether we should move to Yocto 2.2 (not released yet but is on the master branch of Yocto). SAT was split on whether this is a good idea. Walt will check with CES vendors to see if the switch to Yocto 2.2 will break compatibility in the short term (pre-CES). | ||
Line 87: | Line 89: | ||
==== Application Framework and Security EG - Security Blueprint document ==== | ==== Application Framework and Security EG - Security Blueprint document ==== | ||
* Full meeting notes are [[https://wiki.automotivelinux.org/eg-app-fw/meetings?&#october_14_2016 | here]] | * Full meeting notes are [[https://wiki.automotivelinux.org/eg-app-fw/meetings?&#october_14_2016 | here]] | ||
- | Notes: | + | Summary: |
* Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/sec-blueprint) | * Security Blueprint(Github https://github.com/automotive-grade-linux/docs-agl/tree/master/sec-blueprint) | ||
* Identify what is in scope for AGL recognizing that AGL cannot solve all security issues. John will write the initial version for review at the next meeting. ** Due for this meeting. Not complete ** | * Identify what is in scope for AGL recognizing that AGL cannot solve all security issues. John will write the initial version for review at the next meeting. ** Due for this meeting. Not complete ** |