My current nefarious plot...

[Elijah Newren <newren math utah edu>]

Okay, I brought this up last week[1] and no one put forth the effort to
stop me from carrying out my threats (in fact two people even goaded me
on), so I've now got something to increase your workload.  Haha!

I've put together a webpage with instructions on how someone can collect
a set of product-specific triaging guidelines to add to our triage
guide.[2]  I intend to post a link to these instructions along with a
short announcement to gnome-love.  My current draft is below, including
a link to the web page that I have put together.  Please read them and
critique/rewrite/flame.  Note that I will also attach to the
announcement some embarrassing things (which I'll make up) about any
active bugsquad member who doesn't read these and give me some kind of
feedback.[3]

--------- gnome-love announcement: ---------
Project needing volunteers without a steep learning curve...

The GNOME Bugsquad has a project (in addition to standard bug days-- see
http://developer.gnome.org/projects/bugsquad/triage/faq.html#II) for
which it is seeking volunteers.

Background for the Project
The purpose of the Bugsquad is to assist the maintainers of GNOME
software. This is done by triaging bugs so that major bugs do not go
unnoticed and so that maintainers can concentrate on the most important
bugs. (Also, although not officially part of its job, the Bugsquad also
serves as a starting point for many who want to become GNOME
developers.)  The Bugsquad is constantly recruiting new volunteers and
has put together some webpages to explain the general steps involved in
triaging bugs (see
http://developer.gnome.org/projects/bugsquad/triage/).  Those pages
concentrate on things that are common across all products.  However,
there are a number of things that are specific to each product and these
currently these tend to be learned by the Bugsquad members and the
general bugzilla community in a haphazard way..

The Task
We want a web page on product specific guidelines for triaging to be put
together and added to the current bugsquad web pages. This will require
contacting product maintainers and asking them for guidelines,
coordinating and keeping the bugsquad up to date and incorporating their
feedback (maintainers may not be familiar with the bugsquad webpages),
and organize the information and build it into a set of coherent web
pages that can serve as an addition to the current triage guide.

Required Knowledge
The person who volunteers to coordinate this effort should definitely be
familiar with the current triage guide (though it doesn't take long to
become familiar with it, so someone can volunteer for this job even if
they haven't yet read it). For other people assisting with the effort,
familiarity with the triage guide would be beneficial but (depending on
how the tasks are dividing up) not necessarily required.


If you're interested, please see
http://www.math.utah.edu/~newren/linux/random/product-specific-triaging.html
and send me an email.
--------- End announcement: ---------

--------- Footnotes:
[1]
http://mail.gnome.org/archives/gnome-bugsquad/2004-January/msg00030.html
[2]
http://www.math.utah.edu/~newren/linux/random/product-specific-triaging.html
[3] Okay, so this is a total lie, but I really do want some feedback.