On 8/29/26 08:13, Simon Josefsson wrote:
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?
my issue is not with the team, but me having a workflow which is not involving salsa, and uses git with different debian packaging standards.
therefore my initial proposition in the bug: either I take over the blocking package, or I'm handing over the two blocked packages provided all three of them are actively kept up2date (as they are depends of other packages that need it current). if neither of these two options are possible, then for me NMU'ing is the best.
There are literally thousands of Debian Go Team packages maintained as "badly" as these ones. And hundreds of them significantly much worse!
can be, but this package here is the one that blocks me, not the others.
IMHO, we need LESS barriers for making effective contributions.
ack. Regards, Daniel
