DRAFT MINUTES

...

Community: Herbert Damker Eric Murray Randy Levensalor Thorsten Lohmar Toshi Wakayama Masaharu Hattori Rafal Artych 

Agenda

• Antitrust Policy
• Review of previous meeting minutes
• Overall Topics
• Regular Topics
  • Closed PRs and Issues
  • Open Pull Requests
  • New Issues
  • Open Issues
• Any Other Topics

...

• PR #326 Align quality-on-demand with Commonalties regarding optional device object and error message is merged, closing:
  • #313 Align with Commonality decision about optional device object and respective documentation
  • #315 Return 422 instead of 501 if the service is not implemented for specified device
  • #316 Align error responses for Device Object with v0.4.0 of Design Guidelines
  • #328 Device in response object need to be omitted or clearer defined
    • Closed by the following (additional) description within the SessionInfo schema:
      Optional device object only to be returned if provided in createSession. If more than one type of device identifier was provided, only one identifier will be returned (at implementation choice and with the original value provided in createSession). Please note that IP addresses of devices can change and get reused, so the original values may no longer identify the same device. They identified the device at the time of session creation.
    • Thorsten Lohmar commented that the mentioning of the device object in the SessionInfo description is unclear and therefore potentially confusing for readers. He opened QualityOnDemand/issues/340 to address that.
    • The issue will get closed with a reference to Commonalities/issues/259 which is addressing the aspect the error message in cases when both a 3-legged token and a device identifier is presented.

• PR #318 Add query to qos-profiles to query profiles available on a given device is merged and closed:
  • #166 Extend QoS Profile queries to list profiles based on specific users or devices

• PR #299 New API QOD Provision is merged and closed:
  • #268 Provision mode for QoD
• PR #335 Align on Commonalities' subscription-model by using sink and sinkCredentials was created and merged to address:
  • #332 Alignment of notification web hook to CloudEvent subscription model

...

• #292 Scope of QualityOnDemand for Fall24 CAMARA release
  
  • Plan remaining task for public release of v0.11.0 & qod-provisioning:
    • Test definition files: see #245
  • User Stories 
    • qos-profiles Randy Levensalor (new issue #341)
    • quality-on-demand Herbert Damker  (new issue #342)

• Reminder from last meeting: 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 August 23rd, at 14:00 CEST / 12:00 UTC

...