Applying to work with Moodle for GSOC: Difference between revisions
Dan Marsden (talk | contribs) No edit summary |
Dan Marsden (talk | contribs) (add link to Tims post with advice.) |
||
| Line 16: | Line 16: | ||
* [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 [https://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. (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. | * Browse our list of [https://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. (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. | ||
** Read [http://dev.moodle.org/mod/forum/discuss.php?d=1802#p3456 Some advice for applicants] from Tim Hunt, attempting to fix a bug is '''required''' before we will consider your application - no exceptions. | |||
** Ideally follow the steps on https://docs.moodle.org/dev/Git_for_developers. | ** Ideally follow the steps on https://docs.moodle.org/dev/Git_for_developers. | ||
** Alternatively, see [[How to create a patch]]. Attach your patch to the tracker issue and link to the tracker issue in your application. | ** Alternatively, see [[How to create a patch]]. Attach your patch to the tracker issue and link to the tracker issue in your application. | ||
Revision as of 21:20, 24 February 2014
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 GSoC jabber chat:
- In any Jabber client e.g. Pidgin log in using a jabber account e.g. Google Talk.
- Join the group chat gsoc2014@conference.moodle.org. (In Pidgin, set the room as gsoc2014 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.
- While you're there, check out our Introduction to Moodle Programming course. It will help you prepare before starting your project.
- Download Moodle and install it on your local machine. Initially, you may like to try one of our all-in-one packages Moodle4Mac or Moodle for Windows. Later you will create a clone of the Moodle using Git.
- 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. (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.
- Read Some advice for applicants from Tim Hunt, attempting to fix a bug is required before we will consider your application - no exceptions.
- Ideally follow the steps on https://docs.moodle.org/dev/Git_for_developers.
- Alternatively, see How to create a patch. Attach your patch to the tracker issue and link to the tracker issue in your application.
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 that 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 during the project period. Please do not apply if you have other 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
