Blog: Google Summer of Code 2022 ☀️

Google Summer of Code 2022 ☀️ How many contributors are we looking for? What are we looking for in an ideal Jenkins X contributor? What can prospective contributors do? (March 7 - April 19) Interview process and selection criteria (April 19 and May 12) We are very happy to announce that Jenkins X has been selected to participate in the Google Summer of Code (GSoC) 2022! If you are new to GSoC and want to learn more about it, check out their new site. You can find the list of project ideas from Jenkins X here. If you are interested in applying to Jenkins X, please check the timeline. Apply as early as possible. This post aims to give GSoC contributors insight into the selection process and how to get started. We have 3 mentors signed up at the moment and are looking to select a maximum of 2 applicants. We want you to have a great experience contributing to Jenkins X and learn lots of new things! Willingness to learn Jenkins X and engage with the community Independence and a drive to investigate and propose solutions to complex issues that might occur during implementation (Optional) Eventually become a Jenkins X maintainer (and some day mentor new GSoC contributors)! You do not have to complete all of these tasks. This is presented here so that you have some clarity around where to start and which resources to follow. Recommended: Join the jenkins X community slack channels and say hello :) We prefer you post messages in the jenkins-x-dev channel Attend the office hours We prefer you post messages in the jenkins-x-dev channel Attend the office hours Recommended: Interact with potential mentors to understand/review the requirements of the projects. Recommended: Start working on your proposal early on. Optional: Learn about docker Optional: Learn about kubernetes Optional: Learn the basics of golang Optional: Understand Jenkins X concepts and fundamentals by going over the documentation Optional: Set up Jenkins X locally and give it a go (Please don’t spend money running Jenkins X in the cloud). We prefer you use k3s for this, as it’s less resource intensive and can be installed locally on your workstation (linux).