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

(reading forum posts in the community bonding period)
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].
 
* Attend an online orientation meeting (details to be confirmed).
 
* Attend an online orientation meeting (details to be confirmed).
 
* Create a specification for your project in Moodle Docs and post in an appropriate forum asking for feedback.
 
* Create a specification for your project in Moodle Docs and post in an appropriate forum asking for feedback.
Línia 11: Línia 12:
 
* 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 ''gsoc2009@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 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.
 +
* Share your code by adding an entry in the [http://moodle.org/mod/data/view.php?id=6009 Modules and plugins database].
  
 
Each week:
 
Each week:
Línia 22: Línia 26:
 
* Have a meeting with your mentor.
 
* Have a meeting with your mentor.
 
* Participate in the GSOC group chat.
 
* Participate in the GSOC group chat.
 
 
''To be continued...''
 
  
 
==See also==
 
==See also==
  
 
* [[GSOC]]
 
* [[GSOC]]
 
+
* [[Development:Guidelines for contributed code]]
 
 
 
[[Category:GSOC]]
 
[[Category:GSOC]]

Revisió del 19:56, 17 abr 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 (details to be confirmed).
  • Create a specification for your project in Moodle Docs and post in an appropriate forum asking for feedback.
  • Post in your blog about your project specification and/or your first impressions of the Moodle community. You're welcome to use the blog facility on moodle.org or an external blog. Please tag all 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.
  • Share your code by adding an entry in the Modules and plugins database.

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.

See also