| [ << Introduction to contributing ] | [Top][Contents][Index][ ? ] | [ Quick start >> ] | ||
| [ < Introduction to contributing ] | [ Up : Introduction to contributing ] | [ Overview of work flow > ] | ||
1.1 Help us
We need you!
The LilyPond development team is quite small; we really want to get more people involved. Please consider helping your fellow LilyPond users by contributing!
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.
Simple tasks
No programming skills required!
- Mailing list support: answer questions from fellow users.
- Bug reporting: help users create proper Bug reports, and/or join the Bug Squad to organize Issues.
- Grand Regression Test Checking: verify that LilyPond works correctly by examining output of test snippets. Checking one snippet takes less than a minute!
- Documentation: small changes can be proposed by following the guidelines for Documentation suggestions.
- LilyPond Snippet Repository (LSR): create and fix snippets following the guidelines in 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 Quick start.
Contributors using Linux or FreeBSD may also use Lilydev, but if they prefer their own development environment, they should read Working with source code, and Compiling.
Begin by reading Summary for experienced developers.
- Documentation: for large changes, see Documentation work.
- Website: the website is built from the normal documentation source. See the info about documentation, and also Website work.
- Translations: see Translating the documentation, and Translating the website.
- Bugfixes or new features: the best way to begin is to join the Frogs, and read Programming work.
| [ << Introduction to contributing ] | [Top][Contents][Index][ ? ] | [ Quick start >> ] | ||
| [ < Introduction to contributing ] | [ Up : Introduction to contributing ] | [ Overview of work flow > ] | ||