You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by sebb <se...@gmail.com> on 2008/06/20 15:46:12 UTC
Gump nags
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.
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
Re: Gump nags
Posted by sebb <se...@gmail.com>.
On 20/06/2008, Rahul Akolkar <ra...@gmail.com> wrote:
> On 6/20/08, sebb <se...@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.
> >
> > I think we should just use:
> >
> > Gump <general AT gump.apache.org>
> >
> > for them all.
> >
>
> <snip/>
>
> Makes sense to me. Or even:
>
> Gump <issues AT commons.a.o>
>
> so any replies to sender are noticed on our lists.
Good idea; I'll set that up.
>
> -Rahul
>
>
>
> > 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
Re: Gump nags
Posted by Rahul Akolkar <ra...@gmail.com>.
On 6/20/08, sebb <se...@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.
>
> I think we should just use:
>
> Gump <general AT gump.apache.org>
>
> for them all.
>
<snip/>
Makes sense to me. Or even:
Gump <issues AT commons.a.o>
so any replies to sender are noticed on our lists.
-Rahul
> 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
Re: Gump nags
Posted by sebb <se...@gmail.com>.
On 20/06/2008, Martin Cooper <ma...@apache.org> wrote:
> On Fri, Jun 20, 2008 at 6:46 AM, sebb <se...@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.
Good point.
> 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, for Commons that's not all that important.
Also, the from addresses have not been updated as far as I can tell;
some senders are not now particularly active (if at all) in Commons.
>
> --
>
> 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
Re: Gump nags
Posted by Bill Barker <wb...@wilshire.com>.
"Martin Cooper" <ma...@apache.org> wrote in message
news:16d6c6200806201349o55017254hba50462a0c980603@mail.gmail.com...
> On Fri, Jun 20, 2008 at 6:46 AM, sebb <se...@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
Re: Gump nags
Posted by Martin Cooper <ma...@apache.org>.
On Fri, Jun 20, 2008 at 6:46 AM, sebb <se...@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.
--
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
>
>