version that you are working on. See TRANSLATION for details.
@end ignore
+@include general/basic-authors.itexi
+
@node Community
@unnumbered Community
@divClass{column-left-bottom}
@subheading User Discussions and Help
-@subsubheading User mailist: @code{lilypond-user@@gnu.org}
+@subsubheading User mailing list: @code{lilypond-user@@gnu.org}
-This mailist is the main place for users to discuss and help each
-other.
+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,
@subsubheading Other languages
+@quotation
@uref{http://es.groups.yahoo.com/group/lilypond-es,
Spanish yahoo group}
Portugese group}
@uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
-French mailist}
+French mailing list}
@uref{http://www.lilypondforum.nl/,
Dutch forum}
+@end quotation
@divEnd
The easiest way to keep touch is by reading our community
newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
-@subsubheading Releases mailist: @code{info-lilypond@@gnu.org}
+@subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
-This mailist is a low-volume, read-only list which receives
+This mailing list is a low-volume, read-only list which receives
notifications of new releases.
@quotation
@divClass{column-right-bottom}
@subheading Developer Discussion
-@subsubheading Developer mailist: @code{lilypond-devel@@gnu.org}
+@subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
Most developer discussion takes place on this list. Patches
should be sent here.
@end quotation
-@subsubheading Bug mailist: @code{bug-lilypond@@gnu.org}
+@subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
Bug-specific discussion takes place here.
-
-
@node Tiny examples
@unnumberedsec Tiny examples
@subheading What are @qq{Tiny examples}?
A tiny example is an example from which nothing can be removed.
-
-These used to be called @qq{minimal examples}.
@divEnd
@divClass{column-left-bottom}
@node Help us
@unnumberedsec Help us
-FIXME: before going live, rewrite this to apply to lilypond
-generally. Right now it's (deliberately) website-specific.
+TODO: talk about the Frogs, document suggestions, encourage getting
+involved, etc. Maybe mention GLISS and GOP, if those are happening
+in the near future.
-@subheading This document
-@subsubheading High priority / blocks release
+@node Development
+@unnumberedsec Development
-- Features page.
-- python: automatically insert latest version numbers into these
- pages. Script already exists for the old website, but might
- (or might not!) require tweaking.
+@divClass{heading-center}
+@heading Development materials for LilyPond @versionDevel{}
-- translation infrastructure.
+@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}.}
-@subsubheading Low priority / may never
+@divEnd
-- perl: web-texi2html.pl needs to be un-hacked; I did things
- really messily. Possibly even merge/share functions with
- the doc init.pl file?
+@divClass{column-center-top}
+@subheading Release numbers
-- somebody to implement/work on a media=handheld CSS sheet
+There are two sets of releases for LilyPond: stable releases, and
+unstable development releases. Stable versions have an
+even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
+Development versions have an odd-numbered @q{minor} version number
+(e.g., 2.7, 2.9, 2.11).
-- remove the attributes from the <body> tag. In general, clean up
- the HTML produced by texi2html
+@divEnd
+@divClass{column-left-bottom}
+@subheading Download
-@node Development
-@unnumberedsec Development
+Instructions for git and compiling are in the Contributor's Guide.
+@quotation
+@uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
+@end quotation
-@divClass{heading-center}
-@heading Development materials for LilyPond 2.13.3
+Documentation writers and testers will generally want to download
+the latest binary:
-@warning{These are @emph{unstable development} versions. If you
-have the slighest doubt about how to use or install LilyPond, we
-urge you to use the stable @ref{Download}, and read the stable
-@ref{Manuals}.}
+@quotation
-@divEnd
+@downloadDevelLinuxNormal
-@divClass{column-left-bottom}
-@subheading Download
+@downloadDevelLinuxBig
-@uref{http://download.linuxaudio.org/lilypond/binaries/linux-x86/lilypond-2.13.3-1.linux-x86.sh,
-lilypond-2.13.3-1.linux-x86.sh}
+@downloadDevelLinuxPPC
-@uref{http://download.linuxaudio.org/lilypond/binaries/linux-64/lilypond-2.13.3-1.linux-64.sh,
-lilypond-2.13.3-1.linux-64.sh}
+@downloadDevelFreeBSDNormal
-@uref{http://download.linuxaudio.org/lilypond/binaries/linux-ppc/lilypond-2.13.3-1.linux-ppc.sh,
-lilypond-2.13.3-1.linux-ppc.sh}
+@downloadDevelFreeBSDBig
-@uref{http://download.linuxaudio.org/lilypond/binaries/freebsd-x86/lilypond-2.13.3-1.freebsd-x86.sh,
-lilypond-2.13.3-1.freebsd-x86.sh}
+@downloadDevelDarwinNormal
-@uref{http://download.linuxaudio.org/lilypond/binaries/freebsd-64/lilypond-2.13.3-1.freebsd-64.sh,
-lilypond-2.13.3-1.freebsd-64.sh}
+@downloadDevelDarwinPPC
-@uref{
-http://download.linuxaudio.org/lilypond/binaries/darwin-x86/lilypond-2.13.3-1.darwin-x86.tar.bz2,
-lilypond-2.13.3-1.darwin-x86.tar.bz2}
+@downloadDevelWindows
-@uref{
-http://download.linuxaudio.org/lilypond/binaries/darwin-x86/lilypond-2.13.3-1.darwin-ppc.tar.bz2,
-lilypond-2.13.3-1.darwin-ppc.tar.bz2}
+@downloadDevelSource
-@uref{
-http://download.linuxaudio.org/lilypond/binaries/mingw/lilypond-2.13.3-1.mingw.exe,
-lilypond-2.13.3-1.mingw-exe}
+@end quotation
@subheading Manuals
-LM:
+@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}
-MG:
+Glossary:
@uref{mg-html, html}
+@uref{mg-big-html, big html}
@uref{mg-pdf, pdf}
-AE:
-@uref{ae-html, html}
-@uref{ae-pdf, pdf}
+Essay:
+@uref{essay-html, html}
+@uref{essay-big-html, big html}
+@uref{essay-pdf, pdf}
-@smallspace
+Notation:
+@uref{notation-html, html}
+@uref{notation-big-html, big html}
+@uref{notation-pdf, pdf}
-NR:
-@uref{nr-html, html}
-@uref{nr-pdf, pdf}
+Usage:
+@uref{usage-html, html}
+@uref{usage-big-html, big html}
+@uref{usage-pdf, pdf}
-...etc...
-SL-link
-AU-link
+Snippets:
+@uref{snippets-html, html}
+@uref{snippets-big-html, big html}
+@uref{snippets-pdf, pdf}
-FAQ-link (? maybe?)
-Changes-link
-IR-link
+Changes:
+@uref{changes-html, html}
+@uref{changes-big-html, big html}
+@uref{changes-pdf, pdf}
+
+Internals:
+@uref{internals-html, html}
+@uref{internals-big-html, big html}
+@uref{internals-pdf, pdf}
@divEnd
-@divClass{column-right-bottom}
+@divClass{column-right-top}
@subheading Contributors' Guide
-FIXME write CG intro + links.
+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.
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{contributor/index.html, Contributor's guide (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@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)}
+
+@item @uref{contributor.pdf, contributor.pdf}:
+download as a PDF file.
+@emph{(large single download, 2.8 Mb)}
+@item @uref{FIXME, contributor.info}:
+GNU info format for documentation. FIXME, link broken.
+
+@end itemize
+@divEnd
@divEnd
+@divClass{column-right-bottom}
+@subheading Regression tests
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../input/regression/collated-files.html, Regression tests}:
+This releases' 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
+@uref{../input/regression/musicxml/collated-files.pdf, pdf})
+@item @uref{http://lilypond.org/test, Archive of regression tests}:
+Comparisons beteween versions.
+
+@end itemize
+@divEnd
+@divEnd
@node Authors
@unnumberedsec Authors
+@help{Under construction; this is not an accurate list!}
+
combo of:
http://lilypond.org/web/about/thanks
http://lilypond.org/web/switch/
+@divClass{column-left-top}
+@subheading Current Development Team
+
+@divClass{keep-bullets}
+@developersCurrent
+@divEnd
+@divEnd
+
+@divClass{column-right-top}
+@subheading Previous Development Team Positions
+
+@divClass{keep-bullets}
+@developersPrevious
+@divEnd
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Programming contributors
+
+@divClass{keep-bullets}
+@contributorsCore
+
+@subheading Font contributors
+
+@contributorsFont
+
+@subheading Documentation contributors
+
+@contributorsDoc
+
+@subheading Support contributors
+
+@contributorsSupport
+
+@subheading Translation contributors
+
+@contributorsTranslations
+
+@divEnd
+@divEnd
+
@node Publications
@unnumberedsec Publications
@divClass{column-center-top}
-
@subheading What we wrote
@divClass{keep-bullets}
@itemize
-@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})
-
@item
Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
the Art of Shipping}. Forum Internacional Software Livre 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
@divEnd
@divClass{keep-bullets}
@itemize
+@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
@item
December 2005
-linux journal cover Linux Journal publishes an article titled
+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
projects / lilypond.git / blobdiff