[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Do not use control@b.d.o for bug ping-pong



I normally wouldn't respond to -devel about this sort of thing, but
because this is the third time this week that someone has asked
owner@b.d.o to deal with this sort of issue, I am. Please followup to
-devel, not this bug or to owner@b.d.o if you disagree for some
reason.

On Mon, 11 Dec 2006, A. Costa wrote:
> I'm having a hard time keeping a minor but valid bug open in
> 'module-init-tools'.

Maintainers of packages are wholly responsible for determining the
state of bugs assigned to their package. The only exceptions to this
general rule are for bugs affecting the release, where RMs can alter
the states so that the bug affects or doesn't affect the release, and
cases where the tech ctte has overriden the maintainer.[1]

If you disagree with a setting that a maintainer has specifically set,
you should explain in an e-mail to the relevant bug that makes it
clear why the state should be changed. If the maintainer is not
convinced, then ask -devel for advice. If -devel agrees, and the
maintainer is still not convinced, your only choice is to appeal to
the tech ctte to override the maintainer. [If you're doing this, you
better have already written (or gotten someone else to write) the
patch to fix whatever bug you want reopened and fixed; otherwise the
ctte will likely close and ignore your bug report too.]

Maintainers, of course, should not capriciously close bugs or tag or
block them nonsensically, and should attempt to explain why they are
closing bugs or altering states wherever possible, but regardless of
whatever inequities the maintainer has committed, using the control
interface to argue with them will only result in your exclusion from
it.

[None of the above should discourage people from helping maintainers
out by reopening bugs when they appear to have been closed in error,
or tagging bugs to assist maintainers in classifying their bugs of
course. Just don't use control@b.d.o for bug ping-pong.]


Don Armstrong

1: There's also the "Don Armstrong reported it, so you damn well beter
fix it" exception. ;-)
-- 
Debian's not really about the users or the software at all. It's a
large flame-generating engine that the cabal uses to heat their coffee
 -- Andrew Suffield (#debian-devel Fri, 14 Feb 2003 14:34 -0500)

http://www.donarmstrong.com              http://rzlab.ucr.edu



Reply to: