GSoC_2011_Applicant_Guide
If you want to participate in GSoC 2011 as a student, you should do your best to persuade us that you are the best candidate.
You are supposed to make full time job during summer on this project (this means twelve weeks of about forty hours per week). We are not going to accept you if you are not willing this amount of time.
Also please check the GSoC 2011 timeline so that it won't collide much with your exams.
We accept only people who have already made some contribution to phpMyAdmin and are actively discussing details of the proposal on the phpmyadmin-devel mailing list. So you should get in touch with us as soon as possible, look at existing bug reports or feature requests and try to fix/implement some of them.
The best way to show us you are prepared is to publish your git tree (see Git) with some changes fixing bugs or implementing some improvements. This needs to be done by Wednesday, April 20 so that we can use this as one of options to evaluate proposals.
More details about developing phpMyAdmin are available at https://www.phpmyadmin.net/contribute/. See also Tasks for junior developers.
Official GSoC information is available at https://www.google-melange.com/archive/. The timeline on the Google site mentions important dates, in particular:
- March 18: phpMyAdmin has been accepted as a mentoring organization
- March 28: students started submitting their proposal for phpMyAdmin to the Google Melange site
- April 8: was the deadline for applications
- April 20, 19:00 UTC: (phpMyAdmin deadline) applicants should have submitted at least one patch; this is mandatory for our team to evaluate the proposals
- April 22, 07:00 UTC: the phpMyAdmin mentoring team has to give to Google the final matching between mentors and students
The proposal represents yourself, so take care and write a good one. Use our template (it should be automatically used in Google Summer of Code site), fill in all fields and describe project as much as you can.
Choosing good title and summary also helps a lot, especially it makes your proposal easily recognizable among others.
The schedule and list of deliverables is also crucial, because it will be used for your evaluation during the project. If you fail to properly list those, your mentor might expect you to do more work and you will not pass the evaluation.
Don't be afraid of submitting multiple quality proposals, the most exposed ideas from our ideas list usually receive several proposals and we choose only one. So having backup proposal is a good idea.
If you submit your complete proposal early, you can benefit from comments which mentors will give you and update the proposal. You are recommended to subscribe to notifications on proposal page.
We use Git for managing source code and SourceForge.net trackers for tracking bugs/feature requests/patches. You're expected to use these during summer project, so you should know how to use them.
- GSoC 2011 Student Guide - what you will have to do if you are accepted
- GSoC 2011 Ideas List - what are ideas which you might use
- Summer of Code site
- The DOs and DON’Ts of Google Summer of Code: Student Edition - Some tips for students who want to take part in GSoC
Popular destinations:
- Team meetings
- GSoC home
- Developer guidelines
- How to install on Debian and Ubuntu
- Issue and pull-request management
User resources: