DRAFT Minutes after call // to be edited Herbert Damker
Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff:
Community: Herbert Damker
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
| Description | Due date | Assignee | Task appears on |
|---|---|---|---|
| 17 Jun 2024 | Herbert Damker | 2024-06-14 Quality on Demand - Meeting Minutes |
Open/New PRs
- #253 Update READMEs for new meeting link and meeting minutes in wiki
- New PR, subproject management
- #252 feat: move "basePath" /qod/v0 to "url"-property
- New PR, fixes issues #251, see below
- #228 draft for issue #101, see below
- #217 draft for issue #194, on hold?
New Issues
Check if relevant for v0.10.0 or later
- #254 Send notifications for all qosStatus changes
- relevant for v0.10.0
- PR
- #251 Update the "server"-section to align with other CAMARA specifications
- Jan will propose another default apiroot (with an example base path)
- relevant for v0.10.0
- #249 Duration in QosProfile and SessionInfo
- for v0.10.0: documentation/comment in qosProfile, that duration should not exceed 86400 seconds (for now) → PR, Herbert
- to be revisited for v0.11.0
- #247 Clarification: Behaviour when requested duration < minDuration
- PR with dedicated 400 error to be done → xxx
Open Issues - planned for v0.11.0
- #245 Update and enhance test definition file for QOD API
- DT plans to work on it
- Discussion in Commonalities to be considered (PR #117)
- #244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
- Discussion in Commonalities/ICM not finally closed
- OIDC to be used for all operations
- We need to decide about the scope names for each operation (format defined in ICM)
- Text to be included within the YAML (currently available in PR xxx, not yet final)
- #243 Rework definition of QoS flow(s)
- No update
- Dependency on #244
- #166 Extend QoS Profile queries to list profiles based on specific users or devices
- No update
- Dependency on #244
- #101 List endpoint for active sessions of authenticated user
- No update
- Dependency on #244
Any other discussion
- Final release of v0.10.0 → decision within next call, if there are no new issue relevant for the release