X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fcommunity.itexi;h=eea46827a26eac0ee5895f7037499181cca26341;hb=acae40c266a7df9b4882f937c733745c803ac9e4;hp=933e2e83961670fb2e10e52473cd388977f03bc3;hpb=c833f8a341b81466e084ed031362eadeb4a815aa;p=lilypond.git diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index 933e2e8396..eea46827a2 100644 --- a/Documentation/web/community.itexi +++ b/Documentation/web/community.itexi @@ -7,7 +7,9 @@ Guide, node Updating translation committishes.. @end ignore +@include included/acknowledge.itexi @include included/authors.itexi +@include included/gsoc.itexi @include included/helpus.itexi @node Community @@ -48,11 +50,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 @@ -65,10 +70,11 @@ discussing LilyPond. @ref{Publications}: what we wrote, and have had written about us. @item -@ref{Old news}: an archive. +@ref{News}: news from the LilyPond project. @item -@ref{Attic}: announcements and changelogs from past versions. +@ref{Attic}: announcements and changelogs from past versions, +old news, etc. @end itemize @divEnd @@ -83,10 +89,11 @@ discussing LilyPond. * Help us:: * Sponsoring:: * Development:: -* GSoC:: +* Google Summer of Code:: * Authors:: +* Acknowledgements:: * Publications:: -* Old news:: +* News:: * Attic:: @end menu @divEnd @@ -129,7 +136,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 @@ -173,8 +180,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} @@ -182,26 +189,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 - -@subsubheading LilyPond Report +@subheading The LilyPond Blog -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} @@ -228,12 +228,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, @@ -253,7 +253,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, @@ -272,13 +273,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 @@ -410,7 +414,7 @@ then that is a bug. We may already know about this bug. Check here: @example -@uref{http://code.google.com/p/lilypond/issues/list} +@uref{http://sourceforge.net/p/testlilyissues/issues/} @end example @warning{Please @strong{DO NOT} add bug reports directly to the @@ -487,14 +491,15 @@ 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. +In order to be automatically notified about any activity on the +tracker issue, you may subscribe by clicking the envelope +symbol next to the issue title. +Commenting and subscribing require being logged in with a sourceforge account. @divEnd @divClass{column-center-bottom} @@ -595,10 +600,9 @@ active and experienced developers are. Statistics up to version Interested developers: @table @asis -@item @email{dak@@gnu.org, David Kastrup} -Donations are required to let me continue my current fulltime work on -LilyPond. I focus on user and programmer interface design, coherence, -implementation, simplification, documentation, and debugging. +@item @email{lilypond-devel@@gnu.org, LilyPond developer list} +Since no developer currently is listed for commercial development, +your best bet is asking on the developer list. @c Format @c @item @email{name@@adress.domain, Name} @@ -759,7 +763,7 @@ This release's lilypond-book tests. @itemize @item @uref{http://lilypond.org/test, Comparisons between regression tests} -@item @uref{http://lilypond.org/download/binaries/test-output/, +@item @uref{http://lilypond.org/downloads/binaries/test-output/, Archive of all regression tests} @end itemize @@ -780,6 +784,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 @@ -800,7 +805,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 @@ -823,7 +830,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 @@ -853,217 +862,28 @@ 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 ifset - @end multitable +@end ifset -@divEnd -@divEnd - - - - -@node GSoC -@unnumberedsec GSoC - -@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.} - -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! - -We are participating in GSoC as a part of GNU Project. See -@uref{http://www.gnu.org/software/soc-projects/guidelines.html, -GNU GSoC webpage} for information on how to participate. - -@divEnd - -@divClass{column-center-bottom} -@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 suggest your own! -It's also possible to scale down a project if you feel it's too big. - -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. - -@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. - -@strong{Difficulty:} medium - -@strong{Requirements:} C++, MIDI - -@strong{Recommended:} familiarity with LilyPond internals - -@strong{Mentor(s):} Mike Solomon, Carl Sorensen - -@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: - -@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) - -@item -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 - -@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) - -@item -Add a XML output backend, which can then add the 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. - -@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. - -@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 -infrastructure 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 - -@subheading Better tablature support - -@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 - -@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) - -@end itemize @divEnd -@strong{Difficulty:} easy - -@strong{Requirements:} C++ - -@strong{Recommended knowledge:} tablature notation familiarity -@strong{Mentor(s):} Carl Sorensen -@subheading Clean up various compilation warnings - -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. - -@strong{Difficulty:} medium - -@strong{Requirements:} C++ - -@strong{Mentor(s):} Joe Neeman, Reinhold Kainhofer - -@divEnd +@node Google Summer of Code +@unnumberedsec Google Summer of Code +@gsocCurrent @node Authors @@ -1150,6 +970,16 @@ any patch which introduced extra warnings. @divEnd @divEnd +@node Acknowledgements +@unnumberedsec Acknowledgements + +@divClass{column-center-top} +@subheading Acknowledgements + +@divClass{keep-bullets} +@acknowledgementsCurrent +@divEnd +@divEnd @node Publications @@ -1178,18 +1008,16 @@ any patch which introduced extra warnings. @contactUsAbout{academic papers} -@node Old news -@unnumberedsec Old news +@node News +@unnumberedsec 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 +@include web/news-new.itexi +@divClass{column-center-bottom} +@subheading Old News +Older news can be found in the @ref{Attic}, along with older +announcements and changelogs +@divEnd @node Attic @unnumberedsec Attic @@ -1198,6 +1026,7 @@ the @ref{Attic}} @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}, @@ -1211,6 +1040,7 @@ Announcements and news by version: @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}, @@ -1226,10 +1056,27 @@ Descriptive list of changes by version: @divEnd -@divClass{column-center-bottom} +@divClass{column-center-middle-color3} +@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-middle-color3} @subheading Changelogs -Developpers' changelogs by version: +Developers' changelogs by version: @miscLink{ChangeLog-2.10,v2.10}, @miscLink{ChangeLog-2.3,v2.3}, @miscLink{ChangeLog-2.1,v2.1}, @@ -1244,3 +1091,16 @@ Developpers' changelogs by version: @miscLink{CHANGES-0.0,v0.0} @divEnd + +@divClass{column-center-middle-color2 bigger-subsubheadings} +@gsocInactive +@divEnd + +@divClass{column-center-middle-color2} +@subheading Old News + +Older news items dating back to July 2003. Newer news can be found on +the @ref{News} page. +@divEnd + +@include web/news-old.itexi