Difference between revisions of "GSOC expectations"

Jump to: navigation, search
m (During the community bonding period)
(Correct link to GSOC Chat)
Line 15: Line 15:
 
* Login to moodle.org and read any forum posts of interest to you.
 
* Login to moodle.org and read any forum posts of interest to you.
 
* Chat with your mentor(s) (if not contactable, contact Michael d).
 
* Chat with your mentor(s) (if not contactable, contact Michael d).
* Participate in the GSOC group chat ''gsoc2012@conference.moodle.org''.
+
* Participate in the GSOC group chat ''gsoc2013@conference.moodle.org''.
  
 
==During the coding period==
 
==During the coding period==

Revision as of 23:22, 21 April 2013

The following is expected from our GSOC students:

During the community bonding period

  • Ensure you've introduced yourself in our GSOC Introductions forum.
  • Create a specification for your project in Moodle Docs and post in an appropriate Using Moodle forum asking for feedback.
  • Post in your blog about your project specification and/or your first impressions of the Moodle community. Tag your entries 'moodle' and 'gsoc'.
  • Attend an online orientation meeting (date to be confirmed).
  • Subscribe to the GSoC iCal Calendar.
  • Create an issue for your project in the Tracker (Project="Non-core contributed modules", Type=task).
    • Start to create sub-tasks that reflect your project schedule.
  • Arrange a weekly meeting time with your mentor(s).

Each week:

  • Login to moodle.org and read any forum posts of interest to you.
  • Chat with your mentor(s) (if not contactable, contact Michael d).
  • Participate in the GSOC group chat gsoc2013@conference.moodle.org.

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 to Git 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 following the guidelines for contributed code.

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.
  • Participate in the GSOC group chat.

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