desired behaviour

[Keith OHara]

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.