GSOC expectations

Revision as of 12:17, 6 May 2016 by David Mudrak (talk | contribs) (Update community bonding expectations)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


The following is expected from our GSOC students:

During the community bonding period

  • Create a specification for your project in Moodle Docs wiki.
  • Use Moodle forums to get a feedback and discuss the project plan with the community.
  • Post in your blog and reflect on your work on the project specification and/or your first impressions of the Moodle community.
  • Use the Moodle tracker for keeping record of all the tasks and issues related to your project. Contact your mentor to make a CONTRIB component created for you.
  • Arrange a weekly meeting time with your mentor.

Each week:

  • Login to moodle.org and read any forum posts of interest to you and join the discussions there.
  • Chat with your mentor(s)

During the coding period

  • Refine your specification based on feedback from your mentor and the wider Moodle community.
  • Refine/add sub-tasks in your tracker issue.
  • Post your code as patches to tracker sub-tasks initially, alternately changes can be posted in your Git public repository with links added to tracker issues.
  • 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.
  • Towards the end of this period, create user documentation.

Each week:

  • Post in your blog summarising 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.

In the final week

  • Post in your blog a summary of everything you have worked on for GSOC.
  • Finalise your tracker issue with the download link to the code for your project.
  • Post in an appropriate Using Moodle forum to inform the community of your project work.
  • Ensure that user documentation for your project is available in Moodle Docs.
  • If possible, share your code by adding a plugin to the Plugins repository, including discussion and documentation links.

See also