X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fcommunity.itexi;h=88f4eadd1747ccb6a968b67b4464120ac33f0a3c;hb=06d375bb4edf159cb8a9e2ef4a3b6712811cb010;hp=417c4b2415609e70809954dbdc73ede6270d5a80;hpb=08bb579c827a4f5e52dbd8028a71cce2e2133b0e;p=lilypond.git diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index 417c4b2415..88f4eadd17 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 +@node Community @unnumbered Community +@divClass{link-headings} @divClass{column-center-top} @subheading Interacting with the community @@ -18,14 +21,14 @@ @itemize @item -@ref{contact}: get help, discuss, and keep in touch! +@ref{Contact}: get help, discuss, and keep in touch! @item -@ref{tiny examples}: these are @emph{highly} recommended when +@ref{Tiny examples}: these are @emph{highly} recommended when discussing LilyPond. @item -@ref{bug reports}: something went wrong. +@ref{Bug reports}: something went wrong. @end itemize @divEnd @@ -36,13 +39,13 @@ discussing LilyPond. @itemize @item -@ref{help us}: your assistance is requested. +@ref{Help us}: your assistance is requested. @item -@ref{development}: for contributors and testers. +@ref{Development}: for contributors and testers. @item -@ref{authors}: the people who made LilyPond what it is today. +@ref{Authors}: the people who made LilyPond what it is today. @end itemize @divEnd @@ -53,30 +56,31 @@ discussing LilyPond. @itemize @item -@ref{publications}: what we wrote, and have had written about us. +@ref{Publications}: what we wrote, and have had written about us. @item -@ref{old news}: an archive. +@ref{Old news}: an archive. @end itemize @divEnd +@divEnd @divClass{hide} @menu -* contact:: -* tiny examples:: -* bug reports:: -* help us:: -* development:: -* authors:: -* publications:: -* old news:: +* Contact:: +* Tiny examples:: +* Bug reports:: +* Help us:: +* Development:: +* Authors:: +* Publications:: +* Old news:: @end menu @divEnd -@node contact +@node Contact @unnumberedsec Contact @@ -89,10 +93,10 @@ This mailing list is the main place for users to discuss and help each other. @quotation -@uref{http://mail.gnu.org/mailman/listinfo/lilypond-user, +@uref{http://lists.gnu.org/mailman/listinfo/lilypond-user, lilypond-user subscribe and info} -@uref{http://mail.gnu.org/archive/html/lilypond-user/, +@uref{http://lists.gnu.org/archive/html/lilypond-user/, user archive1} @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/, archive2} @@ -103,7 +107,21 @@ archive3} send to lilypond-user with gmane} @end quotation -@warning{When asking questions, please use @ref{tiny examples}!} +@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 @@ -115,7 +133,7 @@ Some level of support is provided on our IRC channel, @end example This channel has no public archive, so any question that may -be useful for others would better be posted to one of the mailing lists. +be useful for others would better be posted to one of the mailing lists. @html
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 @@ -396,174 +431,43 @@ account. @divEnd -@node help us +@node Help us @unnumberedsec Help us -@divClass{heading-center} -@heading We need you! - -The LilyPond development team is quite small; we really want to -get more people involved. Please consider helping us, even with -small tasks -- anything that you do will allow an experienced -developer to work on advanced tasks. +@divClass{column-center-top} +@helpusNeed @divEnd - @divClass{column-left-top} -@subheading Ways of contributing - -Many users ask @qq{I can't program; how can I help?} - @divClass{keep-bullets} -@subsubheading No source, no programming - -@sourceimage{logo-linux,,,} -@sourceimage{logo-freebsd,,,} -@sourceimage{logo-macosx,,,} -@sourceimage{logo-windows,,,} - -@itemize -@item -Mailist support: we have many users asking for him. - -@item -LilyPond Snippet Repository (LSR): create and fix snippets. See -@rcontrib{Adding and editing snippets}. - -@item -Bug reporting: our infrastructure for organizing bug reports only -requires a web browser. Please do not add bugs directly unless -you have learned how we like to handle such reports. See -@rcontrib{Issues}. - -@item -Discussions, reviews, and testing: the developers often ask for -feedback about new documentation, potential syntax changes, and -testing new features. We rarely receive as much feedback as we -would like; please consider responding to these requests! (even -if your only contribution is @qq{wow, looks great!}) - -@end itemize - -@subsubheading With source, no programming - -@sourceimage{logo-linux,,,} -@sourceimage{logo-freebsd,,,} -@sourceimage{logo-macosx,,,} -@sourceimage{logo-windows,,,} - -To get the source code, see @rcontrib{Starting with git}. - -@itemize -@item -Documentation: -@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 - -@subsubheading Programming - -@sourceimage{logo-linux,,,} -@sourceimage{logo-freebsd,,,} -@sourceimage{logo-macosx,,,} - -To the best of our knowledge, nobody has compiled LilyPond on -Windows. We have therefore created @emph{lilybuntu}, a custom -@emph{Ubuntu} variant configured for LilyPond development. This -runs inside a virtual machine, without disturbing the Windows -operating system. For more information, see -@rcontrib{Using a Virtual Machine to Compile LilyPond}. - -@itemize -@item -Bugfixes, new features: the best way to begin is to join the -Frogs. - -@end itemize +@helpusTasks @divEnd @divEnd - @divClass{column-right-top} -@subheading Projects - -@subsubheading Frogs - -Website and mailist: @uref{http://frogs.lilynet.net} - -The Frogs are simple 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 and mailist: TODO - -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 -@divClass{column-center-bottom} -@subheading Legalese -@divClass{legal} -All logos and product images are copyright and trademark -acknowledged. - -@logoLegalLinux - -@logoLegalFreeBSD - -@logoLegalMacOSX - -@logoLegalWindows - -@divEnd - -@divEnd - -@node development +@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 + @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 stable @ref{Download}, and read the stable +@ref{Manuals}.} @divEnd @@ -579,7 +483,7 @@ Development versions have an odd-numbered @q{minor} version number @divEnd -@divClass{column-left-bottom} +@divClass{column-left-top} @subheading Download Instructions for git and compiling are in the Contributor's Guide. @@ -613,122 +517,197 @@ the latest binary: @end quotation +@divEnd -@subheading Manuals - -@help {these need the automatic symlinks or something. Maybe even -a hard-coded url to lilypond.org/docs/2.13 or something??} -Learning: -@uref{lm-html, html} -@uref{lm-big-html, big html} -@uref{lm-pdf, pdf} +@divClass{column-right-top} +@subheading Contributor's Guide -Glossary: -@uref{mg-html, html} -@uref{mg-big-html, big html} -@uref{mg-pdf, pdf} +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. -Essay: -@uref{essay-html, html} -@uref{essay-big-html, big html} -@uref{essay-pdf, pdf} +@docLinksBare{Contributor's Guide, contributor, + @rcontribnamed{Top,Contributor's Guide}, + @manualDevelContributorSplit, + @manualDevelContributorBig, 500 kB, + @manualDevelContributorPdf, 2.8 MB} -Notation: -@uref{notation-html, html} -@uref{notation-big-html, big html} -@uref{notation-pdf, pdf} +@divEnd -Usage: -@uref{usage-html, html} -@uref{usage-big-html, big html} -@uref{usage-pdf, pdf} -Snippets: -@uref{snippets-html, html} -@uref{snippets-big-html, big html} -@uref{snippets-pdf, pdf} +@divClass{column-center-top} +@subheading Regression tests -Changes: -@uref{changes-html, html} -@uref{changes-big-html, big html} -@uref{changes-pdf, pdf} +@divClass{keep-bullets} -Internals: -@uref{internals-html, html} -@uref{internals-big-html, big html} -@uref{internals-pdf, pdf} +@ifclear web_version -@divEnd +@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}) -@divClass{column-right-top} -@subheading Contributors' Guide +@item +@uref{../../input/regression/abc2ly/collated-files.html, abc2ly tests}: +This release's abc2ly tests. +(@uref{../../input/regression/abc2ly/collated-files.pdf, pdf version}) -LilyPond development is a fairly complicated matter. LilyPond is -a large, (mostly) stable project. At any point in time, we have -between 5 and 25 active contributors. In order to help new -contributors, and to keep the whole system (mostly) stable, we -have written a manual for contributors. +@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 -@divClass{keep-bullets} -@itemize +@end ifclear -@item @uref{../contributor/index.html, Contributor's guide (split HTML)}: -the manual is split between many HTML pages. -@emph{(small download for each page)} +@ifset web_version +@subsubheading Development version -@item @uref{../contributor-big-page.html, Contributor's guide (big HTML)}: -read this manual as one huge HTML page. -@emph{(large single download, around 10? Mb)} +@itemize +@item @regtestDevel (@regtestDevelPdf{}) -@item @uref{../contributor.pdf, contributor.pdf}: -download as a PDF file. -@emph{(large single download, 2.8 Mb)} +@item @regtestDevelXml (@regtestDevelXmlPdf{}) -@c @item @uref{TODO, contributor.info}: -@c GNU info format for documentation. TODO, link broken. +@item @regtestDevelAbc (@regtestDevelAbcPdf{}) +@item @regtestDevelLilypondBook (@regtestDevelLilypondBookPdf{}) @end itemize -@divEnd -@divEnd -@divClass{column-right-bottom} -@subheading Regression tests +@subsubheading Stable version -@divClass{keep-bullets} @itemize +@item @regtestStable (@regtestStablePdf{}) -@item @uref{../../input/regression/collated-files.html, Regression tests}: -This releases' 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 releases' MusicXML tests. (also in -@uref{../input/regression/musicxml/collated-files.pdf, pdf}) +@item @regtestStableAbc (@regtestStableAbcPdf{}) + +@item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{}) +@end itemize +@end ifset -@item @uref{http://lilypond.org/test, Archive of regression tests}: -Comparisons beteween versions. +@subsubheading All versions + +@itemize +@item @uref{http://lilypond.org/test, Archive of regression tests}: +Comparisons between versions. @end itemize + @divEnd @divEnd -@node authors -@unnumberedsec Authors -@help{Under construction; this is not an accurate list!} -combo of: +@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 +@docLinkSplit{Learning,learning,@manualDevelLearningSplit} +@tab +@docLinkBig{Learning,learning,@manualDevelLearningBig} +@tab +@docLinkPdf{Learning,learning,@manualDevelLearningPdf} + +@item +@docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit} +@tab +@docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig} +@tab +@docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf} + +@item +@docLinkSplit{Essay,essay,@manualDevelEssaySplit} +@tab +@docLinkBig{Essay,essay,@manualDevelEssayBig} +@tab +@docLinkPdf{Essay,essay,@manualDevelEssayPdf} + +@headitem Regular + +@item +@docLinkSplit{Notation,notation,@manualDevelNotationSplit} +@tab +@docLinkBig{Notation,notation,@manualDevelNotationBig} +@tab +@docLinkPdf{Notation,notation,@manualDevelNotationPdf} + +@item +@docLinkSplit{Usage,usage,@manualDevelUsageSplit} +@tab +@docLinkBig{Usage,usage,@manualDevelUsageBig} +@tab +@docLinkPdf{Usage,usage,@manualDevelUsagePdf} + +@item +@docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit} +@tab +@docLinkBig{Snippets,snippets,@manualDevelSnippetsBig} +@tab +@docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf} + +@headitem Infrequent + +@item +@docLinkSplit{Web,web,@manualDevelWebSplit} +@tab +@docLinkBig{Web,web,@manualDevelWebBig} +@tab +@docLinkPdf{Web,web,@manualDevelWebPdf} + +@item +@docLinkSplit{Changes,changes,@manualDevelChangesSplit} +@tab +@docLinkBig{Changes,changes,@manualDevelChangesBig} +@tab +@docLinkPdf{Changes,changes,@manualDevelChangesPdf} + +@item +@docLinkSplit{Extending,extending,@manualDevelExtendingSplit} +@tab +@docLinkBig{Extending,extending,@manualDevelExtendingBig} +@tab +@docLinkPdf{Extending,extending,@manualDevelExtendingPdf} + +@item +@docLinkSplit{Internals,internals,@manualDevelInternalsSplit} +@tab +@docLinkBig{Internals,internals,@manualDevelInternalsBig} +@tab +@docLinkPdf{Internals,internals,@manualDevelInternalsPdf} + +@ifset web_version +@headitem Downloadable + +@item +@doctarballDevel +@end ifset + +@end multitable + +@divEnd +@divEnd -http://lilypond.org/web/about/thanks -Documentation/topdocs/AUTHORS.texi -and maybe: -http://lilypond.org/web/switch/ +@node Authors +@unnumberedsec Authors @divClass{column-left-top} @subheading Current Development Team @@ -739,7 +718,7 @@ http://lilypond.org/web/switch/ @divEnd @divClass{column-right-top} -@subheading Previous Development Team Positions +@subheading Previous Development Team @divClass{keep-bullets} @developersPrevious @@ -747,164 +726,102 @@ http://lilypond.org/web/switch/ @divEnd -@divClass{column-center-bottom} -@subheading Programming contributors +@divClass{column-center-top} +@subheading Current Contributors @divClass{keep-bullets} -@contributorsCore +@subsubheading Programming -@subheading Font contributors +@coreCurrent -@contributorsFont +@subsubheading Font -@subheading Documentation contributors +@fontCurrent -@contributorsDoc +@subsubheading Documentation -@subheading Support contributors +@docCurrent -@contributorsSupport +@subsubheading Bug squad -@subheading Translation contributors +@bugsquadCurrent -@contributorsTranslations +@subsubheading Support -@divEnd -@divEnd +@supportCurrent +@subsubheading Translation +@translationsCurrent -@node publications -@unnumberedsec Publications +@divEnd +@divEnd -@divClass{column-center-top} -@subheading What we wrote + +@divClass{column-center-bottom} +@subheading Previous Contributors @divClass{keep-bullets} -@itemize +@subsubheading Programming -@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}) +@corePrevious -@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}) +@subsubheading Font -@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}) +@fontPrevious -@end itemize +@subsubheading Documentation -@divEnd -@divEnd +@docPrevious +@c uncomment when we have any previous members -gp +@c @subsubheading Bug squad -@divClass{column-center-bottom} +@c @bugsquadCurrent -@subheading What others wrote +@subsubheading Support -@divClass{keep-bullets} -@itemize +@supportPrevious -@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 in detail engraving -capabilities of both pieces of software. The second article is an -instructive analysis of Rachmaninoff's Piano Prelude 6 engraving, -including comparisons with a reference hand-engraved edition. +@subsubheading Translation -@item -December 2005 +@translationsPrevious -Linux journal cover Linux Journal publishes an article titled -@uref{http://www.linuxjournal.com/article/8364, Make Stunning -Schenker Graphs with GNU LilyPond}. It is a in-depth but hands-on -feature article with crisp LilyPond graphics. Author Kris Shaffer -remarks “GNU Lilypond generates beautiful graphics that make -commercial alternatives seem second-rate.” +@divEnd +@divEnd -@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 `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 +@node Publications +@unnumberedsec Publications -A French article on the LilyPond 2.6 release appeared on -@uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}. +@divClass{column-center-top} +@subheading What we wrote about LilyPond -@item -October 2004 +@divClass{keep-bullets} -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.} +@include we-wrote.itexi -@item -July, August 2004 +@divEnd +@divEnd -Dave Phillips wrote an introductory article for 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 +@divClass{column-center-bottom} -Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on -linuxmusician.com (site now defunct). This interview was also -reviewed in a -@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=, -slashdot story}. +@subheading What people did with LilyPond -@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 -@node old news +@node Old news @unnumberedsec Old news +@include web/news-front.itexi + @include web/news.itexi