@macro helpusNeed
@subheading We need you!
-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!
+Thank you for your interest in helping us --- we would love to see
+you get involved! Your contribution will help a large group of users
+make beautifully typeset music.
-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.
+For a multi-faceted project like LilyPond, sometimes it's tough to know
+where to begin. In addition to the avenues proposed below, you can send
+an e-mail to the @email{mike@@mikesolomon.org, Frog meister}
+letting him know your skill set and asking how you can help or proposing a
+project. He'll be able to give you guidance on how to get started.
+
@end macro
-@macro helpusTasks
+@macro helpusSimple
@subheading Simple tasks
+@strong{No programming skills} required!
+
@itemize
@item
Mailing list support: answer questions from fellow users.
Bug reporting: help users create proper @rweb{Bug reports}, and/or
join the Bug Squad to organize @rcontrib{Issues}.
+@item
+@rcontrib{Grand Regression Test Checking}: verify that LilyPond works correctly
+by examining output of test snippets. Checking one snippet takes less
+than a minute!
+
@item
Documentation: small changes can be proposed by following the
guidelines for @rcontrib{Documentation suggestions}.
@end itemize
-@subheading Moderate tasks
+@end macro
+
+
+@macro helpusAdvanced
+@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{Lilybuntu}.
-}
-
-@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
@end macro
-
+@ignore
@macro helpusProjects
@subheading Projects
implementing new features, documenting the source code: there's a
lot to be done, but most importantly: this is a chance for
everyone to learn more about LilyPond, about Free Software, about
-programming... and to have fun. If you're curious about any of
+programming@dots{} and to have fun. If you're curious about any of
it, then the word is: @emph{Join the Frogs!}
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
giving us a much more stable foundation so that we can move ahead
with larger tasks in the future.
-@warning{GOP will start shortly after the 2.14 release.}
-
@end macro
+@end ignore
projects / lilypond.git / blobdiff