...

...

...

...

...

DRAFT AGENDA

Attendees & Representation

...

Community: Herbert Damker efezhan Eric Murray Joachim Dahlgren Jose Luis Urien PinedoRandy Levensalor Surajj Jaggernath Toshi Wakayama Rafal Artych  Patrice Conil Thorsten Lohmar  dominik.fischer Masaharu Hattori Ramesh Shanmugasundaram Maximilian Laue Jorge Garcia Hospital, CHINTAN LODARIYA

Agenda

• Antitrust Policy
• Review of previous meeting minutesNo comments - remove DRAFT
• Overall Topics
• Regular Topics
  • Open Pull Requests
  • New Issues
  • Issues relevant for v0.11.0
• Any Other Topics

Minutes

Review of previous meeting minutes

• Previous meeting minutes: 2024-05-03 Quality on Demand - Meeting Minutes
  • No comments, agreed to remove "DRAFT"

Overall topics

• New GitHub teams @camaraproject/quality-on-demand_maintainers and @camaraproject/quality-on-demand_codeowners are complete.
• TSC: Reactivated discussion Commonalities/issues/171: Revise the device object definition to simplify it 
  • Telefonica team will set up a dedicated meeting, involving ICM & Commonalities team
  • QoD position? Who from Qod will participate? 
    • Jose Luis Urien Pinedo obviously Image Added ... PhoneNumber yes, IP Address in some cases, Network Access Identifier not yet. To be discussed in which cases the Device object can be made optional (e.g. if already contained in access token)
    • Randy Levensalor to ensure that fixed wireless access will be considered
  • Based on outcome we will enhance our description when to use and how to use the device object

Open Pull Requests

• PR #289 Split QoD in Quality-On-Demand and QoS Profiles APIs by Jose Luis Urien Pinedo 
  • Open comments from to be resolved and PR merged

• PR #294 Update README.md by Jorge Garcia Hospital 
  • ...Open comments resolved online, ready for final review

Closed issues

• #290 Current CI expects certain fixed name for yaml spec
• #265 Proposal to split QoS Sessions and QoS Profiles into two separate API definitions
  • fixed with merged PR #289 

New Issues

• none

Issues relevant for v0.11.0

• #292 Scope of QualityOnDemand for Fall24 CAMARA release
  • Any No updates?, still valid

• #291 Consolidated issue for duration, extentDuration, startedAt, expiredAt, maxDuration and their formats (to be updated)
  • Covers also #288, #281, #280, #266, #249
  • Jose Luis Urien Pinedo
  to
  • will make first
  proposals
  • proposal
  • Previous minutes
    • discussed about maxDuration → establish again as absolute maximum
    • discussed about default for duration 
      • making duration parameter mandatory could be an option

• #265 Proposal to split QoS Sessions and QoS Profiles into two separate API definitions
  • will be fixed with PR #289 

• #257 Error behaviour when session cannot be created due to "time cap" limitation
  • will Will be addressed after PR #289 is merged

• #245 Update and enhance test definition file for QOD API
  • No update
  • Previous content:Waiting for close of issue within Commonalities (to be able to align contribution with them)Telefonica has a feature file for testing, will adapt it to Commonalities results, and then contribute.
  • Commonalities PR #203 with design guidelines for .feature files and test coverage (sunny/rainy test cases). For first meta-release the full coverage will not be required.
    • CAMARA test cases will only test the correct reactions of the API, not the service (e.g. network performance or SLAs)
  • Previous content:
    
    • Sunny test cases have to added before first release candidate of v0.11.0 (mid of June)

• #244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
  • Create PR after split PR is merged (DT?)Eric Murray will create a PR. 

• #166 Extend QoS Profile queries to list profiles based on specific users or devices
  • Randy Levensalor  to  will create a first PR (after split PR is merged)

• #101 List endpoint for active sessions of authenticated user
  • Please review latest proposal on this issue: https://github.com/camaraproject/QualityOnDemand/issues/101#issuecomment-2015041284
  • Draft PR #228 need to be closed and restarted due to the split and based on the discussion.

Further Issues

• #268 Provision mode for QoD
  • To be discussed if it will be in meta release Fall24 (if yes, we need a release candidate until mid of June!) Jorge Garcia Hospital 
  Previous content
  • PR to add it into the scope within README Jorge Garcia Hospital - done
  • Do we need a User Story for that? Yes. Jorge Garcia Hospital 
  If new API, it can be added within the repository as long as we always release it together. New versioning guidelines under discussion in ReleaseManagement allow APIs with different versions in one repository.
  • It would be good to have an user story to get a better understanding of the Provision mode usage and behaviour
  • Jose Luis Urien Pinedo: the Provision mode will be proposed as independent API, 90% same as Session mode API
  • Thorsten Lohmar asked for answers to his questions in https://github.com/camaraproject/QualityOnDemand/issues/268#issuecomment-2079239521

• #286 Review Attribute Descriptions with References to External Specifc
  • No update, previous content: 
    • Herbert Damker check where QoD would be impacted 
    • Maybe into backlog until implementation experiences are available

Any other topics

• Next QoD meeting will be on May 31st, at 14:00 CEST / 12:00 UTC
• Herbert will be on vacation. Meeting will be moderated by XXX? Randy Levensalor 

Action items