[development] Goals of project module and core issue queues
drumm at delocalizedham.com
Tue Jul 3 08:15:02 UTC 2007
Lets take a step back.. what are the goals of project module and the
core issues queues? I would say the primary goal is to make good
releases of Drupal core.
We could take this goal and get to "issue queues should be short" by
saying that short issue queues indicate that Drupal has less issues
and is good, or that reviewers have less things to think about. Large
issue queues happen in all large open source projects. I think we
should focus on the bigger goal and make sure our thinking serves
And how do we measure this? We need to quantitatively show if we are
doing a good or bad job before we can be serious about fixing things.
We do have http://drupal.org/project/issues/statistics/drupal, but I
do not think it is useful. There are plenty of rough metrics that tell
us things, but no single number directly tells us when we have done
With goals in mind, how do we improve project module? How do we know
if the changes are good?
More information about the development