...
- Roll Call
- Action Items Review
- Agenda Bashing
- General Topics
Item 1 How to progress a Edge Cloud MVP (ref PR154)
This is to help accelerate the implementation of an MVP which covers the Edge Cloud lifecycle (including Discovery and Lifecycle management)
Option 1 is to maintain a sub-api separate API along with the existing APIsOption 2: merge PR54 with Simple Edge Discovery to produce a new MVP API for Edge Cloud
Discussed by Sergio, Kev, Thomas, Deepak.
Agreement: Proposed to go with option 2, but do not remove Simple Edge Discovery. . Result will be one new API (name to be decided) that includes 'MVP' lifecycle management and discovery (extending the functionality seen in the Simple Edge Discovery API)
- Item 2 Discussion on Application vs Artefact
Discussed by Sergio, Thomas, Deepak, referring to Jon's comments in PR 154
Agreement: Combine Artifact and Application into a single type and update the PR with a new commicommit
- Any Other Topics
- Discussion led by Sergio on the topics raised in PR 159 on the addition of more granular discovery parameters in the Sime Simple Edge Discovery API
Discussed by Sergio, Kev, Kevin, Thomas, Cristina
To be continued, general thought is that a way of discovering the application endpoint is needed for the 'MVP' API - Fabrizio raised issue 140, and whether we need these branches 0.9.0, 1.0.0, 2.0.0 . If not they should be deleted.
- Discussion led by Sergio on the topics raised in PR 159 on the addition of more granular discovery parameters in the Sime Simple Edge Discovery API
...