[Gstreamer-bugs] [Gstreamer] Request for bug-squad reporting guidelines

[Chris Davidson]

Hello, you're receiving this e-mail because the Gnome bug-squad has
started a new volunteer effort, and we would like some information from
you about your module. We are trying to gather information that the
bug-squad believes will decrease the workload of maintainers and also
increase the cooperation between them and the bug-squad.  This project
is to gather a list of product-specific triaging guidelines that will be
linked from the current bug-squad triage guide.

Requested information guidelines:

	We are looking for a short, bulleted list, of 4 items or less. One of
these items could be a link to another page with more detailed
guidelines, if you feel more elaboration is needed. If you would like
some other kind of special guidelines, please feel free to contact the
bug-squad about it (gnome-bugsquad at gnome.org).


Goal:

	To help the bug-squad assist you, as the maintainer, in fixing bug
reports, getting proper information from improperly filled bugs and
other circumstances that might arise for your particular module. This
will thus eliminate the need for you as a maintainer to check the
validity of reported bugs and give you more time to work on more
important things.

Here is an example guideline for the Gnome-Terminal module

Gnome-Terminal

-If a backtrace shows that it is crashing in function names starting
with "vte_" please reassign the bug to "vte" component 
-If the bug is a crasher or is related to fonts: 
-Ask the user to verify that they are not getting any warnings on stderr
from fontconfig or freetype


Once we receive all the information we will take it and upload it to the
web page. Once this is done we will email you and inform you as to where
the updated information is located. However, if you don't have any
information at the moment or are too busy, feel free to email the
bug-squad (gnome-bugsquad at gnome.org) at any time in the future. We're
also open to any suggestions you may have.