Web-it: update for 2.16.1 release

[lilypond.git] / Documentation / web / community.itexi

diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi
index 6987dec8fcb545b55f8329392e4d632e21808b05..d06932a3ff44905ccc32aac598f7a4c9c1e35b42 100644 (file)
--- a/Documentation/web/community.itexi
+++ b/Documentation/web/community.itexi
@@ -48,7 +48,7 @@ discussing LilyPond.
 @ref{Development}: for contributors and testers.
 
 @item
 @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{Authors}: the people who made LilyPond what it is today.


@@ -67,6 +67,9 @@ discussing LilyPond.
 @item
 @ref{Old news}: an archive.
 
 @item
 @ref{Old news}: an archive.
 

+@item
+@ref{Attic}: announcements and changelogs from past versions.
+

 @end itemize
 @divEnd
 
 @end itemize
 @divEnd
 


@@ -80,10 +83,11 @@ discussing LilyPond.
 * Help us::
 * Sponsoring::
 * Development::
 * Help us::
 * Sponsoring::
 * Development::

-* GSoC::
+* GSoC 2012::

 * Authors::
 * Publications::
 * Old news::
 * Authors::
 * Publications::
 * Old news::

+* Attic::

 @end menu
 @divEnd
 
 @end menu
 @divEnd
 


@@ -515,13 +519,13 @@ demonstrate what you think it should look like!
 
 @divClass{column-left-top}
 @divClass{keep-bullets}
 
 @divClass{column-left-top}
 @divClass{keep-bullets}

-@helpusTasks
+@helpusSimple

 
 @divEnd
 @divEnd
 
 @divClass{column-right-top}
 
 @divEnd
 @divEnd
 
 @divClass{column-right-top}

-@helpusProjects
+@helpusAdvanced

 
 @divEnd
 
 
 @divEnd
 


@@ -555,7 +559,7 @@ in mind the following points:
 
 @itemize
 @item
 
 @itemize
 @item

-LilyPond developers may advertise their services on the lilypnod
+LilyPond developers may advertise their services on the lilypond

 email lists from time to time.
 
 @item
 email lists from time to time.
 
 @item


@@ -865,53 +869,46 @@ manuals can be found at @url{http://lilypond.org}}
 
 
 
 
 
 

-@node GSoC
-@unnumberedsec GSoC
+@node GSoC 2012
+@unnumberedsec GSoC 2012

 
 @divClass{column-center-top}
 @subheading What is 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.}
+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
 
 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}.
+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}
 
 @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 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 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.

 
 

-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
 
 @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
 
 
 @strong{Difficulty:} medium
 


@@ -942,7 +939,7 @@ add a connection from music event to XML tag
 Let all LilyPond engravers do their job
 
 @item
 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)
 
 (basically each stencil / group of stencils) to the music cause
 (and thus to the XML tag in the XML tree)
 


@@ -953,8 +950,9 @@ for each output object to the XML tags
 @end itemize
 @divEnd
 
 @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{Difficulty:} medium
 


@@ -962,7 +960,8 @@ imported from MusicXML and exported back with no unintentional loss of data.
 
 @strong{Mentor(s):} Reinhold Kainhofer, Mike Solomon
 
 
 @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 Improve slurs and ties
 


@@ -983,8 +982,8 @@ deciding on the intended output and writing the actual code.
 @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
 @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
 
 
 @strong{Difficulty:} easy
 


@@ -997,9 +996,9 @@ coming in two variants, with smaller and bigger hole.
 @subheading Improve beaming
 
 Default positioning of regular, cross-staff, broken and kneed beams
 @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{Difficulty:} medium
 


@@ -1009,45 +1008,14 @@ If possible, reduce beaming computation time.
 
 @strong{Mentor(s):} Mike Solomon, Carl Sorensen
 
 
 @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})
 @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
 
 
 @strong{Difficulty:} medium
 


@@ -1160,10 +1128,8 @@ which introduced extra warnings.
 @divEnd
 
 @divClass{column-center-bottom}
 @divEnd
 
 @divClass{column-center-bottom}

-

 @subheading What people did with LilyPond
 
 @subheading What people did with LilyPond
 

-

 @divClass{keep-bullets}
 
 @include others-did.itexi
 @divClass{keep-bullets}
 
 @include others-did.itexi


@@ -1177,6 +1143,66 @@ which introduced extra warnings.
 @node Old news
 @unnumberedsec Old news
 
 @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
 @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
+
+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