X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fcommunity.itexi;h=d6918d1fbc0504526444c58c5edac755016938ac;hb=a1b2abcc60706154216e534e40411f75a93098a4;hp=70cca4e9f86216c0d6487e475a483968bd8223d5;hpb=0896f2cd5bc25632bb534f3ce0a795174c5ede3f;p=lilypond.git diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index 70cca4e9f8..d6918d1fbc 100644 --- a/Documentation/web/community.itexi +++ b/Documentation/web/community.itexi @@ -3,14 +3,17 @@ Translation of GIT committish: FILL-IN-HEAD-COMMITTISH When revising a translation, copy the HEAD committish of the - version that you are working on. See TRANSLATION for details. + version that you are working on. For details, see the Contributors' + Guide, node Updating translation committishes.. @end ignore -@include web/basic-authors.itexi +@include included/authors.itexi +@include included/helpus.itexi @node Community @unnumbered Community +@divClass{link-headings} @divClass{column-center-top} @subheading Interacting with the community @@ -61,6 +64,7 @@ discussing LilyPond. @end itemize @divEnd +@divEnd @divClass{hide} @menu @@ -105,6 +109,20 @@ send to lilypond-user with gmane} @warning{When asking questions, please use @ref{Tiny examples}!} +@subsubheading LilyPond Snippet Repository + +The LilyPond Snippet Repository is a large collection of +user-submitted examples, which can freely be copied and used +in your own works. See what other people have written, +and add your own! + +@example +@uref{http://lsr.dsi.unimi.it} +@end example + +Particularly instructive examples from LSR are included in our +official documentation, in @ref{Snippets}. + @subsubheading IRC @@ -150,7 +168,7 @@ Spanish mailing list} German forum} @uref{http://groups.google.com/group/lilypond-brasil, -Portugese group} +Portuguese group} @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr, French mailing list} @@ -168,7 +186,11 @@ Dutch forum} @subsubheading LilyPond Report The easiest way to keep touch is by reading our community -newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}. +newsletter, the LilyPond Report: + +@example +@uref{http://news.lilynet.net} +@end example @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org} @@ -342,23 +364,22 @@ free to add more information to that report.} If you have discovered a bug which is not listed, please help us by creating a bug report. -@warning{We only accept bug reports in the form of @ref{Tiny -examples}. We have very limited resources to deal with bug -reports, so any non-minimal example will be rejected. Almost +@warning{We only accept bug reports in the form of +@ref{Tiny examples}. We have very limited resources to deal with +bug reports, so any non-minimal example will be rejected. Almost every bug can be demonstrated in four notes or less!} Here is an example of a good bug report: @example -%% the octavation command doesn't -%% change the output at all! - -\version "2.10.0" -\paper@{ ragged-right=##t @} -\relative c''' @{ - c1 - #(set-octavation 1) - c1 +% Accidentals should be printed for only +% the first note in a tie, but this version +% prints flats on both notes. +\version "2.10.1" + +\relative c'' @{ + bes1 ~ + bes1 @} @end example @@ -370,180 +391,100 @@ Here is an example of a good bug report: Once you have verified that the issue is not already known and created a bug report, please send it to us! -Unfortunately there is a strict @qq{no top-posting} check on the -bug list, which is often incorrectly triggered by lilypond files. -To avoid this, please add +@divClass{keep-bullets} +@itemize + +@item +If you are subscribed to the @uref{mailto:bug-lilypond@@gnu.org, +bug-lilypond@@gnu.org} mailing list, send an email like normal. + +@item +If you are not subscribed, you can still post a bug report with +the +@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs, +gmane lilypond.bugs web interface}. + +However, there is a strict @qq{no top-posting} check on the gmane +interface, which is often incorrectly triggered by lilypond files. +To avoid this, please add: @example > I'm not top posting. @end example @noindent -(you must include the @code{>} ) to the top of your bug report. +(you @emph{must} include the @code{>} ) to the top of your bug +report. -@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs, -Post with the gmane lilypond.bugs interface}, or send an email to -@uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}. +@end itemize +@divEnd +@divEnd -Once your bug has been sent to the list, our Bug Meister will -examine the report. He may ask you for more information, or may -add the report to the tracker and let you know what the issue -number is. +@divClass{column-center-bottom} +@subheading Step 4: Wait for a response + +Once your bug has been sent to the list, our Bug Squad will +examine the report. Please allow up to 24 hours, as we have a +limited number of volunteers for this task. They may ask you for +more information, or may add the report to the tracker and let you +know what the issue number is. You may mark the bug so that you automatically receive emails when any activity on the bug occurs. This requires you have a google account. @divEnd +@divClass{column-center-bottom} +@subheading Optional help: show the desired behavior + +Once an issue has been added to the tracker, it can be very +helpful if we can see the desired output. Feel free to add input +code and/or images (possibly created with other tools) which +demonstrate what you think it should look like! + +@divEnd + + @node Help us @unnumberedsec Help us @divClass{column-center-top} -@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! - -Even working on small tasks can have a big impact: taking care -of them let experienced developers work on advanced tasks, instead -of spending time on those simple tasks. +@helpusNeed @divEnd - @divClass{column-left-top} -@subheading Simple tasks - @divClass{keep-bullets} - -@itemize -@item -Mailing list support: answer questions from fellow users. - -@item -Bug reporting: help users create proper @ref{Bug reports}, and aid -the Bug Team in handling @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 -@rcontrib{Adding and editing snippets}. - -@item -Discussions, reviews, and testing: the developers often ask for -feedback about new documentation, potential syntax changes, and -testing new features. Please contribute to these discussions! - -@end itemize - -@subheading Moderate tasks - -@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}.} - -@itemize -@item -Documentation: see -@rcontrib{Documentation work}, and -@rcontrib{Building documentation without compiling LilyPond}. - -@item -Website: the website is built from the normal documentation -source. See the info about documentation, and also -@rcontrib{Website work}. - -@item -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}. - -@end itemize +@helpusTasks @divEnd @divEnd - @divClass{column-right-top} -@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!} - - - -@help{not active yet; either comment out or begin these projects -before 2.14} - -@subsubheading Grand LilyPond Input Syntax Standardization - -Website: @uref{http://lilypond.org/~graham/gliss} - -GLISS will stabilize the (non-tweak) input syntax for the upcoming -LilyPond 3.0. After updating to 3.0, the input syntax for -untweaked music will remain stable for the foreseeable future. - -We will have an extensive discussion period to determine the final -input specification. - -@subsubheading Grand Organizing Project - -Website and mailist: TODO - -GOP is our big recruiting drive for new contributors. +@helpusProjects @divEnd -@ignore -@divClass{column-center-bottom} -@subheading Interested? - -@divEnd -@end ignore - - @node Development @unnumberedsec Development @divClass{heading-center} -@heading Development materials for LilyPond @versionDevel{} +@ifclear web_version + @heading Development for LilyPond @version +@end ifclear +@ifset web_version + @heading Development for LilyPond @versionDevel +@end ifset + +@c we normally don't allow named references, but in this case +@c it's good to emphasize the "stable" part. -gp @warning{These are @emph{unstable development} versions. If you have the slightest doubt about how to use or install LilyPond, we -urge you to use the stable @ref{Download}, and read the stable -@ref{Manuals}.} +urge you to use the @ref{Download, stable Download}, and read the +@ref{Manuals, stable Manuals}.} @divEnd @@ -599,12 +540,11 @@ the latest binary: @divClass{column-right-top} @subheading Contributor's Guide -LilyPond development is a fairly complicated matter. LilyPond is -a large, (mostly) stable project. In order to help new -contributors, and to keep the whole system (mostly) stable, we -have written a manual for contributors. +LilyPond development is a fairly complicated matter. In order to +help new contributors, and to keep the whole system (mostly) +stable, we have written a manual for development tasks. -@docLinks{Contributor's Guide, contributor, +@docLinksBare{Contributor's Guide, contributor, @rcontribnamed{Top,Contributor's Guide}, @manualDevelContributorSplit, @manualDevelContributorBig, 500 kB, @@ -613,27 +553,74 @@ have written a manual for contributors. @divEnd -@c if Downloads was a bit longer, and/or the CG was a bit shorter, -@c this would be great as column-right-top. -gp @divClass{column-center-top} @subheading Regression tests @divClass{keep-bullets} + +@ifclear web_version + +@itemize +@item +@uref{../../input/regression/collated-files.html, Regression tests}: +This release's regtests. +(@uref{../../input/regression/collated-files.pdf, pdf version}) + +@item +@uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}: +This release's musicXML tests. +(@uref{../../input/regression/musicxml/collated-files.pdf, pdf version}) + +@item +@uref{../../input/regression/abc2ly/collated-files.html, abc2ly tests}: +This release's abc2ly tests. +(@uref{../../input/regression/abc2ly/collated-files.pdf, pdf version}) + +@item +@uref{../../input/regression/lilypond-book/collated-files.html, lilypond-book tests}: +This release's lilypond-book tests. +(@uref{../../input/regression/lilypond-book/collated-files.pdf, pdf version}) +@end itemize + +@end ifclear + +@ifset web_version +@subsubheading Development version + +@itemize +@item @regtestDevel (@regtestDevelPdf{}) + +@item @regtestDevelXml (@regtestDevelXmlPdf{}) + +@item @regtestDevelAbc (@regtestDevelAbcPdf{}) + +@item @regtestDevelLilypondBook (@regtestDevelLilypondBookPdf{}) +@end itemize + +@subsubheading Stable version + @itemize +@item @regtestStable (@regtestStablePdf{}) -@item @uref{../../input/regression/collated-files.html, Regression tests}: -This release's tests. (also in -@uref{../input/regression/collated-files.pdf, pdf}) +@item @regtestStableXml (@regtestStableXmlPdf{}) -@item @uref{../../input/regression/musicxml/collated-files.html, -MusicXML Regression tests}: -This release's MusicXML tests. (also in -@uref{../input/regression/musicxml/collated-files.pdf, pdf}) +@item @regtestStableAbc (@regtestStableAbcPdf{}) -@item @uref{http://lilypond.org/test, Archive of regression tests}: -Comparisons between versions. +@item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{}) +@end itemize +@end ifset + + +@subsubheading All versions + +@itemize +@item @uref{http://lilypond.org/test, Comparisons between regression tests} + +@item @uref{http://lilypond.org/download/binaries/test-output/, +Archive of all regression tests} @end itemize + @divEnd @divEnd @@ -642,83 +629,98 @@ Comparisons between versions. @divClass{column-center-bottom} @subheading Manuals +@ifclear web_version +@warning{These manuals are for LilyPond @version{}; the latest +manuals can be found at @url{http://lilypond.org}} +@end ifclear + +@divClass{normal-table} @multitable @columnfractions .3 .3 .3 @headitem Introduction @item -@manualDevelLearningSplit +@docLinkSplit{Learning,learning,@manualDevelLearningSplit} @tab -@manualDevelLearningBig +@docLinkBig{Learning,learning,@manualDevelLearningBig} @tab -@manualDevelLearningPdf +@docLinkPdf{Learning,learning,@manualDevelLearningPdf} @item -@manualDevelGlossarySplit +@docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit} @tab -@manualDevelGlossaryBig +@docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig} @tab -@manualDevelGlossaryPdf +@docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf} @item -@manualDevelEssaySplit +@docLinkSplit{Essay,essay,@manualDevelEssaySplit} @tab -@manualDevelEssayBig +@docLinkBig{Essay,essay,@manualDevelEssayBig} @tab -@manualDevelEssayPdf +@docLinkPdf{Essay,essay,@manualDevelEssayPdf} @headitem Regular @item -@manualDevelNotationSplit +@docLinkSplit{Notation,notation,@manualDevelNotationSplit} @tab -@manualDevelNotationBig +@docLinkBig{Notation,notation,@manualDevelNotationBig} @tab -@manualDevelNotationPdf +@docLinkPdf{Notation,notation,@manualDevelNotationPdf} @item -@manualDevelUsageSplit +@docLinkSplit{Usage,usage,@manualDevelUsageSplit} @tab -@manualDevelUsageBig +@docLinkBig{Usage,usage,@manualDevelUsageBig} @tab -@manualDevelUsagePdf +@docLinkPdf{Usage,usage,@manualDevelUsagePdf} @item -@manualDevelSnippetsSplit +@docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit} @tab -@manualDevelSnippetsBig +@docLinkBig{Snippets,snippets,@manualDevelSnippetsBig} @tab -@manualDevelSnippetsPdf +@docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf} @headitem Infrequent @item -@manualDevelWebSplit +@docLinkSplit{Web,web,@manualDevelWebSplit} @tab -@manualDevelWebBig +@docLinkBig{Web,web,@manualDevelWebBig} @tab -@manualDevelWebPdf +@docLinkPdf{Web,web,@manualDevelWebPdf} @item -@manualDevelChangesSplit +@docLinkSplit{Changes,changes,@manualDevelChangesSplit} @tab -@manualDevelChangesBig +@docLinkBig{Changes,changes,@manualDevelChangesBig} @tab -@manualDevelChangesPdf +@docLinkPdf{Changes,changes,@manualDevelChangesPdf} @item -@manualDevelExtendingSplit +@docLinkSplit{Extending,extending,@manualDevelExtendingSplit} @tab -@manualDevelExtendingBig +@docLinkBig{Extending,extending,@manualDevelExtendingBig} @tab -@manualDevelExtendingPdf +@docLinkPdf{Extending,extending,@manualDevelExtendingPdf} @item -@manualDevelInternalsSplit +@docLinkSplit{Internals,internals,@manualDevelInternalsSplit} @tab -@manualDevelInternalsBig +@docLinkBig{Internals,internals,@manualDevelInternalsBig} @tab -@manualDevelInternalsPdf +@docLinkPdf{Internals,internals,@manualDevelInternalsPdf} + +@ifset web_version +@headitem Downloadable + +@item +@doctarballDevel +@end ifset @end multitable + +@divEnd @divEnd @@ -727,9 +729,6 @@ Comparisons between versions. @node Authors @unnumberedsec Authors -@help{Under construction; this is not an accurate list!} - - @divClass{column-left-top} @subheading Current Development Team @@ -763,6 +762,10 @@ Comparisons between versions. @docCurrent +@subsubheading Bug squad + +@bugsquadCurrent + @subsubheading Support @supportCurrent @@ -791,6 +794,11 @@ Comparisons between versions. @docPrevious +@c uncomment when we have any previous members -gp +@c @subsubheading Bug squad + +@c @bugsquadCurrent + @subsubheading Support @supportPrevious @@ -808,143 +816,29 @@ Comparisons between versions. @unnumberedsec Publications @divClass{column-center-top} -@subheading What we wrote +@subheading What we wrote about LilyPond @divClass{keep-bullets} -@itemize -@item -Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and -the Art of Shipping}. Forum Internacional Software Livre 2006 -(FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf, -PDF 1095k}) - -@item -Erik Sandberg, @emph{Separating input language and formatter in -GNU Lilypond}. Master's Thesis, Uppsala University, Department of -Information Technology March 2006. -(@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf, -PDF 750k}) - -@item -Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system -for automated music engraving}. Proceedings of the XIV Colloquium -on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003. -(@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k}) - -@end itemize +@include we-wrote.itexi @divEnd @divEnd - @divClass{column-center-bottom} -@subheading What others wrote - -@divClass{keep-bullets} -@itemize - -@item -September 2009 - -The German LinuxUser magazine wrote an -@uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel, -article about LilyPond}. - - -@item -February 2008 - -In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html, -articles on his personal site}, Andrew Hawryluk compares Finale -and LilyPond in general terms, and evaluates engraving -capabilities of both pieces of software in detail. The second -article is an instructive analysis of engraving issues in -Rachmaninoff's Piano Prelude No. 6, including comparisons with a -hand-engraved reference edition. +@subheading What people did with LilyPond -@item -June 2006 -@uref{http://distrowatch.com,DistroWatch} awards LilyPond and -@uref{http://distrowatch.com/weekly.php?issue=20060605,writes} -@qq{Ladies and Gentleman, we are pleased to announce that, based -on readers' requests, the DistroWatch May 2006 donation has been -awarded to LilyPond (@euro{}190.00) and Lua (US$250.00).} - -@item -December 2005 - -@uref{http://linuxjournal.com,Linux Journal} publishes an article -titled @uref{http://www.linuxjournal.com/article/8364, Make -Stunning Schenker Graphs with GNU LilyPond}. It is an in-depth -but hands-on feature article with crisp LilyPond graphics. Author -Kris Shaffer remarks @qq{GNU Lilypond generates beautiful graphics -that make commercial alternatives seem second-rate.} - -@item -August 20, 2005 - -The Belgian newspaper De Standaard investigates what drives Free -Software authors in an article titled -@uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6, -Delen van KENNIS zonder WINSTBEJAG} (Non-profit sharing of -knowlegde) in its @q{DS2 bijlage}. LilyPond is used as an example -and the article is interspersed with quotes from an email -interview with Jan Nieuwenhuizen. This marks LilyPond's first -appearance in mainstream printed press. - -@item -June 2005 - -A French article on the LilyPond 2.6 release appeared on -@uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}. - -@item -October 2004 - -The editors of Computer!Totaal, a Dutch computer magazine, -@uref{http://lilypond.org/web/images/computer-totaal.jpeg, -describe LilyPond} in the October 2004 issue as: @qq{Wonderful -free (open source) software [..] The sheet music produced by -LilyPond is exceptionally pretty [..] a very powerful system that -can do almost anything.} - -@item -July, August 2004 - -Dave Phillips wrote an introductory article for -@uref{http://linuxjournal.com,Linux Journal}: At -the sounding edge: LilyPond, parts -@uref{http://www.linuxjournal.com/article/7657, one} and -@uref{http://www.linuxjournal.com/article/7719, two}. - -@item -March 2004 - -Chris Cannam -@uref{http://www.all-day-breakfast.com/cannam/linux-musician/lilypond.html,interviewed} -Han-Wen Nienhuys and Jan Nieuwenhuizen on linuxmusician.com -(original site defunct). This interview was also reviewed in a -@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=, -slashdot story}. - -@item -February 2004 - -Jazz singer Gail Selkirk writes about -@uref{http://www.songbirdofswing.com/editorial_page/lilypond/, -Diving into LilyPond}. @qq{... you can make lead sheets or full -orchestral parts, and the results can be stunning.} -@uref{http://www.computermusic.co.uk/, Computer Music Special}, -issue CMS06. +@divClass{keep-bullets} -@end itemize +@include others-did.itexi @divEnd @divEnd +@contactUsAbout{academic papers} + @node Old news @unnumberedsec Old news @@ -952,5 +846,3 @@ issue CMS06. @include web/news-front.itexi @include web/news.itexi - -