Re: abandoned bug reports

[Graham Percival]

On Mon, Feb 21, 2011 at 02:07:35PM +0200, Dmytro O. Redchuk wrote:
> On Sun 20 Feb 2011, 22:58 Graham Percival wrote:
> > * ^List-ID: LilyPond Bug Reports <bug-lilypond.gnu.org>
> > * @googlecode.com
> > 0bug-lilypond-ignore
> 
> ((i don't want to ignore those messages; let's assume i don't count reading
> them as bugsquadder's job))

Oh, I don't actually _ignore_ those messages... but I definitely
give them a different kind of attention than I give the remaining
emails to bug-lilypond.

> > Yes, absolutely!
> Would it be valid action to mark as invalid those issues which do not contain
> code or description? I doubt it would.

Yes, it would -- but leave that up to the Bug Meister or any
developers.  I mean, don't [1] spend your Bug Squad time looking
through issues and marking certain ones as invalid.

[1] we might add this as a Bug Squad duty at some point in the
future... but for now, don't spend time doing this.  I'd like to
have a whole month in which we don't lose any issues, and in which
bug squad members report that they don't have enough work to fill
15 minuets, before adding any new duties.

> > > Better reports are easier to deal with.
> > Of course -- and one way to get better reports is to reject bad
> > reports.  Don't say "oh well, maybe somebody else can handle
> > this".  Reply immediately to say "I'm sorry, but I cannot
> > understand this report".
> 
> Mmm.. Do you mention emails to bug-lilypond or "badly reported issues" in the
> tracker? Or both?-)

Your primary responsibility is handling emails to bug-lilypond.
If a "badly reported issue" gets onto the tracker, then leave that
for other people to clean up.  :)

Cheers,
- Graham