X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fincluded%2Fhelpus.itexi;h=96f697be4cb95bbf1767356cf3a62ac2fb4ca39f;hb=3f5d679ade0f797d5f907569656223d09b09d5db;hp=b850e9066d6a8113a0e4f91d3516f903f491f088;hpb=d73154f7252d084fd2d5d1a1af13ab4a805bf08c;p=lilypond.git diff --git a/Documentation/included/helpus.itexi b/Documentation/included/helpus.itexi index b850e9066d..96f697be4c 100644 --- a/Documentation/included/helpus.itexi +++ b/Documentation/included/helpus.itexi @@ -1,37 +1,47 @@ @c -*- coding: utf-8; mode: texinfo; -*- -@c This file is part of FIXME +@c This file is part of web/community.itexi and +@c contributor/introduction.itely @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 +@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 -@macro helpusTasks +@macro helpusSimple @subheading Simple tasks +@strong{No programming skills} required! + @itemize @item 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 @@ -41,17 +51,29 @@ testing new features. Please contribute to these discussions! @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{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}.} +@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}. + +Begin by reading @rcontrib{Summary for experienced developers}. @itemize @item -Documentation: see -@rcontrib{Documentation work}, and -@rcontrib{Building documentation without compiling LilyPond}. +Documentation: for large changes, see +@rcontrib{Documentation work}. @item Website: the website is built from the normal documentation @@ -62,49 +84,22 @@ source. See the info about documentation, and also 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{Starting with Git}, -and @rcontrib{Compiling LilyPond}.} - -We suggest that new contributors using Windows use a virtual -machine to run @emph{lilybuntu}. See -@rcontrib{Using a Virtual Machine to Compile LilyPond}. - -@itemize @item -Bugfixes, 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 - +@ignore @macro helpusProjects @subheading Projects -@subsubheading Frogs - -Website and mailist: @uref{http://frogs.lilynet.net} - -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 -Website: @uref{http://lilypond.org/~graham/gliss} +Website: +@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 @@ -113,16 +108,16 @@ untweaked music will remain stable for the foreseeable future. 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: @uref{http://lilypond.org/~graham/gop} +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 @@ -130,9 +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. -@warning{GLISS will start shortly before or after the 2.14 -release.} - @end macro +@end ignore