How do we ensure that people are redirect from alioth to salsa? I think
some redirection support is underway or already working, so it would be
good to set up these redirects.
Redirects only cover the web interface part, so what do we do with the old
git repositories? Could we mark them read-only, to prevent accidental
pushes to the wrong repository?
On Tue, Jan 16, 2018 at 8:54 AM, Michael Stapelberg <stapelb...@debian.org>
> Last I heard, there was still a chance that salsa would be reset in its
> ganneff, is this still the latest, or will salsa definitely keep its data?
> On Thu, Dec 28, 2017 at 11:36 PM, Alexandre Viau <av...@debian.org> wrote:
>> Hello Team,
>> Alioth will be deprecated. We have to move to salsa.debian.org.
>> I have created a pkg-go team:
>> - https://salsa.debian.org/pkg-go-team
>> You may request to join and I will add you as owners.
>> I suggest we move pacakges manually, one by one, as we upload them.
>> There is no rush because Alioth will remain accessible read-only.
>> I will move my own packages as I go, and remove them from git.debian.org
>> at the same time to avoid confusion.
>> I'll also spend some time with dh-make-golang and see if there is an
>> easy way to automatically create projects using the gitlab api...
>> Alexandre Viau
>> Pkg-go-maintainers mailing list
> Best regards,
Pkg-go-maintainers mailing list