Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff:
Community: Rafal Artych Pierre Close Eric Murray Ming HuiJan Friman G. Murat Karabulut Ludovic Robert Sachin kumar Tanja de Groot Uwe Rauschenbach Toyeeb Rehman Parice Conil
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
- Merged PRs
- Agenda Bashing
- General Topics
- Release 0.3.0 status
- Pull Requests review
- Issues review
- Any Other Topics
- Any Other Topics
Minutes
Action Item Review
Task report
Looking good, no incomplete tasks.
Merged PRs
- PR #117 Create API-Testing-Guidelines.md
- PR #124 Update CAMARA_common.yaml
- PR #123 Update API-design-guidelines - Issues 97&98
- PR #115 Set X-Correlator as Required in OAS Definition, X-Version removed
Release 0.3.0
- API linting ruleset:
- PR #110 API linting implementation guideline
- ready for final review (issues discovered during testing were resolved)
- this initial rules is subject to further extensions
- additional workflow defined to be run manually if detailed log of detected warnings is needed
- PR #110 API linting implementation guideline
- PR #74 Initial CAMARA OAS linting ruleset ready for final review
- PR #57 Update OpenAPI security guidelines
- currently mainly guidelines for scope naming
- PR #132 Added filter criteria related Issue 103
- clarification for response filtering parameters
- Draft PR #134 CHANGELOG.md and README.md for release 0.3.0
- needed for producing the release
PRs review
- PR #120 Update CAMARA_common.yaml: add Device headers, fix address
- clarification for header casing added
- PR #131 Update API-design-guidelines to add subscriptionMaxEvents
- Discussion in issue #90
- new parameter and explanation how to use it
Issues review
- Issue #122 Explicitly state how to identify "API Name"
- Possibly covered in PR #57 Update OpenAPI security guidelines
- Issue #126 Proposal - Runtime Restrictions API
- Issue #127 Which error send back when Device Identifier not supported by API Server?
- PR to be created and further discussed if '400 class'
- Issue #128API Design : UNAUTHENTICATED 401
- More comments expected
- Issue #129 API Design - Error Handling should include RFC6749 exception
- More comments expected
- Issue #130 Filtering for data type "boolean"
- More comments expected
- Issue #133 Adopt RFC 9457 error response format
- all commonalities participants and other interested Camara members are requested to provide a "formal" position on this issue
AOB
The Poll on Moving Commonalities meetings to The Linux Foundation platform was sent to the mailing list
The next meeting is on Feb 19th 2024.
Action items
- Upload slide deck for Runtime Restrictions API
- Finalize the process for Release 0.3.0 Rafal Artych
- Prepare PR addressing Issue #127 Ludovic Robert
- Provide your formal postion on Issue #133