lilypond-web: Help us
Help us
=======
We need you!
------------
Thank you for your interest in helping us — we would love to see you get
involved! Your contribution will help a large group of users make
beautifully typeset music.
Even working on small tasks can have a big impact: taking care of
them allows experienced developers work on advanced tasks, instead of
spending time on those simple tasks.
For a multi-faceted project like LilyPond, sometimes it’s tough to
know where to begin. In addition to the avenues proposed below, you can
send an e-mail to the lilypond-devel@gnu.org
(https://lists.gnu.org/mailman/listinfo/lilypond-devel) mailing list,
and we’ll help you to get started.
Simple tasks
------------
*No programming skills* required!
• Mailing list support: answer questions from fellow users.
DONTPRINTYET • Bug reporting: help users create proper 
(lilypond-web)Bug
reports, and/or join the Bug Squad to organize *noteDONTPRINTYET • Bug reporting: help users create proper (lilypond-web)Bug
reports, and/or join the Bug Squad to organize
(lilypond-contributor)Issues.
• Documentation: small changes can be proposed by following the
guidelines for (lilypond-contributor)Documentation
suggestions.
• LilyPond Snippet Repository (LSR): create and fix snippets
following the guidelines in (lilypond-contributor)Adding and
editing snippets.
• Discussions, reviews, and testing: the developers often ask for
feedback about new documentation, potential syntax changes, and
testing new features. Please contribute to these discussions!
Advanced tasks
--------------
These jobs generally require that you have the source code and can
compile LilyPond.
Note: We suggest that contributors using Windows or MacOS X do
*not* attempt to set up their own development environment;
instead, use Lilydev as discussed in
(lilypond-contributor)Quick start.
Contributors using Linux or FreeBSD may also use Lilydev, but if they
DONTPRINTYET prefer their own development environment, they should read
(lilypond-contributor)Working with source code, and *noteDONTPRINTYET prefer their own development environment, they should read
(lilypond-contributor)Working with source code, and
(lilypond-contributor)Compiling.
Begin by reading (lilypond-contributor)Summary for experienced
developers.
• Documentation: for large changes, see
(lilypond-contributor)Documentation work.
• Website: the website is built from the normal documentation source.
See the info about documentation, and also
(lilypond-contributor)Website work.
DONTPRINTYET • Translations: see (lilypond-contributor)Translating the
documentation, and *note(lilypond-contributor)Translating the
DONTPRINTYET • Translations: see (lilypond-contributor)Translating the
documentation, and (lilypond-contributor)Translating the
website.
• Bugfixes or new features: read
(lilypond-contributor)Programming work.
Info Catalog
lilypond-web: Bug reports
lilypond-web: Community
lilypond-web: Sponsoring