2024-07-16 Device Location - Meeting Minutes
ย
Date
Jul 16, 2024
Attendees & Representation
Community: ย @Jose Luis Urien Pinedo @Cetin Alpaycetin @Ludovic Robert @Fernando Prado Cabrillo @Surajj Jaggernath @Joachim Dahlgren @Javier Carro @Akos Hunyadi @Rafal Artychย
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
Proposal: We can apply the proposal described in Commonalities (here)
adding a new termination reason
adding a new attribute to provide rational
Owner: @Maximilian Laue Jul 26, 2024ย
Updateย maxAge-behaviour forย /verifyย &ย /retrieve
Review comments in issue
Decide on 422 vs 200 + UNKNOWN
Proposal: Move to option 1
Owner: @Maximilian Laue but @Jose Luis Urien Pinedo will provide suggestion in the PR Jul 26, 2024ย
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
Proposal:
We align Geofencing with QoD
Owner: @Maximilian Laue Jul 26, 2024ย
It can cause some misalignment with Commonalities but we can fix it in Commonalities later.
https://github.com/camaraproject/QualityOnDemand/issues/305location-retrieval: Alignment of errors with Commonalities
1 approval with comments
Action: @Jose Luis Urien Pinedo approve it and merge it by Jul 16, 2024ย
location-verification: Alignment of errors with Commonalities
2 approvals
Merged
New: device input
Align device object with Guidelines
Make device optional
Add some new doc to info.description
Exception: In Geofencing we keep the device object mandatory.
Test plans
All with some comments, still not approved:
Action: @Jose Luis Urien Pinedo @Ludovic Robert Close the review and merge them before Jul 19, 2024 for Location Verification & Location Retrieval
Ask review from @Toyeeb Rehmanย
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
No objection
Requires 3 files, one per API
PR for location-verification: Create Location Verification API readiness checklist
Action:
We create independent PR for
location-retrieval - owner @Ludovic Robert Jul 19, 2024ย
Geofencingย - owner @Maximilian Laue Jul 26, 2024ย
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....
Proposal: We create them as Draft - we sync when we need to merge to block ourselves when owner are on leave.
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