I have a technical question regarding apps whose name change over the course of their life, or where the community transitions to a fork.
We have a current case with the ZeroBin app (official): It’s been migrated from the original ZeroBin app to the PrivateBin fork. The PrivateBin fork has been designed to stay backward compatible with ZeroBin.
So now we have a YunoHost ZeroBin package, which name is Zerobin (
name field in the manifest), and id is zerobin.
What’s the best procedure to handle a smooth upgrade of current Zerobin instances?
Right now there’s a PR to just upgrade ZeroBin YunoHost package to install latest PrivateBin version. That should make the deal, but we’re still advertising ZeroBin as our official app…
Is there an existing or planned system to rename apps id and still keep track of which app needs to be upgraded?
Otherwise, what would be the best behavior here:
- keep ZeroBin name everywhere (except in the README) as in the PR
- change ZeroBin package name to PrivateBin, and keep the “zerobin” id
- create a new PasteBin app, and remove ZeroBin app from official repository (and move it to the community repository…?). But then, how to have users make the switch to PrivateBin (exept writing about it here on the forum and on the official doc)?
Any information/suggestion will help