[ << Introduction to contributing ] | [Top][Contents][Index][ ? ] | [ Working with source code >> ] | ||
[ < 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 to development!
Even working on small tasks can have a big impact: taking care of them let experienced developers work on advanced tasks, instead of spending time on those simple tasks.
Simple tasks
- 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.
- 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!
Moderate tasks
Note: These jobs generally require that you have the program and documentation source files, but do not require a full development environment. See Working with source code.
- Documentation: see Documentation work, and Building documentation without compiling.
- 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.
Complex tasks
Note: These jobs generally require that you have the source
code and can compile LilyPond. See
Working with source code,
and
Compiling.
We suggest that new contributors using Windows or MacOS X do
not attempt to set up their own development environment;
instead, see
Using a Virtual Machine to Compile LilyPond.
- Bugfixes, new features: the best way to begin is to join the Frogs, and read Programming work.
Projects
Frogs
Website and mailing list:
http://frogs.lilynet.net
The Frogs are ordinary LilyPond users who have chosen to get involved in their favorite software’s development. Fixing bugs, implementing new features, documenting the source code: there’s a lot to be done, but most importantly: this is a chance for everyone to learn more about LilyPond, about Free Software, about programming... and to have fun. If you’re curious about any of it, then the word is: Join the Frogs!
Grand LilyPond Input Syntax Standardization
Website:
http://lilypond.org/~graham/gliss
GLISS will stabilize the (non-tweak) input syntax for the upcoming LilyPond 3.0. After updating to 3.0, the input syntax for untweaked music will remain stable for the foreseeable future.
We will have an extensive discussion period to determine the final input specification.
Note: GLISS will start shortly after 2.14 is released.
Grand Organizing Project
Website:
http://lilypond.org/~graham/gop
GOP will be our big recruiting drive for new contributors. We desperately need to spread the development duties (including “simple tasks” which require no programming or interaction with soruce code!) over more people. We also need to document knowledge from existing developers so that it does not get lost.
Unlike most “Grand Projects”, GOP is not about adding huge new features or completely redesigning things. Rather, it is aimed at giving us a much more stable foundation so that we can move ahead with larger tasks in the future.
Note: GOP will start shortly before or after the 2.14 release.
[ << Introduction to contributing ] | [Top][Contents][Index][ ? ] | [ Working with source code >> ] | ||
[ < Introduction to contributing ] | [ Up : Introduction to contributing ] | [ Overview of work flow > ] |