Urgent decision: timing for split of LocationInsights repository - NOW or later

[hdamker]

Problem description

@camaraproject/location-insights_codeowners @camaraproject/location-insights_maintainers Please consider my proposal which I made within the open PR for device-visit-location. There are three options:

1. Do the split of the repository now asap => clean M3 release for most-frequent-location and a chance for device-visit-location to get into Fall25 (or at least doing an initial release soon)
2. Try to get device-visit-location also ready as release candidate for Fall25 within the repository within few days => high risk for both most-frequent-location and device-visit-location to be NOT part of Fall25, as device-visit-location isn't near to complete (even after the current M3 milestone deadline).
3. Don't merge anything for device-visit-location now, create the M3 release just for most-frequent-location and do the split after M3

My proposal will be in any of the above options to split the repository LocationInsights. These are the steps (subject to approval by APIBacklog or TSC):

• Create issue in API Backlog for short-term approval to split the repository LocationInsights in the following way:

  • Create a new Sandbox API Repository for "DeviceVisitLocation" asap
  • Renaming the existing repository "LocationInsights" into "MostFrequentLocation"
  • Both repositories will keep same Codeowners and mailing list, meeting as before
  • The name "Location Insights" will be reserved to a future Sub Project including the two repositories and potential others (as soon as one of the Sandbox repositories get Incubating status)

• As soon as the repository is created, re-create the pull request DeviceVisitLocation initial version yaml [don't merge, see comment] #22 within the new repository DeviceVisitLocation. There are several options:

  • Work will catch-up and deliver the prerequisites for Fall25 very soon -> we can consider it for Fall25
  • The Sandbox repository will have an initial release independent of the meta-release (that can happen at any time, also before Fall25)
  • The team decides to target Spring25 for device-visit-location (potentially with the second initial release)

With the approach above the repository can progress to a proper M3 release for most-frequent-location, as long there is nothing merged for device-visit-location.

Originally posted by @hdamker in #22 (review)

Expected action

• Take a decision about the way forward
• Create an issue to split LocationInsights, together with a plan about the timing (urgently now, after M3, ...)

Additional context

#22 shall be merged only if there is a plan how to ensure a proper M3 release for the LocationInsights.

[hdamker]

cc: @jgarciahospital @albertoramosmonagas

[albertoramosmonagas]

Hi @hdamker ,

Thanks a lot for laying this out so clearly. We’ve created two onboarding trackers as a first step:

• #238 – DeviceVisitLocation
• #237 – MostFrequentLocation (current LocationInsights)

Following your proposal, the next step would be to create a subproject to host both repositories and move them from Independent to Subproject status. We can then proceed with:

• Renaming the current LocationInsights repository to MostFrequentLocation.
• Creating the new sandbox repository for DeviceVisitLocation.
• Re-creating the PR for DeviceVisitLocation in the new repo once it’s set up.

[hdamker]

Following your proposal, the next step would be to create a subproject to host both repositories and move them from Independent to Subproject status.

Creating the Sub Project is a future thing. Prerequisite is that one of the repositories is ready to get an Incubating API Repository, so not relevant of now. For now both Sandbox API Repositories will have the status "independent". They can decide to work together in a group, sharing the mailing list and minutes (as today the repositories of Connectivity Insights).

[hdamker]

Repository https://github.com/camaraproject/DeviceVisitLocation is already created, the PR #22 can be moved there.

[hdamker]

For renaming of LocationInsights -> MostFrequentLocation see the discussion in camaraproject/APIBacklog#237 ... we can do it either now or postpone to after the M3 release.

[fernandopradocabrillo]

Hi @FabrizioMoggio @chinaunicomyangfan please, take a look at Herbert's proposal to split the repo so each API has its own life cycle and meta releases process.

Thank you!

[FabrizioMoggio]

Hi @FabrizioMoggio @chinaunicomyangfan please, take a look at Herbert's proposal to split the repo so each API has its own life cycle and meta releases process.

Thank you!

I'm not following this release of the API so the decision is up to @chinaunicomyangfan. Anyway, the split is the best way forward in my opinion but this is just a very personal opinion not taking into account the status of the work.

[chinaunicomyangfan]

Spliting the repo is a good idea,I totally agree.
Thanks for @hdamker 's proposal and work.