incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arvind Prabhakar <arv...@apache.org>
Subject Re: Flume Graduation (was Re: June reports in two weeks)
Date Sun, 27 May 2012 04:29:31 GMT
Hi Jukka,

On Sat, May 26, 2012 at 4:43 PM, Jukka Zitting <jukka.zitting@gmail.com>wrote:

> Hi,
>
> On Sat, May 26, 2012 at 7:11 PM, Arvind Prabhakar <arvind@apache.org>
> wrote:
> > * We have established that there is sufficient diversity in the
> committers
> > list.
>
> I tend to look more at actual commit activity than the committers list
> when evaluating the diversity of a project. There are people on the
> Flume committers list who've never committed anything.
>
> Combining information from svn statistics [1] and committer
> affiliations [2] I get the following list of Flume commit activity so
> far this year:
>
>    arvind  - 116 commits - Cloudera
>    prasadm -  22 commits - Cloudera
>    brock   -  16 commits - Cloudera
>    esammer -   4 commits - Cloudera
>    jarcec  -   1 commit  - AVG Technologies
>    juhanic -   1 commit  - CyberAgent
>
> The only two non-Cloudera commits were pretty trivial changes (a
> plugin version upgrade [3] and a spelling fix [4]). My earlier
> classification of Flume as "ready to graduate" [5] was partially based
> on these new committers from outside Cloudera, but the above data
> suggests that they haven't been as active as I would have hoped.
>
> IIUC Flume operates under an RTC model where people are not supposed
> to commit their own changes, which obviously makes the above data less
> relevant for evaluating the true diversity of the community. However,
> seeing only a single trivial commit by both jarcec and juhanic even
> though they became committers already over three months ago does seem
> to suggest that they may not be as comfortable in their committer role
> as people from Cloudera are.
>

As you noted in your comments above - the Flume project tends to follow RTC
with the reviewer committing the code. I happen to have taken up the role
of the reviewer for the most part and hence you see the skewed commit
counts. If you want to see the actual contribution, I would suggest looking
at fixed JIRA issues by assignees. A quick report yields the following:

    aprabhkar - 26 - Cloudera [6]
    brocknoland - 19 - Cloudera [7]
    esammer - 56 - Cloudera [8]
    hshreedharan - 34 - Cloudera [9]
    jarcec - 6 - AVG Technologies [10]
    jmhsieh - 8 - Cloudera [11]
    juhanic - 9 - CyberAgent [12]
    mpercy - 34 - Cloudera [13]
    mlai@apache.org - 1 - Trend Micro [14]
    prasadm - 34 - Cloudera [15]
    tom@cloudera.com - 3 - Cloudera [16]
    will@cloudera.com - 3 - Cloudera [17]

Looking at this, the average number of issues resolved by Cloudera
committers (not counting Tom who is a mentor) is 26, and that for
non-Cloudera committers is 5. Note that this number does not include other
committer work such as the number of code reviews they have done, the
number of design discussions they have participated in, something that is
very valuable to the project.


>
> Do you think this is a problem for the community? If yes, how do you
> plan to fix it? If not, why?
>

I don't think this is a problem because while most Cloudera committers have
the luxury of working on the project during regular working hours, others
do that during their off hours. Hence the majority of contributions coming
from Cloudera.

If all committers were to be non-Cloudera, I am sure the averages will be
low and comparable to what the non-Cloudera contribution rate is at the
moment. In other words, the project growth will definitely slow down, but
the community will remain healthy. This is also indicated by the following
statistics:

User List:
  Messages in May: 171, April: 119
  Number of Subscribers: 102

Dev List:
  Messages in May: 642, April 1024
  Number of Subscribers: 245

[6] http://s.apache.org/2hi
[7] http://s.apache.org/kw
[8] http://s.apache.org/nl
[9] http://s.apache.org/SGe
[10] http://s.apache.org/tR
[11] http://s.apache.org/UvH
[12] http://s.apache.org/A8V
[13] http://s.apache.org/f8M
[14] http://s.apache.org/TIK
[15] http://s.apache.org/wO
[16] http://s.apache.org/Fxb
[17] http://s.apache.org/rw

Thanks,
Arvind Prabhakar



> [1]
> http://svnsearch.org/svnsearch/repos/ASF/search?from=20120101&to=20121231&path=%2Fincubator%2Fflume
> [2] http://incubator.apache.org/flume/team-list.html
> [3] http://svn.apache.org/viewvc?view=revision&revision=1305478
> [4] http://svn.apache.org/viewvc?view=revision&revision=1342066
> [5] http://markmail.org/message/kq5ixay6z3erw3pc
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

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