X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fcommunity.itexi;h=88f4eadd1747ccb6a968b67b4464120ac33f0a3c;hb=76c1654d8e6daceabb68d530729f87194fa49fed;hp=7df64eed64555380fe5ce3e428f22f2c35acb8e2;hpb=7bd6884c300f1a032b5b9f2e0b9ffa5a7938244a;p=lilypond.git diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index 7df64eed64..88f4eadd17 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} @@ -348,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: @@ -360,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) @@ -376,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 @@ -511,10 +540,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. @@ -524,23 +553,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 @@ -649,9 +709,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 @@ -742,28 +799,8 @@ manuals can be found at @url{http://lilypond.org}} @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 @@ -773,20 +810,10 @@ on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003. @subheading What people did with LilyPond -@help{Yeah, this doesn't look bad at all... there's 20-50 papers -out there that cite lilypond; somebody should find at least 3 or 4 -of them, so that it doesn't look so graham-specific.} @divClass{keep-bullets} -@itemize -@item -Graham Percival, Tosten Anders, and George Tzanetakis, -@emph{Generating Targeted Rhythmic Exercises for Music Students -with Constraint Satisfaction Programming}, International Computer -Music Conference 2008. - -@end itemize +@include others-did.itexi @divEnd @divEnd @@ -798,5 +825,3 @@ Music Conference 2008. @include web/news-front.itexi @include web/news.itexi - -