On 7/24/06, Simon Kitching [EMAIL PROTECTED] wrote:
When there are 4 commons lists, how are people going to manage this?
Leave it to those, which are silly enough to use an autoreply for
mailing lists? After all, a little bit of education cannot hurt.
Jochen
--
Whenever you find yourself on
On Sat, 2006-07-22 at 21:53 -0700, Henri Yandell wrote:
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
On 7/24/06, Simon Kitching [EMAIL PROTECTED] wrote:
On Sat, 2006-07-22 at 21:53 -0700, Henri Yandell wrote:
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,
Simon Kitching wrote:
On Sat, 2006-07-22 at 21:53 -0700, Henri Yandell wrote:
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
On 24/07/06, Henri Yandell [EMAIL PROTECTED] wrote:
On 7/24/06, Simon Kitching [EMAIL PROTECTED] wrote:
On Sat, 2006-07-22 at 21:53 -0700, Henri Yandell wrote:
I had a thought just now on the multiple list concept - and a positive
reason for splitting the lists in general. By having lists
Simon Kitching wrote:
One problem is that of temporarily unsubscribing. We've all regularly
seen what happens when someone goes on holiday for a few weeks and sets
their email to auto-respond out of office without unsubscribing from
these lists first.
When there are 4 commons lists, how are
On 21/07/2006 2:08 PM, Simon Kitching wrote:
Allowing people to subscribe to (mail+jira+commit) for a specific
commons component seems to be to me what casual contributors would
really need, but we have no easy way to do that without causing major
damage to the whole commons community.
Yes,
This proposal has merit, in that it allows the main dev list room to
breathe for discussion, which should be its primary purpose. It also has
a very clear benefit in mail archive - in fact its really pretty
essential for that.
Some of the negative respones have focussed around what the needs
On 7/22/06, Brett Porter [EMAIL PROTECTED] wrote:
But, YMMV - the Maven lists are significantly busier than commons.
That wasn't my feeling - we're not very busy at the moment but
generally I thought commons-dev was one of the busier lists at the
ASF.
Comparing:
On 7/22/06, Stephen Colebourne [EMAIL PROTECTED] 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?
Henri Yandell wrote:
On 7/22/06, Brett Porter [EMAIL PROTECTED] wrote:
But, YMMV - the Maven lists are significantly busier than commons.
That wasn't my feeling - we're not very busy at the moment but
generally I thought commons-dev was one of the busier lists at the
ASF.
Comparing:
Stephen Colebourne wrote:
This proposal has merit, in that it allows the main dev list room to
breathe for discussion, which should be its primary purpose. It also has
a very clear benefit in mail archive - in fact its really pretty
essential for that.
Some of the negative respones have
On 7/22/06, Henri Yandell [EMAIL PROTECTED] wrote:
On 7/22/06, Stephen Colebourne [EMAIL PROTECTED] 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
Phil Steitz [EMAIL PROTECTED] wrote:
Commit diffs are not spam, IMO, nor are issue reports / comments.
This is core to what is happening on a project.
This is true for someone deeply involved in the project life, but may be
overwhelming for someone who only wants to keep an eye on the
Henri Yandell wrote on Friday, July 21, 2006 2:16 AM:
A while back Maven moved to having the commits and issues on different
mailing lists and it seems to be going well.
So I'd like to suggest:
[EMAIL PROTECTED] - reply-to to commons-dev
[EMAIL PROTECTED] - reply-to to commons-dev
Henri Yandell wrote on Friday, July 21, 2006 2:16 AM:
A while back Maven moved to having the commits and issues on different
mailing lists and it seems to be going well.
So I'd like to suggest:
[EMAIL PROTECTED] - reply-to to commons-dev
[EMAIL PROTECTED] - reply-to to commons-dev
That
+1
--
Dennis Lundberg
Brett Porter wrote:
+1 to this proposal. I'd also suggest starting the list with the full
list of subscribers so nobody is immediately impacted.
- Brett
On 21/07/2006 10:15 AM, Henri Yandell wrote:
A while back Maven moved to having the commits and issues on
+1 on both.. Although I would also like to see the wiki notifications moved to
the commits list.
The only thing that needs to be done to actually make this work, is to actually advertise the
mailinglist splitup. I missed the fact at some projects (don't remember which ones though), there
was a
A while back Maven moved to having the commits and issues on different
mailing lists and it seems to be going well.
So I'd like to suggest:
[EMAIL PROTECTED] - reply-to to commons-dev
[EMAIL PROTECTED] - reply-to to commons-dev
I think the wiki notifications should stay on the dev list as
I would rather that we find a way to reduce the JIRA noise, but only
the part of it that really is noise. The real JIRA notifications and
commit diffs are as important as the other stuff on this list -
certainly as important as this message ;-)
Phil
On 7/20/06, Henri Yandell [EMAIL PROTECTED]
+1 to this proposal. I'd also suggest starting the list with the full
list of subscribers so nobody is immediately impacted.
- Brett
On 21/07/2006 10:15 AM, Henri Yandell wrote:
A while back Maven moved to having the commits and issues on different
mailing lists and it seems to be going
On 7/20/06, Phil Steitz [EMAIL PROTECTED] wrote:
I would rather that we find a way to reduce the JIRA noise, but only
the part of it that really is noise. The real JIRA notifications and
commit diffs are as important as the other stuff on this list -
certainly as important as this message ;-)
+1
Niall
On 7/21/06, Brett Porter [EMAIL PROTECTED] wrote:
+1 to this proposal. I'd also suggest starting the list with the full
list of subscribers so nobody is immediately impacted.
- Brett
On 21/07/2006 10:15 AM, Henri Yandell wrote:
A while back Maven moved to having the commits and
Hi Henri,
-Original Message-
From: Henri Yandell [mailto:[EMAIL PROTECTED]
Sent: Friday, 21 July 2006 10:16 AM
To: Jakarta Commons Developers List
Subject: [all] Splitting the mailing list
A while back Maven moved to having the commits and issues on different
mailing lists
On 7/20/06, Henri Yandell [EMAIL PROTECTED] wrote:
Is it as important for contributors? If I understand it correctly,
the idea of this change (a bunch of projects seem to be moving this
way) is that the developers see exactly what they used to see and the
contributors get a less spammy list
On 7/20/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 7/20/06, Henri Yandell [EMAIL PROTECTED] wrote:
Is it as important for contributors? If I understand it correctly,
the idea of this change (a bunch of projects seem to be moving this
way) is that the developers see exactly what they used
On 7/20/06, Phil Steitz [EMAIL PROTECTED] wrote:
On 7/20/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 7/20/06, Henri Yandell [EMAIL PROTECTED] wrote:
Is it as important for contributors? If I understand it correctly,
the idea of this change (a bunch of projects seem to be moving this
On Thu, 2006-07-20 at 20:34 -0700, Martin Cooper wrote:
On 7/20/06, Phil Steitz [EMAIL PROTECTED] wrote:
On 7/20/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 7/20/06, Henri Yandell [EMAIL PROTECTED] wrote:
Is it as important for contributors? If I understand it correctly,
the
On 7/20/06, Simon Kitching [EMAIL PROTECTED] wrote:
As far as the arguments about getting new contributors in, I would
like to hear from them.
That's an excellent idea..
Yup. James Ring is one of those, so his reply was quite a surprise (for me).
Maybe a better email would be:
29 matches
Mail list logo
