Should we delete pkg-go-tools, provisioning, migrate-pkg-go-to-salsa etc?

[Otto Kekäläinen <otto@debian.org>]

Hi,

What is the current maintenance plan for these?

https://salsa.debian.org/go-team/infra/pkg-go-tools
https://salsa.debian.org/go-team/infra/provisioning
https://salsa.debian.org/go-team/migrate-pkg-go-to-salsa
https://salsa.debian.org/go-team/stapelbergtest

Should we plan to stop using them and gracefully deprecate them, mark
them archived or delete them?

I have not seen the CI job test_the_archive be useful in any of the
packages I worked on. I am not fully sure if I even understand what
the intent of that CI job, as it is doing only a source package build
and otherwise testing other packages than what actually triggered the
CI run.

See e.g. https://salsa.debian.org/go-team/packages/usql/-/jobs/7283517
failing on various go commands but job passes anyway:
    go: errors parsing go.mod:
    /builds/go-team/packages/usql/go.mod:5: unknown directive: toolchain

The only way to get the test_the_archive job to fail is to give inputs
that don't even produce a source package, e.g. vs
https://salsa.debian.org/go-team/packages/usql/-/jobs/7283480


I am sure these Go team infra pieces were useful 2-3 years ago, but
going forward, does it makes sense to spend energy on maintaining
these?