Jenkins in Google Summer of Code 2022
|
This site is the new docs site currently being tested. For the actual docs in use please go to https://www.jenkins.io/doc. |
Google Summer of Code (GSoC) is a global, online program focused on bringing new contributors into open source software development. GSoC Contributors work with an open source organization on a 12+ week programming project under the guidance of mentors.
GSoC contributors accepted into the program receive a stipend, paid by Google, to work well-defined projects to improve or enhance the Jenkins project. In exchange, numerous Jenkins community members volunteer as "mentors" for GSoC contributors to help integrate them into the open source community and succeed in completing their projects.
GSoC 2022
We are participating in Google Summer of Code 2022. (Jenkins GSoC Organisation Application Form)
The selected projects are
-
Plugin Health Scoring System by Dheeraj Singh Jodha
-
Jenkinsfile Runner Action for GitHub Actions by Yiming Gong
-
Automatic git cache maintenance on the controller by Hrushikesh Rao
-
Pipeline Step Documentation Generator Improvements by Vihaan Thora
They were proposed and selected from these project ideas.
| There are some changes in how GSoC 2021/2022 is organized, including duration of the projects. Jenkins GSoC documentation may be outdated in some places, please refer to the official GSoC website as a source of truth. Our documentation will be updated over time to reflect the changes in the GSoC program, please report any issues you discover. |
GSoC Contributors
-
Information and application guidelines for GSoC contributors
-
Online Meetup: Introduction to Jenkins in GSoC (slides, video)
Org Admins
Org Admins are the people managing the GSoC program for the Jenkins Organization. For 2022, Org Admins are:
-
Alyssa Tong
-
Jean-Marc Meessen
-
Kris Stern
The following checklists and documents describe the role.
Contacts
-
We use the GSoC SIG for communications about GSoC. Projects may also have their own mailing lists, chats and meetings. See details on project pages.
-
We use Discourse for discussions. This is the recommended channel for communications
-
There is also a GSoC Gitter channel for real-time communications, but it is better to use Discourse to request technical feedback or to have long discussions
-
For private matters such as communication difficulties with mentors, GSoC contributors, or Org Admins, please use the this group email.
GSoC Discourse
Public communication channel: GSoC Discourse.
The purpose of GSoC Discourse is for all public communications on GSoC such as new mentor and new GSoC contributor introductions, project proposal questions and discussions, process and timeline related questions.
Chats
-
GSoC Gitter channel for organizational topics related to Jenkins in GSoC
-
Project-specific chats, see project and project idea pages
-
Common developer chats for technical topics
Office hours
Although we use Discourse as the main communication channel, we also have regular "office hours" video calls. During these time slots Jenkins GSoC org admins and mentors are available for any GSoC-related questions.
This meeting will be used for Q&A with GSoC applicants/contributors and mentors before the announcement of accepted projects as well as during the GSoC program. You can add the office hours to your calendar when you visit the Jenkins event calendar. More slots may be added on-demand, e.g. for project-specific discussions.
In addition to these organization-wide meetings, each GSoC project has regular meetings during community bonding and coding phases. See the project pages for the schedule.