[pkg-go] Fwd: golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.changes ACCEPTED into unstable

Martín Ferrari tincho at debian.org
Sat Jan 6 01:40:36 UTC 2018


On 04/01/18 19:31, Alexandre Viau wrote:

> KGB will be very easy to rewrite for the gitlab API.

I have started working on that.

> I am sure we can also adapt PET. In the meantime, maybe just use the QA
> page?
>  -
> https://qa.debian.org/developer.php?login=pkg-go-maintainers@lists.alioth.debian.org

PET will take a lot of effort to migrate, if that ever happens.

> If you don't want to maintain the anonscm links, Alexander Wirt is
> working on a solution and you will still be able to use anonscm links:
>  - https://salsa.debian.org/salsa/AliothRewriter

But now we are introducing inconsistencies in the group packages, while
there was no need to change the links if we have waited.

> However I think maintaining this map and a link will be even more
> complicated.

But that means re-uploading every one of our 891 packages.

>> Honestly, it feels very demotivating that you did this change :(
> 
> You don't have to switch your packages now if you don't want to spend
> the time. I am sure Alioth will remain usable for a while. You can do it
> as you upload them, there is no rush.
> 
> You can also automate it.
> 
> For my packages, I automated the repository creation on salsa and the
> removal from Alioth.

Well, this is part of the problem. These are not "your packages" or "my
packages". We have a team where we decided that mainteinance is
collaborative and that nobody owns the packages.

What you are saying here goes against all that, and reverses efforts put
into making pkg-go collaborative and welcoming.

To make this more evident, I noticed this happened because I wanted to
work on a package that you moved. That package is a dependency of
prometheus, so I *need* to keep it healthy in order to ship prometheus
in Debian. If you look at the changelog of raft, you will see that the
last two uploads were done by me.

-- 
Martín Ferrari (Tincho)



More information about the Pkg-go-maintainers mailing list