Mailing list support: answer questions from fellow users.
@item
-Bug reporting: help users create proper @rweb{Bug reports}, and
-aid the Bug Team in handling @rcontrib{Issues}.
+Bug reporting: help users create proper @rweb{Bug reports}, and/or
+join the Bug Squad to organize @rcontrib{Issues}.
@item
Documentation: small changes can be proposed by following the
guidelines for @rcontrib{Documentation suggestions}.
@item
-LilyPond Snippet Repository (LSR): create and fix snippets. See
+LilyPond Snippet Repository (LSR): create and fix snippets
+following the guidelines in
@rcontrib{Adding and editing snippets}.
@item
@warning{These jobs generally require that you have the program
and documentation source files, but do not require a full
-development environment. See @rcontrib{Starting with Git}.}
+development environment. See
+@rcontrib{Working with source code}.}
@itemize
@item
@subheading Complex tasks
@warning{These jobs generally require that you have the source
-code and can compile LilyPond. See @rcontrib{Starting with Git},
-and @rcontrib{Compiling LilyPond}.}
-
-We suggest that new contributors using Windows use a virtual
-machine to run @emph{lilybuntu}. See
+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
@subsubheading Frogs
-Website and mailist: @uref{http://frogs.lilynet.net}
+Website and mailing list:
+
+@example
+@uref{http://frogs.lilynet.net}
+@end example
The Frogs are ordinary LilyPond users who have chosen to get
involved in their favorite software's development. Fixing bugs,
@subsubheading Grand LilyPond Input Syntax Standardization
-Website: @uref{http://lilypond.org/~graham/gliss}
+Website:
+
+@example
+@uref{http://lilypond.org/~graham/gliss}
+@end example
GLISS will stabilize the (non-tweak) input syntax for the upcoming
LilyPond 3.0. After updating to 3.0, the input syntax for
@subsubheading Grand Organizing Project
-Website: @uref{http://lilypond.org/~graham/gop}
+Website:
+
+@example
+@uref{http://lilypond.org/~graham/gop}
+@end example
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