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 Thank you for your interest in helping us --- we would love to see
9 you get involved! Your contribution will help a large group of users
10 make beautifully typeset music.
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.
16 For a multi-faceted project like LilyPond, sometimes it's tough to know
17 where to begin. In addition to the avenues proposed below, you can send
19 @uref{https://lists.gnu.org/mailman/listinfo/lilypond-devel, lilypond-devel@@gnu.org}
20 mailing list, and we'll help you to get started.
26 @subheading Simple tasks
28 @strong{No programming skills} required!
32 Mailing list support: answer questions from fellow users.
35 Bug reporting: help users create proper @rweb{Bug reports}, and/or
36 join the Bug Squad to organize @rcontrib{Issues}.
39 Documentation: small changes can be proposed by following the
40 guidelines for @rcontrib{Documentation suggestions}.
43 LilyPond Snippet Repository (LSR): create and fix snippets
44 following the guidelines in
45 @rcontrib{Adding and editing snippets}.
48 Discussions, reviews, and testing: the developers often ask for
49 feedback about new documentation, potential syntax changes, and
50 testing new features. Please contribute to these discussions!
58 @subheading Advanced tasks
60 These jobs generally require that you have the source code and can
63 @warning{We suggest that contributors using Windows or MacOS X do
64 @strong{not} attempt to set up their own development environment;
65 instead, use Lilydev as discussed in @rcontrib{Quick start}.}
67 Contributors using Linux or FreeBSD may also use Lilydev, but if
68 they prefer their own development environment, they should read
69 @rcontrib{Working with source code}, and @rcontrib{Compiling}.
71 Begin by reading @rcontrib{Summary for experienced developers}.
75 Documentation: for large changes, see
76 @rcontrib{Documentation work}.
79 Website: the website is built from the normal documentation
80 source. See the info about documentation, and also
81 @rcontrib{Website work}.
84 Translations: see @rcontrib{Translating the documentation}, and
85 @rcontrib{Translating the website}.
88 Bugfixes or new features: read @rcontrib{Programming work}.
99 @subsubheading Grand LilyPond Input Syntax Standardization
102 @rcontrib{Grand LilyPond Input Syntax Standardization (GLISS)}.
104 GLISS will stabilize the (non-tweak) input syntax for the upcoming
105 LilyPond 3.0. After updating to 3.0, the input syntax for
106 untweaked music will remain stable for the foreseeable future.
108 We will have an extensive discussion period to determine the final
111 @warning{GLISS will start shortly after 2.16 is released.}
113 @subsubheading Grand Organizing Project
115 Website: @rcontrib{Grand Organization Project (GOP)}.
117 GOP will be our big recruiting drive for new contributors. We
118 desperately need to spread the development duties (including
119 @qq{simple tasks} which require no programming or interaction with
120 source code!) over more people. We also need to document
121 knowledge from existing developers so that it does not get lost.
123 Unlike most @qq{Grand Projects}, GOP is not about adding huge new
124 features or completely redesigning things. Rather, it is aimed at
125 giving us a much more stable foundation so that we can move ahead
126 with larger tasks in the future.