Applying to work with Moodle for GSOC: Difference between revisions
(Adding note about calendar) |
|||
| Line 13: | Line 13: | ||
* Take a look at our [[Projects for new developers]]. Discuss your ideas on the [http://dev.moodle.org/mod/forum/view.php?id=92 GSOC application forum]. If you have general questions, please ask them on the Jabber chat room mentioned above. | * Take a look at our [[Projects for new developers]]. Discuss your ideas on the [http://dev.moodle.org/mod/forum/view.php?id=92 GSOC application forum]. If you have general questions, please ask them on the Jabber chat room mentioned above. | ||
* [http://tracker.moodle.org/secure/Signup!default.jspa Sign up for a Moodle tracker account]. Please use the same username as for your moodle.org account. | * [http://tracker.moodle.org/secure/Signup!default.jspa Sign up for a Moodle tracker account]. Please use the same username as for your moodle.org account. | ||
* Browse our list of [http://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+MDL+AND+type+in+%28bug%29+AND+status+%3D+open+AND+Difficulty+%3D+Easy+AND+labels+not+in+%28patch%29+ORDER+BY+created+DESC&runQuery=true&clear=true relatively easy Moodle bugs] and suggest a fix for at least one of them. See [[How to create a patch]]. Attach your patch to the tracker issue and link to the tracker issue in your application. (Note that we don't always bother to classify bugs as easy/medium/hard, so you may also want to look at unclassified bugs.) | * Browse our list of [http://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+MDL+AND+type+in+%28bug%29+AND+status+%3D+open+AND+Difficulty+%3D+Easy+AND+labels+not+in+%28patch%29+ORDER+BY+created+DESC&runQuery=true&clear=true relatively easy Moodle bugs] and suggest a fix for at least one of them. See [[How to create a patch]]. Attach your patch to the tracker issue and link to the tracker issue in your application. (Note that we don't always bother to classify bugs as easy/medium/hard, so you may also want to look at unclassified bugs.) It is not essential that your fix is integrated into Moodle. | ||
==Your application== | ==Your application== | ||
Revision as of 00:38, 10 April 2012
Thanks for your interest in Moodle and for considering applying to work with us :-)
If you'd like to chat about your application, please join our gsoc2012 jabber chat:
- In any Jabber client e.g. Pidgin log in using a jabber account e.g. Google Talk.
- Join the group chat gsoc2012@conference.moodle.org. (In Pidgin, set the room as gsoc2012 and the server as conference.moodle.org.) Please use your real name in the chat.
Before submitting your application
- Create an account on moodle.org and browse the Using Moodle course.
- Enrol on the GSOC course on our Moodle Developer Courses site.
- Whilst you're there, check out our Introduction to Moodle Programming course.
- Download Moodle and install it on your local machine. You may like to try one of our all-in-one packages Moodle4Mac or Moodle for Windows.
- Take a look at our Projects for new developers. Discuss your ideas on the GSOC application forum. If you have general questions, please ask them on the Jabber chat room mentioned above.
- Sign up for a Moodle tracker account. Please use the same username as for your moodle.org account.
- Browse our list of relatively easy Moodle bugs and suggest a fix for at least one of them. See How to create a patch. Attach your patch to the tracker issue and link to the tracker issue in your application. (Note that we don't always bother to classify bugs as easy/medium/hard, so you may also want to look at unclassified bugs.) It is not essential that your fix is integrated into Moodle.
Your application
Applications are made through the GSOC site.
Feel free to use the following template, though it's not compulsory.
Personal Details
- Name
- Other contact methods
- Timezone
Project Proposal
What do you plan to do?
Also describe any work or research on this project you have already done.
Schedule of Deliverables
There is a calendar published on the GSoC site that defines periods applicable to GSoC projects. Your schedule should follow this format.
What are the milestones and deliverables for your project? You will be assessed against these. Tell us why you think this schedule is realistic.
Do you have any other commitments during this time? Provide dates, such as holidays, when you will not be available.
Note: We expect your project to be your primary focus this summer. Please do not apply if you have other summer employment.
Open Source Development Experience
Do you have any experience of Open Source software development?
Moodle Tracker issue number(s) of bug(s) you have fixed with patches attached.
Note: We require you to suggest a fix for at least one Moodle bug before considering your project proposal.
Work/Internship Experience
Anything relevant to the project, or related to web design or software development.
Academic Experience
What you're studying at university/college.
Why Moodle
Tell us why you chose to apply to us.
See also
- GSOC - describing Moodle's involvement with Google in their Summer of Code program
- Advice for Students google-summer-of-code
- Google Summer of Code 2012 Frequently Asked Questions
- GSOC Greetings from Tim forum post which describes what mentors look for in applications
