DRAFT AGENDA

Attendees & Representation

...

Community: Toshiyasu Wakayama  Ben Hepworth Jose Luis Urien Nick VrionisEric MurrayÁkos Hunyadi  Herbert Damker Thorsten Lohmar Emil Cheung Gervais-Martial Ngueko Joachim Dahlgren Masaharu Hattori Rafal Artych Ramesh Shanmugasundaram Randy Levensalor Surajj Jaggernath 

Agenda

• Antitrust Policy
• Review of previous meeting minutes
• Overall Topics
• ...
Regular Topics
• Open Pull Requests
• New Issues
• Issues relevant for v0.11.0
• Any Other Topics

...

• PR #306 Add HTTP-status-codes for better Error Handling
  • After discussion reduced to add HTTP-status-code 429
  • Supersedes also the (draft) PR #297 Add error 429 QUOTA_EXCEEDED?
  • Jose Luis Urien will do a cross-check of the PR, also with other APIs like DeviceLocation
  • Target to get it close within next week

• PR #318 Add query to qos-profiles to query profiles available on a given device
  • Addresses #166
  • Open question: one endpoint for all cases? (with which name?)
    • no objections to go with one POST endpoint
    • Randy Levensalor will update the PR

• PR #299 New API QOD Provision
  • Name of
  endpoint to be discussed (see comments from Randy Levensalor within the PR). Eric: "provision" is mobile terminology, would be good to avoid.
  • API changed to qod-provisioning
  • Request to all to review the latest version within the Pull Request. Please add your comments (or approval) until end of next weeks
  • Jorge Garcia Hospital will ask Jose Luis Urien to address the comments.
  To be able to include it within the release candidate we need to conclude the discussions about the PR until the next meeting (starting the final review).

• PR #320 New API Readiness Checklists for quality-on-demand and qos-profiles
  • Created and prefilled to check the current status
  • Need to be updated as part of each release PR

...

• #313 Align with Commonality decision about optional device object and respective documentation
  • To be done together with #315 and #316
  • Herbert Damker volunteered to do the PR after #306 is merged...

• #314 Adding notificationUrl as an optional property in CloudEvents
  • See discussionDiscussion open, DT will check the proposed alternative from Eric

• #315 Return 422 instead of 501 if the service is not implemented for specified device
  • Together with #313?

• #316 Align error responses for Device Object with v0.4.0 of Design Guidelines
  • Together with #313

• #317 Application IPs are not shared by OTT for QOD API
  • Backlog item ?if an enhancement at all
  • Discussion to be continued in the issue

• #321 Remove unresolved reference within quality-on-demand documentation
  • Herbert Damker to create PR, minor change

• #322 Remove cucumber code from the repository - decision request
  • ...no objection to delete the code => PR to be created

Issues relevant for v0.11.0 (if not yet covered by PRs)

• #101 List endpoint for active sessions of authenticated user
  • Jose Luis Urien proposed a list endpoint for provisions within PR #299 and recommends to take this as template
  • PR needs to created soon to get it into the release.
  Randy: name of the endpoint to be considered, see comment in PR #299
  • Use same pattern as above in qos-profiles and change the getSessions from GET to POST with device optional in the body
  • Jose Luis Urien to create the PR.

• #245 Update and enhance test definition file for QOD API
  • Regarding cucumber code, see #322
  Request to all participants to consider to contribute current .feature files
  • Jose Luis Urien will check if internal test definitions can be adapted
  • Most probably we won't have a sufficient test .feature file at M3
  • Target to have it in advance of M4.

• #286 Review Attribute Descriptions with References to External Specifc
  • For quality-on-demand there is only one reference (to be deleted), see #321
  • Proposal to move the issue to backlog - agreed

Review scope and time plan for Release Candidate

...

• PR #320 New API Readiness Checklists for quality-on-demand and qos-profiles
  
  • Current open "to be dones":
    • API Definition (open Issues/PRs)
    • DesignguidelinesfromCommonalitiesapplied (open Issues/PRs)
    • BasicAPItestcases & documentation (see #245!)
    • Changelog update (will be done in release PR)
  • User stories and Enhanced API test cases are not mandatory for  0.x API versions
• Target to have the release candidate PR ready within the next QoD call on July 26th.
• We will go for the Meta-Release with an "Initial" API Version, which means to keep v0.11.0
  • Why we don't go for "Stable":
    • Lack of prerequisites (test cases, certification of previous version)
    • Too many changes between v0.10.0 and v0.11.0, we should have one cycle where we don't introduce breaking changes

Any other topics

• Next QoD meeting will be on July 26th, at 14:00 CEST / 12:00 UTC
• We don't plan to skip meetings until the release (at least for now).

...