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
28 aid the Bug Squad in handling @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. See
36 @rcontrib{Adding and editing snippets}.
39 Discussions, reviews, and testing: the developers often ask for
40 feedback about new documentation, potential syntax changes, and
41 testing new features. Please contribute to these discussions!
45 @subheading Moderate tasks
47 @warning{These jobs generally require that you have the program
48 and documentation source files, but do not require a full
49 development environment. See
50 @rcontrib{Working with source code}.}
55 @rcontrib{Documentation work}, and
56 @rcontrib{Building documentation without compiling}.
59 Website: the website is built from the normal documentation
60 source. See the info about documentation, and also
61 @rcontrib{Website work}.
64 Translations: see @rcontrib{Translating the documentation}, and
65 @rcontrib{Translating the website}.
70 @subheading Complex tasks
72 @warning{These jobs generally require that you have the source
73 code and can compile LilyPond. See
74 @rcontrib{Working with source code},
75 and @rcontrib{Compiling}.
77 We suggest that new contributors using Windows or MacOS X do
78 @strong{not} attempt to set up their own development environment;
80 @rcontrib{Using a Virtual Machine to Compile LilyPond}.
85 Bugfixes, new features: the best way to begin is to join the
86 Frogs, and read @rcontrib{Programming work}.
98 Website and mailist: @uref{http://frogs.lilynet.net}
100 The Frogs are ordinary LilyPond users who have chosen to get
101 involved in their favorite software's development. Fixing bugs,
102 implementing new features, documenting the source code: there's a
103 lot to be done, but most importantly: this is a chance for
104 everyone to learn more about LilyPond, about Free Software, about
105 programming... and to have fun. If you're curious about any of
106 it, then the word is: @emph{Join the Frogs!}
110 @subsubheading Grand LilyPond Input Syntax Standardization
112 Website: @uref{http://lilypond.org/~graham/gliss}
114 GLISS will stabilize the (non-tweak) input syntax for the upcoming
115 LilyPond 3.0. After updating to 3.0, the input syntax for
116 untweaked music will remain stable for the foreseeable future.
118 We will have an extensive discussion period to determine the final
121 @warning{GLISS will start shortly after 2.14 is released.}
123 @subsubheading Grand Organizing Project
125 Website: @uref{http://lilypond.org/~graham/gop}
127 GOP will be our big recruiting drive for new contributors. We
128 desperately need to spread the development duties (including
129 @qq{simple tasks} which require no programming or interaction with
130 soruce code!) over more people. We also need to document
131 knowledge from existing developers so that it does not get lost.
133 Unlike most @qq{Grand Projects}, GOP is not about adding huge new
134 features or completely redesigning things. Rather, it is aimed at
135 giving us a much more stable foundation so that we can move ahead
136 with larger tasks in the future.
138 @warning{GOP will start shortly before or after the 2.14