Date

16 Jul 2024

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

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 26 Jul 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 will provide suggestion in the PR 26 Jul 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 26 Jul 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 approve it and merge it by 16 Jul 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:

• 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 19 Jul 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 19 Jul 2024 
      • Geofencing  - owner Maximilian Laue 26 Jul 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
  • Scope of Location Verification API for Fall24 CAMARA Meta Release
  • Scope of Location-Retrieval for Fall24 CAMARA Release
  • Scope of Geofencing Subscriptions API for Fall24 CAMARA Meta Release
• 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

Action items