tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henry Saputra <henry.sapu...@gmail.com>
Subject Re: [DISCUSS] We need to suppress a huge patch without any proposal or discussion.
Date Thu, 12 Feb 2015 23:23:53 GMT
Sorry for late chiming in to this discussions. But so far what I have
seen is bit lack of documentation in the code, meaning why the code is
here in the first place.

I was able to follow design and discussions pretty well but when it is
time to review the code it is hard to follow why some code are added
and how it is being used in relative to overall flow.

- Henry

On Sat, Dec 20, 2014 at 9:18 PM, Hyunsik Choi <hyunsik@apache.org> wrote:
> 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

View raw message