You are here: start » community » gsoc » gsoc2013 » student_guidelines

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
community:gsoc:gsoc2013:student_guidelines [2013/04/12 00:20]
michael 		community:gsoc:gsoc2013:student_guidelines [2013/04/19 00:22] (current)
Line 45: Line 45:
   * Join the [[http://groups.google.com/group/sahana-eden|Sahana Eden developer's list]]   * Join the [[http://groups.google.com/group/sahana-eden|Sahana Eden developer's list]]
  
 +==== Scope ====
 +It is much better for students to limit the scope of their project and ensure that they complete it to a high standard - quality over quantity! If you have to rush to finish your project and your code is full of hacks and not tested then it is likely that this will eventually have to be re-written. For this reason we encourage students to implement all the functionality of their project by the mid-term evaluation, leaving the second half of GSoC to polish, test, optimize, test, refactor, test, document and test their code.
 +
 +==== Evaluations ====
 +Sahana will evaluate students GSoC projects based on the following required outputs:
 +=== Mid Term ===
 +  * Demonstration - Students must present a demonstration of their project to the Sahana Community during the Sahana Community Call
 +=== Final ===
 +  * Demonstration - Students must present a demonstration of their project to the Sahana Community during the Sahana Community Call
 +  * Video Screen Cast - Students must create and publish a video screencast demonstrating their project   * 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), including:
 +    * User Documentation
 +    * Developer Documentation
 +    * Update BluePrints - include next steps
 +    * Manual Test Scripts
 +   * Sahana Eden Only:
 +    * Unit Tests
 +    * Selenium Automated Test Scripts
  
 ==== Contributor License Agreement ==== ==== 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.  An [[http://bit.ly/SSF-eCLA|electronic form]] may also be submitted (this is much easier). 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.  An [[http://bit.ly/SSF-eCLA|electronic form]] may also be submitted (this is much easier).
- 
-==== 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 ==== ==== 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.+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, study, holidays etc. Review the [[http://www.google-melange.com/gsoc/events/google/gsoc2013|GSoC timeline]]
  
 ===== Application Process ===== ===== Application Process =====
-NOTE: Sahana Software Foundation will be updating its application template. This will be completed by Friday 19th April 2013.+All students applying for GSoC with Sahana are expected to have made previous contributions to Sahana - so if you haven't this is the first thing to do!
  
 ==== Application Template ==== ==== Application Template ====
-Under Construction +It is expected that all students follow this template for their application.
-==== OLD Application Template ==== +
-It is expected that all students follow this template for their application. Entire Application should be within 7500 Characters.+
  
 === 1. Personal Details === === 1. Personal Details ===
-    * Name +  * Name 
-    * Communication details - Email*, Freenode IRC Nickname*, IM, Skype, Blog etc (* compulsory) +  * Contact Details  
-    * Include Biographical information about yourself, your education, country, timezone etc. +    * Email 
-    * If you have a link to a resume/CV/LinkedIn profile, include it here +    * Freenode IRC Nickname 
-    * Please provide an overview of your exposure to similar technologies and/or FOSS in general. +    * Skype 
-    * Please answer the question - “Why would you like to help the Sahana project?” +  * Blog 
- +  * Education 
-=== 2. Personal Availability === +    * University/College 
-    * Have you reviewed the [[http://www.google-melange.com/gsoc/events/google/gsoc2013|timeline]] for GSOC2012? +    * Course/Program 
-    * Do you have any significant conflicts with the listed schedule? If so, please list them here. +    * Year (Current & Total) 
-    * Will you need to finish your project prior to the end of the GSOC? +  * CV 
-    * Are there any significant periods during the summer that you will not be available?  +  * LinkedIn 
-=== 3. Project Abstract === +  * Your Code 
-  +    * GitHub Page 
- +    * LaunchPad Page 
-Provide a brief overview of the proposed idea and objectives you want to achieve with it here. (250 word limit). +  * Please list ALL other commitments between 17th June - 23 Sept 2013 
-=== 4. Project Plan === +  * Technical Skills - list all relevant languages, libraries, and technologies you are experienced in. Include your level (Beginner/Intermediate/Advanced). 
- +  * What experience do you have with Open Source Projects or any other relevant technologies? 
- +  * Why would you like to apply for GSoC with Sahana?
-This section is to provide the detail of your project proposal. Take as much space as is necessary. +
- +
-    * Project Deliverable - What is the essence of the project? What capability are you looking at adding to Sahana that will expand its capability for emergency/disaster management? +
-    * Project Justification - What is the relevance of your idea to the project? Why do you think its important to *have* this idea integrated to the Sahana system. +
-    * Implementation Plan - How are you going to implement your project? Use this section to expand in as much detail as possible how it should be constructed. +
-    * Future Options - Identify some aspects of the project that may not be within the scope of this submission, but could form the basis for future work that would build upon the outcomes of your project +
-    * Relevant Experience - Please list all experience you have that is directly relevant to the proposed project, and how they would help you deliver the project. If you have contributed to the Sahana project previously, please clearly outline your contributions.  +
- +
-You can also include links to additional details like diagrams etc outlining your ideas acting as supplementary information for your proposal outside of this scope. But it is highly advised to follow the KISS principle and stay as specific as possible. +
- +
-=== 5. Project Goals and Timeline ===+
  
-Clearly outline your timeline and goals for the project. All goals must follow the SMART (http://en.wikipedia.org/wiki/SMART_%28project_management%29) methodology - they should be Specific, Measurable, Achievable, Realistic and Time-bound. Each goal should explicitly tell us how we can measure it (e.g. code committed to trunk and can be assessed on demo.sahana.lk) and the date it is due. This should be provided as three columns - Due Date, SMART Goal, and Measure. The project is looking for explicit and well-written goals - proposals that contain broad and general goals will not be accepted. The more specific your goals, the better chance you have of being accepted. +=== 2. Project Details === 
-  +Students are welcome to apply for more than one project in order to increase their chances of getting accepted into GSoC with Sahana. Students are encouraged to ensure that their application for at least one of the project fully show-cases their effort and ability. If the mentors are impressed with the application for one of your projects, but this project is allocated to another student, there may be an opportunity to revise the other project application during the Interim Period. 
-These should be broken down into the following stages. +== BluePrint == 
-  - 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) +Use this [[http://eden.sahanafoundation.org/wiki/BluePrint/Guidelines/Template|BluePrint Template]] to prepare a blueprint for your project. Blueprints should be added as pages on the appropriate Sahana wiki. Students are encouraged to collaborate together on BluePrints, and incorporate input frm the community. The wiki will track contributions to ensure that these are attributed to the correct student. However students are also free to create their own BluePrint.
-  - First trimester (27 May - 16 June) - 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 (17 June - 2 August) - 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 (3 August - 23 September) - 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.+== Outputs == 
 +Please describe the following outputs which you will achieve at the different stages of your GSoC project. 
 +  * //Community Bonding Period// 
 +    * **Learning Goals** eg. Specific Feature within the Sahana Platform/API; How to use new technologies 
 +    * **Outstanding BluePrint Questions** Questions in your blueprints which need to be answered before you start your project 
 +    * **Initial Tasks** Any small tasks you plan on completing to prepare for your project  
 +  * //Mid-Term Evaluation// 
 +    * What features will you demonstrate during your mid-term evaluation? Prepare a initial "script" for this demonstration. 
 +  * //Final Evaluation// 
 +    * **Personal Success Statement** Describe what success will look like for you at the end of GSoC. What will you have learnt? What will you have gained? 
 +    * **Sahana Success Statement** Describe what success will look like for Sahana at the end of your GSoC project. How will Sahana be better?
  
-The intent is to maintain these as a shared Google Spreadsheet so that mentors can track progress in the spreadsheet.+== Plan == 
 +Provide a high level summary of the task you will be doing on your project for the  each of the 14 weeks of GSoC. 
  
-The Project Goals and Timeline will form a significant part of the assessment of your application, as well as mid-term and final evaluations.+==== Application Rating ==== 
 +Student's applications will be rated out of 100 points based on the following weights: 
 +  * 50 points for Sahana Code Contributions 
 +  * 10 points for Community Engagement 
 +  * 10 points previous experience 
 +  * 20 points Project Blue Print 
 +  * 5 points Project Outputs 
 +  * 5 points Project Plan
  
 ==== Communication with Sahana Team During Application Process ==== ==== Communication with Sahana Team During Application Process ====

Trace:

QR Code
QR Code community:gsoc:gsoc2013:student_guidelines (generated for current page)