Aquesta pàgina forma part de la documentació de Moodle en català, tot i que no ha estat traduïda encara. Podeu contribuir obertament a les tasques de traducció. Podeu consultar la Guia d'edició de la documentació i també participar ens els debats del fòrum de traductors de la documentació a moodle.org

GSOC expectations: diferència entre les revisions

De MoodleDocs
Salta a:navegació, cerca
(→‎During the coding period: in the final week)
(Shifted to dev docs)
 
(5 revisions intermèdies per 2 usuaris que no es mostren)
Línia 1: Línia 1:
The following is expected from our GSOC students:
{{Moved_to_dev_docs}}
 
==During the community bonding period==
 
* Ensure you've introduced yourself in our GSOC 2009 [http://dev.moodle.org/mod/forum/view.php?id=87 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 your completed 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 completed project.
* Ensure that the user documentation for your project is complete.
* 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.
 
==See also==
 
* [[GSOC]]
* [[Development:Guidelines for contributed code]]
[[Category:GSOC]]

Revisió de 02:17, 15 set 2011

This development related page is now located in the Dev docs.

See the GSOC expectations page in the Dev docs.