Last modified: 2014-03-26 17:48:15 UTC
http://korma.wmflabs.org/browser/code_contrib_new_gone.html mjust answer these questions: Who are the new code contributors (commits + reviews)? Are they increasing their involvement? Who seems to be on a way out or gone? How are our contributor intake & loss evolving? * Number of new contributors with 1 / 2-5 / 6+ changes submitted in the past 3 months (values may be fine tuned based on actual data). * (How to register increasing engagement versus one-offs or new contributors disengaging and vanishing after a short period?) * Number of contributors stopping contributing or decreasing continuously in the past 3 months. https://www.mediawiki.org/wiki/Community_metrics#Code_contributors_new_.2F_gone
By the way, I've been using this report for some months: <http://www.mediawiki.org/wiki/Gerrit/Reports/Open_changesets_by_newbie_owner> I welcome the new contributors and give some pointers when necessary, add reviewers when missing. Often, if not in most cases, they receive some code review within the day (!); sometimes even a +2, but more often requests by submitter or reviewer rot unaddressed for months and the backlog grows.
Updated this KPI. Now there are two tables, one for newcomers and a second one for people gone. Both follow the same format: http://korma.wmflabs.org/browser/code_contrib_new_gone.html Nemo, in this report you have some more info comparing to your current report. You can see is a person is having probs (no merges in one moth, or abadons ...) and also, yo can see the first date for contribution and a brief activity graph. In next iteration we plan to add ordering for columns, as you have now in your report. Nemo, thoughts about the current of korma report?
(In reply to Alvaro from comment #2) > Nemo, thoughts about the current of korma report? Not really. I sent https://github.com/Bitergia/mediawiki-dashboard/pull/41 The first table is rather straightforward, I've not really tried to understand/analyse the second table and the graph.
The tables and graphs are now considered ready: http://korma.wmflabs.org/browser/code_contrib_new_gone.html We are still missing better strings, but this is a task for me. I'm taking the bug. Help / patches welcome. (In reply to Nemo from comment #3) > The first table is rather straightforward, I've not really tried to > understand/analyse the second table and the graph. The second table show contributors that haven't submitted any patch in the last 6 months. I'm not especially happy about the results it shows, but we can fine tune them, and file separate enhancement requests. Is 6 months a too long period (when we identify them, they are long gone)? Should reviews and comments also be counted (maybe someone hasn't upload a new changeset in 6 months, but they are reviewing others'patches regularly)? Similar thoughts with the graph: it's a good first step, but we can probably improve it. The idea is to show the intake of new contributrs vs the established community; we want to see that we are not stagnant, and hopefully having a healthy trend of newcomers. Should we count only the last 12 months to have a fresher and more dynamic picture of the new contributors versus the established ones? Should we add a line for the number of contributors with more than 10 patches? Should we use a cumulative graph, like "How is the weight of the WMF evolving?" at http://korma.wmflabs.org/browser/who_contributes_code.html ? Separate enhancement requests are welcome.
