Return-Path: 
 <tuscany-dev-return-28082-apmail-ws-tuscany-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-tuscany-dev-archive@locus.apache.org
Received: (qmail 36637 invoked from network); 6 Feb 2008 13:26:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 6 Feb 2008 13:26:33 -0000
Received: (qmail 68824 invoked by uid 500); 6 Feb 2008 13:26:24 -0000
Delivered-To: apmail-ws-tuscany-dev-archive@ws.apache.org
Received: (qmail 68790 invoked by uid 500); 6 Feb 2008 13:26:24 -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 68781 invoked by uid 99); 6 Feb 2008 13:26:24 -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 05:26:24 -0800
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of ant.elder@gmail.com
 designates 66.249.82.230 as permitted sender)
Received: from [66.249.82.230] (HELO wx-out-0506.google.com) (66.249.82.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 13:25:56 +0000
Received: by wx-out-0506.google.com with SMTP id r21so2395016wxc.28
        for <tuscany-dev@ws.apache.org>; Wed, 06 Feb 2008 05:26:03 -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:reply-to:to:subject:in-reply-to:mime-version:content-type:references;
        bh=B01b9jt70QJ5TwuB5Zr5hH5c5XBA6Z56txRgyOqAJ0A=;
        b=LWvTROZ/rPtQ8JkOG9+S6DWdltKauvX9wyWsqVOSnVENc4jeU9vI1gahvAtM84UuaofPvL2W6qInl5jQN3xK46Eq+rM+6/qb8XFY5KyAK19GNNZ8VvvScGjtoLWUkRBxVQrIeSK3yJ1Jd9Lvua2vWQtwOiGyZvnuydy2MQQoPig=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references;
        b=J5cMi9QvW3tPkiCtdoQj69ZAt6nFEw1akn2RjytNssyJEg9RX5WWPSm8upLV2fuufFAzKR4kcsKDJ602E9AAj2ABDpuFkOu6RoN9XNMQlJzw8iWiGN9HeW5gYk4Pcwa1ooU/7IYNvbPduLVRg0gIuRjEJPETqOP7p0SJx9xCTzo=
Received: by 10.70.37.12 with SMTP id k12mr6289499wxk.70.1202304362547;
        Wed, 06 Feb 2008 05:26:02 -0800 (PST)
Received: by 10.70.30.4 with HTTP; Wed, 6 Feb 2008 05:26:02 -0800 (PST)
Message-ID: <71e1b5740802060526j992a65esf8d71073be10435@mail.gmail.com>
Date: Wed, 6 Feb 2008 13:26:02 +0000
From: "ant elder" <ant.elder@gmail.com>
Reply-To: antelder@apache.org
To: tuscany-dev@ws.apache.org
Subject: Re: Graduation next steps
In-Reply-To: <47A7703C.4080202@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_18092_17967283.1202304362546"
References: <71e1b5740801310541m7c74b1aamc00e38805cba81fd@mail.gmail.com>
	 <c0c051b50802010247s554241e7y409bd8306e7712b2@mail.gmail.com>
	 <fbdc6a970802021509nbf6e5dehef5ab86b995e78b1@mail.gmail.com>
	 <47A57370.5010200@apache.org> <47A7703C.4080202@apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_18092_17967283.1202304362546
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------=_Part_18092_17967283.1202304362546--