Diferència entre revisions de la pàgina «GSOC expectations»

Dreceres ràpides: navegació, cerca

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

(During the coding period: rewording final week checklist)
(info update)
Línia 3: Línia 3:
 
==During the community bonding period==
 
==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].
+
* Ensure you've introduced yourself in our GSOC 2011 [http://dev.moodle.org/mod/forum/view.php?id=87 Introductions forum].
* Attend an online orientation meeting on Tuesday 5 May.
+
* Attend an online orientation meeting (date to be confirmed).
 
* Create a specification for your project in Moodle Docs and post in an appropriate Using Moodle forum asking for feedback.
 
* 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'.
+
* Post in your blog about your project specification and/or your first impressions of the Moodle community. Tag your entries 'moodle' and 'gsoc'.
  
 
Each week:
 
Each week:
 
* 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) and/or with Helen.
 
* Chat with your mentor(s) and/or with Helen.
* Participate in the GSOC group chat ''gsoc2009@conference.moodle.org''.
+
* Participate in the GSOC group chat ''gsoc2011@conference.moodle.org''.
  
 
==During the coding period==
 
==During the coding period==
Línia 17: Línia 17:
 
* Refine your specification based on feedback from your mentor and the wider Moodle community.
 
* 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.
 
* 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 your code as patches to tracker subtasks initially.
 
* 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.
 
* 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.
 
* Provide documentation in Moodle Docs.
Línia 27: Línia 27:
  
 
In the final week:
 
In the final week:
* Post in your blog a summary of everything you have worked on for GSOC 2009.  
+
* Post in your blog a summary of everything you have worked on for GSOC 2011.  
 
* 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 project work.  
 
* Post in an appropriate Using Moodle forum to inform the community of your project work.  

Revisió del 08:08, 26 abr 2011

The following is expected from our GSOC students:

During the community bonding period

  • Ensure you've introduced yourself in our GSOC 2011 Introductions forum.
  • Attend an online orientation meeting (date to be confirmed).
  • 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'.

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 gsoc2011@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.
  • 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 2011.
  • 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.

See also