|
Size: 1280
Comment: applicants' page
|
Size: 1962
Comment: added mentors
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| Mercurial is in the process of proposing itself as a Mentoring Organization for Google Summer of Code 2014. On Monday, February 24th we will know whether Mercurial's proposal is accepted or not. This page is intended to track related activity. | Mercurial will be participating in GSoC via the Python project. This page is intended to track related activity. |
| Line 8: | Line 9: |
| 1. Check the [[SummerOfCode/Ideas2013]] pages 1. Do your first wiki edit by adding yourself to the candidate list below |
All candidates should do the following ''before'' completing their application: 1. Check the [[SummerOfCode/Ideas2014]] pages |
| Line 21: | Line 24: |
== 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 ||brodie ||UTC-07:00 (America/San Francisco) || ||Giovanni Gherdovich || [[GiovanniGherdovich|ggherdov]] ||UTC+02:00 (CEST) || |
GSoC 2014
Mercurial will be participating in GSoC via the Python project. This page is intended to track related activity.
1. Candidate Checklist
All candidates should do the following before completing their application:
Check the SummerOfCode/Ideas2014 pages
Subscribe to this page to get email when it changes
Introduce yourself on IRC
Introduce yourself on the mailing list
Read the ContributingChanges pages.
Look at the easy bugs list and contribute a patch
2. 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.
3. 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 discouraged).