You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ozone.apache.org by "Elek, Marton" <el...@apache.org> on 2020/05/04 10:38:31 UTC
April of 2020
I collected statistics from apache/hadoop-ozone github repo (just for
fun) but as I have it, I can share the details of the last month (again,
just for fun ;-) )
TL;DR; April of 2020 was one of the strongest month in the history of Ozone.
TL;DR: THANK YOU FOR ALL THE CONTRIBUTIONS
Number of created PRs: 144
Number of closed PRSs: 141
This is the second highest number since we started the development in
separated repository. The only better month is 2019-11 when we started
to use Sonar:
created closed increment
month
2019-10 111 88 23
2019-11 174 163 11
2019-12 117 105 12
2020-01 112 115 -3
2020-02 103 108 -5
2020-03 125 118 7
2020-04 144 141 3
105 out of the 144 PR are created by committers (which means that the
works are acknowledged)
The Pony-number / bus factor is 5 (the 5 most active contributors are
responsible for the >50% of the PRS). It means that loosing one person
wouldn't make the progress significant slower...
Number of individual PR contributors (unique Github users who created PRs):
month
2019-10 28
2019-11 35
2019-12 34
2020-01 31
2020-02 32
2020-03 37
2020-04 40
Some numbers to improve: 12 committer out of the 40 contributors have
more created prs than reviewed (or commented) prs.
!!!PLEASE HELP WITH MORE REVIEW!!!
Based on Apache Jira [2]:
135 issue is resolved in HDDS projects
120 issue is resoled in COMMON, HDFS, YARN, MAPREDUCE
Yet another month where resolved apache/hadoop-ozone issues > 50 % of
apache/hadoop issues
And again:
THANK YOU,
Marton
[1] Data is retrieved from Github API and checkend with Pandas. There
could be wrong calculation, if you see any error, please let me know.
[2]
project in (HADOOP, MAPREDUCE, YARN, HDFS) and resolutiondate >=
2020-04-01 and resolutiondate < 2020-05-01 and resolution not in
(Duplicate, "Won't Fix", Invalid, Later, "Not A Problem")
project = HDDS and resolutiondate >= 2020-04-01 and resolutiondate <
2020-05-01 and resolution not in (Duplicate, "Won't Fix", Invalid,
Later, "Not A Problem")
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
Re: April of 2020
Posted by Dinesh Chitlangia <di...@apache.org>.
Wow! Thanks for collecting and sharing this insight, Marton!
On Mon, May 4, 2020 at 6:38 AM Elek, Marton <el...@apache.org> wrote:
>
> I collected statistics from apache/hadoop-ozone github repo (just for
> fun) but as I have it, I can share the details of the last month (again,
> just for fun ;-) )
>
>
> TL;DR; April of 2020 was one of the strongest month in the history of
> Ozone.
>
> TL;DR: THANK YOU FOR ALL THE CONTRIBUTIONS
>
>
> Number of created PRs: 144
> Number of closed PRSs: 141
>
> This is the second highest number since we started the development in
> separated repository. The only better month is 2019-11 when we started
> to use Sonar:
>
>
> created closed increment
> month
> 2019-10 111 88 23
> 2019-11 174 163 11
> 2019-12 117 105 12
> 2020-01 112 115 -3
> 2020-02 103 108 -5
> 2020-03 125 118 7
> 2020-04 144 141 3
>
> 105 out of the 144 PR are created by committers (which means that the
> works are acknowledged)
>
>
> The Pony-number / bus factor is 5 (the 5 most active contributors are
> responsible for the >50% of the PRS). It means that loosing one person
> wouldn't make the progress significant slower...
>
> Number of individual PR contributors (unique Github users who created PRs):
>
> month
> 2019-10 28
> 2019-11 35
> 2019-12 34
> 2020-01 31
> 2020-02 32
> 2020-03 37
> 2020-04 40
>
>
> Some numbers to improve: 12 committer out of the 40 contributors have
> more created prs than reviewed (or commented) prs.
>
>
>
> !!!PLEASE HELP WITH MORE REVIEW!!!
>
>
>
>
>
> Based on Apache Jira [2]:
>
> 135 issue is resolved in HDDS projects
> 120 issue is resoled in COMMON, HDFS, YARN, MAPREDUCE
>
> Yet another month where resolved apache/hadoop-ozone issues > 50 % of
> apache/hadoop issues
>
>
>
>
> And again:
>
> THANK YOU,
> Marton
>
>
> [1] Data is retrieved from Github API and checkend with Pandas. There
> could be wrong calculation, if you see any error, please let me know.
>
> [2]
>
> project in (HADOOP, MAPREDUCE, YARN, HDFS) and resolutiondate >=
> 2020-04-01 and resolutiondate < 2020-05-01 and resolution not in
> (Duplicate, "Won't Fix", Invalid, Later, "Not A Problem")
>
>
> project = HDDS and resolutiondate >= 2020-04-01 and resolutiondate <
> 2020-05-01 and resolution not in (Duplicate, "Won't Fix", Invalid,
> Later, "Not A Problem")
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
>