hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <...@apache.org>
Subject Concern about under-communication in the HAWQ community
Date Fri, 01 Apr 2016 22:13:38 GMT

for the past month or so I've been noticing that there's
clearly under-communication going on in the HAWQ
community. In fact, the more activity I see around code
going in with next to 0 activity on dev@

A community needs conversation. Discussion. Consideration
of topics, roadmaps, and feature development.

Here's the most recent example of that:
where a commit recently went in without the JIRA ever
being updated or a solution negotiated/reviewed with
the original submitter. In fact, the content of that commit
is not problem free. For example, the following really
needs to be fixed:
Libhdfs3 is developed by Pivotal and used in HAWQ, which
is a massive parallel database engine in Pivotal Hadoop

A similar example is:
where the original contribution seems to have been
silently ignored and a new issue and code merge on
HAWQ-548 did the exact same thing without recognition
of the previous issue.

Another good example of this would be:
where there was a lot of collaboration on a JIRA driven
by Cos, there was a branch for that work developed in
the tree, but now it seems that branch no longer gets
any attention and it feels like we're restarting this from

I can go on, but I think you get my point.

At this point, I'd like to:
   1. highlight this in our Incubator report
   2. understand how are you guys going to change the situation
Please provide your comments on this thread for both.


View raw message