Web: add regtest checking to helpus, final touches

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

diff --git a/Documentation/included/helpus.itexi b/Documentation/included/helpus.itexi
index 0bb2cffb02367c3d6cd6ece11aab3a96b358ba7b..9aa7be0631d81c3598df62a8e235e326791ee512 100644 (file)
--- a/Documentation/included/helpus.itexi
+++ b/Documentation/included/helpus.itexi
@@ -16,10 +16,10 @@ of spending time on those simple tasks.
 @end macro
 
 
-@macro helpusTasks
+@macro helpusSimple
 @subheading Simple tasks
 
-No source code or compiling required!
+@strong{No programming skills} required!
 
 @itemize
 @item
@@ -29,6 +29,11 @@ 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}.
@@ -45,6 +50,10 @@ testing new features.  Please contribute to these discussions!
 
 @end itemize
 
+@end macro
+
+
+@macro helpusAdvanced
 @subheading Advanced tasks
 
 These jobs generally require that you have the source code and can
@@ -58,6 +67,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}.
 
+Begin by reading @rcontrib{Summary for experienced developers}.
+
 @itemize
 @item
 Documentation: for large changes, see
@@ -80,7 +91,7 @@ Frogs, and read @rcontrib{Programming work}.
 
 @end macro
 
-
+@ignore
 @macro helpusProjects
 @subheading Projects
 
@@ -133,4 +144,5 @@ with larger tasks in the future.
 
 @end macro
 
+@end ignore