@ref{Development}: for contributors and testers.
@item
-@ref{GSoC}: list of projects for Google Summer of Code.
+@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.
@item
@ref{Old news}: an archive.
+@item
+@ref{Attic}: announcements and changelogs from past versions.
+
@end itemize
@divEnd
* Help us::
* Sponsoring::
* Development::
-* GSoC::
+* GSoC 2012::
* Authors::
* Publications::
* Old news::
+* Attic::
@end menu
@divEnd
-@node GSoC
-@unnumberedsec GSoC
+@node GSoC 2012
+@unnumberedsec GSoC 2012
@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.}
+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, 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.
+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 Ideas List
+@subheading Our 2012 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.
+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 inpiration 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.
-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.
+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.
+@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
Let all LilyPond engravers do their job
@item
-add ability to link each output object
+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)
@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.
+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{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 be a nice
+bonus.
@subheading Improve slurs and ties
@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.
+infrastructure to support them. An example is ancient notation breve
+notehead coming in two variants, with smaller and bigger hole.
@strong{Difficulty:} easy
@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.
+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{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.
+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
@divEnd
@divClass{column-center-bottom}
-
@subheading What people did with LilyPond
-
@divClass{keep-bullets}
@include others-did.itexi
@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.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.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 Changelogs
+
+Developpers' 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
projects / lilypond.git / blobdiff