On 12/16/05, Jeff Bailey <email address hidden> wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/3578
>
> Comment:
> Right. My issue here is more the end user experience. I haven't seen a
> bug page in a while (And congrats for this!), but it used to say "report
> a bug", and then not give any hints as to what I might report.
>
> It always felt like being the IT guy staring at the Windows errors that
> said "Talk to your administrator" =)
>
> What I imagine is something like "Hey! You've found a bug. Please
> report a bug saying that at @DTIME@, you got a system error with
> @SESSION_HANDLE@, at @URI@. We'll be able to track everything else down
> with that. Thanks for using Launchpad!"
>
> At that point I feel confident that I'm actually being helpful and
> usefully part of the process.
This is an interesting idea. It reminds me of the sample email the
WordPress developers offer up in the "Requirements" section:
Maybe it would be interesting to extend Jeff's idea into providing
copy-and-pasteable sample wording for the bug report with OOPS code
and provide a link directly to the Launchpad product +filebug page?
(In the hopefully not too distant future, +filebug would be a guided
filebug workflow to help reduce duplicate bug reports.)
On 12/16/05, Jeff Bailey <email address hidden> wrote: /launchpad. net/malone/ bugs/3578
> Public bug report changed:
> https:/
>
> Comment:
> Right. My issue here is more the end user experience. I haven't seen a
> bug page in a while (And congrats for this!), but it used to say "report
> a bug", and then not give any hints as to what I might report.
>
> It always felt like being the IT guy staring at the Windows errors that
> said "Talk to your administrator" =)
>
> What I imagine is something like "Hey! You've found a bug. Please
> report a bug saying that at @DTIME@, you got a system error with
> @SESSION_HANDLE@, at @URI@. We'll be able to track everything else down
> with that. Thanks for using Launchpad!"
>
> At that point I feel confident that I'm actually being helpful and
> usefully part of the process.
This is an interesting idea. It reminds me of the sample email the
WordPress developers offer up in the "Requirements" section:
http:// wordpress. org/about/ requirements/
(Wordpress provides excellent "feel-good documentation", IMHO. :)
Maybe it would be interesting to extend Jeff's idea into providing
copy-and-pasteable sample wording for the bug report with OOPS code
and provide a link directly to the Launchpad product +filebug page?
(In the hopefully not too distant future, +filebug would be a guided
filebug workflow to help reduce duplicate bug reports.)
Cheers,
--
Brad Bollenbach