Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 59872 invoked from network); 25 Jun 2009 06:39:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Jun 2009 06:39:34 -0000 Received: (qmail 94445 invoked by uid 500); 25 Jun 2009 06:39:44 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 94374 invoked by uid 500); 25 Jun 2009 06:39:44 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 94364 invoked by uid 99); 25 Jun 2009 06:39:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jun 2009 06:39:44 +0000 X-ASF-Spam-Status: No, hits=4.2 required=10.0 tests=HTML_MESSAGE,NO_RDNS_DOTCOM_HELO,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.145.54.173] (HELO mrout3.yahoo.com) (216.145.54.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jun 2009 06:39:32 +0000 Received: from sp1-ex07cas01.ds.corp.yahoo.com (sp1-ex07cas01.ds.corp.yahoo.com [216.252.116.137]) by mrout3.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id n5P6cxtG093004 for ; Wed, 24 Jun 2009 23:38:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:from:to:date:subject:thread-topic:thread-index: message-id:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage:content-type:mime-version; b=f8EtLLuMIvjWpXsz0V/+hi3Gwgx6nyvOZjZDjulPAVIsUZsHxcLxcvGCmg5WScHQ Received: from SP1-EX07VS02.ds.corp.yahoo.com ([216.252.116.135]) by sp1-ex07cas01.ds.corp.yahoo.com ([216.252.116.137]) with mapi; Wed, 24 Jun 2009 23:38:59 -0700 From: Devaraj Das To: "core-dev@hadoop.apache.org" Date: Wed, 24 Jun 2009 23:38:57 -0700 Subject: Re: more information about project split Thread-Topic: more information about project split Thread-Index: Acn0FANhqXSLuV1EQ7iTbvbz44lKIwBS5ogU Message-ID: In-Reply-To: <3A42F667-2FB8-42BC-A77D-9A8B1A906171@apache.org> Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C66919595F25Addasyahooinccom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_C66919595F25Addasyahooinccom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable +1 for (4) On 6/23/09 8:33 PM, "Owen O'Malley" wrote: I really prefer the current approach, but clearly we need to reach consensus. Last week we had a case where a developer sent to the users lists because he thought that dev was reserved for jira traffic. That is a bad sign. Doug is the most prolific non-jira poster to core-dev and in 37th place. I think the community is better served by having a mailing list that is dominated by people posting rather than a deluge of jira traffic. Choices: 1. create/resolve/close to dev 2. create/resolve/close to dev, others to jira 3. create/comment/resolve/close to dev 4. all to dev The problem with 3 is that you can add comments on most of the actions. So either you capture all events or you only capture part of the comments. -- Owen --_000_C66919595F25Addasyahooinccom_--