2024-01-12 Quality on Demand - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: na

Community: @Herbert Damker, @Eric Murray, Akos Hunyadi, @Andrew Wajs, Emil Zhang, Guy Vidal, Patrice Conil, @Rafaล‚ A. (Unlicensed), @Ramesh Shanmugasundaram, Randy Levensalor, @Syed Rehman, Thorsten Lohmar, @Toshi Wakayamaย 

Agenda

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

  • Roll Call

  • Action Items Review

  • Agenda Bashing

  • General Topics

    • Open PRs

    • New issues

    • Open Issues - relevant for release v0.10.0

    • Open Issues - planned for v0.11.0

  • Any Other Topics

    • ...

Minutes

Action Item Review

Open/New PRs

  • #253 Update READMEs for new meeting link and meeting minutes in wiki

    • New PR, merged

  • #252ย  feat: move "basePath" /qod/v0 to "url"-property

    • New PR, fixes issues #251, discussion see below

  • #228 draft for issue #101, no update

  • #217 draft for issue #194, no update

New Issues

Check if relevant for v0.10.0 or later

  • #254 Send notifications for all qosStatus changes

    • Relevant for v0.10.0

    • No change to API definition, documentation only

    • Action: PR to be created

  • #251 Update the "server"-section to align with other CAMARA specifications

    • Thorsten will propose another default apiroot (with an example base path) or extend the description

    • Relevant for v0.10.0 (to be aligned with other APIs, e.g. Device Status and Device Location)

  • #249 Duration in QosProfile and SessionInfo

    • Agreement: For v0.10.0 we will add a note within the documentation/comment in the qosProfile maxDuration, that the maximum duration should not exceed 86400 seconds

    • The restriction of the maximum duration will be revisited for v0.11.0

    • Action: PR to be created @Herbert Damker Jan 19, 2024ย ย 

  • #247 Clarification: Behaviour when requested duration < minDuration

    • Action: PR with dedicated 400 error to be done (Who)

Open Issues - planned for v0.11.0

Any other discussion

  • Final release of v0.10.0 โ†’ decision will be taken in next call, if there are no new issue relevant for the release

Action items