@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}
@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}
@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,
@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,
@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
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
@divClass{column-center-top}
@subheading What is Google Summer of Code?
-A global program run by Google that offers students stipends for working
-on open source software projects during summer vacations.
+@uref{https://developers.google.com/open-source/gsoc/, GSoC} is a global
+program that offers students stipends to write code for free software
+and open source projects during the summer. It is an excellent
+opportunity for students to gain experience with real-world software
+development and make a contribution that benefits everyone. It brings
+new contributors to LilyPond and enables students who are already
+involved to become more involved. LilyPond participates in GSoC as part
+of the @uref{http://www.gnu.org/, GNU project}.
+
+We have had GSoC participants in 2012 and 2015 and encourage students to
+apply for future summers.
-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.
+If you have questions or would like to apply, send us an email on our
+developer mailing list (see @ref{Contact}).
@divEnd
-@divClass{column-center-bottom}
-@subheading Our Ideas List
+@divClass{column-center-middle-color2}
+@subheading Project Ideas List
-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.
+Below is a list of projects that was initially drawn up for GSoC 2012.
+It is maintained here as inspiration for future GSoC projects and for
+anyone who is interested in developing LilyPond.
-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.
+Note that this is not an exhaustive list. Other GSoC projects are also
+possible. There are a number of areas where LilyPond could be improved
+and the LilyPond development team is always willing to help those who
+would like to tackle a project like those listed below.
A full list of all the current open issues can be found
-@uref{http://code.google.com/p/lilypond/issues/list, here}.
+@uref{http://sourceforge.net/p/testlilyissues/issues/, here}.
+@divEnd
+
+@divClass{column-center-middle-color3}
@subheading Grace notes
Fix problems with synchronization of grace notes. Grace notes can
@strong{Difficulty:} medium
@strong{Requirements:} C++, MIDI
@strong{Recommended:} familiarity with LilyPond internals
-@strong{Mentor(s):} Mike Solomon, Carl Sorensen
+@strong{Potential Mentors:} Mike Solomon, Carl Sorensen
+
+@divEnd
+@divClass{column-center-middle-color3}
@subheading MusicXML
Improving MusicXML import and export functions:
@strong{Difficulty:} medium
@strong{Requirements:} MusicXML, Python, basic LilyPond knowledge
-@strong{Mentor(s):} Reinhold Kainhofer, Mike Solomon
+@strong{Potential Mentors:} Reinhold Kainhofer, Mike Solomon
Familiarity with other scorewriters (for cross-testing) would also help.
+@divEnd
+@divClass{column-center-middle-color3}
@subheading Improve slurs and ties
The default curves of slurs and ties are often unsatisfactory. Ties
@strong{Difficulty:} hard
@strong{Requirements:} C++, experience with writing heuristics
@strong{Recommended knowledge:} LilyPond knowledge, aesthetic sense
-@strong{Mentor(s):} Mike Solomon
+@strong{Potential Mentor:} Mike Solomon
+
+@divEnd
+@divClass{column-center-middle-color3}
@subheading Adding variants of font glyphs
@divClass{keep-bullets}
@strong{Difficulty:} easy
@strong{Requirements:} MetaFont, C++, good eye for details
@strong{Recommended knowledge:} basic LilyPond knowledge
-@strong{Mentor(s):} Werner Lemberg
+@strong{Potential Mentor:} Werner Lemberg
+@divEnd
+
+@divClass{column-center-middle-color3}
@subheading Improve default beam positioning
For regular, cross-staff, broken and kneed beams. Beaming should depend
@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
+@strong{Potential Mentors:} Mike Solomon, Carl Sorensen
+
+@divEnd
+@divClass{column-center-middle-color3}
@subheading Help improve compilation behavior
Automatic code analysis tools, like valgrind memory leak detection or
@strong{Difficulty:} medium
@strong{Requirements:} C++
-@strong{Mentor(s):} Joe Neeman, Reinhold Kainhofer
+@strong{Potential Mentors:} Joe Neeman, Reinhold Kainhofer
@divEnd
projects / lilypond.git / blobdiff