[Pkg-privacy-maintainers] Migration to Salsa

[Daniel Kahn Gillmor]

On Thu 2018-04-05 13:53:00 +0000, u wrote:
> Daniel Kahn Gillmor:
>> On Wed 2018-03-28 17:21:00 +0000, u wrote:
>>> u:
>> are you aware of https://salsa.debian.org/salsa/AliothRewriter.git ?  if
>> you give them a pull request it'll make the old alioth URLs explicitly
>> do an HTTP redirection to salsa.  I usually make edits to
>> definitions/general.conf, though if you want you could probably create
>> definitions/privacy-team.conf separately if you like.  I'm sure either
>> way would make sense.
>
> I created such a file and submitted a pull request today.
>
> FYI the README reads:
>
> The existance of this list should not mean that VCS control fields
> shouldn't get updated with the next upload. This map is just a
> workaround - after your upload please create another pull request that
> deletes the unneeded entries.
>
> So let's make sure, we delete entries that have updated salsa fields
> afterwards.

hm, I'm not convinced that this README makes sense.  I agree that the
VCS control fields should be updated, but i'm not convinced that we
should remove the unneeded entries.

In particular, if i'm working in a debian "stable" environment, and i do
"debcheckout", it's going to pull from the Vcs fields listed in the
debian sources for the "stable" distro. Those are likely to point to
alioth still.

I don't intend for Alioth to continue to host source repos, and i *want*
the redirection to last as long as anyone might try to visit the Alioth
repositories.

In some future world, where all packages have transitioned to salsa, and
we've stoppoed supporting any version of debian that still includes any
alioth Vcs-* fields, maybe we can remove entries from
AliothRewriter.git.  but in that world, we can just remove
AliothRewriter (and the Alioth git server itself?)  anyway.

so i wouldn't bother with those removals, personally.  keep the
redirections in place!

               --dkg