Google Summer of Code Student Instructions

Thanks for your interest in applying for Google Summer of Code with Dask. We welcome and encourage applications from people in under-represented groups in tech.

All applicants should do the following steps:

Application Steps

1. Review our ideas page to see if you find a project that is interesting to you. Ideas not on this list may also be accepted, but should be discussed with the development team beforehand.

2. Go through our Development Guidelines page to see how to get started developing Dask.

3. We require all applicants have submitted a Pull Request (PR) to Dask before the application due date. So we can prioritize reviewing your PR, please indicate that you are interested in GSoC in the body of your PR and leave a comment linking to it from the GSoC issue thread.

   Fixing any existing issue, or making a contribution to dask-tutorial or dask-examples is sufficient. You can share your plan and ask for advice in the issue thread, and other Dask developers will try to guide you. For a list of good places to start see:

   • dask good first issues
   • dask-distributed good first issues
   • dask-ml good first issues
   • dask-examples good first issues
   • Any contribution of content to dask-tutorial
   • Any contribution of content to dask-examples

4. Develop your application, following the application template below. We suggest developing your application in the open, so others may review your application before you submit it to Google. A good way to do this would be:

• Create a new repository on Github (titled something like "GSoC Application")
• Write your application in a text-based format like markdown (.md file) or reStructuredText (.rst file). Using a text-based format allows using GitHub's reviewing features when reviewing your application.
• Submit your application as a new Pull Request to that repository. This allows adding inline comments when reviewing your application.
• Comment on the GSoC issue thread with a link to your application when you're ready for review, pinging the mentor for the project you're interested (e.g. @their_username)

5. Submit your application to the Google Summer of Code Website. Dask is participating under the "NumFocus" umbrella organization - this is the organization you will select when submitting. The application due date is April 9th, 2019. We suggest submitting your application at least a few days before then, as the website sometimes crashes on the due date due to excess load. See the Google Summer of Code Website for more information.

Application Template

You should include the following information in your application. You should not format your application as a question/answer format for the below questions, but we expect to see all of the above questions answered in your application somewhere.

Title

Please use a succinct title that describes your proposal.

You the person

• Your full name

• University / current enrollment

• Short bio / overview of your background

• How can we contact you?

  • Email
  • GitHub username
  • Any other username you want us to know about

You the programmer

In your project proposal let us know about your programming experience.

• What is your experience programming? Tell us about something you have created.

• What is your experience with Python?

• Have you ever used git or another version control system? Do you have experience using GitHub?

• What is your experience with Open Source? Have you ever contributed to another open source project?

Project Description

Answer the following questions in your application:

• What do you want to achieve?

• What excites you about this project? Why did you choose it?

• What qualifications do you have to implement your idea? Why are you suited to work on this project?

• How much time do you plan to invest in the project before, during, and after the Summer of Code? (we will expect full time 40h/week during GSoC). If you plan to take any vacations over the summer, let us know about it here.

• How will you break your project into smaller tasks? Please provide a schedule of how time will be spent on sub-tasks of the project over the GSoC development period. While we will not hold you to this schedule, this lets us know that you have thought about how to break the project into smaller tasks and will help us monitor your progress throughout the summer.

  Please also note in the schedule where could formulate a pull request. These would be points where you can have a self contained, documented, and tested piece of functionality. Doing this at several points during the summer helps to keep code reviews manageable. A big pull request at the end of the summer will likely be hard to review and merge before the project deadline.

Pull Request Requirement

Please provide a brief summary of your contributions to Dask so far, including unmerged work. You must include at least one link showing that you satisfied this requirement.