[Onboarding Tracker] DeviceVisitLocation

[albertoramosmonagas]

API Repository Information

• API Repository Name: DeviceVisitLocation
• Sub Project (or "Independent"): Independent sandbox
• Mailing List: sp-location-insights@lists.camaraproject.org
• Repository: https://github.com/camaraproject/DeviceVisitLocation
• Wiki Page: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/159907841/DeviceVisitLocation
• API Owner: @camaraproject/device-visit-location_codeowners
• API Proposal: https://github.com/camaraproject/APIBacklog/blob/main/documentation/API%20proposals/APIproposal_DeviceVisitLocation_ChinaUnicom.md
• Original Approval Issue: Urgent decision: timing for split of LocationInsights repository - NOW or later MostFrequentLocation#28 (comment)

---

Onboarding Action Checklist

• Nominate initial code owner(s) (at least one required, by API owner)
• Update APIBacklog.md with status: Onboarding
• Request wiki page and mailing list (email: support@camaraproject.org, clearly state what is needed)
• Confirm mailing list creation (only if Independent Sandbox) (LF Admin)
• Confirm wiki page creation (LF Admin)
• API Repository created (LF Admin via automation)
• Add repository link to API wiki page (LF Admin)
• Update README.md in repo with API details (API owner)
• File issue to update CAMARA website and slide deck (in Marketing repo)
• Update APIBacklog.md with status: Onboarded
• (Optional) Nominate initial maintainers (API owner)
• (Optional) Update Maintainers.md with PR

---

Notifications:
CC: @camaraproject/admins @camaraproject/api-backlog_maintainers @camaraproject/marketing_maintainers

[albertoramosmonagas]

Hi @camaraproject/location-insights_codeowners ,

Could the code owners please confirm whether you would like to maintain your participation in the DeviceVisitLocation repo?

As the splitting will be done within the same group, by default the same code owners and maintainers will be assigned to both repositories.

Please let us know if you prefer any adjustments or if you’d like to revisit the assignments.

[hdamker]

As the splitting will be done within the same group, by default the same code owners and maintainers will be assigned to both repositories.

I will take for now the same team, changes can be done via PRs within the new repository afterwards.

[hdamker]

Repository created: https://github.com/camaraproject/DeviceVisitLocation and mail to support@camaraproject.org send to create the new Repository wiki page.

Kept mailing list, meetings and meeting minutes from LocationInsights for now, but notably there are no meeting minutes for 2025 yet.

@chinaunicomyangfan please see camaraproject/DeviceVisitLocation#2 for the first task within the new repository. Please recreate camaraproject/MostFrequentLocation#22 there.

[albertoramosmonagas]

Hello @camaraproject/device-visit-location_codeowners ,

As part of our effort to keep the onboarding backlog up to date, we’re reviewing trackers that appear inactive but still show open items.

This tracker currently has pending tasks. To move forward efficiently, could you please confirm:

• Whether these tasks are still in progress and expected to be completed soon, or
• If the tracker is outdated and can be archived accordingly.

If there are any blockers or if support is needed to finalize the remaining steps, we’re happy to assist.

Remaining items identified:

• Add repository link to API wiki page (LF Admin)
• Update README.md in repo with API details (API owner)
• File issue to update CAMARA website and slide deck (in Marketing repo)
• (Optional) Nominate initial maintainers (API owner)
• (Optional) Update Maintainers.md with PR

We aim to finalize this cleanup during the current week. Your input would be appreciated to determine the next steps.

Best regards,

[hdamker]

• Add repository link to API wiki page (LF Admin)

That was done some time ago, have updated the checklist(s).
B

• File issue to update CAMARA website and slide deck (in Marketing repo)

Seems we have no clear definition who should do that. My proposal would be that this is created by the API Backlog group as soon the new repository is in good enough shape?

[albertoramosmonagas]

• Add repository link to API wiki page (LF Admin)

That was done some time ago, have updated the checklist(s). B

• File issue to update CAMARA website and slide deck (in Marketing repo)

Seems we have no clear definition who should do that. My proposal would be that this is created by the API Backlog group as soon the new repository is in good enough shape?

Normally, from this point on, the process is for the group or API owner to create the API description in the wiki, in this case DeviceVisitLocation, following the template, and then go to the Marketing group themselves.

In this case, since it is a split of the API that already existed, it would simply be a matter of changing the group, the repository to which it belongs, and the release version and dates, but as you said in previous messages, we can do this at the end of fall25, but just to keep it in mind.

But I am interested in the rest of the points from the group moving forward or having confirmation so that we don't have issues open for so long that they get lost in time @camaraproject/device-visit-location_codeowners