Hey there developers, I've been using LilyPond for a few years, and feel it's high time to give something back. As suggested on the help-us page, I am writing to ask for guidance.
As background, though I am not a professional programmer, I do have a lot of coding experience, mostly in conjunction with my research, mostly in C and Python, and including some large projects. I am conversant with git (though I would not say expert). I don't know much scheme, but I am adept with Emacs Lisp. There are some important differences of course, but a lot of scheme code looks pretty familiar. I like to make things look good (including code!) and take documentation seriously. I have cloned the git repo, and yesterday successfully compiled everything. I would be interested in helping in any way that might use my skills to good effect. I do have one thing now that I'd like to contribute. As has been mentioned on the other lists, the documentation for \defineBarLine is a bit lacking in clarity and completeness. I've re-written the first couple of paragraphs about \defineBarLine in rhythms.itely to address this. Should I just submit the relevant text in lilypond-bugs? Or try to make a merge request? It's 3 or 4 paragraphs (450 words replacing 150), with appropriate texinfo markup. I look forward to your suggestions. -David
