You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Richard Bywater <ri...@xtra.co.nz> on 2004/10/07 01:17:39 UTC
Seperate Lists for Wiki & Commits?
Hi,
Just wondering if there has been any consideration to creating new lists to use for Wiki & Commit updates? (Or maybe just one "update" list)
I know that I can filter these out in the email client but was thinking it might be useful to be able to only receive discussions.
Apologies if this has been discussed before...
Richard.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Seperate Lists for Wiki & Commits?
Posted by Vic Cekvenich <ce...@portalvu.com>.
Yeah, like on the announce list :-_
Richard Bywater wrote:
> Hi,
>
> Just wondering if there has been any consideration to creating new lists to use for Wiki & Commit updates? (Or maybe just one "update" list)
>
> I know that I can filter these out in the email client but was thinking it might be useful to be able to only receive discussions.
>
> Apologies if this has been discussed before...
>
> Richard.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Separate Lists for Wiki & Commits?
Posted by Richard Bywater <ri...@xtra.co.nz>.
Hi Martin,
You make a good point - although I'd probably prefer a digest version of
those kinds of events...
However having said that I didn't mean it to turn into a controversial
issue and was really just making an enquiry. So from my point of view
the issue is now dead and I yield to the more "senior" of you (as I
didn't have a strong view either way).
Richard.
PS When I say senior I mean in terms of Struts work not age :)
Martin Cooper wrote:
>It would seem odd to me that people interested in the development of
>the Struts project would not be interested in seeing what changes are
>being made to the code or to the documentation on the wiki. Without
>tracking those, they would not really be in a position to discuss what
>needs to be done, since they would be missing the current status of
>what *is* being done.
>
>I am also against splitting the list, based on the above and on the
>increased overhead of having multiple lists requiring maintenance and
>moderation.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Separate Lists for Wiki & Commits?
Posted by Martin Cooper <mf...@gmail.com>.
On Wed, 06 Oct 2004 19:45:17 -0400, Mike Kienenberger
<mk...@alaska.net> wrote:
> Richard Bywater <ri...@xtra.co.nz> wrote:
> > Hi,
> >
> > Just wondering if there has been any consideration to creating new lists
> to use for Wiki & Commit updates? (Or maybe just one "update" list)
> >
> > I know that I can filter these out in the email client but was thinking it
> might be useful to be able to only receive discussions.
>
> It's a bit more work to maintain, but it'd really be nice to have
>
> dev-commit -- commit messages
> dev-wiki -- wiki messages
> dev-talk -- discussion
> dev -- all of the above
>
> That maintains "backward compatibility," yet also lets those of us who
> really don't care about the wiki and commit pages to drop them by moving to
> dev-talk.
It would seem odd to me that people interested in the development of
the Struts project would not be interested in seeing what changes are
being made to the code or to the documentation on the wiki. Without
tracking those, they would not really be in a position to discuss what
needs to be done, since they would be missing the current status of
what *is* being done.
I am also against splitting the list, based on the above and on the
increased overhead of having multiple lists requiring maintenance and
moderation.
--
Martin Cooper
>
> -Mike (who's finally reduced his active mailbox down to a mere 539 messages)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Seperate Lists for Wiki & Commits?
Posted by David Graham <gr...@yahoo.com>.
This has been discussed before. I am strongly -1 on creating new lists.
It's every committer's responsibility to monitor as many commits as they
can. Having a separate list encourages people to ignore commit messages.
Email filters completely solve this issue without the overhead and
confusion of additional lists.
David
--- Richard Bywater <ri...@xtra.co.nz> wrote:
> Hi,
>
> Just wondering if there has been any consideration to creating new lists
> to use for Wiki & Commit updates? (Or maybe just one "update" list)
>
> I know that I can filter these out in the email client but was thinking
> it might be useful to be able to only receive discussions.
>
> Apologies if this has been discussed before...
>
> Richard.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Separate Lists for Wiki & Commits?
Posted by Mike Stanley <ms...@mstanley.net>.
-1 - use filters. (but my vote is just opinion and has no real weight)
- Mike
On Wed, 2004-10-06 at 23:52, James Mitchell wrote:
> I am also -1 on this. Why should I have to subscribe to so many lists?
>
>
>
> --
> James Mitchell
> Software Engineer / Open Source Evangelist
> EdgeTech, Inc.
> 678.910.8017
> AIM: jmitchtx
>
> ----- Original Message -----
> From: "Mike Kienenberger" <mk...@alaska.net>
> To: "Struts Developers List" <de...@struts.apache.org>
> Sent: Wednesday, October 06, 2004 7:45 PM
> Subject: Re: Separate Lists for Wiki & Commits?
>
>
> > Richard Bywater <ri...@xtra.co.nz> wrote:
> > > Hi,
> > >
> > > Just wondering if there has been any consideration to creating new lists
> > to use for Wiki & Commit updates? (Or maybe just one "update" list)
> > >
> > > I know that I can filter these out in the email client but was thinking
> it
> > might be useful to be able to only receive discussions.
> >
> > It's a bit more work to maintain, but it'd really be nice to have
> >
> > dev-commit -- commit messages
> > dev-wiki -- wiki messages
> > dev-talk -- discussion
> > dev -- all of the above
> >
> > That maintains "backward compatibility," yet also lets those of us who
> > really don't care about the wiki and commit pages to drop them by moving
> to
> > dev-talk.
> >
> > -Mike (who's finally reduced his active mailbox down to a mere 539
> messages)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
Re: Separate Lists for Wiki & Commits?
Posted by Paul Speed <ps...@progeeks.com>.
Mike Kienenberger wrote:
>
> <more sarcasm>
> Otherwise, why not combine the struts-dev and and struts-user lists? After
> all, email filters can eliminate whichever list you don't want to
> receive..... In fact, we can just have all apache mailing lists go to one
> address....
> </more sarcasm>
>
> -Mike
Come one... surely filtering out auto-generated messages with a nice
easy to filter subject is easier than filtering out the random "How do I
do X?" messages. :) Maybe not comparing apples to oranges but
certainly comparing red apples to green ones. Even for sarcasm it's a
stretch. ;)
-Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Separate Lists for Wiki & Commits?
Posted by Ted Husted <hu...@apache.org>.
On Thu, 07 Oct 2004 00:36:38 -0400, Mike Kienenberger wrote:
>�Most of the people on this list aren't committers. �What's wrong
>�with giving the rest of us a choice if it costs you nothing?
I doubt that an automated solution is going to help much. If sublists posted to a master list, then replying is problematic. Cross-posting is a *huge* problem with project-management mailing lists and more lists breed more cross-posts.
One thing that might help would be to make better use of the existing Struts-Announce mailing list. When something worthwhile happens, someone could post a mention there. It's a moderated list, so any replies would have to go to @user or @dev. (Or some other forum that someone might want to setup with another host.)
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Separate Lists for Wiki & Commits?
Posted by Mike Kienenberger <mk...@alaska.net>.
James Mitchell <jm...@apache.org> wrote:
> I am also -1 on this. Why should I have to subscribe to so many lists?
Well, that's the beauty. You don't. You still subscribe to the
dev@struts.apache.org mailing list which is a superset of the rest.
Transparent change to you. The only difference is that when you send a
message to the dev@struts.apache.org address, it's rerouted to dev-talk.
When a message arrives at dev-talk, dev-commit, or dev-wiki, it's also sent
to anyone on the dev mailing list.
David Graham <gr...@yahoo.com> wrote:
> This has been discussed before. I am strongly -1 on creating new lists.
> It's every committer's responsibility to monitor as many commits as they
> can. Having a separate list encourages people to ignore commit messages.
Most of the people on this list aren't committers. What's wrong with giving
the rest of us a choice if it costs you nothing?
The Struts project is free to maintain a policy that committers must be
subscribed to dev.
> Email filters completely solve this issue without the overhead and
> confusion of additional lists.
<sarcasm>
The same could be said of spam, but I'd rather opt-in for mailings rather
than opt-out after they arrive at my computer.
</sarcasm>
There's no overhead once it's set up.
<more sarcasm>
Otherwise, why not combine the struts-dev and and struts-user lists? After
all, email filters can eliminate whichever list you don't want to
receive..... In fact, we can just have all apache mailing lists go to one
address....
</more sarcasm>
-Mike
> ----- Original Message -----
> From: "Mike Kienenberger" <mk...@alaska.net>
> To: "Struts Developers List" <de...@struts.apache.org>
> Sent: Wednesday, October 06, 2004 7:45 PM
> Subject: Re: Separate Lists for Wiki & Commits?
>
>
> > Richard Bywater <ri...@xtra.co.nz> wrote:
> > > Hi,
> > >
> > > Just wondering if there has been any consideration to creating new
lists
> > to use for Wiki & Commit updates? (Or maybe just one "update" list)
> > >
> > > I know that I can filter these out in the email client but was
thinking
> it
> > might be useful to be able to only receive discussions.
> >
> > It's a bit more work to maintain, but it'd really be nice to have
> >
> > dev-commit -- commit messages
> > dev-wiki -- wiki messages
> > dev-talk -- discussion
> > dev -- all of the above
> >
> > That maintains "backward compatibility," yet also lets those of us who
> > really don't care about the wiki and commit pages to drop them by moving
> to
> > dev-talk.
> >
> > -Mike (who's finally reduced his active mailbox down to a mere 539
> messages)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Separate Lists for Wiki & Commits?
Posted by James Mitchell <jm...@apache.org>.
I am also -1 on this. Why should I have to subscribe to so many lists?
--
James Mitchell
Software Engineer / Open Source Evangelist
EdgeTech, Inc.
678.910.8017
AIM: jmitchtx
----- Original Message -----
From: "Mike Kienenberger" <mk...@alaska.net>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Wednesday, October 06, 2004 7:45 PM
Subject: Re: Separate Lists for Wiki & Commits?
> Richard Bywater <ri...@xtra.co.nz> wrote:
> > Hi,
> >
> > Just wondering if there has been any consideration to creating new lists
> to use for Wiki & Commit updates? (Or maybe just one "update" list)
> >
> > I know that I can filter these out in the email client but was thinking
it
> might be useful to be able to only receive discussions.
>
> It's a bit more work to maintain, but it'd really be nice to have
>
> dev-commit -- commit messages
> dev-wiki -- wiki messages
> dev-talk -- discussion
> dev -- all of the above
>
> That maintains "backward compatibility," yet also lets those of us who
> really don't care about the wiki and commit pages to drop them by moving
to
> dev-talk.
>
> -Mike (who's finally reduced his active mailbox down to a mere 539
messages)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Separate Lists for Wiki & Commits?
Posted by Mike Kienenberger <mk...@alaska.net>.
Richard Bywater <ri...@xtra.co.nz> wrote:
> Hi,
>
> Just wondering if there has been any consideration to creating new lists
to use for Wiki & Commit updates? (Or maybe just one "update" list)
>
> I know that I can filter these out in the email client but was thinking it
might be useful to be able to only receive discussions.
It's a bit more work to maintain, but it'd really be nice to have
dev-commit -- commit messages
dev-wiki -- wiki messages
dev-talk -- discussion
dev -- all of the above
That maintains "backward compatibility," yet also lets those of us who
really don't care about the wiki and commit pages to drop them by moving to
dev-talk.
-Mike (who's finally reduced his active mailbox down to a mere 539 messages)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org