Rub21 left a comment (openstreetmap/openstreetmap-website#7089)
> When we say "keep X and drop Y", what do we plan to do with the existing
> data? Would it be dropped from DB entirely, recategorised, something else?
Good question. A couple of ideas:
1. Legacy traces (Grant's idea, shared by Minh in a recent sync — hope I caught
it well): instead of deleting anything, the traces with the deprecated
visibility levels stay as "legacy" — kept in the database but not served by the
API, and ignored by new features (like the upcoming GPS tiles).
About this, I think it may complicate the code to keep legacy and the new
visibilities together, but it is something we can discuss further.
2. Grace period: give users 3 to 6 months to change the visibility of their
traces or delete them, with a notification by email or banner. After that
period, the remaining public and private traces would be migrated to trackable.
Nothing would be deleted from the database — only the visibility flag would
change, and the API would serve the points in a different way.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/7089#issuecomment-4478563504
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/7089/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
