DRAFT MINUTES
Date
Attendees & Representation
Community: Jose Luis Urien Pinedo, Joachim Dahlgren, Akos Hunyadi, Cetin Alpaycetin, Ludovic Robert, Javier Carro
Agenda
Antitrust Policy
Approve previous meeting minutes
Approved ?
Open issues and PRs
Minutes
Meta release (Fall24)
M5 completed on Sept 15th, as scheduled.
M6 scheduled on Sept 30th: Retrospective.
Feedback to be provided here
Meta release (Spring25)
M0: Sept. 30th: Kick-off
New
Support of Multi-SIM lines in DeviceLocation APIs
Derived from camaraproject/Commonalities#302
Device Location APIs are specially problematic as location is linked to a physical device, not to a phone number
Discussion during meeting:
The issue has a technical aspect but it is more important for Product Management.
For Location-verification probably we can consider that if any device is in 'the zone' then the result will be true. Perhaps same for geofencing.
For location-retrieval the issue is more critical as sending back an array of location is probably not a good solution
We need to think about UC
Action for each company to work with product team to refine the requirement
Old
Add an “Area” data-type into CAMARA_common.yaml
No new comments
From previous meeting:
Some new comments in related issue in Commonalities
Not urgent but let's keep an eye on it
How to understand the response parameter area in the device retrieval API (#255)
No new comments
From previous meeting:
Proposal makes sense.
To be discussed
alignement with the freshness (for maxAge management)
Discussion during meeting:
Square meter could be the unit
The design should be aligned with maxAge
Ludovic Robert will draft a PR
AOB
The issue to improve Geofencing with LOOSE, MODERATE, STRICT 'flavor' is still open #133
Should be part of the discussion for next version.
Add an issue in commonalities for Retrieve subscription filtering limitation based on the phone number retrieved from the access token