Community Attendees:
Thorsten Lohmar , steve.vickers , Masaharu Hattori , Rajat Kandoi , Barath K , Tanja de Groot , @fadime demirer, Alejandro Palmier
Community Attendees:
LF Staff:
Agenda
Antitrust Policy
Agreement of last minutes (Link)
Action Items Review
Agenda 1
Agenda 2
Minutes
Topic 1
Comments
Action items
CAMARA Agreement Process Discussion (Link)
Discussion of Issues and Pull Requests
Issue #16: [Backlog] Question on QoD booking proposal
Can be closed?
Issue #14: Discussion on overlapping with IoT Data Transfer Activation API
Issue #11: Usage Scenarios for Dedicated Networks
Pull Request #12: Description of Usage Scenarios for the Dedicated Networks API
Issue #10: API Design Requirements
Pull Request #15: API Design considerations
Minutes
Agreement of minutes
No Comments, agreed.
Relation to QoD booking API (issue #16)
Masaharu - Issue #16 can be closed since the QoD booking API will become its own sandbox API (discussed in API backlog as the agreed way). Issue closed.
Relation to IoT Data Transfer API (issue #14)
Thorsten: Open question asked but not clear if it can be answered
Rajat: Can it be reasoned as a requirement?
Rajat: Suggested we make a note on the principle of it, and request closing the issue.
Tanja: Can also create a new issue with reference to this issue / requirement.
Agreed with Tanja’s proposal. Thorsten to create the issue.
CAMARA Agreement process
Discussion - agreed to check with Herbert on the rules and potentially request clarification from Governance.
PR #12 and PR#15
Walk through and agreed 2 week extension to “finalize” (otherwise implicit accept by Code owners)
Release tracker
Currently marked as Spring. Unrealistic to meet this goal. Agreed however to keep it as is and update when we have a bit more detail.
Action items
- Thorsten Lohmar : Create new issue - “what info does DN API return for co-relation” and close related issue #16
- Rajat Kandoi : Experiment with images / make a proposal for a WoW in the DN API Sub project