@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
@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"
@node Help us
@unnumberedsec Help us
- TODO: talk about the Frogs, document suggestions, encourage getting
-@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
-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}.
+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. 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
@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
@unnumberedsec Development
-
@divClass{heading-center}
@heading Development materials for LilyPond @versionDevel{}
@subheading Contributors' 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.
+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}.
+
@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)}
+@*@ @ @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)}
+@*@ @ @emph{(large single download, 500 kb)}
@item @uref{../contributor.pdf, contributor.pdf}:
download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
+@*@ @ @emph{(large single download, 2.8 Mb)}
@c @item @uref{TODO, contributor.info}:
@c GNU info format for documentation. TODO, link broken.
@divEnd
@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
@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
+@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-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
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
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.
+including comparisons with a reference hand-engraved edition.
@item
December 2005
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.
+appearance in mainstream printed press.
@item
June 2005
projects / lilypond.git / blobdiff