googlecodein:organising

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
googlecodein:organising [2011/10/31 21:42] – Fix the link to the ideas page. BrooksDavisgooglecodein:organising [2021/01/25 05:14] (current) – Remove 3 broken hyperlinks. SashaVigole
Line 1: Line 1:
 ====== FreeBSD in the Google Code-In contest ====== ====== FreeBSD in the Google Code-In contest ======
  
-**It is not guaranteed that we'll qualify for 2011 due to lack of time (list of projects gets published November, 9th)**+STUDENTS: This page is for internal organisation of %%FreeBSD%%'s projects in GCIN 2011.  For information about how to get started with the %%FreeBSD%% tasks, please see [[GoogleCodeIn/GettingStarted]]
  
-**WARNING! Google Code-In is not %%GSoC%%. It requires different kind of mentoring.** +----
-**You must spend more time with young people. You may expect them to know very little about** +
-**Open Source (or maybe literally nothing). You must understand, that teenagers may be unfamiliar with rules of communication and coordination in %%FreeBSD%% (Google page says it's common for teenagers to use all CAPS while communicating with you etc..) Google expects faster turnaround time (<= 36 hours) in GCIN than in %%GSoC%% for mentor's support. You're expected to give a hand where necessary, always; you have to be very patient too. Good relationship with applicants is crucial to get them to use %%FreeBSD%% after Google Code-In is finished.** +
-\\  +
-\\  +
-**Think twice before becoming Google Code-In mentor for %%FreeBSD%%, please!**+
  
-Google Code-In is a contest targetted to pre-university students. Its purpose+Google Code-In is a contest targeted to pre-university students. Its purpose
 is to engage young people in an Open Source world as well as to promote is to engage young people in an Open Source world as well as to promote
 computer engineering among high-school students. computer engineering among high-school students.
Line 33: Line 28:
   - User Interface: Tasks related to user experience research or user interface design and interaction   - User Interface: Tasks related to user experience research or user interface design and interaction
  
-To find more about the Google Code-In contest: +To find more about the Google Code-In contest: ''%%http://code.google.com/intl/pl/opensource/gci%%''
- +
-[[http://code.google.com/intl/pl/opensource/gci/]]+
  
 Below is the list of ideas. Putting an idea to the list automatically Below is the list of ideas. Putting an idea to the list automatically
Line 44: Line 37:
 **actively mentor and help participants with their problems over the duration** **actively mentor and help participants with their problems over the duration**
 **of the contest.** **of the contest.**
 +
 +**WARNING! Google Code-In is not %%GSoC%%. It requires different kind of mentoring.**
 +**You must spend more time with young people. You may expect them to know very little about**
 +**Open Source (or maybe literally nothing). You must understand, that teenagers may be unfamiliar with rules of communication and coordination in %%FreeBSD%% (Google page says it's common for teenagers to use all CAPS while communicating with you etc..) Google expects faster turnaround time (<= 36 hours) in GCIN than in %%GSoC%% for mentor's support. You're expected to give a hand where necessary, always; you have to be very patient too. Good relationship with applicants is crucial to get them to use %%FreeBSD%% after Google Code-In is finished.**
 +\\ 
 +\\ 
 +**Think twice before becoming Google Code-In mentor for %%FreeBSD%%, please!**
  
 ===== Proposing FreeBSD tasks for the Google Code-In ===== ===== Proposing FreeBSD tasks for the Google Code-In =====
Line 50: Line 50:
 for the task, description and a mentor assigned to the task. for the task, description and a mentor assigned to the task.
  
-To cite  [[http://www.google-melange.com/gci/document/show/gci_program/google/gci2011/rules]]:+To cite  Google Code-In Rules, point 6a: ''%%http://www.google-melange.com/gci/document/show/gci_program/google/gci2011/rules%%''
  
 <code> <code>
Line 64: Line 64:
 ===== Information for the FreeBSD Google Code-In mentors ===== ===== Information for the FreeBSD Google Code-In mentors =====
  
-This page is very important. Please read and understand it: +This page is very important. Please read and understand it: ''%%http://code.google.com/p/google-code-in/wiki/GCIAdminMentorInformation%%''
- +
-[[http://code.google.com/p/google-code-in/wiki/GCIAdminMentorInformation]]+
  
 ===== Lists of tasks for particular years ===== ===== Lists of tasks for particular years =====
  
-[[GoogleCodeIn/2011|FreeBSD Google Code-In idea list of 2011]]+[[GoogleCodeIn/2011Tasks|FreeBSD Google Code-In idea list of 2011]] 
 + 
 +---- 
 + 
 +{{tag>Historical}}
  
  • googlecodein/organising.1320097348.txt.gz
  • Last modified: 2011/10/31 21:42
  • by BrooksDavis