| Dear Community Member,
you may recall from the Developer Summit, that the Advisory Board is funding a project to model our review process to help identify bottlenecks and develop a strategy going forward. At this stage, we have - A database (including agreed schema) that sucks in data from xen-devel@ and git - An agreed set of metrics (more to this later) - An early report highlighting some issues : I don't want to share it yet as there are still too many question marks
However, I wanted to share the metrics we will be able to collect shortly (some of which will feature in an initial analysis). Then there will be a second stage of the project, which will largely depend on what we learn.
In any case, I wanted to share what kind of metrics we will be able to collect and analyse. You will need to refer to [1] in some cases. The data below can be collected per individual patch and per patch series. We will also be able to run histograms of various kinds on most of them (e.g. will be able to use attributes under "Community" and apply them to "Time" - in other word create a histogram of say "time to first review" over "contributors/reviewers", or "time to merge" over "Number of files touched", etc.)
Time analysis:
--------------
This section focuses on the time to reach some step in the review process and you need to look at [1]
- Time to merge: Time between 1 and C
- TIme to commit: Time between A and C
- Time to first review: Time between 1 and its first review comment - Time to review (cumulated): sum of all all of the grey segments in [1] - Time to re-work (cumulated): sum of all all of the orange segments in [1]
All of these metrics can be visualized in terms of median/mean evolution, but also histograms or distributions that may help to understand the data.
Backlog analysis:
-----------------
- Review completed: Patches that were successfully merged.
- Review active: Patches that were recently reviewed (basically patches with a review taking place during the last 7 days.
- Review stalled: Patches older than 1 year.
- Review ongoing: Patches younger than 1 year.
Note: we will probably change the threshold to something else
Complexity Analysis:
--------------------
- Number of revisions
- Number of 'touched' files
- Number of added and removed lines
- Number of comments received
For patch series only:
- Number of patches per series
All of these metrics can be visualized in terms of median/mean evolution, but also histograms or distributions that may help to understand the data.
Community:
----------
- People sending patches/patch series
- People reviewing patches/patch series
- Vendors sending patches/patch series
- Vendors reviewing patches/patch series
All of these metrics can be visualized in terms of median/mean evolution, but also histograms or distributions that may help to understand the data.
Best Regards Lars ----
Reference Diagram [1]
| 
