Merge branch 'master' into lilypond/translation

[lilypond.git] / Documentation / web / community.itexi

diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi
index 86a9b6d572a4aa32738b5cda8217d6fe0a7a60b9..a9ae0ed3fabc1bc4d42dacb5007262eb55a5743c 100644 (file)
--- a/Documentation/web/community.itexi
+++ b/Documentation/web/community.itexi
@@ -107,6 +107,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 owm 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
 
@@ -348,9 +362,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 +374,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 +389,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
@@ -649,9 +676,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
 
@@ -739,7 +763,7 @@ 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
@@ -771,13 +795,36 @@ on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
 
 @divClass{column-center-bottom}
 
-@subheading What others wrote
+@subheading What people did with LilyPond
+
 
 @divClass{keep-bullets}
 @itemize
 
 @item
-null
+Graham Percival, Tosten Anders, and George Tzanetakis,
+@emph{Generating Targeted Rhythmic Exercises for Music Students
+with Constraint Satisfaction Programming}, International Computer
+Music Conference 2008.
+
+@item
+Alexandre Tachard Passos, Marcos Sampaio, Pedro Kröger, Givaldo de Cidra,
+@emph{Functional Harmonic Analysis and Computational Musicology
+in Rameau}, Proceedings of the 12th Brazilian Symposium on Computer
+Music, 2009, pp. 207-210.
+
+@item
+Alberto Simões, Anália Lourenço and José João Almeida,
+@emph{Using Text Mining Techniques for Classical Music Scores Analysis},
+New Trends in Artificial Intelligence, 2007 J. Neves et al ed.
+
+@item
+
+Kevin C. Baird 2005,
+@emph{Real-time generation of music notation via audience interaction using
+python and GNU lilypond}. Proceedings of the 2005 Conference on New interfaces
+For Musical Expression (Vancouver, Canada, May 26 - 28, 2005).
+
 
 @end itemize