From 34dfd63e87741541273a00fbe63eb099a1b4e08e Mon Sep 17 00:00:00 2001 From: Don Armstrong Date: Sat, 17 Jul 2010 02:02:54 +0000 Subject: [PATCH] * add debbugs reopen war --- templates/email/debbugs-reopenwar.txt | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 templates/email/debbugs-reopenwar.txt diff --git a/templates/email/debbugs-reopenwar.txt b/templates/email/debbugs-reopenwar.txt new file mode 100644 index 0000000..3c0c126 --- /dev/null +++ b/templates/email/debbugs-reopenwar.txt @@ -0,0 +1,25 @@ +If a maintainer closes a bug, and after a single round of explanation, +still does not agree with reopening the bug, the bug should stay +closed. + +If you disagree with the maintainer, then your choices are to either +attempt to: + +1) convince the maintainer that your viewpoint is correct, preferably +by submitting a patch which fixes the perceived problem, along with +rationale as to why the patch is correct. + +2) attempt to convince the technical committee that the maintainer is +incorrect, and should be overridden. This necessitates a patch as +required for #1. + +In neither case should you reopen bugs that a maintainer has +closed.[1] Continuing to do so will result in restricting your use of +control@bugs.debian.org. + + +Don Armstrong + +1: It is of course acceptable to reopen a bug in cases when the +maintainer is likely to agree with you, but that is clearly not the +case here. -- 2.39.2