1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: 6671c51302bd71216a7d4c698c475e2abf0d78b4
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. For details, see the Contributors'
7 Guide, node Updating translation committishes..
10 @c This file is part of web/community.itexi and
11 @c contributor/introduction.itely
14 @subheading We need you!
16 Thank you for your interest in helping us --- we would love to see
17 you get involved! Your contribution will help a large group of users
18 make beautifully typeset music.
20 Even working on small tasks can have a big impact: taking care of
21 them allows experienced developers work on advanced tasks, instead
22 of spending time on those simple tasks.
24 For a multi-faceted project like LilyPond, sometimes it's tough to know
25 where to begin. In addition to the avenues proposed below, you can send
27 @uref{https://lists.gnu.org/mailman/listinfo/lilypond-devel, lilypond-devel@@gnu.org}
28 mailing list, and we'll help you to get started.
34 @subheading Simple tasks
36 @strong{No programming skills} required!
40 Mailing list support: answer questions from fellow users.
43 Bug reporting: help users create proper @rweb{Bug reports}, and/or
44 join the Bug Squad to organize @rcontrib{Issues}.
47 Documentation: small changes can be proposed by following the
48 guidelines for @rcontrib{Documentation suggestions}.
51 LilyPond Snippet Repository (LSR): create and fix snippets
52 following the guidelines in
53 @rcontrib{Adding and editing snippets}.
56 Discussions, reviews, and testing: the developers often ask for
57 feedback about new documentation, potential syntax changes, and
58 testing new features. Please contribute to these discussions!
66 @subheading Advanced tasks
68 These jobs generally require that you have the source code and can
71 @warning{We suggest that contributors using Windows or MacOS X do
72 @strong{not} attempt to set up their own development environment;
73 instead, use Lilydev as discussed in @rcontrib{Quick start}.}
75 Contributors using Linux or FreeBSD may also use Lilydev, but if
76 they prefer their own development environment, they should read
77 @rcontrib{Working with source code}, and @rcontrib{Compiling}.
79 Begin by reading @rcontrib{Summary for experienced developers}.
83 Documentation: for large changes, see
84 @rcontrib{Documentation work}.
87 Website: the website is built from the normal documentation
88 source. See the info about documentation, and also
89 @rcontrib{Website work}.
92 Translations: see @rcontrib{Translating the documentation}, and
93 @rcontrib{Translating the website}.
96 Bugfixes or new features: read @rcontrib{Programming work}.
103 @macro helpusProjects
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.