Google summer of code 2012
1 like474 views
The document provides an overview of Google Summer of Code (GSoC) 2012, outlining its application process, important timelines, and necessary preparations for prospective student participants. It emphasizes the importance of finding the right project and organization, effective communication with mentors, and adhering to guidelines while coding. Additionally, it highlights the historical success rates and resources available for students to improve their chances of acceptance and successful project completion.
Google summer of code 2012
- 1. Summer of Code 2012 Kathiravelu Pradeeban AbiWord
- 6. Shout!
- 7. Apply.
- 8. Code.
- 10. What Else?
- 11. Google Summer of Code (GSoC) Code for a chosen open source project for 3 months.
- 12. Google pays you! 3 milestones. Getting Accepted.
- 13. Mid-Evaluations.
- 14. Final Evaluations. A certificate.
- 15. An awesome tshirt and gifts!
- 16. {500, 2250, 2250} USD.
- 17. Some statistics of 2011 175 Organizations 2096 mentors and co-mentors. Submitted 3,731 students, from 97 countries.
- 18. 5,651 proposals. Accepted 1115 students/projects 68 countries.
- 20. Success Rate.. is pretty high! Passed Midterm-Evaluations Success rate upto mid - 90%+. Passed Final Evaluations.
- 21. Success rate – 88%
- 22. Google Open Source Blog on GSoC
- 24. Why Google Summer of Code?
- 25. What do you need? ♥
- 26. Time Line (2011) January 24 th : Program Announced.
- 27. February 28 th – March11 th : Organizations apply.
- 28. March 18 th : List of Accepted Organizations.
- 29. March 18 th - 27 th : Students discussing project ideas.
- 30. March 28 th – April 8 th : Students application period.
- 31. Time Line After getting accepted.. April 25 th : Accepted Students announced. : Community Bonding Period Begins. May 23 rd : Coding Begins.
- 32. July 11 th – July 15 th : Mid Evaluations.
- 33. Aug 15 th – Suggested Pencils Down. Tests, Documentation improvements, etc.
- 34. Time Line Concluding Aug 22 nd – Firm Pencils Down. Stop Work! Aug 26 th – Final Evaluation Deadline.
- 35. Aug 29 th – Final Results.
- 36. Aug 30 th – Begin Code Submission to Google.
- 37. Before you begin.. Google Summer of Code is all about being Open Source.
- 38. Get your basics right.
- 39. Netiquettes.
- 40. Sign up to the lists.
- 41. Join the relevant channel.
- 42. Technologies .. Version Control Systems - SVN, CVS, GIT, Mercurial, .. Build Tools - Ant, Maven, .. IDE - IntelliJ IDEA, Eclipse, ..
- 43. Microsoft Visual Studio, Anjuta, ..
- 44. Network Etiquettes Be Specific and clear.
- 45. Research (google.. ;)) before asking.
- 46. Be helpful to others.
- 48. NO CAPS! ( UNLESS YOU ARE SHOUTING! )
- 49. Don't take messages personally.
- 50. Dn't snd ur sms msgs to thrds or lsts.
- 51. Language/English
- 52. Mailing lists Post only to the relevant list User, Dev, .. Check the mail archives first.
- 58. IRC Etiquettes Be an observer first.
- 59. Refer to others using their irc nick.
- 60. Don't expect immediate replies; wait.
- 61. Don't post bulk of text into irc. Post error logs to http://pastebin.com/ or http://paste.ubuntu.com/ and share the url instead.
- 62. Find a mentoring organization.. Have a look at the list of GSoC2011.
- 63. 175 Last year!
- 65. Google as the mentoring organization.
- 66. Introduce GSoC to an organization (Sounds Smart!).
- 67. Find THE right project.. Go through the projects list. Some organizations publish pretty soon.
- 68. Have a look at the 2011's. Dev mailing lists.
- 69. Talk to the mentors. IRC, mail, ... New features/enhancements Bug/Issue tracker – JIRA, Bugzilla, ...
- 70. What makes you special? Experience Being a great user doesn't mean that you can be a good developer. Your interests and motivation Pick something you really enjoy doing.
- 71. Being a great developer doesn't mean that you can be a good contributor. Opportunities What makes you the right person?
- 73. Not much time to learn a new language (?) Prove It! Patches.
- 75. Project expertise Bug reports and fixes.
- 76. Check the list archives and the project wikis and web sites.
- 77. Opportunities.. Project that matches your previous work.
- 78. Choose the right project.
- 79. Timezone Difference Use it effectively
- 80. For Sri Lanka,GMT + 0530. Multiple Applications (20!)
- 81. Preferences!
- 84. Ask questions.
- 85. Most importantly, Answer others' questions! Mentor is your friend (respect)
- 86. Be Known.. NO Sir, Madam, aiya, akki, machan ..
- 87. First Name or Preferred calling name.
- 88. No Mr. Dr. either. Be heard!
- 89. Be visible!
- 90. Be responsive!
- 91. Be quick!
- 92. Apply Register as a student for GSoC.
- 93. Use the project's wiki or site for draft proposal, if applicable.
- 94. Get mentor's opinion and improve.
- 95. Apply on Google's melange . Can edit later, till the last minute! Check often for the comments from the mentors / co-mentors
- 96. attend to them.
- 97. Propose .. ♡ How to impress the mentor/developers?
- 98. Stick to the organization's template.
- 99. Abstract.
- 100. Introduce yourself properly. Focus on the relevant facts.
- 101. Why do you fit? Your skill sets.
- 102. List of the patches (if any) you have submitted.
- 103. Propose .. Project Goals Proves you got them correct. Deliverables Code, Documentation, test cases, .. Description Benefits to the organization and other projects.
- 104. Can also be given along with the time line.
- 105. Propose .. Time line Finer details.
- 106. Break upto periods of 3 - 4 days.
- 107. Testing takes time.
- 109. Some organizations require considerable work hrs/week (40 ?). Links References and additional details.
- 111. Email:
- 112. Project Title:
- 113. Synopsis: A short description of your project. Benefits to the organization/project and/or other project(s): Deliverables: Quantifiable results.
- 114. e.g: “ At the end of my project, AbiWord’s piece table will be 50 times faster .” Project Details: A more detailed description of your project: Project Schedule: How long will the project take?
- 115. When can you begin work?
- 116. Do you know of any planned absences or other major conflicts summer classes, vacations, etc.
- 117. Bio: Who are you?
- 118. What makes you the best person to work on this project? Additional Requirements: Patches / Specific requirements for the project. Further Related Information:
- 119. After the submission.. Don't go invisible! Evaluation is still going on.. ;) You may be asked to provide additional information. Patches.
- 120. Screenshots. Start coding on your project. only if you didn't apply for multiple projects. Be motivated.
- 121. Got Selected? \yay/ Don't Panic.
- 122. You have one more month just to mingle with the developers and the code base. Mentor(s) are there to help you!
- 123. Keep touch with the developers.
- 124. Users.
- 125. Community Bonding Period Go through the code base and documentation.
- 126. Coding styles and coding guide lines.
- 127. Start with simple hacks.
- 128. Understand the project idea more.
- 129. Come up with a design.
- 130. Communicate often irc/lists/forums/wiki
- 131. Coding.. Easiest task of all.. ;) Commit often, if given committership. Send daily patches otherwise.
- 132. Meaningful Commit messages. Keep others updated (Daily ?). IRC, dev lists, personal mails, wiki, conference calls, skype, blog posts Get feedback from the mentor(s).
- 133. Plan for the mid and final evaluations early, with the mentor.
- 134. Conclude/Continue.. Pencils Down Date
- 135. Firm Pencils Down Date GSoC Coding ends here. Get a tarball of all the diff files to submit to Google.
- 136. Focus on becoming a committer if not already given committership. Keep contributing (if possible).
- 137. What else? More FOSS? Annual?
- 138. Stipend?
- 139. Student?
- 140. Country/Location?
- 141. More Open Source programs/contests.. OpenOffice.org Internship
- 143. Wesnoth Summer Art Scholarship
- 144. Umit Summer of Code (USoC)
- 145. Season of KDE (SoK)
- 146. The OpenMRS Internship Program (OIP)
- 147. Joomla! Student Outreach Program
- 148. Ruby Summer of Code
- 149. Fedora Summer Coding http://fedoraproject.org/wiki/Summer_Coding_2010
- 151. Project Lists for 2011.. AbiWord
- 152. PhpMyAdmin
- 153. Kubuntu
- 154. DocBook Wiki
- 155. [Refer to the projects list of 2011 of the organizations till the GSoC 2012 is announced.]
- 156. Some links.. ;) GSoC-2011 FAQ
- 158. GSoC Student Guide
- 159. Proposal [Pradeeban] - GSoC 2009 AbiWord
- 160. Proposal [Pradeeban] - GSoC 2010 OMII-UK/OGSA-DAI
- 161. Proposal [Konstantin] - GSoC 2006 Drupal
- 162. Are you ready? Have a look at the past projects.
- 163. Proposals available online. Wikis, blogs, .. Apache Software Foundation Tomcat, Derby, Axis2, and more ..
- 164. More slots and more choices. Find the projects' mailing lists and IRC. AbiWord [email_address]
- 165. [email_address]
- 167. For more Information .. Join Local GSoC Google Groups Group for Sri Lankan students: http://groups.google.com/group/gsoc-srilanka Local GSoC IRC channel Sri Lanka - #gsoc-lk at irc.freenode.net. Drop me a line. ;) [email_address] kkpradeeban.blogspot.com Logos/images used in the presentation are owned by the respective open source organizations or the individual, and used for the particular non - commercial informative purpose only.
- 168. Questions?..
- 169. Wish you all the best..