Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-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 BDC3D10645 for ; Sun, 21 Dec 2014 05:40:35 +0000 (UTC) Received: (qmail 57182 invoked by uid 500); 21 Dec 2014 05:40:33 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 57137 invoked by uid 500); 21 Dec 2014 05:40:33 -0000 Mailing-List: contact dev-help@tajo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.apache.org Delivered-To: mailing list dev@tajo.apache.org Received: (qmail 57127 invoked by uid 99); 21 Dec 2014 05:40:33 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Dec 2014 05:40:33 +0000 Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 330651A01DB for ; Sun, 21 Dec 2014 05:40:31 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id rp18so2758380iec.24 for ; Sat, 20 Dec 2014 21:40:29 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.107.36.5 with SMTP id k5mr15285547iok.13.1419140429936; Sat, 20 Dec 2014 21:40:29 -0800 (PST) Received: by 10.107.166.132 with HTTP; Sat, 20 Dec 2014 21:40:29 -0800 (PST) In-Reply-To: References: Date: Sun, 21 Dec 2014 14:40:29 +0900 Message-ID: Subject: Re: [DISCUSS] We need to suppress a huge patch without any proposal or discussion. From: Jihoon Son To: "dev@tajo.apache.org" Content-Type: multipart/alternative; boundary=001a1140f54e36835a050ab36186 --001a1140f54e36835a050ab36186 Content-Type: text/plain; charset=UTF-8 +1 I totally agree with you. I also suffered the same problem. The huge patch makes the code review difficult, and thus the review process might be delayed. We should partition a large issue into several smaller sub tasks. I also know that this part is not easy, but we need to try by making a detailed proposal. Sincerely, Jihoon 2014-12-21 14:18 GMT+09:00 Hyunsik Choi : > Hi folks, > > I happy to see that Tajo community is going well and is getting healthy. > > For the sake of more healthy community and contribution, I propose > that we suppress a huge patch without any proposal and enough > discussion. > > We sometimes can see huge patch contributions without any proposal and > discussion. Honestly, I did too. In such cases, it is very hard to > give any guidance about the direction because patches already proceed > too far from starting point. As a result, reviewers feel lots of > burden to give comments. Also, contributors also need to do > unnecessary works if reviews give comments. > > In detail, we need to submit some detailed proposal if necessary. > Also, any guy need to ask some proposal if necessary. Actually, we > have done so far. But, we need to be eager to do so. > > How do you think about it? > > Best regards, > Hyunsik > --001a1140f54e36835a050ab36186--