LilyPond Odd Jobs

[Graham Percival]

Here is a list of jobs that are available.  They have all been mentioned 
as things that I could do; I think they're all useful things to be done, 
but I don't have the resources to do them in the near future.

If you're interested in helping, please ask for more info.  If you'd 
like to help but aren't interested in anything from this list, please 
feel free to ask for something else to work on.  Trust me, I can find 
something else for you.  :)



Lilypond Odd Jobs
-----------------

- Cameron Horsburgh has agreed to monitor the lilypond-user maillist for 
documentation issues.


ONE-SHOT JOBS (estimated time: 30min - 2 hrs each)
- create example for automatic accidental examples that demonstrates 
everything
- add avoid-slur settings to everything in scm/script.scm
- preprocessor docs
- convert-ly bugs and tips
- musicxml: current features, limitations
- pdf chapter headings (in sidebar)
- special markup command examples (note head styles, rotation, etc: 
complicated stuff to show off some possibilities).  Maybe as LSR or 
input/test/ instead of manual.


TECHNICAL ABILITY REQUIRED
- integrate LSR:
http://lists.gnu.org/archive/html/lilypond-devel/2006-08/msg00146.html
(once LSR is done)
- clean up input/test/
- copy any useful examples from input/regression into input/test/


GENERAL EDITING / JANITORIAL:
- check manual for current correctness (does it make sense, is the info 
up-to-date, etc)
- verify anything in the "bugs" sections
- standardize # signs
http://lists.gnu.org/archive/html/lilypond-devel/2006-10/msg00180.html
- avoid future tense
http://lists.gnu.org/archive/html/lilypond-devel/2006-01/msg00076.html


ADVANCED
- So, another thing for the todo list
is to do through ly/music-functions-init.ly  and add a doc string to every
function listed.
- downloadable program reference (is it working?  if not, what does it 
need?)
- Some type of doc. that oulined the lexical construction of Lilypond 
would be helpful.