Google Summer of Code 2016
El Proyecto Fedora ha representado el programa Google Summer of Code durante diez años y también participamos en el programa de 2016. Esta página wiki sirve como portal de GSoC. No dude en contactarnos a través del listado sumer-coding para obtener aclaraciones y más información. También puede usar el canal de IRC, #fedora-summer-coding.
Estudiantes
Students who are looking for challenges and would like to contribute to the world’s most leading and innovative Linux distribution, this could be the chance. Please feel free to contact and refer to the material and start contacting mentors.
¿Por qué pasar el verano trabajando en FOSS?
Cuando trabajas abiertamente con software libre, creas un corpus de trabajo que te acompaña toda la vida. En lugar de una tarea de programación realizada por miles de estudiantes y relegada al fondo del cajón al final del semestre, trabajar con software libre es una oportunidad para contribuir a un proyecto vivo.
Trabajar en FOSS te da la oportunidad de:
-
Trabaje con bases de código grandes y del mundo real.
-
Colabora con ingenieros reales y otros expertos profesionales.
-
Contribuya a algo significativo mientras aprende y gana valor estudiantil.
-
Aprenda herramientas y procesos similares a los que utilizará si trabaja en tecnología después de graduarse.
-
Haz amigos y contactos en todo el mundo.
-
Posiblemente atraiga la atención que le permita conseguir una pasantía o un trabajo después de graduarse.
-
Create lifetime connections.
¿Por qué trabaja con Fedora?
Nuestro proyecto es grande y diverso. Son muy experimentados en trabajar con contribuidores nuevos y ayudarlos para triunfar.
Many long-time contributors continue to be around, lending expertise and mentoring. People who stay around the community and do good work are noticed. They get hired for jobs from it, including being hired by Red Hat. Past Google Summer of Code students were hired by Red Hat, as well as interns in various positions. This is just an example, as experience and reputation in the Fedora Project communities is influential on your career in many ways. As long-standing communities with many facets, it is possible for you to find many rewarding sub-projects to work on.
Debes saber que contribuir al software libre no requiere grandes habilidades de programación ni nada por el estilo. Solo necesitas interés y curiosidad, y estar dispuesto a sentirte cómodo estando productivamente perdido. Este es el estado de aprendizaje a través de la búsqueda de soluciones.
Guía paso a paso para estudiantes
Please check the step-by-step guide for students.
Administración
In order to clarify matters and/or obtain more information related with this year’s GSoC with Fedora, please contact the administrators directly (please consider CCing the summer-coding list where ever possible).
Mentores
The contributors of the Fedora Project can propose ideas and mentor them. Please feel free to check following links and please add your ideas to the main idea page. Furthermore, if you are not interested in proposing an idea but still want to support the program, please check the students' idea page and pick one as per your interest.
Como trabajar con estudiantes
-
One way is to provide an idea for students to work on. This idea might be very well planned out, in which case you may need a high-level of contact with the student to get it implemented correctly.
-
It is harder to find success where you are completely certain of how an idea needs to be implemented; finding a student with the skills and interest to implement a specific solution is a lot harder than finding a student with enough skills to respond to a use case need.
-
Where you can have looser ideas, you may be able to find a student who works as a sort-of intern who can implement a solution to a use case you have. In past experiences, students going after a use case are more likely to get somewhere with self-direction.
-
You may also want to work with a student who brings an idea to your sub-project. This requires a different level of communication throughout the project, but can be the most rewarding.
Responsabilidades del mentor
You are an essential part of the student’s success, the project’s success, and the success for your overall organization (Fedora, JBoss.org, or another).
Sus responsabilidades incluyen:
-
Ser una interfaz para un subproyecto o SIG identificado en Fedora.
-
Ayudar a los estudiantes a comunicarse con el proyecto en general y con cualquier etapa previa.
-
Be the final, accountable person for deciding if the student is successful or not, which affects payment.
Comunicación
Mailing List (GSOC related) : summer-coding
Mailing List (Technical) : devel
IRC : Channel - #fedora-summer-coding or #fedora-devel on Freenode
Cronología (Versión estudiante)
-
Referencia: Cronología Completa
-
13 de octubre de 2025: programa anunciado.
-
8 de febrero de 2016: 19:00 UTC Las organizaciones de mentoría pueden comenzar a enviar solicitudes a Google.
-
19 de febrero: 19:00 UTC Fecha límite de solicitud para organizaciones de mentoría.
-
20 - 29 de febrero: Los administradores del programa de Google revisan las solicitudes de la organización.
-
29 de febrero, 19:00 UTC Lista de organizaciones de mentoría aceptadas publicada en el sitio web de Google Summer of Code 2016.
Período intermedio: Los futuros estudiantes discuten ideas de proyectos con posibles organizaciones de mentoría.
-
14 de marzo: 19:00 UTC Se abre el período de solicitud de estudiantes.
-
25 de marzo: 19:00 UTC Fecha límite de solicitud de estudiantes.
Interim Period: Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
Interim Period: Slot allocation trades happen among organizations. Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
-
22 April: Accepted student proposals announced on the Google Summer of Code 2016 site.
Community Bonding Period: Students get to know mentors, read documentation, get up to speed to begin working on their projects.
-
23 May: Students begin coding for their Google Summer of Code projects; Google begins issuing initial student payments provided tax forms are on file and students are in good standing with their communities.
Work Period: Mentors give students a helping hand and guidance on their projects.
-
20 June: 19:00 UTC Mentors and students can begin submitting mid-term evaluations.
-
'''27 June: 19:00 UTC '''Mid-term evaluations deadline; Google begins issuing mid-term student payments provided passing student survey is on file.
Work Period: Mentors give students a helping hand and guidance on their projects.
-
15 August: Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc.
-
21 to 23 August: Final week: Students tidy code, write tests, improve documentation and submit their code sample. Students also submit their final mentor evaluation.
-
23 August: Mentors can start submitting final student evaluations.
-
29 August: 19:00 UTC Final evaluation deadline
-
30 August: Final results of Google Summer of Code 2016 announced
-
Late October: Mentor Summit at Google. Mentors and Organization Administrators from each participating organization are invited to Google for an unconference to collaborate on ideas to make the program better and to make new friends too!
Want to help? Learn how to contribute to Fedora Docs ›