Section 2.5 of the Mentoring Organization agreement specifies that projects cannot be documentation.
http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/org_admin_agreement So it seems to me that unless we turn this project into a texi2html-to-texi2any translator, it is out of scope. Carl Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone -------- Original message -------- From: Urs Liska <u...@openlilylib.org> Date: 02/04/2016 2:14 AM (GMT-07:00) To: Federico Bruni <f...@inventati.org> Cc: lilypond-devel <lilypond-devel@gnu.org> Subject: Re: Mentors needed for GSoC suggestions Am 03.02.2016 um 12:14 schrieb Federico Bruni: > Hi Urs > > I jump in late to ask if the transition to texi2any might be added to > the list. > It might not be a sexy project but it's very needed and we all know > how much the documentation is important for LilyPond. > > If Graham confirms his availability to be a mentor for this project, > we may add this fifth project. > > http://lists.gnu.org/archive/html/lilypond-devel/2015-07/msg00204.html > https://github.com/barrykp/lilypond-texinfo > https://sourceforge.net/p/testlilyissues/issues/1557/ > > What do you think? > Unfortunately Graham "is not in a position to provide GSoC style mentoring". However, he would be willing to offer a few hours of feedback to a LilyPond developer. So: if someone volunteers to at least make a GSoC-page-like project description of it I can integrate that in the patch I'm currently preparing. Urs _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
