2025-03-25 DeviceLocation Minutes
Community Attendees:
@Jose Luis Urien Pinedo @Cetin Alpaycetin @Ludovic Robert @Surajj Jaggernath @Maximilian.Laue @Joachim Dahlgren
Community Attendees:
LF Staff:
Agenda
Antitrust Policy
Approve previous meeting minutes
Approved ? yes
Open issues and PRs
Minutes
Spring25 Meta-release
TSC declared M5 on March 20th
If some issue is reported on r2.2 we would need to consider a path release r2.3, with potential version upgrade
https://github.com/camaraproject/DeviceLocation/issues/296
Issue kept open to allow companies to submit new test statements for the past release
New
No new issues and PRs during the last 2 weeks
Confluence updated
New DeviceLocation API Description folder with API descriptions (the ones published in www.camaraproject.org )
DeviceLocation Participants to be filled? Please, do it
Pending
Enhancement Request: Add IMEI as a Device Identifier for Location Retrieval API
From previous meeting:
New comments challenging the requirement
Should we keep this open? We keep open for a couple of weeks more
No new comments, decide if we close it
We decided to move this to a discussion, but first we need that functionality to be available for this repo
@Ludovic Robert to ask for it
Fall25 (already labeled)
issue 133 - Define guidelines for geofencing implementation
One new comment by @Ludovic Robert . He will complete the proposal with both cases
Rest of contributors, please review
Backlog (from previous meeting)
https://github.com/camaraproject/DeviceLocation/issues/308
Discuss if we should reconsider the responses for Location retrieval and align them with Location verification (4xx vs 2xx for unknown location)
To be further commented, @Ludovic Robert will take a look
Discuss data minimization for geofencing event
Aligned with r2.2 but more future discussion on the topic is expected, so we keep the issue open
Potentially in scope for next meta in Commonalities, should be discussed there
No change for now, letโs double check
[Geofencing] Support for polygon area type
Ilya to continue working on the proposal
Keep open and decide if itโs in scope for Fall25
No update
AOB
Be aware that next meeting will be at daylight saving time, but meeting time is still at 8:00 UTC (so it will be 10:00 CEST)