Return-Path: 
 <dev-return-110467-apmail-commons-dev-archive=commons.apache.org@commons.apache.org>
Delivered-To: apmail-commons-dev-archive@www.apache.org
Received: (qmail 82047 invoked from network); 22 Jun 2008 00:58:57 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 22 Jun 2008 00:58:57 -0000
Received: (qmail 22397 invoked by uid 500); 22 Jun 2008 00:58:57 -0000
Delivered-To: apmail-commons-dev-archive@commons.apache.org
Received: (qmail 22302 invoked by uid 500); 22 Jun 2008 00:58:57 -0000
Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@commons.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@commons.apache.org>
List-Post: <mailto:dev@commons.apache.org>
List-Id: <dev.commons.apache.org>
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Delivered-To: mailing list dev@commons.apache.org
Received: (qmail 22291 invoked by uid 99); 22 Jun 2008 00:58:57 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Jun 2008 17:58:57 -0700
X-ASF-Spam-Status: No, hits=-1.0 required=10.0
	tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of jak-commons-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jun 2008 00:58:06 +0000
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1KADuS-0004va-TK
	for dev@commons.apache.org; Sun, 22 Jun 2008 00:58:24 +0000
Received: from pool-71-104-92-48.lsanca.dsl-w.verizon.net ([71.104.92.48])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <dev@commons.apache.org>; Sun, 22 Jun 2008 00:58:24 +0000
Received: from wbarker by pool-71-104-92-48.lsanca.dsl-w.verizon.net with
 local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <dev@commons.apache.org>; Sun, 22 Jun 2008 00:58:24 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: dev@commons.apache.org
From: "Bill Barker" <wbarker@wilshire.com>
Subject: Re: Gump nags
Date: Sat, 21 Jun 2008 17:58:30 -0700
Lines: 54
Message-ID: <g3k837$2tr$1@ger.gmane.org>
References: <25aac9fc0806200646o638285a0t7aa604ea1a59afe0@mail.gmail.com>
 <16d6c6200806201349o55017254hba50462a0c980603@mail.gmail.com>
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: pool-71-104-92-48.lsanca.dsl-w.verizon.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Original
Sender: news <news@ger.gmane.org>
X-Virus-Checked: Checked by ClamAV on apache.org


"Martin Cooper" <martinc@apache.org> wrote in message 
news:16d6c6200806201349o55017254hba50462a0c980603@mail.gmail.com...
> On Fri, Jun 20, 2008 at 6:46 AM, sebb <sebbaz@gmail.com> wrote:
>
>> The Gump nag messages are currently sent from lots of different mail
>> addresses, all of which have to be subscribed (or allowed to post) to
>> the dev list.
>
>
> IIRC (not a sure thing ;) it was set up this way so that the Gump team 
> knows
> who to nag when something breaks and doesn't get fixed. These days, I seem
> to only see Gump nags when the whole lot fails for some reason, so I'm not
> sure how useful having the individual names is any more.
>

Yes.  The meta-data part of Gump can be edited by any ASF committer.  The 
latest round of failures was caused by a committer from xml-commons adding a 
project.  However, since there was a typo that made the xml not well-formed, 
this caused the entire file to not be parsed.  This caused xml-apis to not 
be recogonized, which pretty much hosed all ant-based projects.  Since most 
commons projects still mostly use their ant build for Gump, this resulted in 
the massive spam.

> --
> Martin Cooper
>
>
>> I think we should just use:
>>
>> Gump <general AT  gump.apache.org>
>>
>> for them all.
>>
>> This would avoid any problems if the real person from whom the mail is
>> supposed to come decides to unsubscribe from the list.
>>
>> Any reasons to keep the (historical) from settings?
>>
>> All the nags are sent to the dev address.
>> [If some nags were to be sent to outside addresses, then a specific
>> from address might be necessary]
>>
>> S///
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org