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 No source code or compiling 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!
48 @subheading Advanced tasks
50 These jobs generally require that you have the source code and can
53 @warning{We suggest that contributors using Windows or MacOS X do
54 @strong{not} attempt to set up their own development environment;
55 instead, use Lilydev as discussed in @rcontrib{Quick start}.}
57 Contributors using Linux or FreeBSD may also use Lilydev, but if
58 they prefer their own development environment, they should read
59 @rcontrib{Working with source code}, and @rcontrib{Compiling}.
61 Begin by reading @rcontrib{Summary for experienced developers}.
65 Documentation: for large changes, see
66 @rcontrib{Documentation work}.
69 Website: the website is built from the normal documentation
70 source. See the info about documentation, and also
71 @rcontrib{Website work}.
74 Translations: see @rcontrib{Translating the documentation}, and
75 @rcontrib{Translating the website}.
78 Bugfixes or new features: the best way to begin is to join the
79 Frogs, and read @rcontrib{Programming work}.
91 Website and mailing list:
94 @uref{http://frogs.lilynet.net}
97 The Frogs are ordinary LilyPond users who have chosen to get
98 involved in their favorite software's development. Fixing bugs,
99 implementing new features, documenting the source code: there's a
100 lot to be done, but most importantly: this is a chance for
101 everyone to learn more about LilyPond, about Free Software, about
102 programming... and to have fun. If you're curious about any of
103 it, then the word is: @emph{Join the Frogs!}
107 @subsubheading Grand LilyPond Input Syntax Standardization
110 @rcontrib{Grand LilyPond Input Syntax Standardization (GLISS)}.
112 GLISS will stabilize the (non-tweak) input syntax for the upcoming
113 LilyPond 3.0. After updating to 3.0, the input syntax for
114 untweaked music will remain stable for the foreseeable future.
116 We will have an extensive discussion period to determine the final
119 @warning{GLISS will start shortly after 2.16 is released.}
121 @subsubheading Grand Organizing Project
123 Website: @rcontrib{Grand Organization Project (GOP)}.
125 GOP will be our big recruiting drive for new contributors. We
126 desperately need to spread the development duties (including
127 @qq{simple tasks} which require no programming or interaction with
128 source code!) over more people. We also need to document
129 knowledge from existing developers so that it does not get lost.
131 Unlike most @qq{Grand Projects}, GOP is not about adding huge new
132 features or completely redesigning things. Rather, it is aimed at
133 giving us a much more stable foundation so that we can move ahead
134 with larger tasks in the future.