User Tools
agl-distro:oct2017-f2f
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
agl-distro:oct2017-f2f [2017/10/22 21:35] waltminer Meeting minutes |
agl-distro:oct2017-f2f [2017/11/08 04:47] (current) nnishiguchi [Agenda] |
||
|---|---|---|---|
| Line 40: | Line 40: | ||
| "C" column: ADIT's understanding for AAAA. \\ | "C" column: ADIT's understanding for AAAA. \\ | ||
| "F" column: suggestion based on "C" column for High level API interface, or it is comment for Soundmanager API. \\ | "F" column: suggestion based on "C" column for High level API interface, or it is comment for Soundmanager API. \\ | ||
| + | As a result of the discussion, I updated comparison table as {{:agl-distro:api_comparison_a05.xlsx|}}.\\ | ||
| **Friday Oct 20 (all times CET)** | **Friday Oct 20 (all times CET)** | ||
| Line 65: | Line 66: | ||
| Between the meeting on Thursday morning to discuss the High Level (app level) API and the meeting on Friday a lot of progress was made. | Between the meeting on Thursday morning to discuss the High Level (app level) API and the meeting on Friday a lot of progress was made. | ||
| - | * We will continue with the High Level API proposed by Audiokinetic. Francois stated that he has taken nearly as far as he can at this time. The Thursday meeting spent a lot of time detailing the need for the API as proposed and working through some use cases. | + | * We will continue with the High Level API proposed by Audiokinetic. {{:agl-distro:highlevelaudio_dresdenamm_final.pdf|}} Francois stated that he has taken nearly as far as he can at this time. The Thursday meeting spent a lot of time detailing the need for the API as proposed and working through some use cases. |
| * In order to migrate legacy apps to AAAA and the new API, Fulup agreed to have IoT.bzh make the code available in the Yocto/CI build rather than building the code via the SDK. The SDK version allowed IoT.bzh to progress the concept to this point, but we need to make the API available generally. | * In order to migrate legacy apps to AAAA and the new API, Fulup agreed to have IoT.bzh make the code available in the Yocto/CI build rather than building the code via the SDK. The SDK version allowed IoT.bzh to progress the concept to this point, but we need to make the API available generally. | ||
| * Once the code has been added to the build, Konsulko will look at what is required to port the legacy reference apps the new API before the CES Integration Session in mid-November. | * Once the code has been added to the build, Konsulko will look at what is required to port the legacy reference apps the new API before the CES Integration Session in mid-November. | ||
| Line 78: | Line 79: | ||
| 14:30 - 15:30 Security Topics | 14:30 - 15:30 Security Topics | ||
| - | * Oshri Yahav of Saferide.io made a proposal about security. | + | * Oshri Yahav of Saferide.io made a proposal about security. {{:agl-distro:saferide_open_source_project.pdf|}} |
| * Discussed the process for security issues in AGL code | * Discussed the process for security issues in AGL code | ||
| * Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism. | * Walt will clean out the existing EG-Security mail list so we can make use of this as a private discussion mechanism. | ||
agl-distro/oct2017-f2f.1508708130.txt.gz ยท Last modified: 2017/10/22 21:35 by waltminer
Page Tools
