+@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
+