Hi, > > While I personally think e-mail-based workflows can be quite nice, the > > BTS' asynchronous nature did cause me a lot of extra pointless work > > when I was an outsider attempting to learn the ropes. Being not 100% > > confident with the system, I way too often found myself waiting > > minutes – as much as 10 or 15 – for replies to simple operations. > > agree with this. Also the noisy reply to every message is pretty > unhelpful - even gmail cant work out what is being acknowledged > > > I'd like to help improve the docuemntation, and suggest ways to make it > less confusing to use, but the bts's own bug list makes me wonder if > anyone would review
I submitted 4 years ago https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/6, which got some approving comments, but nobody merged it. Your time is probably better used contributing to the Debian Developers Reference or other docs. Honestly, I suspect bugs.debian.org is intentionally cumbersome to use to deter "noobies", and raise the bar for submission so high, that any bug that actually gets filed is likely already well researched by a Debian expert and half of the time comes with a patch attached. Unfortunately it also leads to maintainers having to put more effort in maintaining the bug reports as the barrier for contributors to help out with bug triage etc way too high.
