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 to development!
12 Even working on small tasks can have a big impact: taking care
13 of them let experienced developers work on advanced tasks, instead
14 of spending time on those simple tasks.
20 @subheading Simple tasks
24 Mailing list support: answer questions from fellow users.
27 Bug reporting: help users create proper @rweb{Bug reports}, and/or
28 join the Bug Squad to organize @rcontrib{Issues}.
31 Documentation: small changes can be proposed by following the
32 guidelines for @rcontrib{Documentation suggestions}.
35 LilyPond Snippet Repository (LSR): create and fix snippets
36 following the guidelines in
37 @rcontrib{Adding and editing snippets}.
40 Discussions, reviews, and testing: the developers often ask for
41 feedback about new documentation, potential syntax changes, and
42 testing new features. Please contribute to these discussions!
46 @subheading Moderate tasks
48 @warning{These jobs generally require that you have the program
49 and documentation source files, but do not require a full
50 development environment. See
51 @rcontrib{Working with source code}.}
56 @rcontrib{Documentation work}, and
57 @rcontrib{Building documentation without compiling}.
60 Website: the website is built from the normal documentation
61 source. See the info about documentation, and also
62 @rcontrib{Website work}.
65 Translations: see @rcontrib{Translating the documentation}, and
66 @rcontrib{Translating the website}.
71 @subheading Complex tasks
73 @warning{These jobs generally require that you have the source
74 code and can compile LilyPond. See
75 @rcontrib{Working with source code},
76 and @rcontrib{Compiling}.
78 We suggest that new contributors using Windows or MacOS X do
79 @strong{not} attempt to set up their own development environment;
86 Bugfixes, new features: the best way to begin is to join the
87 Frogs, and read @rcontrib{Programming work}.
99 Website and mailing list:
102 @uref{http://frogs.lilynet.net}
105 The Frogs are ordinary LilyPond users who have chosen to get
106 involved in their favorite software's development. Fixing bugs,
107 implementing new features, documenting the source code: there's a
108 lot to be done, but most importantly: this is a chance for
109 everyone to learn more about LilyPond, about Free Software, about
110 programming... and to have fun. If you're curious about any of
111 it, then the word is: @emph{Join the Frogs!}
115 @subsubheading Grand LilyPond Input Syntax Standardization
120 @uref{http://lilypond.org/~graham/gliss}
123 GLISS will stabilize the (non-tweak) input syntax for the upcoming
124 LilyPond 3.0. After updating to 3.0, the input syntax for
125 untweaked music will remain stable for the foreseeable future.
127 We will have an extensive discussion period to determine the final
130 @warning{GLISS will start shortly after 2.14 is released.}
132 @subsubheading Grand Organizing Project
137 @uref{http://lilypond.org/~graham/gop}
140 GOP will be our big recruiting drive for new contributors. We
141 desperately need to spread the development duties (including
142 @qq{simple tasks} which require no programming or interaction with
143 source code!) over more people. We also need to document
144 knowledge from existing developers so that it does not get lost.
146 Unlike most @qq{Grand Projects}, GOP is not about adding huge new
147 features or completely redesigning things. Rather, it is aimed at
148 giving us a much more stable foundation so that we can move ahead
149 with larger tasks in the future.
151 @warning{GOP will start shortly before or after the 2.14