[Trisquel-devel] Issue (Bug) reporting rules - 2nd draft. Seeking peer review/feedback.

Grant H. sirgrant at member.fsf.org
Sat Jun 2 21:50:30 CEST 2012

Dear Trisquel devs and volunteers.

Recently a thread on the forums/mailing list
has brought the attention of bug-fixes and issues to to the community.

Currently the longest standing open bug on the bug tracker is 3 years
and 29 weeks old.  We also have several bugs in the 2 year range.
However, many of these bugs are introduced into Trisquel by upstream or
are requests that should be handled upstream.  Thus I have attempted to
create "issue reporting policy" to help streamline the issue tracker.

I have written a short 2 page policy that people should consider before
reporting bugs to the issue tracker.  This would hopefully cut down on
clutter and bugs that could be fixed by others.  I have attached the
draft policy in ODT and PDF format for others to read.  Feedback is
requested hopefully this can help make the issue tracker a little easier
to manage.

*Grant H.
*Email: SirGrant at member.fsf.org
*Ask me for my GPG key
*I'm an FSF member -- Help us support software freedom!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Bugs.odt
Type: application/vnd.oasis.opendocument.text
Size: 17678 bytes
Desc: not available
URL: <http://listas.trisquel.info/pipermail/trisquel-devel/attachments/20120602/0aa9ee5e/attachment-0001.odt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Bugs.pdf
Type: application/pdf
Size: 309318 bytes
Desc: not available
URL: <http://listas.trisquel.info/pipermail/trisquel-devel/attachments/20120602/0aa9ee5e/attachment-0001.pdf>

More information about the Trisquel-devel mailing list