Since 2005, Google has run an awesome open source software development program, called the Google Summer of Code (GSoC), which specifically targets students. Under this program, Google funds students to write code for open source projects during the northern hemisphere's summer timeframe. StarKit, a scientific code to model the physical properties of stars, participates in this program to get young minds engaged in scientific software development. The process is as follows:

• The student writes a project proposal for StarKit.
  • Sometimes their project idea caters to something that the StarKit collaboration suggests and sometimes it's an idea entirely of the student's conception.
• Proposals are reviewed, evaluated, and ranked by the StarKit collaboration.
• Google allocates a certain number of slots to each participating organization
  • That, in turn, determines how many student developers work with the StarKit collaboration.

This page will help you to familiarize yourself with GSoC, the StarKit collaboration and provides a guideline for applications.

Some members of the StarKit GSoC team also work with TARDIS GSoC. As a general example, we put proposals here that were selected for TARDIS GSoC 2016 and can serve as a reference for future proposals for StarKit:

• mishinma_gsoc_application.pdf
• ftsamis_gsoc_2016.pdf
• karandesai_gsoc_2016.pdf

If you are interested, follow the steps:

1. go through checklist
2. check out what we expect from you (expectations, acceptance requirements and application guidelines)
3. get familiar with StarKit and pick a project from our Ideas Page
4. apply

We have compiled some background information about StarKit and the science we do with it as well as some of our suggested projects for GSoC 2017 on the Ideas Page.

You are also welcome to come up with your own project ideas and discuss them with the StarKit mentors. We're here to help you become new open source developers, so don't be shy if you have any questions. The best way to get in contact is to chat with us on Gitter.

GSoC is about getting people involved and contributing to open source over the long-term. As such, we heavily weight our application selection process towards students that are interested in remaining involved in TARDIS and open source software development long after GSoC has ended.

GSoC is not a job! If you think this is just a summer job, then GSoC is probably not for you. It's only like a job in terms of planning your time commitment over the summer.

Additionally, submissions are graded based on the perception of the submitter's abilities to complete the task within the program timeframe, the general consensus on the technical approach being proposed, and overall interest in having such modifications made to StarKit. Particular notice is made of students that are responsive to questions and readily interactive in the gitter channel. Communication is a great thing!

Just about every GSoC organization receives considerably more project proposals than can be accepted. Every application gets read multiple times and reviewed in detail. Of those applications, only a small subset is selected, so keep in mind that the selection process is rather competitive and difficult.

Whether or not you are accepted, contributing to open source outside of GSoC is one of the main goals of the program and is the best way to be noticed and get your proposal accepted. Keep that in mind. Thanks for your interest and we look forward to working with new StarKit developers!

adapted from the BRL-CAD page