Return-Path: X-Original-To: apmail-hawq-dev-archive@minotaur.apache.org Delivered-To: apmail-hawq-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2484318772 for ; Tue, 29 Sep 2015 18:49:14 +0000 (UTC) Received: (qmail 8167 invoked by uid 500); 29 Sep 2015 18:49:04 -0000 Delivered-To: apmail-hawq-dev-archive@hawq.apache.org Received: (qmail 8122 invoked by uid 500); 29 Sep 2015 18:49:04 -0000 Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hawq.incubator.apache.org Delivered-To: mailing list dev@hawq.incubator.apache.org Received: (qmail 8075 invoked by uid 99); 29 Sep 2015 18:49:04 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2015 18:49:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EDC89C724E for ; Tue, 29 Sep 2015 18:49:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.312 X-Spam-Level: **** X-Spam-Status: No, score=4.312 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Raa8_XRgkhaT for ; Tue, 29 Sep 2015 18:48:54 +0000 (UTC) Received: from mail-io0-f173.google.com (mail-io0-f173.google.com [209.85.223.173]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 75B02204DF for ; Tue, 29 Sep 2015 18:48:53 +0000 (UTC) Received: by iofh134 with SMTP id h134so21567565iof.0 for ; Tue, 29 Sep 2015 11:48:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=0k+yVzAYK0B3GicqWTlKhf3/EP8Q5bJrnLajwnvQJ7E=; b=Izpn28SkLk+vhv/ccQx44B4B0TlqAd2jmZn8hS+9XZ1EtvCZuKlB5sby4sklUxrl2g p9ZCvTEhWI2oYROsl0NdLBcI3Qr5oJZXIfuIjXZ/EAU6gLZfuIctYTBKSBktXUoLkWiG zfLzkw9w/8WC8D4x4PNDiWMVo6oXaxWVJjwvMCiy7pCQShab0KkMeF9Asr2A86O9Y0an Ew02sJ1x6edH3AMqVdKwRNqX4Bmw5JgegaHvbQDHNW21yGUM/HybU16DZ1FxFEHBB4SY BETuVt0enP1ijG5jYHL0R2ST7wPgI9mXi3+UN1+DmCkel3lC0S7nisDAXhHpeTY9GbEj OA9g== X-Gm-Message-State: ALoCoQnAwQ7EQq1V2586XuRYLvMdyx/dKPQ7Dca3Rwm9XoN7iT1cqRgImdbs4GiaF74uXGNQp0/Z X-Received: by 10.107.15.159 with SMTP id 31mr227060iop.159.1443552532172; Tue, 29 Sep 2015 11:48:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.10.21 with HTTP; Tue, 29 Sep 2015 11:48:32 -0700 (PDT) In-Reply-To: <20150929101233.GY19314@boudnik.org> References: <20150928122903.GI19314@boudnik.org> <20150929101233.GY19314@boudnik.org> From: Caleb Welton Date: Tue, 29 Sep 2015 20:48:32 +0200 Message-ID: Subject: Re: Staying with RTC (review-then-commit) rule To: dev@hawq.incubator.apache.org Content-Type: multipart/alternative; boundary=001a113ee868e55f6b0520e7434d --001a113ee868e55f6b0520e7434d Content-Type: text/plain; charset=UTF-8 Konstantin, thanks for the references, it's helpful seeing what other projects have done and the discussions they have had. Right now I'm inclined to follow Roman's advice of starting with RTC at least until we've gotten into the swing of things Apache style. This also seems in-line with the contribution guidelines that Lei sketched out [1] which seems to assume a RTC model. The LazyConsensus model seems like a good addition to a pure RTC. The voting guidelines that you posted seem to indicate 3 +1's are typical. >From a hallway conversation with Roman it sounded like 1 or 2 are equally common. So... I propose: - Use RTC and revisit if we feel this is too much overhead - Start with 2 +1's defining consensus - Allow LazyConsensus - Update the contribution guidelines accordingly Agree/Disagree? Hopefully we can get some more people to weigh in. Caleb [1] https://cwiki.apache.org/confluence/display/HAWQ/Contributing+to+HAWQ#ContributingtoHAWQ-Codereview On Tue, Sep 29, 2015 at 12:12 PM, Konstantin Boudnik wrote: > On Mon, Sep 28, 2015 at 11:06PM, CHANG Lei wrote: > > CTR (Commit then Review) or RTC (Review then commit) is a process we need > > to finalize soon. Actually, most of the hawq code developed before > follows > > CTR. > > > > And I just found some other commits on the branch (that does not get 2 > +1s, > > looks from Caleb :-) > > > > So IMO, to get this finalized might be a good practice for an apache > voting > > process on Procedural item (http://www.apache.org/foundation/voting.html > ). > > While using voting to rubber-stamp a procedural vote is a legit use of the > voting process, let's only use it after the consensus [1] is reached. > Voting > isn't a replacement nor a right mechanism to establish policies or > practices > within the community. A couple of good examples of gaining the consensus > through the community relevant to the topic are [2] and [3] > > Cos > > [1] https://www.apache.org/foundation/voting.html#LazyConsensus > [2] http://bit.ly/1gLeArc > [3] > http://apache-ignite-developers.2346864.n4.nabble.com/Jira-Process-tp1816p1831.html > > > Most committers do not know about the process. > > > > Cheers > > Lei > > > > > > On Mon, Sep 28, 2015 at 8:45 PM, Caleb Welton > wrote: > > > > > Konstantin, I don't think all the developers are aware of the > differences > > > between CTR and RTC. Would you care to elaborate on the contribution > > > protocols? > > > > > > Thanks! > > > > > > > > > On Mon, Sep 28, 2015 at 2:29 PM, Konstantin Boudnik > > > wrote: > > > > > > > I am the big advocate of CTR model and has been pushing it in a > number of > > > > the > > > > projects before. However, for the very early ones like Hawq right > now, > > > RTC > > > > might make more sense: it takes time to learn how to add new trusty > > > people > > > > to > > > > the community; also for new committers it helps to learn the code > faster > > > by > > > > doing the mandatory reviews. But before you know it, I will be doing > > > rounds > > > > here pushing for CTR ;) > > > > > > > > Cos > > > > > > > > On Mon, Sep 28, 2015 at 03:11PM, Roman Shaposhnik wrote: > > > > > Hi! > > > > > > > > > > just wanted to say what I said on HAWQ-7, but > > > > > since not all of us are watching that JIRA, I think > > > > > it would be useful to repeat it here. > > > > > > > > > > While there's nothing wrong with lazy consensus, > > > > > but initially I'd suggest staying with RTC model. > > > > > Thus +1 from somebody else should be explicitly > > > > > required. > > > > > > > > > > I don't think there's any disagreement, but I just > > > > > wanted to have it explicitly mentioned. > > > > > > > > > > Thanks, > > > > > Roman. > > > > > > > > --001a113ee868e55f6b0520e7434d--