Getting Involved with openLilyLib

I think openLilyLib can become a valuable resource for anyone interested in producing musical documents, be it scores or texts, and I'm happy having set up this website to assemble the efforts. But as it turned out the project became considerably more extensive than expected, and I could really use any form and amount of assistance. Therefore I ask anybody interested in one or more of the topics presented here to consider joining in one way or the other.

There are several ways you can get involved and help developing openLilyLib.
The first and most "natural" way is to actually use the software and documents and provide feedback through the different issue trackers at GitHub or the openlilylib-user mailing list.

If you want to contribute more than just feedback then please get in touch with us directly by sending us an email to . Any help is appreciated, but below you'll find an – incomplete – summary of specific topics. Apart from that you may get inspired by skimming through the issue trackers.

If you think you can provide some insight on any LilyPond related issue, please don't hesitate to write a tutorial or a blog post about it. We are equally happy about a one-page HowTo or a thirty-page essay. Our tutorials are rendered in LaTeX, but if the contribution is interesting we will surely aid you with or can even do the conversion from word processor documents. If you can provide an already-finished document feel free to send it to us, in other cases it is recommended to get in touch before actually starting to write your document.

If you feel that you have ideas or existing functions that are in line with oll-lib's focus we are happy about your contribution. Currently there isn't much content in the library so you can't probably get the idea about its focus, though.

If you are experienced and/or interested in API documentation like with javadoc or comparable tools you are invited to join discussion about the basic design of that package. Please refer to the Wiki page. Later we'll implement the library/application with Python.
For the development of the \annotate function I could really use the help of someone with considerable Scheme experience. This part will also be developed with Python later.

The most natural way to assist in the development of lilyglyphs is to provide new predefined commands in order to increase the package's coverage. I can't to do much more than add commands I actually need for my own writing, so this is actually a perfect candidate for "crowd developing".
On the other hand there are still some more technical issues on the LaTeX and Python side where assistance would be highly appreciated.

Different from the other sub-projects musicexamples is actually aiming for a somewhat finished "1.0" release. The LaTeX package is nearly finished (except for some open issues), but I could use some more assistance in the development of the LilyPond part. An experienced Scheme coder would be welcome to help with writing functions to conditionally compile scores and do after-compilation cleanup.
Finally there will be some Python scripts that are needed to manage the LilyPond generated scores and keep them up to date. Work on this hasn't begun yet, any assistance would be highly appreciated.