Skip to content

Contributor Guidance for Google Summer of Code

Jump to bottom
Douglas DeMaio edited this page Jan 24, 2023 · 4 revisions

How to apply

Application checklist:

  • Read the links and instructions given on 101.opensuse.org for mentees. All projects are listed on the mentee page.

  • Choose one of the projects listed and click on the more details to get information about the specific project.

  • The more details link will bring you to a github page (listed project as an issue) that lists details of that specific Google Summer of Code project under openSUSE's mentoring organization.

  • Use the github comments and/or contact information to talk with a prospective mentor about what goals a GSoC applicant aims to achieve. Contributors can receive help from the creator of the issue (listed project) to refine the project ideas. Listening to your mentors' recommendations is very important at this stage! Understanding what mentors expect from you as a contributor and decide together on how often there should be communication between the mentor and contributor.

  • Admins of the project encourage GSoC contributors to fix a bug or make a pull request (or equivalent) prior to an application, we do appreciate an contribution you can provide. Your code doesn't have to be accepted or merged, but it will be visible to the public and let others in the community know you are willing to contribute to projects. Your pull request (PR) does have to be your own work. A mentors help is ok, but code you did not write is not.

Write your application (with help from your mentors!)

  • The 2022 application template is available here. All applications must go through Google's application system; we can't accept any application unless it is submitted there.

  • Use the descriptive title and include your project name in Google's system. Good example: "Automatic system tuning for openSUSE" Bad example: "My gsoc project"

  • Make it easy for your mentors to give you feedback. If you're using Google docs, enable comments and submit a "draft" (we can't see the "final" versions until applications close). If you're using a format that doesn't accept comments, make sure your email is on the document and don't forget to check for feedback!

  • Submit your application to Google before the deadline. We actually recommend you submit a few days early in case you have internet problems or the system is down. Google does not extend the deadline, so it's best to be prepared early! You can edit your application up until the system closes.

Tip

Communication is probably the most important part of the application process. Talk to our mentors and other developers, listen when they give you advice, and demonstrate that you've understood by incorporating their feedback into what you're proposing. A lot of applicants who have not listened to mentor feedback are rejected by the project, so please be mindful of this fact. If your mentors tell you that a project idea won't work for them, you're probably not going to get accepted unless you change it.

What goes in an application?

An ideal application will contain 6 things:

  • A descriptive title including the name of the project you want to work with (if this is missing, your application may be rejected!)
  • Information about you, including contact information.
  • Link to a code contribution you have made to your organization. (Usually this is a link to a pull request.)
  • Information about your proposed project. This should be fairly detailed and include a timeline.
  • Information about other commitments that might affect your ability to work during the GSoC period. (exams, classes, holidays, other jobs, weddings, etc.) We can work around a lot of things, but it helps to know in advance.
  • In the application, list a link to your contribution.

Getting in Touch

The openSUSE Community has a Code of Conduct. Mentors and contributors are asked to abide by it as members of the openSUSE community.

Clone this wiki locally