Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: GSOC expectations.

GSOC expectations: Difference between revisions

From MoodleDocs
Line 6: Line 6:
* Attend an online orientation meeting (details to be confirmed).
* Attend an online orientation meeting (details to be confirmed).
* Create a specification for your project in Moodle Docs and post in an appropriate forum asking for feedback.
* Create a specification for your project in Moodle Docs and post in an appropriate forum asking for feedback.
* Post in your blog about your project specification and/or your first impressions of the Moodle community. You're welcome to use the blog facility on moodle.org or an external blog. Please tag all entries 'Moodle' and 'GSOC'.
* Post in your blog about your project specification and/or your first impressions of the Moodle community. Please tag your entries 'moodle' and 'gsoc'.


Each week:
Each week:

Revision as of 19:25, 22 April 2009

The following is expected from our GSOC students:

During the community bonding period

  • Ensure you've introduced yourself in our GSOC 2009 Introductions forum.
  • Attend an online orientation meeting (details to be confirmed).
  • Create a specification for your project in Moodle Docs and post in an appropriate forum asking for feedback.
  • Post in your blog about your project specification and/or your first impressions of the Moodle community. Please tag your entries 'moodle' and 'gsoc'.

Each week:

  • Login to moodle.org and read any forum posts of interest to you.
  • Chat with your mentor(s) and/or with Helen.
  • Participate in the GSOC group chat gsoc2009@conference.moodle.org.

During the coding period

  • Refine your specification based on feedback from your mentor and the wider Moodle community.
  • Add subtasks to your tracker issue in roughly chronological order for all your project milestones.
  • Post your code as patches to tracker subtasks initially, then once CVS permission is granted, develop code in Moodle's CVS repository.
  • Post regularly in the forums to build a dialogue with the community. Advertise major milestones to maintain community interest and draw in new testers and more feedback.
  • Provide documentation in Moodle Docs.
  • Share your code by adding an entry in the Modules and plugins database.

Each week:

  • Post in your blog summarizing what you've been working on, any problems you've run into, and what you're planning to do next.
  • Have a meeting with your mentor.
  • Participate in the GSOC group chat.

See also