X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fcommunity.itexi;h=fa6826b541fc5f1a0549a1d773f2dcb5d70af015;hb=674ed28bf0355426499a9ce19562d11d1addca42;hp=5a7662a274760d8c1d0dc980c56cc098ce16e582;hpb=2944a83e59f487894a214769392ce27289accb71;p=lilypond.git diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index 5a7662a274..fa6826b541 100644 --- a/Documentation/web/community.itexi +++ b/Documentation/web/community.itexi @@ -7,6 +7,7 @@ Guide, node Updating translation committishes.. @end ignore +@include included/acknowledge.itexi @include included/authors.itexi @include included/helpus.itexi @@ -48,11 +49,14 @@ discussing LilyPond. @ref{Development}: for contributors and testers. @item -@ref{GSoC}: list of projects for Google Summer of Code. +@ref{Google Summer of Code}: ideas for Google Summer of Code (GSoC). @item @ref{Authors}: the people who made LilyPond what it is today. +@item +@ref{Acknowledgements}: projects and institutions that support LilyPond + @end itemize @divEnd @@ -67,6 +71,9 @@ discussing LilyPond. @item @ref{Old news}: an archive. +@item +@ref{Attic}: announcements and changelogs from past versions. + @end itemize @divEnd @@ -80,10 +87,12 @@ discussing LilyPond. * Help us:: * Sponsoring:: * Development:: -* GSoC:: +* Google Summer of Code:: * Authors:: +* Acknowledgements:: * Publications:: * Old news:: +* Attic:: @end menu @divEnd @@ -125,7 +134,7 @@ in your own works. See what other people have written, and add your own! @example -@uref{http://lsr.dsi.unimi.it} +@uref{http://lsr.di.unimi.it} @end example Particularly instructive examples from LSR are included in our @@ -169,8 +178,8 @@ be useful for others would better be posted to one of the mailing lists. @subsubheading Other languages @quotation -@uref{http://lists.gnu.org/mailman/listinfo/lilypond-es, -Spanish mailing list} +@uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr, +French mailing list} @uref{http://www.lilypondforum.de/, German forum} @@ -178,26 +187,19 @@ German forum} @uref{http://groups.google.com/group/lilypond-brasil, Portuguese group} -@uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr, -French mailing list} - -@uref{http://www.lilypondforum.nl/, -Dutch forum} +@uref{http://lists.gnu.org/mailman/listinfo/lilypond-es, +Spanish mailing list} @end quotation - @divEnd @divClass{column-right-top} -@subheading Stay Informed +@subheading The LilyPond Blog -@subsubheading LilyPond Report - -The easiest way to keep touch is by reading our community -newsletter, the LilyPond Report: +Read our community blog, @q{Scores of Beauty}: @example -@uref{http://news.lilynet.net} +@uref{http://lilypondblog.org} @end example @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org} @@ -224,12 +226,12 @@ archive3} @divClass{column-right-bottom} -@subheading Developer Discussion +@subheading Developer Discussions and Translations @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org} -Most developer discussion takes place on this list. Patches -should be sent here. +Developer discussions take place on this list. Patches can also be sent +here. @quotation @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel, @@ -249,7 +251,8 @@ send to lilypond-devel with gmane} @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org} -Bug-specific discussion takes place here. +Bug reports and discussions should be sent here. Do not send patches +to this list. @quotation @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond, @@ -268,13 +271,16 @@ archive3} @warning{Before sending a message to the bug list, please read our guidelines for @ref{Bug reports}.} -@divEnd -@divClass{column-right-bottom} -@subheading Sensitive emails +@subsubheading Translation mailing list: @code{translations@@lilynet.org} -Private matters should be sent to Graham Percival (project -manager), who will discuss it with those concerned. +All discussions about translating LilyPond manuals should be sent here. +Do not send patches to this list. + +@quotation +@uref{http://lilypond-translations.3384276.n2.nabble.com/, +Translation mailing list archive} +@end quotation @divEnd @@ -483,14 +489,14 @@ report. Once your bug report has been sent to the list, our Bug Squad will examine it; they may ask you for more information. You will be notified -when the report will be added to the bug tracker. Please allow up to 4 days, -as we have a limited number of volunteers for this task. +when the report will be added to the bug tracker. Please allow up to 4 +days, as we have a limited number of volunteers for this task. Once a bug has been added to the tracker, you can comment it to add more information about it. You may also mark the bug so that you automatically receive emails when -any activity on the bug occurs. This requires you have a google -account. +any activity on the bug occurs. This requires you have a google account +login. @divEnd @divClass{column-center-bottom} @@ -776,6 +782,7 @@ manuals can be found at @url{http://lilypond.org}} @divClass{normal-table} @multitable @columnfractions .3 .3 .3 @headitem Introduction + @item @docLinkSplit{Learning,learning,@manualDevelLearningSplit} @tab @@ -796,7 +803,9 @@ manuals can be found at @url{http://lilypond.org}} @docLinkBig{Essay,essay,@manualDevelEssayBig} @tab @docLinkPdf{Essay,essay,@manualDevelEssayPdf} +@end multitable +@multitable @columnfractions .3 .3 .3 @headitem Regular @item @@ -819,7 +828,9 @@ manuals can be found at @url{http://lilypond.org}} @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig} @tab @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf} +@end multitable +@multitable @columnfractions .3 .3 .3 @headitem Infrequent @item @@ -849,15 +860,17 @@ manuals can be found at @url{http://lilypond.org}} @docLinkBig{Internals,internals,@manualDevelInternalsBig} @tab @docLinkPdf{Internals,internals,@manualDevelInternalsPdf} +@end multitable @ifset web_version +@multitable @columnfractions .3 @headitem Downloadable @item @doctarballDevel +@end multitable @end ifset -@end multitable @divEnd @divEnd @@ -865,201 +878,161 @@ manuals can be found at @url{http://lilypond.org}} -@node GSoC -@unnumberedsec GSoC +@node Google Summer of Code +@unnumberedsec Google Summer of Code @divClass{column-center-top} @subheading What is Google Summer of Code? -Quoting -@uref{http://www.google-melange.com/gsoc/homepage/google/gsoc2012, GSoC website}, -@qq{Google Summer of Code is a global program that offers students -stipends to write code for open source projects. Google has worked -with the open source community to identify and fund exciting projects -for the upcoming summer.} +A global program run by Google that offers students stipends for working +on open source software projects during summer vacations. -The LilyPond Team decided that this is an excellent opportunity to find -new contributors, encourage students already participating in LilyPond -development to become more involved, and - last but not least - write some -great code for the benefit of all! - -In addition to getting paid for your work, you'll gain experience in -software development, which many of previous GSoC students describe as -@emph{invaluable} (and you'll get a t-shirt, too!). - -If you have any questions, read -@uref{http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs, GSoC FAQ} -or contact us at @code{lilypond-devel@@gnu.org}. +It is an excellent opportunity to find new contributors, and encourage +students already participating in LilyPond development, to become more +involved. One of our contributors was accepted in the 2012 program as +part of the @uref{http://www.gnu.org/, GNU project}; and we are always +looking for others to participate in future programs. @divEnd -@divClass{column-center-bottom} +@divClass{column-center-middle-color2} @subheading Our Ideas List -Below is a list of projects suggested for GSoC students. If you don't -see a project that suits you, feel free to contact us and suggest your own! -It's also possible to scale down a project if you feel it's too big. +Below is a list of projects that were suggested for the GSoC 2012 +students and is retained here as an inspiration for anyone +who is interested in developing LilyPond for future GSoC projects. + +There are many more things that can be done to improve LilyPond and +members of the LilyPond development team are always willing to help +those who would like to tackle projects such as those listed below. -We require that every student has basic @code{git} knowledge, and -recommend that everyone applying for projects other than the last one -have basic music notation knowledge. +A full list of all the current open issues can be found +@uref{http://code.google.com/p/lilypond/issues/list, here}. +@divEnd + +@divClass{column-center-middle-color3} @subheading Grace notes -Fix problems with synchronization of grace notes, -together with all underlying architecture (see -@uref{http://code.google.com/p/lilypond/issues/detail?id=34, issue 34 in our tracker}). -Grace notes are confusing to LilyPond's timing because they're like -going back in time. This causes weird effects, especially when one staff -has a grace note and the other doesn't. +Fix problems with synchronization of grace notes. Grace notes can +intefere with LilyPond's timing and cause odd effects, especially when +multiple staffs are used where some have grace notes and others don't. @strong{Difficulty:} medium - @strong{Requirements:} C++, MIDI - @strong{Recommended:} familiarity with LilyPond internals - @strong{Mentor(s):} Mike Solomon, Carl Sorensen +@divEnd + +@divClass{column-center-middle-color3} @subheading MusicXML -Adding comprehensive MusicXML export and improving import, -together with tests checking that it works. Depending on time available, -implement some or all of the following: +Improving MusicXML import and export functions: @divClass{keep-bullets} @itemize @item Handle basic musical content export like the MIDI export (i.e. using -dedicated exporter classes, derived from the translator class) +dedicated exporter classes, derived from the translator class). @item -Build the XML tree of the basic musical content, -add a connection from music event to XML tag +Build the XML tree of the basic musical content, add a connection from +music event to XML tag. @item -Let all LilyPond engravers do their job +Let all LilyPond engravers do their job. @item -add ability to link each output object -(basically each stencil / group of stencils) to the music cause -(and thus to the XML tag in the XML tree) +Link each output object (i.e. each stencil or group of stencils) to the +music cause (and thus to the XML tag in the XML tree). @item -Add a XML output backend, which can then add the layout information -for each output object to the XML tags +Add an XML output backend, which can then add layout information for +each output object to the XML tags. @end itemize @divEnd -The goal will be considered achieved when a (previously chosen) score could be -imported from MusicXML and exported back with no unintentional loss of data. - @strong{Difficulty:} medium - @strong{Requirements:} MusicXML, Python, basic LilyPond knowledge - @strong{Mentor(s):} Reinhold Kainhofer, Mike Solomon -familiarity with other scorewriters (for cross-testing) would be a nice bonus. +Familiarity with other scorewriters (for cross-testing) would also help. +@divEnd + +@divClass{column-center-middle-color3} @subheading Improve slurs and ties -The default shape of slur and tie curves is often unsatisfactory. -Ties on enharmonic notes @code{@{ cis'~ des' @}} are not supported, -ties "broken" by clef or staff change aren't supported well. -The project includes collecting and sorting examples of bad output, -deciding on the intended output and writing the actual code. +The default curves of slurs and ties are often unsatisfactory. Ties +@q{broken} by clef or staff changes are not handled well. The project +could include collecting and sorting examples of bad output, deciding on +the intended output and writing code to improve them. @strong{Difficulty:} hard - @strong{Requirements:} C++, experience with writing heuristics - @strong{Recommended knowledge:} LilyPond knowledge, aesthetic sense - @strong{Mentor(s):} Mike Solomon -@subheading Adding special variant of font glyphs -Adding on-staff-line, between-staff-line, shorter and narrower variants -of some glyphs, for example accidentals, together with a generic -infrasctucture to support them. An example is ancient notation breve notehead -coming in two variants, with smaller and bigger hole. - -@strong{Difficulty:} easy - -@strong{Requirements:} MetaFont, C++, good eye for details - -@strong{Recommended knowledge:} basic LilyPond knowledge - -@strong{Mentor(s):} Werner Lemberg - -@subheading Improve beaming - -Default positioning of regular, cross-staff, broken and kneed beams -should be improved. Beaming should depend on context and neighbor notes (see -@uref{http://icking-music-archive.org/lists/sottisier/sottieng.pdf, section 2.2 here}). -If possible, reduce beaming computation time. - -@strong{Difficulty:} medium - -@strong{Requirements:} C++, experience with writing heuristics - -@strong{Recommended knowledge:} aesthetic sense - -@strong{Mentor(s):} Mike Solomon, Carl Sorensen +@divEnd -@subheading Better tablature support +@divClass{column-center-middle-color3} +@subheading Adding variants of font glyphs @divClass{keep-bullets} @itemize @item -non-monotonic string tunings, like Ukulele - -@item -create tablature input mode (currently musical information is entered -in western-common-music-notation-terms, i.e. @qq{a quarter f sharp note} -and then converted to tablature) for transcribing medieval lute tablature - -@item -implement modern tablature features, such as bends, pull-off, hammer-on +Adding @q{on} and @q{between} staff-line variants. @item -if a fretboard shape is defined for a given chord, use this information when -displaying the chord on the staff (and not just display a default chord shape) +Shorter and narrower variants of some glyphs for example, accidentals. +Another, more specific example could be an ancient notation breve +notehead coming in two variants one with a small or big @q{hole} within +it. @end itemize @divEnd @strong{Difficulty:} easy +@strong{Requirements:} MetaFont, C++, good eye for details +@strong{Recommended knowledge:} basic LilyPond knowledge +@strong{Mentor(s):} Werner Lemberg -@strong{Requirements:} C++ +@divEnd + +@divClass{column-center-middle-color3} +@subheading Improve default beam positioning + +For regular, cross-staff, broken and kneed beams. Beaming should depend +on context and neighbor notes +(see @uref{http://icking-music-archive.org/lists/sottisier/sottieng.pdf, +section 2.2 here}). If possible also reduce beaming-computation time. -@strong{Recommended knowledge:} tablature notation familiarity +@strong{Difficulty:} medium +@strong{Requirements:} C++, experience with writing heuristics +@strong{Recommended knowledge:} aesthetic sense +@strong{Mentor(s):} Mike Solomon, Carl Sorensen -@strong{Mentor(s):} Carl Sorensen +@divEnd -@subheading Clean up various compilation warnings +@divClass{column-center-middle-color3} +@subheading Help improve compilation behavior -Clean up compiler warnings, static code analysis, and valgrind warnings. -Automatic code analysis tools (warnings in @code{g++} and @code{clang}) -and analysis tools like valgrind memory leak detection and callgrind code -profilers provide valuable information about possible flaws in C++ code. -Cleaning these warnings would allow us to automatically reject any patch -which introduced extra warnings. +Automatic code analysis tools, like valgrind memory leak detection or +callgrind code profilers, provide valuable information about possible +flaws in our C++ code. Cleaning up warnings would allow us to automate +the rejection of any patch which introduced extra warnings. @strong{Difficulty:} medium - @strong{Requirements:} C++ - @strong{Mentor(s):} Joe Neeman, Reinhold Kainhofer @divEnd - - @node Authors @unnumberedsec Authors @@ -1144,6 +1117,16 @@ which introduced extra warnings. @divEnd @divEnd +@node Acknowledgements +@unnumberedsec Acknowledgements + +@divClass{column-center-top} +@subheading Acknowledgements + +@divClass{keep-bullets} +@acknowledgementsCurrent +@divEnd +@divEnd @node Publications @@ -1160,10 +1143,8 @@ which introduced extra warnings. @divEnd @divClass{column-center-bottom} - @subheading What people did with LilyPond - @divClass{keep-bullets} @include others-did.itexi @@ -1177,6 +1158,85 @@ which introduced extra warnings. @node Old news @unnumberedsec Old news +@divClass{heading-center} +@warning{Many old announcements and changelogs can be found in +the @ref{Attic}} +@divEnd + @include web/news-front.itexi @include web/news.itexi + + +@node Attic +@unnumberedsec Attic + +@divClass{column-center-top} +@subheading Announcements + +Announcements and news by version: +@uref{http://lilypond.org/doc/v2.16/Documentation/web/index#Lilypond-2_002e16_002e0-released_0021-August-24_002c-2012-1,v2.16}, +@uref{http://lilypond.org/doc/v2.14/Documentation/web/index#LilyPond-2_002e14_002e0-released_0021-June-6_002c-2011,v2.14}, +@miscLink{announce-v2.12,v2.12}, +@miscLink{announce-v2.10,v2.10}, +@miscLink{announce-v2.8,v2.8}, +@miscLink{announce-v2.6,v2.6}, +@miscLink{announce-v2.4,v2.4}, +@miscLink{announce-v2.2,v2.2}, +@miscLink{announce-v2.0,v2.0}, +@miscLink{ANNOUNCE-1.2,v1.2}, +@miscLink{ANNOUNCE-1.0,v1.0}, +@miscLink{ANNOUNCE-0.1,v0.1} + +Descriptive list of changes by version: +@uref{http://lilypond.org/doc/v2.16/Documentation/changes/index.html,v2.16}, +@uref{http://lilypond.org/doc/v2.14/Documentation/changes/index.html,v2.14}, +@uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS,v2.12}, +@uref{http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS,v2.10}, +@uref{http://lilypond.org/doc/v2.8/Documentation/topdocs/NEWS,v2.8}, +@uref{http://lilypond.org/doc/v2.6/Documentation/topdocs/NEWS,v2.6}, +@uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS,v2.4}, +@uref{http://lilypond.org/doc/v2.2/Documentation/topdocs/out-www/NEWS,v2.2}, +@uref{http://lilypond.org/doc/v2.0/Documentation/topdocs/out-www/NEWS,v2.0}, +@uref{http://lilypond.org/doc/v1.8/Documentation/topdocs/out-www/NEWS,v1.8}, +@uref{http://lilypond.org/doc/v1.6/Documentation/out-www/NEWS,v1.6}, +@miscLink{NEWS-1.4,v1.4}, +@miscLink{NEWS-1.2,v1.2} + +@divEnd + +@divClass{column-center-bottom} +@subheading Thanks + +Thanks to developers, contributors, bug hunters and suggestions for +@miscLink{THANKS-2.16,v2.16}, +@miscLink{THANKS-2.14,v2.14}, +@miscLink{THANKS-2.12,v2.12}, +@miscLink{THANKS-2.10,v2.10}, +@miscLink{THANKS-2.8,v2.8}, +@miscLink{THANKS-2.6,v2.6}, +@miscLink{THANKS-2.4,v2.4}, +@miscLink{THANKS-2.2,v2.2}, +@miscLink{THANKS-2.0,v2.0}, +@miscLink{THANKS-1.8,v1.8} + +@divEnd + +@divClass{column-center-bottom} +@subheading Changelogs + +Developers' changelogs by version: +@miscLink{ChangeLog-2.10,v2.10}, +@miscLink{ChangeLog-2.3,v2.3}, +@miscLink{ChangeLog-2.1,v2.1}, +@miscLink{ChangeLog-1.5,v1.5 (1)}, +@miscLink{CHANGES-1.5,v1.5 (2)}, +@miscLink{CHANGES-1.4,v1.4}, +@miscLink{CHANGES-1.3,v1.3}, +@miscLink{CHANGES-1.2,v1.2}, +@miscLink{CHANGES-1.1,v1.1}, +@miscLink{CHANGES-1.0,v1.0}, +@miscLink{CHANGES-0.1,v0.1}, +@miscLink{CHANGES-0.0,v0.0} + +@divEnd