DRAFT AGENDA
Date
Attendees & Representation
Community:
Agenda
Antitrust Policy
Approve previous meeting minutes
Approved ?
Open issues and PRs
Minutes
Release patch r1.3
To be considered. Candidate fixes:
Issue:Update errormessage for unsupported device identifieres Small typo in
GENERIC_422_UNSUPPORTED_DEVICE_IDENTIFIERS- example, PR: Update errormessage for unsupported device identifieresFix links for geofencing-subscriptions in README, add links also to Changelog
New
Answered by Cetin Alpaycetin
Update location-retrieval with add
maxSurfacemanagementAfter issue How to understand the response parameter area in the device retrieval API
Review and comment
Old
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 last 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
No new comments, discuss during meeting.
The issue to improve Geofencing with LOOSE, MODERATE, STRICT 'flavor' is still open #133
From previous meeting: Should be part of the discussion for next version.
Waiting for commonalities
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 itz
Evolution of subscription guidelines that may affect geofencing-subscriptions: