From: Alan Mackenzie <acm@muc.de>
To: Glenn Morris <rgm@gnu.org>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>,
Don Armstrong <don@donarmstrong.com>,
emacs-devel@gnu.org
Subject: Re: Spammers are now closing bugs
Date: Tue, 21 Apr 2009 07:27:56 +0000 [thread overview]
Message-ID: <20090421072756.GB1082@muc.de> (raw)
In-Reply-To: <jzr5zn9ok2.fsf@fencepost.gnu.org>
Hi, Glenn,
On Mon, Apr 20, 2009 at 02:18:21PM -0400, Glenn Morris wrote:
> Stefan Monnier wrote:
> > The incoming messages should be filtered the same way that messages to
> > emacs-devel get filtered (i.e. they need to be moderated).
> The moderation must already be being done, but at the wrong point.
> gnu-emacs-bug is moderated (many thanks to those who do so), and
> almost no spam gets through to the list. All the spam that gets sent
> to the bug tracker gets passed on to the bug list, but does not appear
> there, so people must be moderating it out. But at this stage, it's
> already entered the tracker.
> The moderation step should be shifted to be _before_ things reach the
> tracker, rather than after. (Though this found no favour the last time
> I suggested it;
> http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00889.html)
I missed that thread last August. The argument (from Eli) was that
having the bug-gnu-emacs moderators also moderate the bug tracker email
would be too much of a burden for them. As one of the bug-gnu-emacs
moderators, I don't believe this would be the case. To me, it is
scarcely more effort to moderate 10 messages than 1; indeed, finding only
1 message is an anti-climax, and finding none at all is a major let down.
;-). At least one of my colleagues on b-g-e is super efficient, since I
rarely see much on the moderation page.
So, yes, let's moderate the bug-tracker. How easy is this to set up?
What does Don say?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2009-04-21 7:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 19:20 Spammers are now closing bugs Glenn Morris
2009-04-19 19:28 ` Sven Joachim
2009-04-19 23:41 ` Jason Rumney
2009-04-20 10:48 ` Samuel Bronson
2009-04-20 14:27 ` Stefan Monnier
2009-04-20 18:18 ` Glenn Morris
2009-04-20 21:07 ` Stefan Monnier
2009-05-04 21:09 ` Glenn Morris
2009-05-05 3:55 ` Stephen J. Turnbull
2009-04-21 7:27 ` Alan Mackenzie [this message]
2009-04-21 17:16 ` Glenn Morris
2009-04-22 3:14 ` Stephen J. Turnbull
2009-04-22 17:07 ` Eli Zaretskii
2009-04-20 18:14 ` Glenn Morris
2009-04-20 18:30 ` Sven Joachim
2009-04-20 18:40 ` Glenn Morris
2009-04-21 3:13 ` Stephen J. Turnbull
2009-04-21 3:31 ` Glenn Morris
2009-04-21 5:47 ` Miles Bader
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=20090421072756.GB1082@muc.de \
--to=acm@muc.de \
--cc=don@donarmstrong.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=rgm@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).