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

introsmedia at lavabit.com introsmedia at lavabit.com
Sun Jun 3 18:37:38 CEST 2012


> From: Grant H. <sirgrant at member.fsf.org>
> Date: 2012/6/2
> Subject: [Trisquel-devel] Issue (Bug) reporting rules - 2nd draft. Seeking
> peer review/feedback.
> To: trisquel-devel at listas.trisquel.info
>
>
> Dear Trisquel devs and volunteers.
>
> Recently a thread on the forums/mailing list
> (https://trisquel.info/en/forum/solve-bugs-timeframe-depending-priority)
> 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.

Feedback for "Before Reporting a issue" section:

1. "Before Reporting a issue:" should be "Before reporting an issue:"

2. In item 3, "the issue" appears twice.

3. In item 3, if the issue tracker is not going to be used for support
requests, the "support request" category should be removed from the issue
creation form.

4. In item 3, "[...] then Trisquel" should be "[...] than Trisquel".

5. In item 4. I think you should consider removing the "feature request"
category until there's more manpower.

Feedback for "When Reporting a issue" section:

1. "When Reporting a issue:" should be "When reporting an issue:"

2. For item 2, a template would be useful. I was trying to come up with a
template for reporting my issues[1], but I really don't know what's what
developers find more helpful.

General feedback:

This information about bug reporting should be linked from the page that
appears when you click on "Create a new issue".


[1]. https://trisquel.info/en/issues/5018

--
sirgazil
http://introsmedia.wordpress.com/




More information about the Trisquel-devel mailing list