Return-Path: 
 <tuscany-dev-return-28084-apmail-ws-tuscany-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-tuscany-dev-archive@locus.apache.org
Received: (qmail 64933 invoked from network); 6 Feb 2008 16:01:20 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 6 Feb 2008 16:01:20 -0000
Received: (qmail 97267 invoked by uid 500); 6 Feb 2008 16:01:10 -0000
Delivered-To: apmail-ws-tuscany-dev-archive@ws.apache.org
Received: (qmail 97245 invoked by uid 500); 6 Feb 2008 16:01:10 -0000
Mailing-List: contact tuscany-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:tuscany-dev-help@ws.apache.org>
List-Unsubscribe: <mailto:tuscany-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:tuscany-dev@ws.apache.org>
List-Id: <tuscany-dev.ws.apache.org>
Reply-To: tuscany-dev@ws.apache.org
Delivered-To: mailing list tuscany-dev@ws.apache.org
Received: (qmail 97222 invoked by uid 99); 6 Feb 2008 16:01:10 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 08:01:10 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of luckbr1975@gmail.com
 designates 64.233.184.232 as permitted sender)
Received: from [64.233.184.232] (HELO wr-out-0506.google.com) (64.233.184.232)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 16:00:42 +0000
Received: by wr-out-0506.google.com with SMTP id 50so2848969wra.18
        for <tuscany-dev@ws.apache.org>; Wed, 06 Feb 2008 08:00:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=dSnzQbpYcUG6Hy+vljjAXDjx7g9XRGU3L+gNEn42iQk=;
        b=bE6+GHxruCbBGTMqBHAZr8/5eu7lTDJbl+mib8W9tRyfWoSp87LGUfvhCRXjwIgbqD5dJIb1UwYP2YnBkU2UGZ1Thv4ztX0M3klhm8BeykUg/8jk3y77vEASr1HA8pxbANUwLzQNOJHwcTGREintVzUNRiirz4oTmjVBH1r207I=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=iiPhR6j9LF8pTdUwFxF7VcN1BiyjgI/g3EhGK1eeVBn3dYmCFGgTWjV3IpKs6GRMJX4+VBxH1232VmgDyJcAzp5qfqwP/PCicdd0/kwAw6E5hKbzjvswi06sVSGpjdXndIeJLfewzYl99tYU20ym3YCDhSDLi11QU7/5PnbklLY=
Received: by 10.114.66.2 with SMTP id o2mr4164457waa.111.1202313641299;
        Wed, 06 Feb 2008 08:00:41 -0800 (PST)
Received: by 10.114.76.18 with HTTP; Wed, 6 Feb 2008 08:00:41 -0800 (PST)
Message-ID: <5a75db780802060800y3a9844d8m88aa0ae81c9942e8@mail.gmail.com>
Date: Wed, 6 Feb 2008 08:00:41 -0800
From: "Luciano Resende" <luckbr1975@gmail.com>
To: tuscany-dev@ws.apache.org, antelder@apache.org
Subject: Re: Graduation next steps
In-Reply-To: <71e1b5740802060526j992a65esf8d71073be10435@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <71e1b5740801310541m7c74b1aamc00e38805cba81fd@mail.gmail.com>
	 <c0c051b50802010247s554241e7y409bd8306e7712b2@mail.gmail.com>
	 <fbdc6a970802021509nbf6e5dehef5ab86b995e78b1@mail.gmail.com>
	 <47A57370.5010200@apache.org> <47A7703C.4080202@apache.org>
	 <71e1b5740802060526j992a65esf8d71073be10435@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

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 <ant.elder@gmail.com> wrote:
> On Feb 4, 2008 8:06 PM, Simon Nash <nash@apache.org> 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org