+LilyPond es muy bueno creando notación no estándar. Tener que
+@emph{codificar} cada uno de los elementos gráficos en lugar de
+simplemente @emph{dibujarlo} puede parecer engorroso pero de hecho
+es una gran virtud. Se pueden implementar funcionalidades
+notacionales nuevas con apariencia consistente, disposición
+automática y una interfaz sintáctica natural.
+
+Dentro del sistema de biblioteca
+@uref{https://github.com/openlilylib/oll-core, openLilyLib} el
+alumno creará una infraestructura fundamental y unos bloques
+constructivos para hacer más fácil la creación de notación
+contemporánea. Además (al menos) @emph{un} paquete en concreto se
+desarrollará para cubrir alguna notación contemporánea específica,
+como por ejemplo el estilo de algún compositor dado, técnicas de
+ejecución extendidas para un instrumento específico o una cierta
+categoría de efectos.
+
+@emph{Dificultad:} media
+
+@emph{Requisitos:} Scheme (interacción con las interioridades de LilyPond),
+técnicas de notación contemporánea
+
+@emph{Conocimientos recomendados:} habilidad para la elaboración de marcos de funcionamiento jerárquicos
+
+@emph{Mentores:} @strong{NN,} Urs Liska
+
+
+@subsubheading Reescritura de la extensión de LilyPond para LibreOffice con Python
+
+La extensión @uref{http://ooolilypond.sourceforge.net/,
+OOoLilyPond} hace posible incluir de forma muy práctica fragmentos
+de partitura de LilyPond dentro de documentos de
+OpenOffice.org/LibreOffice Writer, Draw e Impress, manteniendo al
+mismo tiempo la fuente y la imagen juntas. Después de muchos años
+sin desarrollo, se ha iniciado una tarea de hacer de nuevo que la
+extensión sea compatible con las versiones actuales de LibreOffice
+y de LilyPond.
+
+Sin embargo, según el ecosistema de LibreOffice ha cambiado
+significativamente, ahora es posible reescribir la extensión con
+Python y PyQt. Esto no solo será más potente en general, sino que
+permitirá la integración de funcionalidades de
+@uref{http://frescobaldi.org, Frescobaldi}, tales como el
+resaltado de sintaxis, facilidades durante la escritura,
+asistentes de partitura o transformaciones musicales.
+
+@emph{Dificultad:} baja/media
+
+@emph{Requisitos:} Python, PyQt, conceptos básicos de LilyPond y
+de extensiones de LibreOffice
+
+@emph{Conocimientos recomendados:} Familiaridad con la base de
+código de Frescobaldi o disposición para aprenderla durante el
+período fijado
+
+@emph{Mentor(es):} Joram Berger, Urs Liska, (Thorsten Behrens/LibreOffice)
+
+
+@subsubheading Pruebas y documentación automatizadas para openLilyLib
+
+@uref{https://github.com/openlilylib, openLilyLib} is an extension
+framework for LilyPond code providing a “snippets” repository and
+a suite of integrated packages such as for example page layout
+tools or scholarly annotations. It is very powerful and
+promising, but to really get off the ground two features are
+missing: automated testing and documentation generation.
+
+Automated testing is necessary to ensure modifications to
+functionality don't break other functions within the library.
+There is already some Automated Testing of the “snippets”
+repository with Github's Travis server, but this has to be
+reconsidered and extended to cover the standalone packages too.
+
+In order to be usable for a wider range of LilyPond users on a
+“consumer level” openLilyLib needs proper documentation. This
+documentation has to be generated from the sources, so a system is
+needed that requires package authors to document the input files
+and provide additional usage examples, from which documentation is
+generated. Ideally but not necessarily this is implemented as a
+Git hook, i.e. automatically upon each update to the repository.
+We don't prescribe the tools and approaches to be used, but the
+most widely used language in the LilyPond domain is Python, so
+there would be some bias towards that. Alternatively a Scheme
+solution could be fine so generating the documentation would
+actually be triggered by “compiling” a certain LilyPond input
+file. In general it is advisable to make use of proven concepts
+and tools from other languages.
+
+The eventual output of the documentation should be a static HTML
+site that can be viewed locally and/or uploaded to a website. But
+it would be beneficial if the tool would first generate an
+intermediate representation (e.g. a JSON file with additional
+media files) from which a Single Page Application could retrieve
+content for display on openLilyLib's
+@uref{https://openlilylib.org, website}. Development of such a
+SPA @emph{can} be part of the GSoC project, but is optional.
+
+@emph{Dificultad:} media
+
+@emph{Requisitos:} Python or Scheme, static website generator(s) or
+(Node.js based) dynamic web application technology. Continuous
+Integration (can be learned during the bonding period)
+
+@emph{Mentores:} Urs Liska, Matteo Ceccarello
+
+
+@subsubheading MusicXML
+
+Mejora de las funciones de importación y exportación de MusicXML:
+
+File interchange between LilyPond and other applications using
+MusicXML is still a difficult matter. To import MusicXML it has
+to be converted manually by the @code{musicxml2ly} script. Export
+@emph{to} MusicXML is only available as a rudimentary feature
+inside Frescobaldi. In order to provide natural interchange
+between LilyPond and MusicXML based applications there's the need
+of actual import functionality and a dedicated export backend.
+
+Importing XML shall provide file, line and column to add origin
+attributes to generated objects. That way point and click can be
+made available in Frescobaldi or other supported IDEs.
+
+Exporting XML shall be realized with an exporter class like the
+MIDI export. This may be based on the work already done in
+@uref{https://github.com/DavidGarfinkle/Lilypond_MusicXMLexport, GSoC 2015}
+by David Garfinkle. It should be checked if it is possible to use
+another XML library than the one provided by guile-2 in order to
+have this feature available in current LilyPond (which is based on
+guile-1.8).
+
+@emph{Dificultad:} media
+
+@emph{Requisitos:} MusicXML, Python, Scheme, basic LilyPond knowledge
+
+@emph{Conocimientos recomendados:} Familiarity with other scorewriters (for cross-testing)
+
+@emph{Mentor:} Jan-Peter Voigt
+
+@divEnd
+
+
+@divClass{column-center-middle-color2}
+@subheading Información para los solicitantes o participantes
+
+In order to have a satisfying experience with GSoC applicants are
+strongly advised to thoroughly read the following recommendations.
+Some of these are relevant for the application process, others for
+the time within the project.
+
+@itemize
+
+@item
+Read all applicable information on the program's website,
+particularly the
+@uref{https://developers.google.com/open-source/gsoc/resources/manual,
+students' manual}. Make sure you fulfil all of Google's
+prerequisites and are willing to join the program as a full-time
+commitment over the coding period of three months.
+
+@item
+Please get in touch with us as soon as possible if you are
+interested in applying with a project. Mentor availability may
+change without notice, project proposals may need fine-tuning, and
+many other reasons might require us to reject or ignore an
+application that hasn't been discussed before.
+
+@item
+We do not know in advance how many “slots” we will have available
+for projects, so please be aware that you may find yourself in
+competition with other applicants or not. Interested or even
+enthusiastic response from our mentors is no guarantee of
+eventually being accepted, and @emph{not} being accepted does not
+necessarily indicate a negative evaluation of your application.
+If we have to decide between different applicants there may be
+various aspects to consider.
+
+@item
+Integration in the LilyPond community is a fundamental part of
+GSoC, and we expect our students to make substantial efforts to
+become community members. Within the @emph{bonding period} we
+expect you to write a blog post about your project (either on
+@uref{http://lilypondblog.org, Scores of Beauty} or on any other
+blog) and to be active on our mailing lists, introducing yourself
+but also communicating about unrelated tasks. This goes beyond
+the mere setting up of a working environment and familiarizing
+yourself with the relevant code, but we think it is crucial for
+the GSoC project to be mutually satisfying.
+
+@item
+If you are accepted to the program you will have one mentor
+explicitly assigned to your project. With this mentor you will
+have to agree upon a communication strategy, be it emails,
+chatrooms, issue trackers or voice/video chats. Regular
+communication is absolutely crucial for the success of a GSoC
+project so you are stricly required to keep talking to your
+mentor. But keep in mind that your mentor has explicitly taken
+over the responsibility for your project, and while unlike you he
+isn't paid for this activity you are still entitled to get regular
+attention from him.
+
+@item
+In order to get support from your mentor you have to give him a
+chance to follow your progress and efforts. Therefore it is
+important to regularly commit your changes to the versioning
+repository you are working on. Don't hesitate making unfinished
+code available because you are afraid of criticism, and don't
+suppress questions because you think they might be considered
+stupid. But ideally your code should at any time be accompanied
+by compatible testing code. Your mentor may not be able to
+properly assess your code by only @emph{reading} it without the
+opportunity to apply it in a real example.
+
+@end itemize
+
+Existe una lista de proyectos inactivos en el @ref{Desván}.
+Mantenemos en la lista los proyectos que aún se consideran
+valiosos, pero para los cuales no existe en la actualidad ningún
+mentor disponible.
+
+@divEnd