1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. For details, see the Contributors'
7 Guide, node Updating translation committishes..
10 @include included/authors.itexi
11 @include included/helpus.itexi
16 @divClass{link-headings}
18 @divClass{column-center-top}
19 @subheading Interacting with the community
24 @ref{Contact}: get help, discuss, and keep in touch!
27 @ref{Tiny examples}: these are @emph{highly} recommended when
31 @ref{Bug reports}: something went wrong.
36 @divClass{column-left-bottom}
37 @subheading Making LilyPond better
42 @ref{Help us}: your assistance is requested.
45 @ref{Sponsoring}: financial contributions.
48 @ref{Development}: for contributors and testers.
51 @ref{GSoC}: list of projects for Google Summer of Code.
54 @ref{Authors}: the people who made LilyPond what it is today.
59 @divClass{column-right-bottom}
60 @subheading Miscellaneous
65 @ref{Publications}: what we wrote, and have had written about us.
68 @ref{Old news}: an archive.
71 @ref{Attic}: announcements and changelogs from past versions.
96 @unnumberedsec Contact
99 @divClass{column-left-bottom}
100 @subheading User Discussions and Help
102 @subsubheading User mailing list: @code{lilypond-user@@gnu.org}
104 This mailing list is the main place for users to discuss and help
108 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user,
109 lilypond-user subscribe and info}
111 @uref{http://lists.gnu.org/archive/html/lilypond-user/,
113 @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
115 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
118 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
119 send to lilypond-user with gmane}
122 @warning{When asking questions, please use @ref{Tiny examples}!}
124 @subsubheading LilyPond Snippet Repository
126 The LilyPond Snippet Repository is a large collection of
127 user-submitted examples, which can freely be copied and used
128 in your own works. See what other people have written,
132 @uref{http://lsr.dsi.unimi.it}
135 Particularly instructive examples from LSR are included in our
136 official documentation, in @ref{Snippets}.
141 Some level of support is provided on our IRC channel,
144 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
147 This channel has no public archive, so any question that may
148 be useful for others would better be posted to one of the mailing lists.
151 <form action="http://webchat.freenode.net"
155 <input name="nick" type="text" size="15" value="">
157 <input name="channels" type="hidden" value="lilypond">
158 <input type="submit" value="Join #lilypond IRC Chat">
161 <script language="JavaScript" type="text/javascript">
162 var username = "web";
163 var lang = window.navigator.userLanguage ? window.navigator.userLanguage
164 : window.navigator.language;
165 username += '-' + lang.substr(0, 2);
166 username += '-' + navigator.appName.substr(0, 2);
167 username += navigator.appCodeName.replace (" ", "").substr(0, 2);
168 username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
169 document.forms["f_lily_irc"].nick.value = username;
173 @subsubheading Other languages
176 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
177 Spanish mailing list}
179 @uref{http://www.lilypondforum.de/,
182 @uref{http://groups.google.com/group/lilypond-brasil,
185 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
188 @uref{http://www.lilypondforum.nl/,
195 @divClass{column-right-top}
196 @subheading Stay Informed
198 @subsubheading LilyPond Report
200 The easiest way to keep touch is by reading our community
201 newsletter, the LilyPond Report:
204 @uref{http://news.lilynet.net}
207 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
209 This mailing list is a low-volume, read-only list which receives
210 notifications of new releases.
213 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
214 info-lilypond subscribe and info}
216 @uref{http://lists.gnu.org/archive/html/info-lilypond/,
218 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
220 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
223 @c don't include gmane posting here. -gp
230 @divClass{column-right-bottom}
231 @subheading Developer Discussion
233 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
235 Most developer discussion takes place on this list. Patches
239 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
240 lilypond-devel subscribe and info}
242 @uref{http://lists.gnu.org/archive/html/lilypond-devel/,
244 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
246 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
249 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
250 send to lilypond-devel with gmane}
254 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
256 Bug-specific discussion takes place here.
259 @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
260 bug-lilypond subscribe and info}
262 @uref{http://lists.gnu.org/archive/html/bug-lilypond/,
264 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
266 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
269 @c don't include gmane posting here. -gp
272 @warning{Before sending a message to the bug list, please read our
273 guidelines for @ref{Bug reports}.}
277 @divClass{column-right-bottom}
278 @subheading Sensitive emails
280 Private matters should be sent to Graham Percival (project
281 manager), who will discuss it with those concerned.
287 @unnumberedsec Tiny examples
289 @divClass{column-center-top}
290 @subheading What are @qq{Tiny examples}?
292 A tiny example is an example from which @strong{nothing} can be removed.
295 @divClass{column-left-bottom}
296 @subheading Why create them?
298 @divClass{keep-bullets}
302 The simpler the example is, the quicker potential helpers can
303 understand it and help you.
306 A tiny example demonstrates that you have put effort towards
307 solving the problem yourself. When people send huge portions of
308 input, it looks like they don't care if we help them or not.
311 Creating a tiny example helps you to understand what is
312 happening. Many false problem reports can be avoided by
313 attempting to create a tiny example; if you cannot replicate a
314 @qq{bug} in a tiny example, then the problem was probably an
315 insufficient understanding of LilyPond, not an actual bug!
323 @divClass{column-right-bottom}
324 @subheading How to create them?
326 @divClass{keep-bullets}
330 Include the @code{\version} number.
333 Make it small! Examples about spacing or page layout might
334 require many bars of music, but most issues can be reproduced
335 using less than a single measure.
338 When trying to create an example, try commenting out @w{(@code{%}
339 or @code{%@{ @dots{} %@}})} sections of your file. If you
340 can comment something while still demonstrating the main idea,
341 then remove the commented-material.
344 Avoid using complicated notes, keys or time signatures, unless
345 the bug is about the behavior of those items.
348 Do not use @code{\override} or @code{\set} commands unless the bug
349 is about those specific commands.
352 Optionally, attach an image showing the desired graphical output.
359 @divClass{column-center-bottom}
360 @subheading How tiny should they be?
362 Is the code below a minimal example?
366 \include "english.ly"
371 \numericTimeSignature
373 <cs' d'' b''>16 <cs' d'' b''>8.
374 %% Here: the tie on the D's looks funny
375 %% Too tall? Left-hand endpoint is not aligned with the B tie?
377 <cs' d'' b''>8 [ <b d'' a''> ]
382 Well, it is not very big, but a truly minimal example is here:
387 % middle tie looks funny here:
388 <c' d'' b''>8. ~ <c' d'' b''>8
392 Very few tiny examples exceed 10 lines of code -
393 quite often 4 lines are enough to demonstrate the problem!
399 @unnumberedsec Bug reports
402 @divClass{heading-center}
403 If you have input that results in a crash or wrong output,
407 @divClass{column-center-top}
408 @subheading Step 1: Known bugs
410 We may already know about this bug. Check here:
413 @uref{http://code.google.com/p/lilypond/issues/list}
416 @warning{Please @strong{DO NOT} add bug reports directly to the
417 bug tracker. Once an issue has been added to the tracker, feel
418 free to add more information to that report.}
423 @divClass{column-left-bottom}
424 @subheading Step 2: Creating a bug report
426 If you have discovered a bug which is not listed,
427 please help us by creating a bug report.
429 @warning{We only accept reports in the form of
430 @ref{Tiny examples}. We have very limited resources,
431 so any non-minimal example will be rejected. Almost
432 every bug can be demonstrated in four notes or less!}
434 Here is an example of a good bug report:
437 % Accidentals should be printed for only
438 % the first note in a tie, but this version
439 % prints flats on both notes.
450 @divClass{column-right-bottom}
451 @subheading Step 3: Sending a bug report
453 Once you have verified that the issue is not already known and
454 created a bug report, please send it to us!
456 @divClass{keep-bullets}
460 If you are subscribed to the @uref{mailto:bug-lilypond@@gnu.org,
461 bug-lilypond@@gnu.org} mailing list, send an email like normal.
464 If you are not subscribed, you can still post a bug report with
466 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
467 gmane lilypond.bugs web interface}.
469 However, there is a strict @qq{no top-posting} check on the gmane
470 interface, which is often incorrectly triggered by lilypond files.
471 To avoid this, please add:
474 > I'm not top posting.
478 (you @emph{must} include the @code{>} ) to the top of your bug
485 @divClass{column-center-bottom}
486 @subheading Step 4: Wait for a response
488 Once your bug report has been sent to the list, our Bug Squad will
489 examine it; they may ask you for more information. You will be notified
490 when the report will be added to the bug tracker. Please allow up to 4 days,
491 as we have a limited number of volunteers for this task.
493 Once a bug has been added to the tracker, you can comment it to add
494 more information about it.
495 You may also mark the bug so that you automatically receive emails when
496 any activity on the bug occurs. This requires you have a google
500 @divClass{column-center-bottom}
501 @subheading Optional help: show the desired behavior
503 Once an issue has been added to the tracker, it can be very
504 helpful if we can see the desired output. Feel free to add input
505 code and/or images (possibly created with other tools) which
506 demonstrate what you think it should look like!
513 @unnumberedsec Help us
515 @divClass{column-center-top}
520 @divClass{column-left-top}
521 @divClass{keep-bullets}
527 @divClass{column-right-top}
534 @unnumberedsec Sponsoring
536 @divClass{keep-bullets}
537 @divClass{column-left-top}
543 @item some users have paid for new features
544 @item some developers have added new features for hire
547 The LilyPond project does not organize such efforts; we neither
548 endorse nor discourage such agreements. Any contracts between
549 private individuals is the business of those individuals, not
554 @divClass{column-right-top}
555 @subheading Guidelines
557 Any user wanting to offer money in exchange for work should bear
558 in mind the following points:
562 LilyPond developers may advertise their services on the lilypond
563 email lists from time to time.
566 Any agreements between private individuals should include the
567 normal precautions when conducting business: who pays, how much do
568 they pay, with what method of payment, and upon what set of
569 conditions. We suggest that any ambiguity or uncertainty in these
570 questions should be resolved before any work begins.
576 @divClass{column-center-bottom}
577 @subheading Interested developers
579 Here is a list of people who have expressed an interest in
580 bounties. Note that the amount of work done by individuals varies
581 quite a bit throughout the years. We do not guarantee that this
582 list is up-to-date, nor do we guarantee that the people listed
583 here have any ability. The only criteria is "XYZ asked to be
584 listed on this page".
586 Looking at the git history is a good way to determine who the most
587 active and experienced developers are. Statistics up to version
590 @multitable @columnfractions .3 .3 .3
591 @item @uref{http://lilypond.org/~graham/gitstats-all/, overall history}
592 @tab @uref{http://lilypond.org/~graham/gitstats-1year/, past year}
593 @tab @uref{http://lilypond.org/~graham/gitstats-3months/, past three months}
596 Interested developers:
598 @item @email{dak@@gnu.org, David Kastrup}
599 Donations are required to let me continue my current fulltime work on
600 LilyPond. I focus on user and programmer interface design, coherence,
601 implementation, simplification, documentation, and debugging.
604 @c @item @email{name@@adress.domain, Name}
605 @c area of interest (256 chars max)
614 @unnumberedsec Development
616 @divClass{heading-center}
618 @heading Development for LilyPond @version
621 @heading Development for LilyPond @versionDevel
625 @c we normally don't allow named references, but in this case
626 @c it's good to emphasize the "stable" part. -gp
627 @warning{These are @emph{unstable development} versions. If you
628 have the slightest doubt about how to use or install LilyPond, we
629 urge you to use the @ref{Download, stable Download}, and read the
630 @ref{Manuals, stable Manuals}.}
634 @divClass{column-center-top}
635 @subheading Release numbers
637 There are two sets of releases for LilyPond: stable releases, and
638 unstable development releases. Stable versions have an
639 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
640 Development versions have an odd-numbered @q{minor} version number
641 (e.g., 2.7, 2.9, 2.11).
646 @divClass{column-left-top}
649 Instructions for git and compiling are in the Contributor's Guide.
652 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
655 Documentation writers and testers will generally want to download
660 @downloadDevelLinuxNormal
662 @downloadDevelLinuxBig
664 @downloadDevelLinuxPPC
666 @downloadDevelFreeBSDNormal
668 @downloadDevelFreeBSDBig
670 @downloadDevelDarwinNormal
672 @downloadDevelDarwinPPC
674 @downloadDevelWindows
683 @divClass{column-right-top}
684 @subheading Contributor's Guide
686 LilyPond development is a fairly complicated matter. In order to
687 help new contributors, and to keep the whole system (mostly)
688 stable, we have written a manual for development tasks.
690 @docLinksBare{Contributor's Guide, contributor,
691 @rcontribnamed{Top,Contributor's Guide},
692 @manualDevelContributorSplit,
693 @manualDevelContributorBig, 500 kB,
694 @manualDevelContributorPdf, 2.8 MB}
699 @divClass{column-center-top}
700 @subheading Regression tests
702 @divClass{keep-bullets}
708 @uref{../../input/regression/collated-files.html, Regression tests}:
709 This release's regtests.
710 (@uref{../../input/regression/collated-files.pdf, pdf version})
713 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
714 This release's musicXML tests.
715 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
718 @uref{../../input/regression/abc2ly/collated-files.html, abc2ly tests}:
719 This release's abc2ly tests.
720 (@uref{../../input/regression/abc2ly/collated-files.pdf, pdf version})
723 @uref{../../input/regression/lilypond-book/collated-files.html, lilypond-book tests}:
724 This release's lilypond-book tests.
725 (@uref{../../input/regression/lilypond-book/collated-files.pdf, pdf version})
731 @subsubheading Development version
734 @item @regtestDevel (@regtestDevelPdf{})
736 @item @regtestDevelXml (@regtestDevelXmlPdf{})
738 @item @regtestDevelAbc (@regtestDevelAbcPdf{})
740 @item @regtestDevelLilypondBook (@regtestDevelLilypondBookPdf{})
743 @subsubheading Stable version
746 @item @regtestStable (@regtestStablePdf{})
748 @item @regtestStableXml (@regtestStableXmlPdf{})
750 @item @regtestStableAbc (@regtestStableAbcPdf{})
752 @item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{})
757 @subsubheading All versions
760 @item @uref{http://lilypond.org/test, Comparisons between regression tests}
762 @item @uref{http://lilypond.org/download/binaries/test-output/,
763 Archive of all regression tests}
772 @divClass{column-center-bottom}
776 @warning{These manuals are for LilyPond @version{}; the latest
777 manuals can be found at @url{http://lilypond.org}}
780 @divClass{normal-table}
781 @multitable @columnfractions .3 .3 .3
782 @headitem Introduction
784 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
786 @docLinkBig{Learning,learning,@manualDevelLearningBig}
788 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
791 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
793 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
795 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
798 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
800 @docLinkBig{Essay,essay,@manualDevelEssayBig}
802 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
807 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
809 @docLinkBig{Notation,notation,@manualDevelNotationBig}
811 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
814 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
816 @docLinkBig{Usage,usage,@manualDevelUsageBig}
818 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
821 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
823 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
825 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
830 @docLinkSplit{Web,web,@manualDevelWebSplit}
832 @docLinkBig{Web,web,@manualDevelWebBig}
834 @docLinkPdf{Web,web,@manualDevelWebPdf}
837 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
839 @docLinkBig{Changes,changes,@manualDevelChangesBig}
841 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
844 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
846 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
848 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
851 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
853 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
855 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
858 @headitem Downloadable
875 @divClass{column-center-top}
876 @subheading What is Google Summer of Code?
879 @uref{http://www.google-melange.com/gsoc/homepage/google/gsoc2012, GSoC website},
880 @qq{Google Summer of Code is a global program that offers students
881 stipends to write code for open source projects. Google has worked
882 with the open source community to identify and fund exciting projects
883 for the upcoming summer.}
885 The LilyPond Team decided that this is an excellent opportunity to find
886 new contributors, encourage students already participating in LilyPond
887 development to become more involved, and - last but not least - write some
888 great code for the benefit of all!
890 We are participating in GSoC as a part of GNU Project. See
891 @uref{http://www.gnu.org/software/soc-projects/guidelines.html, GNU GSoC webpage}
892 for information on how to participate.
896 @divClass{column-center-bottom}
897 @subheading Our Ideas List
899 Below is a list of projects suggested for GSoC students. If you don't
900 see a project that suits you, feel free to suggest your own!
901 It's also possible to scale down a project if you feel it's too big.
903 We require that every student has basic @code{git} knowledge, and
904 recommend that everyone applying for projects other than the last one
905 have basic music notation knowledge.
907 @subheading Grace notes
909 Fix problems with synchronization of grace notes,
910 together with all underlying architecture (see
911 @uref{http://code.google.com/p/lilypond/issues/detail?id=34, issue 34 in our tracker}).
912 Grace notes are confusing to LilyPond's timing because they're like
913 going back in time. This causes weird effects, especially when one staff
914 has a grace note and the other doesn't.
916 @strong{Difficulty:} medium
918 @strong{Requirements:} C++, MIDI
920 @strong{Recommended:} familiarity with LilyPond internals
922 @strong{Mentor(s):} Mike Solomon, Carl Sorensen
926 Adding comprehensive MusicXML export and improving import,
927 together with tests checking that it works. Depending on time available,
928 implement some or all of the following:
930 @divClass{keep-bullets}
934 Handle basic musical content export like the MIDI export (i.e. using
935 dedicated exporter classes, derived from the translator class)
938 Build the XML tree of the basic musical content,
939 add a connection from music event to XML tag
942 Let all LilyPond engravers do their job
945 add ability to link each output object
946 (basically each stencil / group of stencils) to the music cause
947 (and thus to the XML tag in the XML tree)
950 Add a XML output backend, which can then add the layout information
951 for each output object to the XML tags
956 The goal will be considered achieved when a (previously chosen) score could be
957 imported from MusicXML and exported back with no unintentional loss of data.
959 @strong{Difficulty:} medium
961 @strong{Requirements:} MusicXML, Python, basic LilyPond knowledge
963 @strong{Mentor(s):} Reinhold Kainhofer, Mike Solomon
965 familiarity with other scorewriters (for cross-testing) would be a nice bonus.
967 @subheading Improve slurs and ties
969 The default shape of slur and tie curves is often unsatisfactory.
970 Ties on enharmonic notes @code{@{ cis'~ des' @}} are not supported,
971 ties "broken" by clef or staff change aren't supported well.
972 The project includes collecting and sorting examples of bad output,
973 deciding on the intended output and writing the actual code.
975 @strong{Difficulty:} hard
977 @strong{Requirements:} C++, experience with writing heuristics
979 @strong{Recommended knowledge:} LilyPond knowledge, aesthetic sense
981 @strong{Mentor(s):} Mike Solomon
983 @subheading Adding special variant of font glyphs
984 Adding on-staff-line, between-staff-line, shorter and narrower variants
985 of some glyphs, for example accidentals, together with a generic
986 infrasctucture to support them. An example is ancient notation breve notehead
987 coming in two variants, with smaller and bigger hole.
989 @strong{Difficulty:} easy
991 @strong{Requirements:} MetaFont, C++, good eye for details
993 @strong{Recommended knowledge:} basic LilyPond knowledge
995 @strong{Mentor(s):} Werner Lemberg
997 @subheading Improve beaming
999 Default positioning of regular, cross-staff, broken and kneed beams
1000 should be improved. Beaming should depend on context and neighbor notes (see
1001 @uref{http://icking-music-archive.org/lists/sottisier/sottieng.pdf, section 2.2 here}).
1002 If possible, reduce beaming computation time.
1004 @strong{Difficulty:} medium
1006 @strong{Requirements:} C++, experience with writing heuristics
1008 @strong{Recommended knowledge:} aesthetic sense
1010 @strong{Mentor(s):} Mike Solomon, Carl Sorensen
1012 @subheading Better tablature support
1014 @divClass{keep-bullets}
1018 non-monotonic string tunings, like Ukulele
1021 create tablature input mode (currently musical information is entered
1022 in western-common-music-notation-terms, i.e. @qq{a quarter f sharp note}
1023 and then converted to tablature) for transcribing medieval lute tablature
1026 implement modern tablature features, such as bends, pull-off, hammer-on
1029 if a fretboard shape is defined for a given chord, use this information when
1030 displaying the chord on the staff (and not just display a default chord shape)
1035 @strong{Difficulty:} easy
1037 @strong{Requirements:} C++
1039 @strong{Recommended knowledge:} tablature notation familiarity
1041 @strong{Mentor(s):} Carl Sorensen
1043 @subheading Clean up various compilation warnings
1045 Clean up compiler warnings, static code analysis, and valgrind warnings.
1046 Automatic code analysis tools (warnings in @code{g++} and @code{clang})
1047 and analysis tools like valgrind memory leak detection and callgrind code
1048 profilers provide valuable information about possible flaws in C++ code.
1049 Cleaning these warnings would allow us to automatically reject any patch
1050 which introduced extra warnings.
1052 @strong{Difficulty:} medium
1054 @strong{Requirements:} C++
1056 @strong{Mentor(s):} Joe Neeman, Reinhold Kainhofer
1064 @unnumberedsec Authors
1066 @divClass{column-left-top}
1067 @subheading Current Development Team
1069 @divClass{keep-bullets}
1074 @divClass{column-right-top}
1075 @subheading Previous Development Team
1077 @divClass{keep-bullets}
1083 @divClass{column-center-top}
1084 @subheading Current Contributors
1086 @divClass{keep-bullets}
1087 @subsubheading Programming
1095 @subsubheading Documentation
1099 @subsubheading Bug squad
1103 @subsubheading Support
1107 @subsubheading Translation
1109 @translationsCurrent
1115 @divClass{column-center-bottom}
1116 @subheading Previous Contributors
1118 @divClass{keep-bullets}
1119 @subsubheading Programming
1127 @subsubheading Documentation
1131 @c uncomment when we have any previous members -gp
1132 @c @subsubheading Bug squad
1136 @subsubheading Support
1140 @subsubheading Translation
1142 @translationsPrevious
1150 @unnumberedsec Publications
1152 @divClass{column-center-top}
1153 @subheading What we wrote about LilyPond
1155 @divClass{keep-bullets}
1157 @include we-wrote.itexi
1162 @divClass{column-center-bottom}
1163 @subheading What people did with LilyPond
1165 @divClass{keep-bullets}
1167 @include others-did.itexi
1172 @contactUsAbout{academic papers}
1176 @unnumberedsec Old news
1178 @divClass{heading-center}
1179 @warning{Many old announcements and changelogs can be found in
1183 @include web/news-front.itexi
1185 @include web/news.itexi
1189 @unnumberedsec Attic
1191 @divClass{column-center-top}
1192 @subheading Announcements
1194 Announcements and news by version:
1195 @uref{http://lilypond.org/doc/v2.14/Documentation/web/index#LilyPond-2_002e14_002e0-released_0021-June-6_002c-2011,v2.14},
1196 @miscLink{announce-v2.12,v2.12},
1197 @miscLink{announce-v2.10,v2.10},
1198 @miscLink{announce-v2.8,v2.8},
1199 @miscLink{announce-v2.6,v2.6},
1200 @miscLink{announce-v2.4,v2.4},
1201 @miscLink{announce-v2.2,v2.2},
1202 @miscLink{announce-v2.0,v2.0},
1203 @miscLink{ANNOUNCE-1.2,v1.2},
1204 @miscLink{ANNOUNCE-1.0,v1.0},
1205 @miscLink{ANNOUNCE-0.1,v0.1}
1207 Descriptive list of changes by version:
1208 @uref{http://lilypond.org/doc/v2.14/Documentation/changes/index.html,v2.14},
1209 @uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS,v2.12},
1210 @uref{http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS,v2.10},
1211 @uref{http://lilypond.org/doc/v2.8/Documentation/topdocs/NEWS,v2.8},
1212 @uref{http://lilypond.org/doc/v2.6/Documentation/topdocs/NEWS,v2.6},
1213 @uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS,v2.4},
1214 @uref{http://lilypond.org/doc/v2.2/Documentation/topdocs/out-www/NEWS,v2.2},
1215 @uref{http://lilypond.org/doc/v2.0/Documentation/topdocs/out-www/NEWS,v2.0},
1216 @uref{http://lilypond.org/doc/v1.8/Documentation/topdocs/out-www/NEWS,v1.8},
1217 @uref{http://lilypond.org/doc/v1.6/Documentation/out-www/NEWS,v1.6},
1218 @miscLink{NEWS-1.4,v1.4},
1219 @miscLink{NEWS-1.2,v1.2}
1223 @divClass{column-center-bottom}
1224 @subheading Changelogs
1226 Developpers' changelogs by version:
1227 @miscLink{ChangeLog-2.10,v2.10},
1228 @miscLink{ChangeLog-2.3,v2.3},
1229 @miscLink{ChangeLog-2.1,v2.1},
1230 @miscLink{ChangeLog-1.5,v1.5 (1)},
1231 @miscLink{CHANGES-1.5,v1.5 (2)},
1232 @miscLink{CHANGES-1.4,v1.4},
1233 @miscLink{CHANGES-1.3,v1.3},
1234 @miscLink{CHANGES-1.2,v1.2},
1235 @miscLink{CHANGES-1.1,v1.1},
1236 @miscLink{CHANGES-1.0,v1.0},
1237 @miscLink{CHANGES-0.1,v0.1},
1238 @miscLink{CHANGES-0.0,v0.0}