Issue 5167/4: Parser: let `assignment_id' return a symbol

[lilypond.git] / Documentation / included / helpus.itexi

diff --git a/Documentation/included/helpus.itexi b/Documentation/included/helpus.itexi
index 22ab4ea4fef0967a3f9507ab70b17b4ed143083e..96f697be4cb95bbf1767356cf3a62ac2fb4ca39f 100644 (file)
--- a/Documentation/included/helpus.itexi
+++ b/Documentation/included/helpus.itexi
@@ -5,21 +5,27 @@
 @macro helpusNeed
 @subheading We need you!
 
 @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!
+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 allows experienced developers work on advanced tasks, instead
 of spending time on those simple tasks.
 
 
 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
+@uref{https://lists.gnu.org/mailman/listinfo/lilypond-devel, lilypond-devel@@gnu.org}
+mailing list, and we'll help you to get started.
+

 @end macro
 
 
 @end macro
 
 

-@macro helpusTasks
+@macro helpusSimple

 @subheading Simple tasks
 
 @subheading Simple tasks
 

-No source code or compiling required!
+@strong{No programming skills} required!

 
 @itemize
 @item
 
 @itemize
 @item


@@ -45,6 +51,10 @@ testing new features.  Please contribute to these discussions!
 
 @end itemize
 
 
 @end itemize
 

+@end macro
+
+
+@macro helpusAdvanced

 @subheading Advanced tasks
 
 These jobs generally require that you have the source code and can
 @subheading Advanced tasks
 
 These jobs generally require that you have the source code and can


@@ -58,6 +68,8 @@ 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}.
 
 they prefer their own development environment, they should read
 @rcontrib{Working with source code}, and @rcontrib{Compiling}.
 

+Begin by reading @rcontrib{Summary for experienced developers}.
+

 @itemize
 @item
 Documentation: for large changes, see
 @itemize
 @item
 Documentation: for large changes, see


@@ -73,34 +85,16 @@ Translations: see @rcontrib{Translating the documentation}, and
 @rcontrib{Translating the website}.
 
 @item
 @rcontrib{Translating the website}.
 
 @item

-Bugfixes or new features: the best way to begin is to join the
-Frogs, and read @rcontrib{Programming work}.
+Bugfixes or new features: read @rcontrib{Programming work}.

 
 @end itemize
 
 @end macro
 
 
 @end itemize
 
 @end macro
 

-
+@ignore

 @macro helpusProjects
 @subheading Projects
 
 @macro helpusProjects
 @subheading Projects
 

-@subsubheading Frogs
-
-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,
-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
-it, then the word is: @emph{Join the Frogs!}
-
-

 
 @subsubheading Grand LilyPond Input Syntax Standardization
 
 
 @subsubheading Grand LilyPond Input Syntax Standardization
 


@@ -114,7 +108,7 @@ untweaked music will remain stable for the foreseeable future.
 We will have an extensive discussion period to determine the final
 input specification.
 
 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
 
 
 @subsubheading Grand Organizing Project
 


@@ -131,8 +125,7 @@ features or completely redesigning things.  Rather, it is aimed at
 giving us a much more stable foundation so that we can move ahead
 with larger tasks in the future.
 
 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 macro
 

+@end ignore