DRAFT AGENDA
Date
Attendees & Representation
Community: Jose Luis Urien Cetin Alpaycetin Ludovic Robert Fernando Prado Cabrillo Surajj Jaggernath Joachim Dahlgren Javier Carro Ákos Hunyadi Rafal Artych
Agenda
Antitrust Policy
- Approve previous meeting minutes
- Approved?
- Open issues and PRs
...
- 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
- Proposal: We can apply the proposal described in Commonalities (here)
- Waiting for Commonalities
- 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 will provide suggestion in the PR
Alignment with Commonalities
...
- 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
- It can cause some misalignment with Commonalities but we can fix it in Commonalities later.
- We align Geofencing with QoD
- https://github.com/camaraproject/QualityOnDemand/issues/305location-retrieval: Alignment of errors with Commonalities
- 1 approval with comments
- Action: Jose Luis Urien approve it and merge it by
- 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:
- Testing plan for location verification
- Geofencing feature file
- Add Test Definition for location Retrieval
- Action: Jose Luis Urien Ludovic Robert Close the review and merge them before 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
- Geofencing - owner Maximilian Laue
- We create independent PR for
- 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
...