X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fcommunity.itexi;h=b31ea50a63c9c9863134412d10557cc740dc294b;hb=564a1793b951d6d4dff555c80dbfeb36374c3ac0;hp=25c9fa88b5496993d5474be408ac188ebb3a0a53;hpb=f115fc1bdeb3fdd356db670ef4fe3e6b9aee019c;p=lilypond.git diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index 25c9fa88b5..b31ea50a63 100644 --- a/Documentation/web/community.itexi +++ b/Documentation/web/community.itexi @@ -13,6 +13,7 @@ @node Community @unnumbered Community +@divClass{link-headings} @divClass{column-center-top} @subheading Interacting with the community @@ -63,6 +64,7 @@ discussing LilyPond. @end itemize @divEnd +@divEnd @divClass{hide} @menu @@ -107,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 @@ -152,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} @@ -170,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} @@ -344,9 +364,9 @@ 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: @@ -356,7 +376,6 @@ Here is an example of a good bug report: %% change the output at all! \version "2.10.0" -\paper@{ ragged-right=##t @} \relative c''' @{ c1 #(set-octavation 1) @@ -372,25 +391,39 @@ 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 -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. +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 @@ -431,10 +464,12 @@ account. @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 @@ -507,10 +542,10 @@ stable, we have written a manual for development tasks. @subheading Regression tests @divClass{keep-bullets} -@itemize @ifclear web_version +@itemize @item @uref{../../input/regression/collated-files.html, Regression tests}: This release's regtests. @@ -520,23 +555,54 @@ This release's regtests. @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 @regtestStableXml (@regtestStableXmlPdf{}) + +@item @regtestStableAbc (@regtestStableAbcPdf{}) + +@item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{}) +@end itemize @end ifset +@subsubheading All versions + +@itemize @item @uref{http://lilypond.org/test, Archive of regression tests}: Comparisons between versions. - @end itemize + @divEnd @divEnd @@ -645,9 +711,6 @@ manuals can be found at @url{http://lilypond.org}} @node Authors @unnumberedsec Authors -@help{Under construction; this is not an accurate list!} - - @divClass{column-left-top} @subheading Current Development Team @@ -735,143 +798,29 @@ manuals can be found at @url{http://lilypond.org}} @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. - -@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 +@subheading What people did with LilyPond -@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 @@ -879,5 +828,3 @@ issue CMS06. @include web/news-front.itexi @include web/news.itexi - -