Your message dated Thu, 6 Jan 2011 00:51:03 +0800 with message-id <[email protected]> and subject line Re: Suggestion for a template for bug reports has caused the Debian Bug report #321623, regarding Suggestion for a template for bug reports to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 321623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321623 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: reportbug Version: 3.15 Severity: wishlist Hello, thanks for reportbug! it's been a while I was considering proposing some template for reportbug which would include questions such as the ones in the Flanagan Critical Incident technique[1]. After some discussion in #debtags-devel, we came out with this possible template to use in the body of the mail for 'novice' and 'advanced' levels in reportbug: -------------------------------------------------------------------- Please enter your report here, including all details you may find useful. <cursor initially placed here> If you think it's appropriate, you could also try to answer these questions: * What led up to the situation? * Exactly what did the you do or not do that was especially effective or ineffective? * What was the outcome or result of this action? * What outcome did you expect? -------------------------------------------------------------------- It would be interesting to include it, even temporarily as an experiment, to see if it helps. [1] 4 standard questions used in post-incident interviews to increase the quality of the data collected. -- Package-specific info: ** Environment settings: DEBEMAIL="[email protected]" EMAIL="[email protected]" ** /home/enrico/.reportbugrc: mode expert -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Versions of packages reportbug depends on: ii python2.3 2.3.5-6 An interactive high-level object-o Versions of packages reportbug recommends: ii python2.3-iconvcodec 1.1.2-1 Python universal Unicode codec, us -- no debconf information
--- End Message ---
--- Begin Message ---On Wed, Jan 05, 2011 at 12:54:38PM +0100, Sandro Tosi wrote: > On Sat, Aug 06, 2005 at 03:57:23PM +0200, Enrico Zini wrote: > > It would be interesting to include it, even temporarily as an > > experiment, to see if it helps. > > Do you still think this experiment is worth trying? For the novice levels maybe. I guess the bug should be something more like "running in novice mode, reportbug should use a message template to guide people to report detailed bugs". I've seen such guided templates in many BTSes and they generally look like a good idea for new users. It may make more sense to lift some tried and tested templates from other BTSes rather than to recreate our own, though. I'll attempt anyway to reword my original CIT[1]-based proposal in a clearer way ([2] has various other questions or wordings to pick from), although reusing some template from other BTSes has the added advantage of giving users some familiar environment: Please try to be detailed in your report, providing enough context to enable others to understand and reproduce the issue. Please consider: * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? [1] http://en.wikipedia.org/wiki/Critical_Incident_Technique [2] http://www.humanresources.hrvinet.com/questions-of-critical-incident-technique/ Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________ Reportbug-maint mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
