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
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}
@uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
info-lilypond subscribe and info}
-@uref{http://mail.gnu.org/archive/html/info-lilypond/,
+@uref{http://lists.gnu.org/archive/html/info-lilypond/,
info archive1}
@uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
archive2}
should be sent here.
@quotation
-@uref{http://mail.gnu.org/mailman/listinfo/lilypond-devel,
+@uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
lilypond-devel subscribe and info}
-@uref{http://mail.gnu.org/archive/html/lilypond-devel/,
+@uref{http://lists.gnu.org/archive/html/lilypond-devel/,
devel archive1}
@uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
archive2}
Bug-specific discussion takes place here.
@quotation
-@uref{http://mail.gnu.org/mailman/listinfo/bug-lilypond,
+@uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
bug-lilypond subscribe and info}
-@uref{http://mail.gnu.org/archive/html/bug-lilypond/,
+@uref{http://lists.gnu.org/archive/html/bug-lilypond/,
bug archive1}
@uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
archive2}
@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 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
-@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
+
@warning{These are @emph{unstable development} versions. If you
have the slightest doubt about how to use or install LilyPond, we
@divEnd
-@divClass{column-left-bottom}
+@divClass{column-left-top}
@subheading Download
Instructions for git and compiling are in the Contributor's Guide.
@end quotation
+@divEnd
-@subheading Manuals
-
-@divClass{keep-bullets}
-@itemize
-
-@item
-Learning:
-
-@manualDevelLearningSplit
-@* @manualDevelLearningBig
-@* @manualDevelLearningPdf
-
-@item
-Glossary:
-
-@manualDevelGlossarySplit
-@manualDevelGlossaryBig
+@divClass{column-right-top}
+@subheading Contributor's Guide
-@manualDevelGlossaryPdf
+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.
-@item
-Essay:
+@docLinksBare{Contributor's Guide, contributor,
+ @rcontribnamed{Top,Contributor's Guide},
+ @manualDevelContributorSplit,
+ @manualDevelContributorBig, 500 kB,
+ @manualDevelContributorPdf, 2.8 MB}
-@manualDevelEssaySplit
+@divEnd
-@manualDevelEssayBig
-@manualDevelEssayPdf
+@divClass{column-center-top}
+@subheading Regression tests
+@divClass{keep-bullets}
+@itemize
-@c separate introduction, regular, infrequent manuals
-@smallspace
+@ifclear web_version
@item
-Notation:
-
-@manualDevelNotationSplit
-
-@manualDevelNotationBig
-
-@manualDevelNotationPdf
+@uref{../../input/regression/collated-files.html, Regression tests}:
+This release's regtests.
+(@uref{../../input/regression/collated-files.pdf, pdf version})
@item
-Usage:
+@uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
+This release's musicXML tests.
+(@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
+@end ifclear
-@manualDevelUsageSplit
+@ifset web_version
+@item @regtestDevel (@regtestDevelPdf{})
-@manualDevelUsageBig
+@item @regtestDevelXml (@regtestDevelXmlPdf{})
-@manualDevelUsagePdf
+@item @regtestStable (@regtestStablePdf{})
-@item
-Snippets:
+@item @regtestStableXml (@regtestStableXmlPdf{})
+@end ifset
-@manualDevelSnippetsSplit
-
-@manualDevelSnippetsBig
-
-@manualDevelSnippetsPdf
+@item @uref{http://lilypond.org/test, Archive of regression tests}:
+Comparisons between versions.
-@c separate introduction, regular, infrequent manuals
-@smallspace
+@end itemize
+@divEnd
+@divEnd
-@item
-Web:
-@manualDevelWebSplit
-@manualDevelWebBig
+@divClass{column-center-bottom}
+@subheading Manuals
-@manualDevelWebPdf
+@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
-Changes:
-
-@manualDevelChangesSplit
-
-@manualDevelChangesBig
-
-@manualDevelChangesPdf
+@docLinkSplit{Learning,learning,@manualDevelLearningSplit}
+@tab
+@docLinkBig{Learning,learning,@manualDevelLearningBig}
+@tab
+@docLinkPdf{Learning,learning,@manualDevelLearningPdf}
@item
-Extend:
+@docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
+@tab
+@docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
+@tab
+@docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
-@manualDevelExtendingSplit
+@item
+@docLinkSplit{Essay,essay,@manualDevelEssaySplit}
+@tab
+@docLinkBig{Essay,essay,@manualDevelEssayBig}
+@tab
+@docLinkPdf{Essay,essay,@manualDevelEssayPdf}
-@manualDevelExtendingBig
+@headitem Regular
-@manualDevelExtendingPdf
+@item
+@docLinkSplit{Notation,notation,@manualDevelNotationSplit}
+@tab
+@docLinkBig{Notation,notation,@manualDevelNotationBig}
+@tab
+@docLinkPdf{Notation,notation,@manualDevelNotationPdf}
@item
-Internals:
+@docLinkSplit{Usage,usage,@manualDevelUsageSplit}
+@tab
+@docLinkBig{Usage,usage,@manualDevelUsageBig}
+@tab
+@docLinkPdf{Usage,usage,@manualDevelUsagePdf}
-@manualDevelInternalsSplit
+@item
+@docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
+@tab
+@docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
+@tab
+@docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
-@manualDevelInternalsBig
+@headitem Infrequent
-@manualDevelInternalsPdf
+@item
+@docLinkSplit{Web,web,@manualDevelWebSplit}
+@tab
+@docLinkBig{Web,web,@manualDevelWebBig}
+@tab
+@docLinkPdf{Web,web,@manualDevelWebPdf}
-@end itemize
-@divEnd
-@divEnd
+@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}
-@divClass{column-right-top}
-@subheading Contributor's Guide
+@item
+@docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
+@tab
+@docLinkBig{Internals,internals,@manualDevelInternalsBig}
+@tab
+@docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
-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.
+@ifset web_version
+@headitem Downloadable
-@warning{This manual is not intended to be read sequentially; new
-contributors should only read the sections which are relevant to
-them. For more information about different jobs, see
-@ref{Help us}.}
+@item
+@doctarballDevel
+@end ifset
-@docLinks{Contributor's Guide, contributor,
- @rcontribnamed{Top,Contributor's Guide},
- @manualDevelContributorSplit,
- @manualDevelContributorBig, 500 kB,
- @manualDevelContributorPdf, 2.8 MB}
+@end multitable
@divEnd
-
-
-@divClass{column-right-top}
-@subheading Frogs: new contributors
-
-The Frogs are a collection of new contributors being mentored in
-how to @qq{eat} (fix) bugs and add new features to LilyPond.
-Programmers unfamiliar with LilyPond are encouraged to send
-patches to the Frogs first for initial discussion and
-encouragement.
-
-Website and mailist: @uref{http://frogs.lilynet.net}
-
@divEnd
-@divClass{column-right-bottom}
-@subheading Regression tests
-@divClass{keep-bullets}
-@itemize
-@item @uref{../../input/regression/collated-files.html, Regression tests}:
-This release's tests. (also in
-@uref{../input/regression/collated-files.pdf, pdf})
-
-@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 @uref{http://lilypond.org/test, Archive of regression tests}:
-Comparisons between versions.
-
-@end itemize
-@divEnd
-@divEnd
@node Authors
@unnumberedsec Authors
@docCurrent
+@subsubheading Bug squad
+
+@bugsquadCurrent
+
@subsubheading Support
@supportCurrent
@docPrevious
+@c uncomment when we have any previous members -gp
+@c @subsubheading Bug squad
+
+@c @bugsquadCurrent
+
@subsubheading Support
@supportPrevious
The German LinuxUser magazine wrote an
@uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
-article about lilypond}.
+article about LilyPond}.
@item
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.
+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 writes
+@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).}
+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 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.”
+@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
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
+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
projects / lilypond.git / blobdiff