commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: Gump nags
Date Sun, 22 Jun 2008 00:58:30 GMT

"Martin Cooper" <> wrote in message
> On Fri, Jun 20, 2008 at 6:46 AM, sebb <> 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>
>> 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:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message