* Ian Jackson <[EMAIL PROTECTED]> [060713 22:03]:
> Matt Zimmerman writes ("Re: Fundamental flaw in bug reporting system"):
> > We want users who don't know how to write a good bug report to become users
> > who do, not get discouraged and not contribute at
On Thu, Jul 13, 2006 at 08:44:57PM +0100, Ian Jackson wrote:
> I don't think picking a package and comparing bug reports like for
> like across two distributions is `anecdotal evidence'. Anecdotal
> evidence is statements like `well I tried to submit a bug report and
> was discouraged'.
Yes, I st
On Thu, Jul 13, 2006 at 08:45:27PM +0100, Ian Jackson wrote:
> Matt Zimmerman writes ("Re: Fundamental flaw in bug reporting system"):
> > We want users who don't know how to write a good bug report to become users
> > who do, not get discouraged and not contribute a
Matt Zimmerman writes ("Re: Fundamental flaw in bug reporting system"):
> We want users who don't know how to write a good bug report to become users
> who do, not get discouraged and not contribute at all.
This idea is based on the misapprehension that we are short of bug
re
Adam McKenna writes ("Re: Fundamental flaw in bug reporting system"):
> On Tue, Jul 11, 2006 at 05:16:52PM +0100, Ian Jackson wrote:
> > It works because it acts as a filter. Ability and willingness to
> > write a good bug report are correlated pretty strongly with abili
On Tue, 11 Jul 2006, Adam McKenna wrote:
> The amount of noise in the system is really a secondary concern if it leads
> to bugs getting reported faster and fixed faster.
I can state that noise in the BTS is a hindrance to my work, and causes less
bugs to be triaged and/or fixed by myself when I h
On Tue, Jul 11, 2006 at 05:16:52PM +0100, Ian Jackson wrote:
> If you really think this, please go and look at the bug reports filed
> against Ubuntu in the Launchpad bugtracker. For example, compare
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=apt
> with
> https://launchpad.net/distros/
On Tue, 11 Jul 2006, Matt Zimmerman wrote:
> We want users who don't know how to write a good bug report to become users
> who do, not get discouraged and not contribute at all.
Those who get discouraged so fast they won't even send an email directly to
the maintainer (yes, users do figure out how
On Tue, Jul 11, 2006 at 05:16:52PM +0100, Ian Jackson wrote:
> Adam McKenna writes ("Re: Fundamental flaw in bug reporting system"):
> > Frustrating the user could lead to an even poorer quality bug report than
> > would have been given in the first place.
>
>
Adam McKenna writes ("Re: Fundamental flaw in bug reporting system"):
> I don't think this logically follows.. I don't see how "inaccessibility"
> of the BTS would necessarily result in better quality bug reports.
If you really think this, please go and l
On Thu, Jun 29, 2006 at 11:30:33AM +0100, Ian Jackson wrote:
> The slight inaccessibility in the bug reporting facilies is an
> appropriate part of our approach to improving bug report quality.
I don't think this logically follows.. I don't see how "inaccessibility"
of the BTS would necessarily r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 28, 2006 at 02:54:09PM -0700, Michael Wheatley wrote:
> I would understand a steep learning curve but this is a catch 22 overhang.
>
> I am a complete newbie. The install went great and I have my command
> line. Then I spend hours trying
On Thu, Jun 29, 2006 at 11:30:33AM +0100, Ian Jackson wrote:
> Michael Wheatley writes ("Fundamental flaw in bug reporting system"):
> > I would understand a steep learning curve but this is a catch 22 overhang.
> >
> > I am a complete newbie. The install w
On Mon, Aug 28, 2006 at 02:54:09PM -0700, Michael Wheatley wrote:
> The fundamental problem is that a newbie lacks the understanding of
> the system or the patience that is needed to submit a bug
> report.
I hate to break it to you, but becoming an advanced user does not make
you more patient
On Thu, Jun 29, 2006 at 11:30:33AM +0100, Ian Jackson wrote:
> The slight inaccessibility in the bug reporting facilies is an
> appropriate part of our approach to improving bug report quality.
Right, but is "improving bug report quality" the aim of the bug
reporting? I believe it rather is "impro
"Michael Wheatley" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
I would understand a steep learning curve but this is a catch 22 overhang.
I am a complete newbie. The install went great and I have my command
line. Then I spend hours trying to find info on loading a GUI and the
On Thu, 29 Jun 2006, Evan Prodromou wrote:
> On Thu, 2006-29-06 at 11:30 +0100, Ian Jackson wrote:
> > I think that the difficulty of submitting a Debian bug report via the
> > BTS (which is after all a fairly minor challenge to anyone who can
> > read and understand documentation) provides a very
On Thu, 2006-29-06 at 11:30 +0100, Ian Jackson wrote:
> I think that the difficulty of submitting a Debian bug report via the
> BTS (which is after all a fairly minor challenge to anyone who can
> read and understand documentation) provides a very useful barrier
> against poor-quality bug reports.
On Thursday 29 June 2006 12:30, Ian Jackson wrote:
> The purpose of a bug report is to help the developers improve the
> software. There are times when a particular user lacks the capability
> (whether background knowledge or aptitude) to write a bug report that
> can serve that purpose. It is be
Michael Wheatley writes ("Fundamental flaw in bug reporting system"):
> I would understand a steep learning curve but this is a catch 22 overhang.
>
> I am a complete newbie. The install went great and I have my command
> line. Then I spend hours trying to find info on
I would understand a steep learning curve but this is a catch 22 overhang.
I am a complete newbie. The install went great and I have my command
line. Then I spend hours trying to find info on loading a GUI and the
closest I get is GNOME support telling me to "Click on the session
icon" but a
21 matches
Mail list logo
