X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fcommunity.itexi;h=719367e35aa6eb19a71ec14275afec92070783aa;hb=2f7de62c4aae9fca03fd754a9f44ff02a272eb30;hp=d26509623a673974348adf5c68c25635c1f04b98;hpb=abf0836f8aab813d08b6981413dc9f83eff0b70f;p=lilypond.git diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index d26509623a..719367e35a 100644 --- a/Documentation/web/community.itexi +++ b/Documentation/web/community.itexi @@ -47,6 +47,9 @@ discussing LilyPond. @item @ref{Development}: for contributors and testers. +@item +@ref{GSoC 2012}: our ideas for 2012 edition of Google Summer of Code. + @item @ref{Authors}: the people who made LilyPond what it is today. @@ -64,6 +67,9 @@ discussing LilyPond. @item @ref{Old news}: an archive. +@item +@ref{Attic}: announcements and changelogs from past versions. + @end itemize @divEnd @@ -77,9 +83,11 @@ discussing LilyPond. * Help us:: * Sponsoring:: * Development:: +* GSoC 2012:: * Authors:: * Publications:: * Old news:: +* Attic:: @end menu @divEnd @@ -390,12 +398,16 @@ quite often 4 lines are enough to demonstrate the problem! @node Bug reports @unnumberedsec Bug reports + +@divClass{heading-center} +If you have input that results in a crash or wrong output, +then that is a bug. +@divEnd + @divClass{column-center-top} @subheading Step 1: Known bugs -If you have input that results in a crash or an erroneous output, -then that is a bug. There is a list of current bugs on our google -bug tracker, +We may already know about this bug. Check here: @example @uref{http://code.google.com/p/lilypond/issues/list} @@ -411,12 +423,12 @@ free to add more information to that report.} @divClass{column-left-bottom} @subheading Step 2: Creating a bug report -If you have discovered a bug which is not listed, please help us -by creating a bug report. +If you have discovered a bug which is not listed, +please help us by creating a bug report. -@warning{We only accept bug reports in the form of -@ref{Tiny examples}. We have very limited resources to deal with -bug reports, so any non-minimal example will be rejected. Almost +@warning{We only accept reports in the form of +@ref{Tiny examples}. We have very limited resources, +so any non-minimal example will be rejected. Almost every bug can be demonstrated in four notes or less!} Here is an example of a good bug report: @@ -473,13 +485,14 @@ report. @divClass{column-center-bottom} @subheading Step 4: Wait for a response -Once your bug has been sent to the list, our Bug Squad will -examine the report. Please allow up to 4 days, as we have a -limited number of volunteers for this task. They may ask you for -more information, or may add the report to the tracker and let you -know what the issue number is. +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. -You may mark the bug so that you automatically receive emails when +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. @divEnd @@ -856,6 +869,165 @@ manuals can be found at @url{http://lilypond.org}} +@node GSoC 2012 +@unnumberedsec GSoC 2012 + +@divClass{column-center-top} +@subheading What is Google Summer of Code? + +It is 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 and encourage students already participating in LilyPond +development to become more involved. One of our contributors was accepted +for 2012 edition of the program as part of the +@uref{http://www.gnu.org/, GNU project}; +we hope to participate in future editions as well. + +@divEnd + +@divClass{column-center-bottom} +@subheading Our 2012 Ideas List + +Below is a list of projects that we suggested for GSoC 2012 students. +Although the application period is over, we decided to keep this webpage +online as an inspiration for anyone who is interested in developing LilyPond. +Some members of the development team are willing to help people who would like +to tackle these projects. + +Of course, there are many more things to improve in LilyPond, including +very small ones. A full list of all known issues can be found +@uref{http://code.google.com/p/lilypond/issues/list, here}. + +@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 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 Authors @unnumberedsec Authors @@ -956,10 +1128,8 @@ manuals can be found at @url{http://lilypond.org}} @divEnd @divClass{column-center-bottom} - @subheading What people did with LilyPond - @divClass{keep-bullets} @include others-did.itexi @@ -973,6 +1143,85 @@ manuals can be found at @url{http://lilypond.org}} @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