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 Documentation: small changes can be proposed by following the
34 guidelines for @rcontrib{Documentation suggestions}.
37 LilyPond Snippet Repository (LSR): create and fix snippets
38 following the guidelines in
39 @rcontrib{Adding and editing snippets}.
42 Discussions, reviews, and testing: the developers often ask for
43 feedback about new documentation, potential syntax changes, and
44 testing new features. Please contribute to these discussions!
52 @subheading Advanced tasks
54 These jobs generally require that you have the source code and can
57 @warning{We suggest that contributors using Windows or MacOS X do
58 @strong{not} attempt to set up their own development environment;
59 instead, use Lilydev as discussed in @rcontrib{Quick start}.}
61 Contributors using Linux or FreeBSD may also use Lilydev, but if
62 they prefer their own development environment, they should read
63 @rcontrib{Working with source code}, and @rcontrib{Compiling}.
65 Begin by reading @rcontrib{Summary for experienced developers}.
69 Documentation: for large changes, see
70 @rcontrib{Documentation work}.
73 Website: the website is built from the normal documentation
74 source. See the info about documentation, and also
75 @rcontrib{Website work}.
78 Translations: see @rcontrib{Translating the documentation}, and
79 @rcontrib{Translating the website}.
82 Bugfixes or new features: the best way to begin is to join the
83 Frogs, and read @rcontrib{Programming work}.
95 Website and mailing list:
98 @uref{http://frogs.lilynet.net}
101 The Frogs are ordinary LilyPond users who have chosen to get
102 involved in their favorite software's development. Fixing bugs,
103 implementing new features, documenting the source code: there's a
104 lot to be done, but most importantly: this is a chance for
105 everyone to learn more about LilyPond, about Free Software, about
106 programming... and to have fun. If you're curious about any of
107 it, then the word is: @emph{Join the Frogs!}
111 @subsubheading Grand LilyPond Input Syntax Standardization
114 @rcontrib{Grand LilyPond Input Syntax Standardization (GLISS)}.
116 GLISS will stabilize the (non-tweak) input syntax for the upcoming
117 LilyPond 3.0. After updating to 3.0, the input syntax for
118 untweaked music will remain stable for the foreseeable future.
120 We will have an extensive discussion period to determine the final
123 @warning{GLISS will start shortly after 2.16 is released.}
125 @subsubheading Grand Organizing Project
127 Website: @rcontrib{Grand Organization Project (GOP)}.
129 GOP will be our big recruiting drive for new contributors. We
130 desperately need to spread the development duties (including
131 @qq{simple tasks} which require no programming or interaction with
132 source code!) over more people. We also need to document
133 knowledge from existing developers so that it does not get lost.
135 Unlike most @qq{Grand Projects}, GOP is not about adding huge new
136 features or completely redesigning things. Rather, it is aimed at
137 giving us a much more stable foundation so that we can move ahead
138 with larger tasks in the future.