1 @c -*- coding: utf-8; mode: texinfo; -*-
2 @c This file is part of web/community.itexi and
3 @c contributor/introduction.itely
6 @subheading We need you!
8 The LilyPond development team is quite small; we really want to
9 get more people involved. Please consider helping your fellow
10 LilyPond users by contributing!
12 Even working on small tasks can have a big impact: taking care of
13 them allows experienced developers work on advanced tasks, instead
14 of spending time on those simple tasks.
20 @subheading Simple tasks
22 @strong{No programming skills} required!
26 Mailing list support: answer questions from fellow users.
29 Bug reporting: help users create proper @rweb{Bug reports}, and/or
30 join the Bug Squad to organize @rcontrib{Issues}.
33 @rcontrib{Grand Regression Test Checking}: verify that LilyPond works correctly
34 by examining output of test snippets. Checking one snippet takes less
38 Documentation: small changes can be proposed by following the
39 guidelines for @rcontrib{Documentation suggestions}.
42 LilyPond Snippet Repository (LSR): create and fix snippets
43 following the guidelines in
44 @rcontrib{Adding and editing snippets}.
47 Discussions, reviews, and testing: the developers often ask for
48 feedback about new documentation, potential syntax changes, and
49 testing new features. Please contribute to these discussions!
57 @subheading Advanced tasks
59 These jobs generally require that you have the source code and can
62 @warning{We suggest that contributors using Windows or MacOS X do
63 @strong{not} attempt to set up their own development environment;
64 instead, use Lilydev as discussed in @rcontrib{Quick start}.}
66 Contributors using Linux or FreeBSD may also use Lilydev, but if
67 they prefer their own development environment, they should read
68 @rcontrib{Working with source code}, and @rcontrib{Compiling}.
70 Begin by reading @rcontrib{Summary for experienced developers}.
74 Documentation: for large changes, see
75 @rcontrib{Documentation work}.
78 Website: the website is built from the normal documentation
79 source. See the info about documentation, and also
80 @rcontrib{Website work}.
83 Translations: see @rcontrib{Translating the documentation}, and
84 @rcontrib{Translating the website}.
87 Bugfixes or new features: the best way to begin is to join the
88 Frogs, and read @rcontrib{Programming work}.
100 Website and mailing list:
103 @uref{http://frogs.lilynet.net}
106 The Frogs are ordinary LilyPond users who have chosen to get
107 involved in their favorite software's development. Fixing bugs,
108 implementing new features, documenting the source code: there's a
109 lot to be done, but most importantly: this is a chance for
110 everyone to learn more about LilyPond, about Free Software, about
111 programming... and to have fun. If you're curious about any of
112 it, then the word is: @emph{Join the Frogs!}
116 @subsubheading Grand LilyPond Input Syntax Standardization
119 @rcontrib{Grand LilyPond Input Syntax Standardization (GLISS)}.
121 GLISS will stabilize the (non-tweak) input syntax for the upcoming
122 LilyPond 3.0. After updating to 3.0, the input syntax for
123 untweaked music will remain stable for the foreseeable future.
125 We will have an extensive discussion period to determine the final
128 @warning{GLISS will start shortly after 2.16 is released.}
130 @subsubheading Grand Organizing Project
132 Website: @rcontrib{Grand Organization Project (GOP)}.
134 GOP will be our big recruiting drive for new contributors. We
135 desperately need to spread the development duties (including
136 @qq{simple tasks} which require no programming or interaction with
137 source code!) over more people. We also need to document
138 knowledge from existing developers so that it does not get lost.
140 Unlike most @qq{Grand Projects}, GOP is not about adding huge new
141 features or completely redesigning things. Rather, it is aimed at
142 giving us a much more stable foundation so that we can move ahead
143 with larger tasks in the future.