Return-Path: Delivered-To: apmail-hive-dev-archive@www.apache.org Received: (qmail 33290 invoked from network); 20 Jan 2011 02:49:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Jan 2011 02:49:14 -0000 Received: (qmail 68197 invoked by uid 500); 20 Jan 2011 02:49:14 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 68006 invoked by uid 500); 20 Jan 2011 02:49:13 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 67998 invoked by uid 99); 20 Jan 2011 02:49:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jan 2011 02:49:12 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of heyongqiangict@gmail.com designates 209.85.216.48 as permitted sender) Received: from [209.85.216.48] (HELO mail-qw0-f48.google.com) (209.85.216.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jan 2011 02:49:06 +0000 Received: by qwh6 with SMTP id 6so88284qwh.35 for ; Wed, 19 Jan 2011 18:48:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=l4ExoTqZWiHO+shyTUAgoW10fgM9x4u96ato98jAucY=; b=D6jSKsCEz3/YidhAlL9qF3UZGfByqEorESgQGV3BzxEM96+0WTIUzBBhzosXMgDhmD W9XayLzhL+3sHwwRR067wZGxSurWQkBFg7Gbq7Ns+ZC9gMNK3nII9fm5fLSqdREHVz0j OYzHfkaUnprbx0Ph50LpvLVwqTScn9OZSG65A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=rhHUt8L6Kg6lKNiNH1TqaB9ubXTzozYdi3U2hehPT5bNBOERn6kSYHWiPyP78LrTM6 DEwi8TR9NrlqSwmtPdMps4/xovIz6547SdcGZXtOv1a/TH+NcqtAiyQVdsRmu12lPUGT zGxvXFven77DEzO9EqbsDaQFj0lupNn8rz4nU= MIME-Version: 1.0 Received: by 10.229.91.10 with SMTP id k10mr1248711qcm.141.1295491725201; Wed, 19 Jan 2011 18:48:45 -0800 (PST) Received: by 10.229.136.146 with HTTP; Wed, 19 Jan 2011 18:48:45 -0800 (PST) In-Reply-To: References: Date: Wed, 19 Jan 2011 18:48:45 -0800 Message-ID: Subject: Re: patch review process From: yongqiang he To: dev@hive.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org +1 for option 2. In general, we as a community should be nice to all contributors, and should avoid doing things that make contributors not comfortable, even that requires some work from committers. Sometimes it is especially true for new contributors, like we need to be more patience for new people. It seems a free style and contribution focused environment would be better to encourage people to do more contributions of different kinds. thanks -yongqiang On Wed, Jan 19, 2011 at 6:37 PM, Namit Jain wrote: > > > > It would be good to have a policy for submitting a new patch for review. > If the patch is small, usually it is pretty easy to review.But, if it lar= ge, > a GUI like reviewboard (https://reviews.apache.org) makes it easy. > > So, going forward, I would like to propose either of the following. > > 1. All patches must go through reviewboard > 2. If a contributor/reviewer creates a reviewboard request, > =A0 =A0 all subsequent review requests should go through the reviewboard. > > > I would personally vote for 2., since for small patches, we don=92t reall= y need a > reviewboard. > > But, please vote, and based on that, we can come up with a policy. > Let us know, if you think of some other option. > > Thanks, > -namit > >