The LilyPond development team is quite small; we really want to
get more people involved. Please consider helping your fellow
-LilyPond users by contributing to development!
+LilyPond users by contributing!
-Even working on small tasks can have a big impact: taking care
-of them let experienced developers work on advanced tasks, instead
+Even working on small tasks can have a big impact: taking care of
+them allows experienced developers work on advanced tasks, instead
of spending time on those simple tasks.
@end macro
@macro helpusTasks
@subheading Simple tasks
+No source code or compiling required!
+
@itemize
@item
Mailing list support: answer questions from fellow users.
@end itemize
-@subheading Moderate tasks
+@subheading Advanced tasks
+
+These jobs generally require that you have the source code and can
+compile LilyPond.
+
+@warning{We suggest that contributors using Windows or MacOS X do
+@strong{not} attempt to set up their own development environment;
+instead, use Lilydev as discussed in @rcontrib{Quick start}.}
+
+Contributors using Linux or FreeBSD may also use Lilydev, but if
+they prefer their own development environment, they should read
+@rcontrib{Working with source code}, and @rcontrib{Compiling}.
-@warning{These jobs generally require that you have the program
-and documentation source files, but do not require a full
-development environment. See
-@rcontrib{Working with source code}.}
+Begin by reading @rcontrib{Summary for experienced developers}.
@itemize
@item
-Documentation: see
-@rcontrib{Documentation work}, and
-@rcontrib{Building documentation without compiling}.
+Documentation: for large changes, see
+@rcontrib{Documentation work}.
@item
Website: the website is built from the normal documentation
Translations: see @rcontrib{Translating the documentation}, and
@rcontrib{Translating the website}.
-@end itemize
-
-
-@subheading Complex tasks
-
-@warning{These jobs generally require that you have the source
-code and can compile LilyPond. See
-@rcontrib{Working with source code},
-and @rcontrib{Compiling}.
-@*@*
-We suggest that new contributors using Windows or MacOS X do
-@strong{not} attempt to set up their own development environment;
-instead, see
-@rcontrib{Using a Virtual Machine to Compile LilyPond}.
-}
-
-@itemize
@item
-Bugfixes, new features: the best way to begin is to join the
+Bugfixes or new features: the best way to begin is to join the
Frogs, and read @rcontrib{Programming work}.
@end itemize
@subsubheading Grand LilyPond Input Syntax Standardization
Website:
-
-@example
-@uref{http://lilypond.org/~graham/gliss}
-@end example
+@rcontrib{Grand LilyPond Input Syntax Standardization (GLISS)}.
GLISS will stabilize the (non-tweak) input syntax for the upcoming
LilyPond 3.0. After updating to 3.0, the input syntax for
We will have an extensive discussion period to determine the final
input specification.
-@warning{GLISS will start shortly after 2.14 is released.}
+@warning{GLISS will start shortly after 2.16 is released.}
@subsubheading Grand Organizing Project
-Website:
-
-@example
-@uref{http://lilypond.org/~graham/gop}
-@end example
+Website: @rcontrib{Grand Organization Project (GOP)}.
GOP will be our big recruiting drive for new contributors. We
desperately need to spread the development duties (including
@qq{simple tasks} which require no programming or interaction with
-soruce code!) over more people. We also need to document
+source code!) over more people. We also need to document
knowledge from existing developers so that it does not get lost.
Unlike most @qq{Grand Projects}, GOP is not about adding huge new
giving us a much more stable foundation so that we can move ahead
with larger tasks in the future.
-@warning{GOP will start shortly before or after the 2.14
-release.}
-
@end macro