|
Size: 1885
Comment:
|
Size: 1885
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 26: | Line 26: |
| ||Ankur Ankan ||Advanced Revset Optimization ||aplavin|| ||Plavin Alexander ||Advanced Hgweb support || || |
||Ankur Ankan ||Advanced Revset Optimization |||| ||Plavin Alexander ||Advanced Hgweb support ||aplavin || |
GSoC 2013
Mercurial has been selected as a Mentoring Organization for Google Summer of Code 2013. This page is intended to track related activity.
1. Candidate Checklist
Check the SummerOfCode/Ideas2013 pages
- Add yourself to the candidate list below
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
3. Known Candidates
Multiple candidates can apply for the same project.
Candidates name |
interested in |
IRC handle |
Ankur Ankan |
Advanced Revset Optimization |
|
Plavin Alexander |
Advanced Hgweb support |
aplavin |
4. Possible 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).
- Kevin Bullock
- Giovanni Gherdovich