tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@apache.org>
Subject Re: 1st hit for Apache Tez
Date Thu, 17 Jul 2014 18:36:37 GMT
I don't see the point being made here. The project got seeded with some
initial code, so it is only natural that big contributions initially come
from those who 'know' the code-base. That said, there are contributions
from folks all around if not at the same scale, and these are only growing
by the time. Give it enough time, and you will see much larger
contributions beside feature/bug reports.

I can repeat oft-quoted lines on statistics. The graph doesn't show the
efforts done by others from Apache Pig and Apache Hive communities who have
been largely driving the direction of the project by making suggestions for
feature requests and filing bug reports. Also, not sure of the conclusions
hinted at that can be made by looking at the team-list page.


On Thu, Jul 17, 2014 at 10:24 AM, Doug Cutting <cutting@apache.org> wrote:

> On Thu, Jul 17, 2014 at 9:59 AM, Hitesh Shah <hitesh@apache.org> wrote:
> > To answer your question, the initial codebase that was used to seed the
> Incubator
> > podling came from Hortonworks (
> http://wiki.apache.org/incubator/TezProposal ).
> The vast majority of contribution since then has also been by Hortonworks.
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12314426&statistictype=assignees&selectedProjectId=12314426&reportKey=com.atlassian.jira.plugin.system.reports%3Apie-report&Next=Next
> http://tez.incubator.apache.org/team-list.html
> Doug

NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message