commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell" <flame...@gmail.com>
Subject Re: [all] Splitting the mailing list
Date Sun, 23 Jul 2006 04:53:10 GMT
On 7/22/06, Henri Yandell <flamefew@gmail.com> wrote:
> On 7/22/06, Stephen Colebourne <scolebourne@btopenworld.com> wrote:
> > The proposal suggests two new lists, but I'd argue thats unecessary. One
> > for svn, jira, wiki and gump is all thats needed. Basically everythng
> > that is non-discussion and *might* be regarded as 'spam'.
> >
> > So, +1 to one new list, commons-auto? commons-build?, commons-gen?
> >
> > Or perhaps this should be a jakarta-wide list if we are one-jakarta ;-)
>
> I'm not tied to multiple lists - so one list is fine by me.

I had a thought just now on the multiple list concept - and a positive
reason for splitting the lists in general. By having lists for
commits, jira, wiki, ci etc filters become a lot, lot easier. Much
easier for someone to come up with a list of commits they're
interested in and we can have people who are interested in their own
defined groupings while having to still see the general dev
discussions as they come through.

A far more predictable version of the [xxx] convention without the
risk that you'd miss the Re: svn commit emails.

The reason this occurred to me was that I pondered the 'mad'
suggestion of having dev@jakarta and thinking that it might not be as
mad as it sounds :)

Hen

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


Mime
View raw message