lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GOP pre-planning: Frog bugfixing


From: Valentin Villenave
Subject: Re: GOP pre-planning: Frog bugfixing
Date: Thu, 11 Dec 2008 20:41:55 +0100

2008/12/11 Graham Percival <address@hidden>:
> LilyPond Frogs
>
> No, this isn't my new name for the French translation team.  :)

Oh, I thought it was.

> The idea behind Frogs is simple: each person will fix an average
> of one bug per week.  You can either fix an existing bug, or
> report a new bug and fix it.  We won't quibble over the severity
> of the bug; if a new Frog (Tadpole? ;)  is only comfortable fixing
> "program errors" or similar false warning messages, those will
> still count towards his "1 bug per week" average.  If you feel
> skilled and ambitious, go ahead and fix the dreaded #34 in a
> week.  :)

You're missing one thing IMHO: feature requests (and, possibly
bounties). We have quite a few of these, and this requires
super-skilled and super-dedicated frogs, possibly working as a team
(like the awesome work that has been done recently on harp pedals).

As for bounties, it is a shame that everytime a person says "I'm
willing to throw a few bucks in" we can't be there to answer "you're
welcome, here's my paypal account" :)

I think we should have a list of feature request associated with
bounties, for everyone interested to be able to make the auction climb
a bit more. That could possibly encourage Frogs to dive into the Pond
;-)

> I'm hesitated slightly about proposing this since I'm not
> qualified to be the FrogMeister.  I have 3 or 4 candidates in
> mind, but I don't want to name names since I don't know if they're
> interested/willing.

I think we all can guess who you mean :-)

> As a final hint, any doc person who is willing to switch to being
> the FrogMeister has my enthusiastic support.  I know that I
> discouraged you guys from doing coding during GDP, but that
> fixed-term project is over, and fostering more code developers is
> more important now.  :)

I strongly agree.

Cheers,
Valentin




reply via email to

[Prev in Thread] Current Thread [Next in Thread]