Last week, esmerel and I wrote up the handbook for the Views' Bug Squad, and we did a bit of a soft launch, only immediately telling people on IRC. This turned out to be a good thing, because a bug on drupal.org prevented us from actually getting it going, and all of the drupal.org maintainers who could fix the bug were, unsurprisingly, busy on the redesign.

After a few days, the redesign calmed down a bit, and the bug was fixed and deployed. The Views' Bug Squad handbook is now live. It contains instructions on how to join and what is expected of people contributing to the Bug Squad.

In the week or so that we've had this thing live, it's already been a great success, there's been a lot of motion in the Views' issue queue. The open issue count is still over a thousand, but issues marked 'fixed' are not actually considered closed for two weeks. Hopefully in a week or so, fixed issues will start dropping out and that number will start to decrease.

Anyone who commented that they want to join, please visit the Views' Bug Squad handbook, and go and submit the issue.

(To the person who commented about contacting people who are working in the issue queue, if they're already using the issue queue a lot they should see the Join the Bug Squad issues and get pointed to the right place easily enough. I will not contact someone via their contact form cold to recruit them into this, that doesn't sit well with me).

Comments

This is a great idea! Hopefully it will get a lot of the issues closed up in the Views queue.

I was just thinking recently we need something like this for the Drupal core issue queue - especially the issues that come in for Drupal 6, since participants in the core queue rarely ever look at those. I think probably the same principles could apply, in terms of statuses.

Thank you for the easy-understandable and structured approach.

Add new comment