Applying to work with Moodle for GSOC: Difference between revisions

Revision as of 20:16, 10 March 2014

Thanks for your interest in Moodle and for considering applying to work with us :-)

If you have any questions, please post in the GSOC application forum. (You'll need to enrol on the GSoC 2014 course first.)

Create an account on moodle.org and browse the Moodle in English course.
Enrol on the GSoC 2014 course on our Moodle Developer Courses site.
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 in the GSOC application forum.
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.
- Read Tips for when you are trying to fix a bug
- Also see 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.

Applications are made through the GSoC 2014 site.

Feel free to use the following template, though it's not compulsory.

Personal Details

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.

@@ Line 14: / Line 14: @@
 * 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.
-** Read [http://dev.moodle.org/mod/forum/discuss.php?d=1826 Tips for when you are trying to fix bugs]
+** Read [http://dev.moodle.org/mod/forum/discuss.php?d=1826 Tips for when you are trying to fix a bug]
 ** Also see 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.