I prefer to keep the JIRA notifications on the tuscany-dev list. IMHO, we developers should pay attensions to issues in addition to adding features :-). In some projects like Axis2, they seem to use JIRA to drive the development activities. A simple mail filter can help organize the inbox if you want to put them into a JIRA folder.

Anyway, I guess the bottom line is that we need to work hard to keep the number of open JIRAs down to a reasonable level :-).

Thanks,
Raymond

----- Original Message ----- From: "Luciano Resende" <[EMAIL PROTECTED]>
To: <[email protected]>; <[EMAIL PROTECTED]>
Sent: Wednesday, February 06, 2008 8:00 AM
Subject: Re: Graduation next steps


If we are going to remove JIRAs from dev list, my personal preference
would be to have a notification list and have JIRA, Build
notifications, etc sent to this list. But I'm still not convinced that
moving JIRA out of the dev mailing list is the best solution here.

On Feb 6, 2008 5:26 AM, ant elder <[EMAIL PROTECTED]> wrote:
On Feb 4, 2008 8:06 PM, Simon Nash <[EMAIL PROTECTED]> wrote:

<snip>

> - route the JIRA traffic out of the dev list as suggested by Matthieu
> >
> I understand that this traffic can get a bit overwhelming at times, but
> I'd like to make the case that it does have value for new developers
> (though not for users).  One of the best ways to start down the path to
> becoming a contributor and committer is through writing or fixing > JIRAs.
> Having the JIRA traffic appear on the dev list helps people to see what
> JIRAs others are writing and can encourage new contributors to jump in
> with a comment or a fix, or to write other JIRAs themselves.
>

I'm quite sympathetic to that view but also see the problem of the dev list flooded by JIRA activity so I'm now leaning to having the JIRA activity sent
to the commit list where it would still available to anyone interested.
Anyone else have comments or preferences?

   ...ant




--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to