---

Participating in LilyPond development

Mailing lists

Development is discussed on

lilypond-devel@gnu.org.

Browse the archives here.

Brilliant hackers

We want our patches cooked as follows:

• Follow the coding standards..
• No complete files, only diffs
• Unified diff (diff -u).
• ChangeLog entries
• patches for Documentation/topdocs/AUTHORS.texi and THANKS, if appropriate.

Our entry point is in main() (lily/main.cc). Grep the source code for TODO for inspiration. Good luck.

“But I am not brilliant!”

There is lots to do, and not all of it requires programming. Read our call for help for more information.

Report bugs

Providing high-quality bug reports is an excellent way to contribute to LilyPond. Please read our guidelines for reporting bugs.

Documentation

If you are interested in helping with the documentation, please read our pages about documentation suggestions and the LilyPond Snippet Repository.

Submitting patches

If you want to contribute fixes of any kind, use the following procedure

• Check out the latest sources via GIT at git.sv.gnu.org

      git clone git://git.sv.gnu.org/lilypond.git
      

• Make your changes,
• Create a patch:

        git commit -a 
        git-format-patch HEAD^
      

• Send an email to lilypond-devel@gnu.org, including or attaching the patch.

---