On Wed, Mar 2, 2011 at 7:35 AM, Ralph Palmer <[email protected]> wrote:
> > > On Tue, Feb 22, 2011 at 12:24 AM, Graham Percival < > [email protected]> wrote: > >> 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 >> >> _______________________________________________ >> bug-lilypond mailing list >> [email protected] >> http://lists.gnu.org/mailman/listinfo/bug-lilypond >> > > Greetings - > > To get myself up to speed on this thread would probably expend at least > half of my 15 minutes. > > I use gmail, and I set up my mail as closely as I could figure out how to > to Graham's suggested configuration. I delete all bug-ignore and > Sorry - hit the wrong button. So, delete all bug-answer and bug-ignore items. I then start with the oldest of the remaining emails. I delete anything with "issue nnnn" in the subject line. Anything else, I look to see if it's a simple discussion or an actual bug (or issue). If it's an issue, I try to add it as succinctly as I can as an issue. This morning, in 15 minutes, I was able to get rid of bug-answers and bug-ignore, delete about a half-dozen other emails from bug-current, submit one issue, start catching up on this thread, and writing this reply. I've just passed 25 minutes. I'm also often unsure whether to submit issues when there seems to be an ongoing discussion between two or more people. In that case, I usually cut to the chase (check the later emails in the thread) to see if it looks like the problem should be submitted as an issue (yet). I hope this explication helps, and I would appreciate an evaluation - that is, whether it seems I'm doing things in an appropriate fashion or not. Ralph _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
