students.html

---
layout: default
title: Students
class: page page-students
current: students
current-sub: students
permalink: students/
---
<script src="http://openlayers.org/api/OpenLayers.js"></script>
<script defer="defer" src="/js/map.js"></script>
<script src="/js/cities.js"></script>


<section class="main container">
    <div class="wrapper clearfix">
        {% include students_sidebar.html %}

        <article class="content">
            <h2>{{page.title}}</h2>

            <p>Student registrations for Rails Girls Summer of Code closed the <strong>7th of June.</strong>
            We received applications from all over the world!</p>

            <div style="width:650px; height:400px" id="map"></div>

            <p><strong>Congratulations for being accepted into Rails Girls Summer of Code go out to the following teams!</strong></p>

            <ol>
              <li>Carla (Australia) and Anja (Germany) to work on: Sinatra and Farm Subsidy Open Government Data</li>
              <li>Cecilia (Argentinia) and Mayn (Norway) to work on: Open Source Job Board</li>
              <li>Jaqcueline Homan (USA) and Angela Ebirim (UK) to work on Hackety Hack</li>
              <li>Jen and Joyce (both USA) to work on: Bundler</li>
              <li>Laura and Adriana (both Colombia) to work on: Rails (Conductor)</li>
              <li>Magdalena (Poland) to work on: impress.js</li>
              <li>Maja and Nina (both Slovenia) to work on: Spree</li>
              <li>Nicole (Germany) and Laura (USA) to work on: RailsApps and Rubinius</li>
              <li>Sakshi and Pallavi (both India) to work on: Diaspora</li>
              <li>Wiktoria and Alicja (both Poland) to work on: Species+</li>
            </ol>

            <p>(ordered alphabetically, not by ranking)</p>

            <p id="more-options">If you have applied and your team is not on this list - don’t worry. That does
            not mean your summer can’t be a Summer of Code! Here is what you can do:</p>
        </article>

        <article class="content">
            <p><strong>1) Join the program as a volunteering student / team</strong></p>

            <p>If you want to work on your project without monetary support, then please tell
            us. We will automatically accept you into the program and you’ll get all the
            benefits like access to remote support chat rooms, supervision, visibility to
            the community etc.</p>

            <p><strong>2) Cross your fingers</strong></p>

            <p>We are trying to raise more money for the campaign and hope that we will be able
            to offer some extra last-minute slots. If we have sufficient budget, we will do
            another selection round next week.</p>

            <p>Please tell us if there’s a deadline on which you’d need to be notified at the
            latest so you can still start working on your project on July 1st (some of you
            might need extra time to prepare).</p>

            <p>Also, if you were planning to work on a project that was also chosen by a team
            from the ones listed above, please update your application.</p>

            <p><strong>3) Get involved with your local communities</strong></p>

            <p>If you don’t want to stick to a strict coding program, but want to continue
            getting more into code, we can help you form project groups for coding, find
            user groups, organize Hackdays, Summer Camps etc. If you get in touch we will
            try connect you and help with this.</p>

            <hr>

            <p>Details about who and how to apply are still printed below for those who may be interested in applying in the future.</p>

            <p>We invite all to apply for the program who:</p>
            <ul>
                <li>attended at least one Rails Girls or similar Ruby introduction workshop.</li>
                <li>expanded their Ruby skills after the workshop in a study group or independently by working on a Ruby project.</li>
                <li>can spend at least two and ideally three months this summer working on the project.</li>
                <li>have found another student to pair up with and a coach (we can help with that).</li>
            </ul>
            <p>An ideal group to apply would consist of two students (who will both be paid) and one or more coaches (who won't be paid).</p>

            <h3>How will this work?</h3>
            <h4>1. Find a pair and a coach</h4>
            <p>Before you can apply to the Rails Girls Summer of Code you need to find</p>
            <ul>
                <li>a coach that is able to support you throughout the project as well as,</li>
                <li>ideally, another student who you'd pair-program with.</li>
            </ul>
            <p>It is not a requirement to find a pair, but you will have a higher chance of being accepted.</p>
            <p>Coaches should have sufficient time throughout the project in order to support you well. What exactly that means will depend largely on your skills, the project, and other factors, so you'll need to discuss this with your pair and coach. It probably should be at least a few hours a day, more in the beginning of the project, probably less near the end. The more time they have the better. If they're not able to do this alone it is fine if coaches team up.</p>
            <p>Talk to them and figure out how to make sure that throughout the project:</p>
            <ul>
                <li>You have a good place to work (ideally a desk next to your coach).</li>
                <li>They can support you well and have enough time (please try to be more specific and know the hours / days when they can help). </li>
            </ul>
            <p>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.</p>
            <p>You are responsible for finding your pair and coach, but we will do our best to help!</p>
        </article>
        <aside class="sidebar">
            <div class="scribble13"></div>
        </aside>
        <article class="content">
            <h4>2. Submit your application with your pair and coach</h4>
            <p>Please meet with coach and pair. You should feel comfortable working with them closely for 3 months.</p>
            <p>Together with you and your pair, coaches are supposed to:</p>
            <ul>
                <li>interview you both about the level of your expertise.</li>
                <li>make recommendations and preferences about projects.</li>
            </ul>
            <p>Once all of you have made sure that you meet the requirements you can submit your application.</p>
            <h4>3. Selection (ranking)</h4>
            <p>The deadline for the application is set on the 7th of June. </p>
            <p>We will make sure that all the applications meet all the requirements.</p>
            <p>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.</p>
            <p>Therefore we will favor applications based on these criteria:</p>
            <ul>
                <li>you are a woman. (This initiative is focused on bringing more women into the world of open source. Men are not excluded, however women are given priority.) </li>
                <li>you have a sufficient experience level.</li>
                <li>you can do 3 months rather than less.</li>
                <li>your coach has enough time available to guide you.</li>
                <li>you have a pair.</li>
                <li>your project's project visibility.</li>
            </ul>
            <p><strong>About the last two criteria:</strong> Maintainers/mentors as well as sponsors who provide coaches will get to name their favorite coach/student teams and might be involved in the selection process. However they do not have the main say, them favoring teams will be one criteria among others, and this will fairly be discussed with the coaches and organizers.</p>
            <p>The committee will rank your application based on these criteria. Applications that meet them the most will make it into the final stages.</p>
            <p>If we end up with more suitable students than places, we will have to do a random draw.</p>
            <h3>The Rules</h3>
            <p>If you apply, please make sure to follow these rules:</p>
            <ol>
                <li>You need a coach (we can help there) or a team of coaches.</li>
                <li>You need to be able to work full-time for at least two months, even better three.</li>
                <li>Your coach needs to be available for support for a sufficient amount of time (at least a few hours per day).</li>
                <li>You should have a workplace where you can work comfortably and find your coach's support easily. Ideally sitting next to them.</li>
                <li>You should have attended at least one Rails Girls workshop (or an equivalent like RailsBridge).</li>
                <li>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 e.g. code examples, Github Account.</li>
                <li>You should not already be a professional Ruby developer.</li>
            </ol>
        </article>
        <aside class="sidebar">
            <div class="scribble14"></div>
        </aside>
        <!-- <div class="fullwidth">
            <a href="https://docs.google.com/forms/d/158MlfRepVVZh9NjskR7-fuNJz5EsgzRnhrmTD94HXwY/viewform" class="button" title="to the student registration" target="_blank">Apply now!</a>
        </div> -->
    </div>
</section> <!-- / .main -->