unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Don Armstrong <don@donarmstrong.com>
To: emacs-devel@gnu.org
Subject: Re: bug tracker spam
Date: Sun, 1 Jun 2008 10:48:45 -0700	[thread overview]
Message-ID: <20080601174845.GC10430@volo.donarmstrong.com> (raw)
In-Reply-To: <8a7ida45v3.fsf@fencepost.gnu.org>

On Sat, 31 May 2008, Glenn Morris wrote:
> Don Armstrong wrote:
> > Just mail me; I use rm. ;-)
> 
> It would be nice if getting rid of spam was something maintainers
> could do. Perhaps just tagging things as spam so that they appear in
> a separate section of the summary until they are fully removed.

Usually we use a cgi script so people can mark bugs that contain or
are spam, and an administrator manually removes them later. The reason
why this shouldn't be handled by maintainers is that it's the only
action that cannot be reverted in the bts. [I suppose that eventually
I'll have to come up with a method that scales better than the current
ones, but it's scaled to > 450,000 bugs in Debian, and there are a
bunch of things that need fixing which are higher on my priority
list.]

> more spam: #304, #340

Deleted.

> There are also things like #312, #313, #207 that seem to be mistakes.
> I don't know what to do about those.

Anything that's not clearly spam, I suggest to keep. [They'll
disappear from the main page as they get archived, so it won't be a
problem long-term.]

> Couple of other questions:
> 
> How do I close a report in such a way that it is marked "this is not
> a bug"? This isn't the same as "wontfix", IMO.

You just close it, explaining that it's not a bug and why in the -done
message. [A lot of the -done messages I've seen so far have been far
too terse to extract any useful information from; it makes it really
useful if a done message includes at least the commit message that
caused a bug to be fixed and the revision.]

If this happens a lot, we can add a notabug tag.

> How do you (or will you) control who is allowed to manipulate bug
> reports?

We don't, generally speaking, because controlling it doesn't scale. If
there's a problem, we can blacklist people. [I have all of about 5
entries in Debian's blacklist out of tens of thousands who have
modified bugs, so it's rarely a problem.]


Don Armstrong

-- 
After the first battle of Sto Lat, I formulated a policy which has
stood me in good stead in other battles. It is this: if an enemy has
an impregnable stronghold, see he stays there.
 -- Terry Pratchett _Jingo_ p265

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




  reply	other threads:[~2008-06-01 17:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29 23:26 bug tracker spam Glenn Morris
2008-05-29 23:51 ` Don Armstrong
2008-05-29 23:59   ` Glenn Morris
2008-05-30  0:30     ` Don Armstrong
2008-05-31 19:43       ` Glenn Morris
2008-06-01 17:48         ` Don Armstrong [this message]
2008-06-01 21:48         ` Stefan Monnier
2008-05-30  5:24 ` David Hansen
  -- strict thread matches above, loose matches on Subject: below --
2008-08-20 16:58 Glenn Morris
2008-08-20 18:57 ` Andreas Schwab
2008-08-20 20:11   ` Glenn Morris
2008-08-21  5:28     ` Eli Zaretskii
2008-08-21 16:02       ` Glenn Morris
2008-08-21 16:42         ` Eli Zaretskii
2008-08-21 17:22           ` Glenn Morris
2008-08-21 17:52             ` Glenn Morris
2008-08-21 19:18               ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080601174845.GC10430@volo.donarmstrong.com \
    --to=don@donarmstrong.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).