Differences

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

Link to this comparison view

Next revision
Previous revision
developers:gsoc:general_information [2015/07/26 19:27]
nurupo moved over
developers:gsoc:general_information [2019/01/07 22:17] (current)
nurupo [Student information] Update student guide link
Line 1: Line 1:
 ====== General Google Summer of Code Information ====== ====== General Google Summer of Code Information ======
  
-See also: **[[developers:​gsoc:​2015:​ideas|Ideas for GSoC 2015]]**, [[developers:​gsoc:​2014:​ideas|2014]].+See also: **[[developers:​gsoc:​2016:​ideas|Ideas for GSoC 2016]]**, [[developers:​gsoc:​2015:​ideas|2015]], [[developers:​gsoc:​2014:​ideas|2014]].
  
-===== Summary ===== 
 Tox, or Project Tox, is a FLOSS (Free/​Libre/​Open Source Software), distributed,​ and secure instant messaging application aimed to replace Skype. Tox's goal is to be an easy to use, all-in-one communication platform (including audio and video chats in the future) that ensures users' full privacy and secure message delivery. We seek adoption among everyone from the tech savvy to the tech uninclined, by dealing with the complicated stuff in our core library and providing attractive and intuitive interfaces for all sorts of platforms. Tox, or Project Tox, is a FLOSS (Free/​Libre/​Open Source Software), distributed,​ and secure instant messaging application aimed to replace Skype. Tox's goal is to be an easy to use, all-in-one communication platform (including audio and video chats in the future) that ensures users' full privacy and secure message delivery. We seek adoption among everyone from the tech savvy to the tech uninclined, by dealing with the complicated stuff in our core library and providing attractive and intuitive interfaces for all sorts of platforms.
  
 ===== Common information for all participants ===== ===== Common information for all participants =====
-All participants should be familiar with the GSoC [[https://www.google-melange.com/gsoc/events/​google/​gsoc2015|timeline]] shown on the Google Summer of Code website and be aware of the deadlines.+All participants should be familiar with the GSoC [[https://developers.google.com/​open-source/gsoc/timeline|timeline]] shown on the Google Summer of Code website and be aware of the deadlines.
  
-It's also important to read through [[https://www.google-melange.com/gsoc/document/​show/​gsoc_program/​google/​gsoc2015/​help_page|FAQ]] from the Google Summer of Code website, since it contains many useful information.+It's also important to read through [[https://developers.google.com/​open-source/gsoc/faq|FAQ]] from the Google Summer of Code website, since it contains many useful information.
  
 ===== Student information ===== ===== Student information =====
-We expect students to produce something complete in the 3 months. While some projects might require more time than others to complete, we expect you to be able to work 40 hours per week, as if it was a full time employment. You should communicate with your mentor on regular basis, discussing the project, as well as push your code in your repository, on regular basis too, so that your mentor could see the progress you are making. +Students should be aware that we are looking for people who have a legitimate interest in Open Source Software and are participating because they support what we do. We are not looking for a person with the best code and attending the best school, ​nor for someone ​who is going to run away after the 3 months are over.
- +
-Students should be aware that we are looking for people who have a legitimate interest in Open Source Software and are participating because they support what we do. We are not looking for a person with the best code and attending the best school, ​but who is going to run away after the 3 months are over.+
  
 You should start familiarizing yourself with the components that you plan on working on before the start date. Our developers are available on [[users:​community|IRC]] for help. GSoC reserves a lot of time for bonding, so use that time wisely. You should start familiarizing yourself with the components that you plan on working on before the start date. Our developers are available on [[users:​community|IRC]] for help. GSoC reserves a lot of time for bonding, so use that time wisely.
Line 20: Line 17:
 Go over [[#Common information for all participants|Common information for all participants]]. Go over [[#Common information for all participants|Common information for all participants]].
  
-You might find it useful to read [[http://en.flossmanuals.net/GSoCStudentGuide/|GSoC Student Guide]].+You might find it useful to read [[https://google.github.io/gsocguides/​student/|GSoC Student Guide]]
 + 
 +==== Expectations ==== 
 +  * Produce something complete in the 3 months. 
 +  * While some projects might require more time than others to complete, we expect you to be able to work 40 hours per week, as if it was a full time employment. 
 +  * Communicate with your mentor every working day. Just say “Hello” if you like. 
 +  * Commit code early and push to the repository often, so that your mentor could see the progress you are making and comment on your code. 
 +  * Write short weekly progress reports for the entire organization to see answering the following questions (don't be afraid to add many details) 
 +    * What did you get done this week? 
 +    * What do you plan on doing next week? 
 +    * Are you blocked on anything? 
 + 
 +Failure to meet any of these expectations will result in the student failing GSoC.
  
 ==== Proposal guidelines ==== ==== Proposal guidelines ====
Line 29: Line 38:
 Here are some things to address in your proposal: Here are some things to address in your proposal:
  
-  * Who are you? What are you studying?+  * Who are you? What are you studying? What degree are you perusing?
   * What is your e-mail address? What is your IRC nick? What is your account on GitHub or other collaborative websites?   * What is your e-mail address? What is your IRC nick? What is your account on GitHub or other collaborative websites?
   * What exactly you are intending to do? What will not be done?   * What exactly you are intending to do? What will not be done?
Line 45: Line 54:
   * What is your native language? Would you be comfortable working with a mentor whose native language is English?   * What is your native language? Would you be comfortable working with a mentor whose native language is English?
   * What time zone do you live in? Maybe we could assign you a mentor that lives closer to your time zone, so that you won't have to wait too long for mentor'​s reply.   * What time zone do you live in? Maybe we could assign you a mentor that lives closer to your time zone, so that you won't have to wait too long for mentor'​s reply.
 +  * Have you participated in GSoC before?
 +  * How many times? Which year? Which project?
 +  * Have you applied but were not selected? When?
  
 ==== Advice ==== ==== Advice ====
Line 60: Line 72:
  
 **Start early**\\ **Start early**\\
-Try to submit a patch for a project you are willing to be working on or make some small demo/ui mockup of your proposal (don't spend much time on it). This shows your interest in the project and will make your proposal more noticeable by developers.+Contact mentors, set up the development environment and try to submit a patch for a project you are willing to be working on or make some small demo/ui mockup of your proposal (don't spend much time on it). This shows your interest in the project and ability to use developer tools, which will make your proposal ​much more noticeable by mentors.
  
 **Come speak to us beforehand**\\ **Come speak to us beforehand**\\
-You are much more likely to have your proposal picked ​if we recognize ​you from our [[IRC]] ​channel.+You are much more likely to be selected ​if you discuss your project idea with mentors through email or [[users:​community|IRC]]. Simply submitting your proposal and doing nothing is a very **bad idea**.
  
 **Don'​t stop on us**\\ **Don'​t stop on us**\\
-We get hundreds of proposals for just four or eight slots, so we advise you to send proposals to several organizations. This will increase your chance of being accepted in GSoC.+We get hundreds of proposals for just a few slots, so we advise you to send proposals to several organizations. This will increase your chance of being accepted in GSoC.
  
 ===== Mentor information ===== ===== Mentor information =====
Line 79: Line 91:
 Make sure you go over [[#Common information for all participants|Common information for all participants]]. Make sure you go over [[#Common information for all participants|Common information for all participants]].
  
-You might also find it useful to read [[http://en.flossmanuals.net/gsocmentoring/|GSoC Mentor Guide]].+You might also find it useful to read [[https://google.github.io/gsocguides/​mentor/|GSoC Mentor Guide]].
  
 <WRAP center round info 50%> <WRAP center round info 50%>
 This page uses [[http://​creativecommons.org/​licenses/​by-sa/​3.0/​|Creative Commons Licensed]] content from [[https://​community.kde.org/​GSoC|KDE Community Wiki]] ([[https://​community.kde.org/​index.php?​title=GSoC&​amp;​action=history|view authors]]) This page uses [[http://​creativecommons.org/​licenses/​by-sa/​3.0/​|Creative Commons Licensed]] content from [[https://​community.kde.org/​GSoC|KDE Community Wiki]] ([[https://​community.kde.org/​index.php?​title=GSoC&​amp;​action=history|view authors]])
 </​WRAP>​ </​WRAP>​
Print/export