@include web/basic-authors.itexi
-@node community
+@node Community
@unnumbered Community
@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
@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
@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
@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
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}
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 IRC
@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
<form action="http://webchat.freenode.net"
@subsubheading Other languages
@quotation
-@uref{http://es.groups.yahoo.com/group/lilypond-es,
-Spanish yahoo group}
+@uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
+Spanish mailing list}
@uref{http://www.lilypondforum.de/,
German forum}
@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}
@end quotation
@warning{Before sending a message to the bug list, please read our
-guidelines for @ref{bug reports}.}
+guidelines for @ref{Bug reports}.}
@divEnd
-@node tiny examples
+@node Tiny examples
@unnumberedsec Tiny examples
@divClass{column-center-top}
-@node bug reports
+@node Bug reports
@unnumberedsec Bug reports
@divClass{column-center-top}
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:
@divEnd
-@node help us
+@node Help us
@unnumberedsec Help us
-@divClass{heading-center}
-@heading We need you!
+@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 us, even with
-small tasks -- anything that you do will allow an experienced
-developer to work on advanced tasks.
+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.
@divEnd
@divClass{column-left-top}
-@subheading Ways of contributing
-
-Many users ask @qq{I can't program; how can I help?}
+@subheading Simple tasks
@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.
+Mailing list support: answer questions from fellow users.
@item
-LilyPond Snippet Repository (LSR): create and fix snippets. See
-@rcontrib{Adding and editing snippets}.
+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
-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}.
+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. 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!})
+testing new features. Please contribute to these discussions!
@end itemize
-@subsubheading With source, no programming
-
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}
-@sourceimage{logo-macosx,,,}
-@sourceimage{logo-windows,,,}
+@subheading Moderate tasks
-To get the source code, see @rcontrib{Starting with git}.
+@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:
+Documentation: see
+@rcontrib{Documentation work}, and
@rcontrib{Building documentation without compiling LilyPond}.
@item
@end itemize
-@subsubheading Programming
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}
-@sourceimage{logo-macosx,,,}
+@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}.}
-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
+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.
+Frogs, and read @rcontrib{Programming work}.
@end itemize
Website and mailist: @uref{http://frogs.lilynet.net}
-The Frogs are simple LilyPond users who have chosen to get
+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
@subsubheading Grand LilyPond Input Syntax Standardization
-Website and mailist: TODO
+Website: @uref{http://lilypond.org/~graham/gliss}
GLISS will stabilize the (non-tweak) input syntax for the upcoming
LilyPond 3.0. After updating to 3.0, the input syntax for
@divEnd
-@divClass{column-center-bottom}
-@subheading Legalese
-
-@divClass{legal}
-All logos and product images are copyright and trademark
-acknowledged.
-
-@logoLegalLinux
-@logoLegalFreeBSD
-
-@logoLegalMacOSX
-
-@logoLegalWindows
+@ignore
+@divClass{column-center-bottom}
+@subheading Interested?
@divEnd
+@end ignore
-@divEnd
-@node development
+@node Development
@unnumberedsec Development
-
@divClass{heading-center}
@heading Development materials for LilyPond @versionDevel{}
@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
@subheading Manuals
-@help {these need the automatic symlinks or something. Maybe even
-a hard-coded url to lilypond.org/docs/2.13 or something??}
+@divClass{keep-bullets}
+@itemize
+@item
Learning:
-@uref{lm-html, html}
-@uref{lm-big-html, big html}
-@uref{lm-pdf, pdf}
+@manualDevelLearningSplit
+@* @manualDevelLearningBig
+@* @manualDevelLearningPdf
+
+@item
Glossary:
-@uref{mg-html, html}
-@uref{mg-big-html, big html}
-@uref{mg-pdf, pdf}
+@manualDevelGlossarySplit
+@* @manualDevelGlossaryBig
+@* @manualDevelGlossaryPdf
+
+@item
Essay:
-@uref{essay-html, html}
-@uref{essay-big-html, big html}
-@uref{essay-pdf, pdf}
+@manualDevelEssaySplit
+@* @manualDevelEssayBig
+@* @manualDevelEssayPdf
+
+@c separate introduction, regular, infrequent manuals
+@smallspace
+
+@item
Notation:
-@uref{notation-html, html}
-@uref{notation-big-html, big html}
-@uref{notation-pdf, pdf}
+@manualDevelNotationSplit
+@* @manualDevelNotationBig
+@* @manualDevelNotationPdf
+
+@item
Usage:
-@uref{usage-html, html}
-@uref{usage-big-html, big html}
-@uref{usage-pdf, pdf}
+@manualDevelUsageSplit
+@* @manualDevelUsageBig
+@* @manualDevelUsagePdf
+
+@item
Snippets:
-@uref{snippets-html, html}
-@uref{snippets-big-html, big html}
-@uref{snippets-pdf, pdf}
+@manualDevelSnippetsSplit
+@* @manualDevelSnippetsBig
+@* @manualDevelSnippetsPdf
+
+@c separate introduction, regular, infrequent manuals
+@smallspace
+
+@item
+Web:
+
+@manualDevelWebSplit
+@* @manualDevelWebBig
+@* @manualDevelWebPdf
+
+@item
Changes:
-@uref{changes-html, html}
-@uref{changes-big-html, big html}
-@uref{changes-pdf, pdf}
+@manualDevelChangesSplit
+@* @manualDevelChangesBig
+@* @manualDevelChangesPdf
+
+@item
+Extend:
+
+@manualDevelExtendingSplit
+@* @manualDevelExtendingBig
+@* @manualDevelExtendingPdf
+
+@item
Internals:
-@uref{internals-html, html}
-@uref{internals-big-html, big html}
-@uref{internals-pdf, pdf}
+@manualDevelInternalsSplit
+@* @manualDevelInternalsBig
+@* @manualDevelInternalsPdf
+
+@end itemize
+@divEnd
@divEnd
@divClass{column-right-top}
-@subheading Contributors' Guide
+@subheading Contributor's Guide
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
+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.
-@divClass{keep-bullets}
-@itemize
+@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 @uref{../contributor/index.html, Contributor's guide (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
+@docLinks{Contributor's Guide, contributor,
+ @rcontribnamed{Top,Contributor's Guide},
+ @manualDevelContributorSplit,
+ @manualDevelContributorBig, 500 kB,
+ @manualDevelContributorPdf, 2.8 MB}
-@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)}
+@divEnd
-@item @uref{../contributor.pdf, contributor.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
-@c @item @uref{TODO, contributor.info}:
-@c GNU info format for documentation. TODO, link broken.
+@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}
-@end itemize
-@divEnd
@divEnd
@divClass{column-right-bottom}
@itemize
@item @uref{../../input/regression/collated-files.html, Regression tests}:
-This releases' tests. (also in
+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 releases' MusicXML tests. (also in
+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 beteween versions.
+Comparisons between versions.
@end itemize
@divEnd
@divEnd
-@node authors
-@unnumberedsec Authors
+@node Authors
+@unnumberedsec Authors
@help{Under construction; this is not an accurate list!}
-combo of:
-
-http://lilypond.org/web/about/thanks
-
-Documentation/topdocs/AUTHORS.texi
-
-and maybe:
-http://lilypond.org/web/switch/
-
@divClass{column-left-top}
@subheading Current Development Team
@divEnd
@divClass{column-right-top}
-@subheading Previous Development Team Positions
+@subheading Previous Development Team
@divClass{keep-bullets}
@developersPrevious
@divEnd
+@divClass{column-center-top}
+@subheading Current Contributors
+
+@divClass{keep-bullets}
+@subsubheading Programming
+
+@coreCurrent
+
+@subsubheading Font
+
+@fontCurrent
+
+@subsubheading Documentation
+
+@docCurrent
+
+@subsubheading Support
+
+@supportCurrent
+
+@subsubheading Translation
+
+@translationsCurrent
+
+@divEnd
+@divEnd
+
+
@divClass{column-center-bottom}
-@subheading Programming contributors
+@subheading Previous Contributors
@divClass{keep-bullets}
-@contributorsCore
+@subsubheading Programming
+
+@corePrevious
-@subheading Font contributors
+@subsubheading Font
-@contributorsFont
+@fontPrevious
-@subheading Documentation contributors
+@subsubheading Documentation
-@contributorsDoc
+@docPrevious
-@subheading Support contributors
+@subsubheading Support
-@contributorsSupport
+@supportPrevious
-@subheading Translation contributors
+@subsubheading Translation
-@contributorsTranslations
+@translationsPrevious
@divEnd
@divEnd
-@node publications
+@node Publications
@unnumberedsec Publications
@divClass{column-center-top}
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})
+PDF 750k})
@item
Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
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
+@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
-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.”
+@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
-appearance in mainstream printed press.
+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
@item
July, August 2004
-Dave Phillips wrote an introductory article for Linux Journal At
+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 interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
-linuxmusician.com (site now defunct). This interview was also
-reviewed in a
+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}.
@divEnd
-@node old news
+@node Old news
@unnumberedsec Old news
+@include web/news-front.itexi
+
@include web/news.itexi
+
+
projects / lilypond.git / blobdiff