1 @c -*- coding: utf-8; mode: texinfo; -*-
2 @c This file is part of FIXME
5 @subheading We need you!
7 The LilyPond development team is quite small; we really want to
8 get more people involved. Please consider helping your fellow
9 LilyPond users by contributing to development!
11 Even working on small tasks can have a big impact: taking care
12 of them let experienced developers work on advanced tasks, instead
13 of spending time on those simple tasks.
19 @subheading Simple tasks
23 Mailing list support: answer questions from fellow users.
26 Bug reporting: help users create proper @rweb{Bug reports}, and
27 aid the Bug Team in handling @rcontrib{Issues}.
30 Documentation: small changes can be proposed by following the
31 guidelines for @rcontrib{Documentation suggestions}.
34 LilyPond Snippet Repository (LSR): create and fix snippets. See
35 @rcontrib{Adding and editing snippets}.
38 Discussions, reviews, and testing: the developers often ask for
39 feedback about new documentation, potential syntax changes, and
40 testing new features. Please contribute to these discussions!
44 @subheading Moderate tasks
46 @warning{These jobs generally require that you have the program
47 and documentation source files, but do not require a full
48 development environment. See @rcontrib{Starting with Git}.}
53 @rcontrib{Documentation work}, and
54 @rcontrib{Building documentation without compiling LilyPond}.
57 Website: the website is built from the normal documentation
58 source. See the info about documentation, and also
59 @rcontrib{Website work}.
62 Translations: see @rcontrib{Translating the documentation}, and
63 @rcontrib{Translating the website}.
68 @subheading Complex tasks
70 @warning{These jobs generally require that you have the source
71 code and can compile LilyPond. See @rcontrib{Starting with Git},
72 and @rcontrib{Compiling LilyPond}.}
74 We suggest that new contributors using Windows use a virtual
75 machine to run @emph{lilybuntu}. See
76 @rcontrib{Using a Virtual Machine to Compile LilyPond}.
80 Bugfixes, new features: the best way to begin is to join the
81 Frogs, and read @rcontrib{Programming work}.
93 Website and mailist: @uref{http://frogs.lilynet.net}
95 The Frogs are ordinary LilyPond users who have chosen to get
96 involved in their favorite software's development. Fixing bugs,
97 implementing new features, documenting the source code: there's a
98 lot to be done, but most importantly: this is a chance for
99 everyone to learn more about LilyPond, about Free Software, about
100 programming... and to have fun. If you're curious about any of
101 it, then the word is: @emph{Join the Frogs!}
105 @subsubheading Grand LilyPond Input Syntax Standardization
107 Website: @uref{http://lilypond.org/~graham/gliss}
109 GLISS will stabilize the (non-tweak) input syntax for the upcoming
110 LilyPond 3.0. After updating to 3.0, the input syntax for
111 untweaked music will remain stable for the foreseeable future.
113 We will have an extensive discussion period to determine the final
116 @warning{GLISS will start shortly after 2.14 is released.}
118 @subsubheading Grand Organizing Project
120 Website: @uref{http://lilypond.org/~graham/gop}
122 GOP will be our big recruiting drive for new contributors. We
123 desperately need to spread the development duties (including
124 @qq{simple tasks} which require no programming or interaction with
125 soruce code!) over more people. We also need to document
126 knowledge from existing developers so that it does not get lost.
128 Unlike most @qq{Grand Projects}, GOP is not about adding huge new
129 features or completely redesigning things. Rather, it is aimed at
130 giving us a much more stable foundation so that we can move ahead
131 with larger tasks in the future.
133 @warning{GLISS will start shortly before or after the 2.14