#pragma section-numbers 2
= GSoC 2014 =

Mercurial will be participating in GSoC via the Python project. This page is intended to track related activity.

<<TableOfContents>>

== Candidate Checklist ==

All candidates should do the following ''before'' completing their application:

 1. Check the [[SummerOfCode/Ideas2014]] pages
 1. [[http://mercurial.selenic.com/wiki/SummerOfCode/2013?action=subscribe|Subscribe to this page]] to get email when it changes
 1. Introduce yourself on [[IRC]]
 1. Introduce yourself on the [[MailingLists#The_Mercurial-Devel_list|mailing list]]
 1. Read the ContributingChanges pages.
 1. Look at the [[http://bz.selenic.com/buglist.cgi?quicksearch=keyword:easy|easy bugs list]] and contribute a patch

== Things we look for in a candidate ==
 * Demonstrates understanding of our tools, procedures, and source code by successfully submitting patches (see last step above)
 * Participates in the community, especially via IRC
 * Makes a commitment to work on GSoC full-time
 * Gives an indication that she or he enjoys working with Mercurial enough to become a long-term contributor, after GSoC is over.

== Mentors ==
Mentors are there to help students interface with the community. A good mentor will have experience with our patch review process per ContributingChanges, and know who to direct students to consult about particular topics. Mentors will be expected to take some time weekly to help their students, including sitting in on a weekly IRC meeting (to be scheduled once participants are selected). A mentor '''does not''' need to be an expert in their student's project area (in fact, this is [[http://markmail.org/message/u7pj4hhhocs4pds6|discouraged]]).
||Name ||IRC handle ||Timezone offset ||
||Kevin Bullock ||TheMystic ||UTC-05:00 (CDT) ||
||Brodie Rao ||[[BrodieRao|brodie]] ||UTC-07:00 (America/San Francisco) ||
||Giovanni Gherdovich || [[GiovanniGherdovich|ggherdov]] ||UTC+02:00 (CEST) ||