An Analysis of the RFS Process
I was curious about the current efficacy of the BTS-based RFS process,
and so created some charts[1] to provide visibility. The state
classification used for the chart data is not completely vetted, but I
believe it to be good enough to identify trends.
The RFS Activity chart[2] shows a open RFS count that is not under
control. Post-freeze, submissions are averaging 20-30 per month. The
backlog is at an all-time high, and is growing at about the same rate
- a solid 20/month.
The Comment Activity chart[3] shows the number of comments on open RFS
bugs vs. age. Of the 112 currently open RFS issues that are more than
a month old, 59 (52%) have no comments beyond the original author
entry. A significant portion of the rest have just a second entry,
also by the author.
For this process to be effective, RFS resolutions need to be happening
at a sustained rate of about 3-4 times the current level. It would
also be better for community relations if the median comment count
were higher.
Click on or hover over chart data points for more information.
1 - http://davesteele.github.io/debian-rfs-stats/
2 - http://davesteele.github.io/debian-rfs-stats/rfsactivity.html
3 - http://davesteele.github.io/debian-rfs-stats/commentactivity.html
--
"Le mieux est l'ennemi du bien" - Voltaire
Reply to: