Daniel Baumann <[email protected]> writes: > On 8/28/26 22:13, Simon Josefsson wrote: >> It sounds like you would be a good (co)-maintainer/uploader of them? > > We're going in circles. To summarize, I understand that the Go team > isn't maintaining this concrete package as active as I would like it > to be (and doesn't want to take over the other two), and I don't want > to join the Go team at this point. So I will continue the bug+NMU way > for the time being.
Whatever works best for you and the packages -- although there is no rule that says you have to be a Go team member to be in the uploaders field and prepare uploads of packages without the NMU-process, is there? There are literally thousands of Debian Go Team packages maintained as "badly" as these ones. And hundreds of them significantly much worse! I'm not sure what if anything can be done about this, beyond having people effectively doing QA uploads of unrelated go packages when they need to for some other dependency (like you do here). And letting go of zombie packages which has no use and eat up our precious QA time. IMHO, we need LESS barriers for making effective contributions. Barriers create frustration, like you showed here. I think that probably everyone working on Go packages in Debian shares the same frustration about poorly maintained Debian Go packages. /Simon
signature.asc
Description: PGP signature
