Issue Triage
This is a working group focusing on triage for issues on Drupal.org. Triage is the activity of categorizing, updating and adding information to issues so developers know where their efforts are most needed. This group maintains guidelines for managing the issue queue, suggests targets for bug hunters, and connects people who are helping Drupal developers by doing triage.
As of December 2006, there are 1500 active issues in core and almost 10000 total active issues, giving the false impression that Drupal is buggy, unreliable and unresponsive. Join the ITWG to help counteract this!
Sessions on Community and Code Review Wanted For Drupalcon 2008
My name is Matthew Pare and I'm a Co-Chair for the "Community and Core" track for Drupalcon Boston 2008. Over the last couple of weeks we have been planning and brainstorming to make Drupalcon Boston 2008 the best Drupalcon to date! One of our recommended track session topics is "Code Review" and since your viewing this post on the Issue Triage group I thought you would be excellent candidates for submitting sessions on the topic.
x.y.z is no longer an issue target in Drupal 5.0
This message is cross-posted to the "issue tracking and software releases" group because of the 5.0 functionality that prompted me to write it,, but is primarily intended for the Issue Triage group. Perhaps I'm only groping for a larger audience -)
Now that Drupal.org is running 5.0 RC2 / HEAD, project.module has seen some great changes - among them is that "x.y.z" is no longer accepted as a version for issues.
Welcome to Issue Triage!
As it says in the group description:
As of December 2006, there are 1500 active issues in core and almost 10000 total active issues, giving the false impression that Drupal is buggy, unreliable and unresponsive. Join the ITWG to help counteract this!
... "ITWG" being the Issue Triage Working Group (copying the IETF is lame? yes). This is not a group for the developers who squash bugs; this is a group for the obsessive-compulsive types who don't want to contribute patches, but would like to help manage the issue queue. No one seems to be doing this at the moment, but it's a job that needs doing.
