DRAFT AGENDA
Date
Attendees & Representation
Type @ and your name to indicate your attendance
Community:
Agenda
Antitrust Policy
- Approve previous meeting minutes
- Approved?
- Open issues and PRs
Minutes
Meta release (Fall24)
Schedule
- M3 by July 21st
- First RC to be published
- This is not a hard deadline. Subprojects may reduce the period between M3 and M4
- M4 by August 31st
- Hard deadline to have all final contents for meta-release approved
- Actions towards M3:
- Type your task here, using "@" to assign to a user and "//" to select a due date
Functionality
- Add handling when the requested geofence
area
cannot be covered- Waiting for Commonalities
- Update
maxAge
-behaviour for/verify
&/retrieve
- Review comments in issue
- Decide on 422 vs 200 + UNKNOWN
Alignment with Commonalities
Errors
- geofencing: Alignment of errors with Commonalities
- 1 approval
- 1 comment suggesting to not include all possible HTTP codes. This issue was also discussed in QoD
- https://github.com/camaraproject/QualityOnDemand/issues/305location-retrieval: Alignment of errors with Commonalities
- 1 approval with comments
- location-verification: Alignment of errors with Commonalities
- 2 approvals
New: device input
- Align device object with Guidelines
- Make device optional
- Add some new doc to info.description
Test plans
All with some comments, still not approved:
- Testing plan for location verification
- Geofencing feature file
- Add Test Definition for location Retrieval
API readiness checks
Common issue: Provide API readiness checklist
- Proposal to upgrade location-verification API to first stable relase (v1.0.0) as it is the only one that fulfills the requirement to have a previous public release certified
- Discuss if there are objections
- Requires 3 files, one per API
- PR for location-verification: Create Location Verification API readiness checklist
- One of the checks is to add a link to the User Stories:
- PR for location-verification: location-verification Create Location Verification User Story
- Discuss on how we manage to add all meta data for the 3 APIs: Create PRs for each change, keep PR open until everything is OK....
Scopes for meta-release
- Issues created and linked in DeviceLocation API Release Tracking
- Review if we need to update anything
Other New
- Issue: Add an “Area” data-type into CAMARA_common.yaml
- Referencing Commonalities issue
Ongoing (not for Meta-release)
- Polygon area type added
- PR195