← Back to team overview

launchpad-dev team mailing list archive

Re: Minor point about responding to bug reports.

 

On 2009-08-16 23:45:08 +0100, Tom Berger wrote:
> 2009/8/16 Karl Fogel <karl.fogel@xxxxxxxxxxxxx>:
[...]
> > I think you've got a very good point, in that I was overeager in adding
> > those new comments -- their "distraction cost" is too high.
> >
> > But in the first response to a report, it is still very worthwhile to
> > solicit coding help (except when it's obvious that the reporter is not a
> > good candidate).  That is, the real penalty here is the additional
> > email/comment.  Adding an additional "noise event" should be avoided,
> > you're absolutely right.  But in a response comment that one is making
> > anyway (such as the two Danilo made in those examples I gave), it's
> > useful to follow the https://dev.launchpad.net/BugHandling guidelines.
> >
> > (Maybe that's what you were saying too?  I wasn't sure.)
> 
> Yes, I agree. If you're already making a comment describing how to a
> the bug, and are offering help to anyone wishing to fix it, the format
> you suggested indeed looks optimal. I'll definitely make use of it in
> such cases.

Perhaps one could encourage the use of the "mentorship" feature LP
offers and people willing to help/advice should add themselves as
mentors to the bug.

And add a list (or link to a list) with bugs which have mentoring
available to some prominent place.
(Unfortunately it doesn't seem to be possible to search for bugs with
mentorship available).

Michael



Follow ups

References