GSOC expectations: Difference between revisions
From MoodleDocs
Helen Foster (talk | contribs) (→During the coding period: in the final week) |
Helen Foster (talk | contribs) (→During the coding period: rewording final week checklist) |
||
| Line 27: | Line 27: | ||
In the final week: | In the final week: | ||
* Post in your blog a summary of | * Post in your blog a summary of everything you have worked on for GSOC 2009. | ||
* Add a comment to your tracker issue with the download link to the code for your project. | * Add a comment to 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 | * Post in an appropriate Using Moodle forum to inform the community of your project work. | ||
* Ensure that | * Ensure that user documentation for your project is available in Moodle Docs. | ||
* Share your project code by adding an entry in the [http://moodle.org/mod/data/view.php?id=6009 Modules and plugins database], including download, discussion and documentation links. | * Share your project code by adding an entry in the [http://moodle.org/mod/data/view.php?id=6009 Modules and plugins database], including download, discussion and documentation links. | ||
Revision as of 13:22, 13 August 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 on Tuesday 5 May.
- 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. 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.
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.
In the final week:
- Post in your blog a summary of everything you have worked on for GSOC 2009.
- Add a comment to 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.
- Share your project code by adding an entry in the Modules and plugins database, including download, discussion and documentation links.
