[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
desired behaviour
From: |
Keith OHara |
Subject: |
desired behaviour |
Date: |
Fri, 07 Jan 2011 19:49:11 -0800 |
User-agent: |
Opera Mail/11.00 (Win32) |
Dear Phil and the bug squadders,
Is the desired behaviour(*) of LilyPond information that you want to have in
the tracker?
I notice that items get fixed faster when the desired output is clear.
Knowing this, users have motivation to clearly describe what they want, and
might use LilyPond to construct an image of what they want, maybe producing a
workaround, which might be a prototype for the real solution.
With desired output defined, programmers can more easily tell if attacking
the issue would be an enjoyable addition to their hobby. The more often the
issue affects users, the more likely somebody will post desired output, thus
naturally making it more likely to be fixed sooner. Tinkerers can more easily
contribute to areas where they know the LilyPond engine, but not the
application area (e.g., me and the lyrics spacing issues). People other than
original bug-finder might be the ones who state the desired output.
Disagreement about just what is desired can be ironed out, if required, before
programming work is started.
-Keith
[*] Note my use of, to me, foreign spelling in a transparent attempt to curry
favor.
- desired behaviour,
Keith OHara <=
- Re: desired behaviour, Joe Neeman, 2011/01/08
- Re: desired behaviour, Phil Holmes, 2011/01/08
- Re: desired behaviour, Keith OHara, 2011/01/08
- Re: desired behaviour, Graham Percival, 2011/01/09
- Re: desired behaviour, Graham Percival, 2011/01/09
- Re: desired behaviour, Keith OHara, 2011/01/10
- Re: desired behaviour, Graham Percival, 2011/01/11
- Re: desired behaviour, Keith OHara, 2011/01/11
- Re: desired behaviour, Graham Percival, 2011/01/11