Student selection process

Introduction

This page aims to summarise the student selection process we developed at the 8.5.13 meeting.

This will be subject to discussion for a limited period, after which we will make an official statement.

Our goal is to come to an agreement by Sunday 12th May 12pm.

In order to avoid an overwhelming amount of applications that we would not be able to process, we want to split the process into several steps in order to filter them. There will also be a number of rules that the application should follow.

Once we're done discussing this, we will explain the process on a page on our website.

Requirements

(We should list requirements/prerequisites at the very top.)

The Process

1. Find a pair and a coach

Before you can apply to the Rails Girls Summer of Code you need to find

• a coach that is able to support you throughout the project as well as,
• ideally, another student who you'd pair-program with.

It is not a requirement to find a pair, but you will have a higher chance to be accepted.

Coaches should have sufficient time throughout the project in order to support you well. If they're not able to do this alone it is fine if coaches team up. Talk to them and figure out how to make sure that througout the project:

• You have a good place to work (ideally a desk next to your coach).
• They can support you well and have enough time.

The best starting point for finding a pair and coach is to contact your local Rails Girls and Ruby communities. Ask on the Rails Girls Summer of Code community mailing list. Ask on Twitter.

You are responsible for finding your pair and coach, but we will do our best to help.

2. Submit your application with your pair and coach

Please meet with your pair and coach(es). You should feel comfortable working with them closely for 3 months.

Together with you coaches are supposed to

• interview you about the level of your expertise and
• make recommendations and preferences about projects

Once all of you have made sure that you meet the requirements you can submit your application.

3. Selection VERSION A (ranking)

(There will be a deadline for applications which we need to decide on.)

We will make ensure that all the applications meet all the requirements.

The goal of Rails Girls Summer of Code is to get you in touch with the Open Source community and allow you to take your first steps in contributing to it. This will be a learning process for you. But we also want to make sure that you have a good chance at succeeding with this.

Therefor we will favor applications based on these critierias:

• you have a pair
• your experience level
• you can do 3 months rather than less
• you are a women

We sort the applications according to how many of the criteria they meet (level of experience, if pair or not etc.) Applications that meet most criteria will be ranked first.

If there are then more applications than places, we will draw.

3. Selection VERSION B (raffle)

(There will be a deadline for applications which we need to decide on.)

We will make ensure that all the applications meet all the requirements.

We will then do a random draw from all applications, but pairs will have a double chance to make it compared to single students.

If we have remaining budget after this we will try to find more students. If we have remaining applications we will try to find more sponsors.

The Rules

If you apply, please make sure to follow these rules:

1. You need a coach (we can help there) or a team of coaches.
2. You need to be able to work full-time for at least two months, even better three.
3. Your coach needs to be available for support for a sufficient amount of time.
4. You should have a workplace where you can work comfortably and find your coach's support easily. Ideally sitting next to them.
5. You should have attended at least one Rails Girls workshop (or an equivalent like RailsBridge).
6. You need a certain amount of programming experience in Ruby, so you should at least have worked independently or in a study group on a Ruby project. Please provide concrete examples of what you've done.
7. You should not already be a professional Ruby developer.