You are here: start » community » gsoc » gsoc2011_student_guidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
community:gsoc:gsoc2011_student_guidelines [2011/03/02 03:56]
bitner created stub from 2010 guidelines 		community:gsoc:gsoc2011_student_guidelines [2011/03/12 16:29] (current)
Line 1: Line 1:
-====== Guidelines for Students Participating in Google Summer of Code 2010 for Sahana ======+====== Guidelines for Students Participating in GSOC 2011 for SSF ====== 
 + 
 +===== Overview ===== 
 +  * Prior GSOC Students with the Sahana Software Foundation **will** be considered as applicants this year. 
 +  * Students must submit a bug fix for the project first. (Please engage with proposed mentors to identify an appropriate bug that will demonstrate your skills and capabilities).  
 +  * Students should get involved with projects now 
 +  * Our priorities and [[community:gsoc:gsoc2011_ideas|project ideas]] are likely to be weighted more favorably. 
 + 
 +===== Expectations ===== 
 + 
 +==== Coding ==== 
 + 
 +It is expected that students will read and follow the developer guidelines for the project that they are working with.\\ 
 + 
 +For Agasti (PHP): 
 +  * [[agasti:start|Agasti wiki]] 
 +    * [[agasti:vesuvius:start|Vesuvius]] 
 +    * [[agasti:mayon:start|Mayon]] 
 +    * [[agasti:developer:coding_guidelines| Coding Guidelines]] 
 +For Eden (Python/web2py): 
 +  * [[http://eden.sahanafoundation.org|Eden wiki]] 
 +  * [[http://eden.sahanafoundation.org/wiki/DeveloperGuidelines|Developer Guidelines]] 
 + 
 +==== Communication ==== 
 +  * It is expected that students will report to the main Sahana discussion list (discuss@lists.sahanafoundation dot org) at the beginning of the project to introduce themselves and their project to the rest of the Sahana community. 
 +  * It is expected that students will report to the main Sahana discussion list at a minimum once every other week providing a summary of current activities with pointers to their work in the code and on the wiki. 
 +  * It is also advisable to keep all development related discussions on the developer's mailing lists (see below) so that other developers can provide feedback & suggestions on the ideas being worked out and for future archival purposes. 
 +  * GSOC-related discussions should be prefaced with "[GSOC]" in the subject line. 
 + 
 +=== IRC Channels === 
 +We maintain and monitor the followin IRC Channels on freenode.  A web interface is available at http://webchat.freenode.net: 
 +  * #Sahana - main disussion channel 
 +  * #Sahana-Agasti - for Agasti developers 
 +  * #Sahana-Eden - for Eden developers 
 +  * #Sahana-Meeting - for meetings 
 +All channels are logged.  See http://www.sahanafoundation.org/chat for more information. 
 + 
 +=== Mailing Lists === 
 +We maintain several e-mail discussion lists.  The main point of entry for prospect GSOC students and GSOC discussions and reports to the community through the GSOC program is our main discussion list: discuss@lists.sahanafoundation dot org. 
 +  * Join the [[https://lists.sourceforge.net/lists/listinfo/sahana-maindev|Main Sahana Discussion list]] 
 +  * Join the [[https://lists.sourceforge.net/lists/listinfo/sahana-agasti|Sahana-Agasti developer's list]] 
 +  * Join the [[http://groups.google.com/group/sahana-eden|Sahana Eden developer's list]] 
 + 
 + 
 +==== Contributor License Agreement ==== 
 + 
 +In keeping with Sahana Software Foundation policy, all accepted students must sign and return a [[foundation:start#contributor_license_agreement|Contributor License Agreement]].  A {{:foundation:ssf_cla.pdf|CLA form}} may be downloaded here and should be scanned and returned to cla-submissions at SahanaFoundation dot org.  Alternative means of return by post or fax are provided on the form.  
 + 
 +==== Documentation ==== 
 +  * It is expected that students will document all of their work in an appropriate place on the Sahana wiki (mentors will help with where to put things and with wiki access). 
 + 
 +==== Work Load ==== 
 +  * It is expected that students will treat this as a full time job (This means approximately 40 hours per week). Students should disclose any other commitments to other jobs, internships, etc. 
 ===== Application Process ===== ===== Application Process =====
 ==== Application Template ==== ==== Application Template ====
Line 13: Line 66:
  
 === 2. Personal Availability === === 2. Personal Availability ===
-    * Have you reviewed the [[http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#timeline|Important Dates and Times]] for GSOC2010?+    * Have you reviewed the [[http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline]] for GSOC2011?
     * Do you have any significant conflicts with the listed schedule? If so, please list them here.     * Do you have any significant conflicts with the listed schedule? If so, please list them here.
     * Will you need to finish your project prior to the end of the GSOC?     * Will you need to finish your project prior to the end of the GSOC?
Line 40: Line 93:
 These should be broken down into the following stages. These should be broken down into the following stages.
   - Work already undertaken - What research have you undertaken in this area in advance? (these can just be bullet points and are not required to follow the SMART methodology)   - Work already undertaken - What research have you undertaken in this area in advance? (these can just be bullet points and are not required to follow the SMART methodology)
-  - First trimester (26 April - 23 May) - identify the SMART goals you have for the community bonding period. Most of these are likely to revolve around further scoping of the project with the community, engaging with the community, and updating and finalizing the project plan. +  - First trimester (25 April - 23 May) - identify the SMART goals you have for the community bonding period. Most of these are likely to revolve around further scoping of the project with the community, engaging with the community, and updating and finalizing the project plan. 
-  - Second trimester (24 May - 12 July) - identify the draft SMART goals you have for the first half of the project. These will be used to assess project process and form the basis for the mid-term evaluation. +  - Second trimester (24 May - 11 July) - identify the draft SMART goals you have for the first half of the project. These will be used to assess project process and form the basis for the mid-term evaluation. 
-  - Third trimester (13 July - 9 August) - identify the draft SMART goals you have for the second half of the project. These will be used to assess the whole project and in conjunction with the mid-term goals, form the basis for the final evaluation.+  - Third trimester (12 July - 15 August) - identify the draft SMART goals you have for the second half of the project. These will be used to assess the whole project and in conjunction with the mid-term goals, form the basis for the final evaluation.
  
 We recognize that the goals may change during the project, and the mentors will accept modifications to the goals at any time. For example, discussion during the community engagement stage may change the scope of the project, and the goals may need to be subsequently modified. As such, the goals are not hard-and-fast, but we do want to see reasonable effort go into the initial project timeline. We recognize that the goals may change during the project, and the mentors will accept modifications to the goals at any time. For example, discussion during the community engagement stage may change the scope of the project, and the goals may need to be subsequently modified. As such, the goals are not hard-and-fast, but we do want to see reasonable effort go into the initial project timeline.
Line 54: Line 107:
 It is encouraged for students to communicate with the Sahana team members during the application process to help guide their applications. It is encouraged for students to communicate with the Sahana team members during the application process to help guide their applications.
 Venues to discuss projects: Venues to discuss projects:
-  * [[https://lists.sourceforge.net/lists/listinfo/sahana-maindev| Sahana development mailing list]]. Mark the subject of your mails for GSoC related discussions with  **[gsoc10]**+  * [[https://lists.sourceforge.net/lists/listinfo/sahana-maindev| Sahana development mailing list]]. Mark the subject of your mails for GSoC related discussions with  **[gsoc2011]**
   * [[http://sahana.lk/chat| IRC (irc.freenode.net/#sahana)]]   * [[http://sahana.lk/chat| IRC (irc.freenode.net/#sahana)]]
  
-===== Expectations =====+If your questions are specific to a particular Sahana Project (Agasti or Eden), mentors may direct you to a more specific mailing list or IRC channel. You should not expect to use personal email or direct messaging to communicate with mentors.
  
-==== Coding Standards ==== 
-  * It is expected that students read up on the developer guidelines from the project wiki beforehand to have an overview of the Sahana system 
-For PHP: 
-  * [[dev:home| Dev Wiki]], especially the coding conventions & [[http://www.cs.trincoll.edu/hfoss/wiki/The_Sahana_Code_Base|this documentation]] to understand the Sahana file system & code base. 
-For Python: 
-  * [[http://trac.sahanapy.org/wiki/DeveloperGuidelines|Developer Guidelines]] 
- 
-==== Communication ==== 
-  * It is expected that students will report to the Sahana development mailing list at the beginning of the project to introduce themselves and their project to the rest of the Sahana community. 
-  * It is expected that students will report to the Sahana development mailing list at a minimum once every other week providing a summary of current activities with pointers to their work in the code and on the wiki. 
-  * It is also advisable to keep all development related discussions on the mailing lists so that other developers can provide feedback & suggestions on the ideas being worked out and for future archival purposes. 
-==== Documentation ==== 
-  * It is expected that students will document all of their work in an appropriate place on the Sahana wiki (mentors will help with where to put things and with wiki access). 
- 
-==== Work Load ==== 
-  * It is expected that students will treat this as a full time job.  
  

Trace:

QR Code
QR Code community:gsoc:gsoc2011_student_guidelines (generated for current page)