Google Summer Of Code 2018: Call for mentors

Published on 1/6/2018 by Oleg Nenashev

    This year the Jenkins project is interested in participating in Google Summer of Code (GSoC). As in 2016/2017, we are looking for mentors. So yes, we are looking for you :)

    Jenkins GSoC

    What is GSoC?

    GSoC is an annual international program which encourages college-aged students to participate with open source projects during the summer break between classes.

    Students accepted into the program receive a stipend, paid by Google, to work on well-defined projects to improve or enhance the Jenkins project. In exchange, numerous Jenkins community members volunteer as mentors for students to help integrate them into the open source community and succeed in completing their summer projects.

    What do mentors get?

    • A student who works full-time in the area of your interest for several months

    • Joint projects with Jenkins experts, lots of fun and ability to study something together

    • Limited-edition of swags from Google and Jenkins project

    • Maybe: Participation in GSoC Mentor Summit and other GSoC events/meetups

    Conditions

    Mentors are expected to…​

    • Be passionate about Jenkins

    • Lead the project in the area of their interest

    • Actively participate in the project during student selection, community bonding and coding phases (March - August)

    • Work in teams of 2+ mentors per 1 each student

    • Dedicate a consistent and significant amount of time, especially during the coding phase (~5 hours per week in a team of two mentors)

    Mentorship does NOT require strong expertise in Jenkins plugin development. The main objective is to guide students and to get them involved into the Jenkins community. GSoC org admins will help to find advisors if a special expertise is needed.

    Disclaimer: We cannot guarantee that the Jenkins organization gets accepted to GSoC. Even if it gets accepted, we may need to select projects depending on student applications and the number of allocated project slots.

    Timeline

    • Dec 2017 - started collecting project ideas

    • Jan 17 - Status review at the Jenkins Governance Meeting. Outcome: decision whether we apply to GSoC in 2018.

    • Jan 21 - Application to GSoC (deadline - Jan 23)

    • Feb 12 - List of accepted mentoring organizations published

    • Mar 05 - Deadline for project idea proposals

    • Next - GSoC Timeline

    How to apply?

    If you are interested in proposing a project or joining an existing one, please respond to this thread in the Jenkins Developer mailing list. We aggregate/review proposals in this document where you just need to describe the idea and introduce yourself.

    Please propose new project ideas for discussion until March 05. You can join an existing project at any time, including community bonding and coding periods.

    Project requirements

    • GSoC is about code (though it may and likely should include some documentation and testing work)

    • Projects should be about Jenkins (plugins, core, infrastructure, integrations, etc.)

    • Projects should be potentially doable by a student in 3-4 months

    You can find more information about requirements and practices in the GSoC Mentor Guide.

    About the Author
    Oleg Nenashev
    		Oleg Nenashev

    Jenkins core maintainer and board member, open source software and open hardware advocate, TOC chair in the Continuous Delivery Foundation. Oleg started using Hudson for Hardware/Embedded projects in 2008 and became an active Jenkins contributor in 2012. Nowadays he maintains [Jenkinsfile Runner](https://github.com/jenkinsci/jenkinsfile-runner/), contributes to several Jenkins SIGs and outreach programs (Google Summer of Code, Hacktoberfest) and organizes Jenkins meetups in Switzerland and Russia. Oleg works on open source programs and [Keptn](https://keptn.sh/) at the [Dynatrace](https://dynatrace.com), Open Source Program Office.