googlecodein:application:2011

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:application:2011 [2011/10/31 21:54] – Fix small style problems and typos. WojciechKoszekgooglecodein:application:2011 [2021/04/26 04:55] (current) – Use MailTo macros. JethroNederhof
Line 14: Line 14:
 rwatson rwatson
 ==== Why has your org chosen to participate in Google Code-in? ==== ==== Why has your org chosen to participate in Google Code-in? ====
-First and formost, we hope to attract more young people within 13-17 age range to use %%FreeBSD%%. We would like to obtain a feedback and contributions from young people in order to better understand the entry cost to the %%FreeBSD%% developers. We would like to learn, what first time users expect from the Operating System. GCIN offers an execellent form of introduction and evaluation to the Open Source world. By mentoring students, we hope to gain new and improved funtionality as a result of submitted contributions. Third, by participating in GCIN we increase our exposure to young people within high-schools and secondary schools in general.+First and formost, we hope to attract more young people within 13-17 age range to use %%FreeBSD%%. We would like to obtain a feedback and contributions from young people in order to better understand the entry cost to the %%FreeBSD%% developers. We would like to learn, what first time users expect from the Operating System. GCIN offers an execellent form of introduction and evaluation to the Open Source world. By mentoring students, we hope to gain new and improved functionality as a result of submitted contributions. Third, by participating in GCIN we increase our exposure to young people within high-schools and secondary schools in general.
 ==== Please list the years your organization has participated in Google Summer of Code ==== ==== Please list the years your organization has participated in Google Summer of Code ====
 2005-2011 2005-2011
 ==== What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for Google Code-in 2010-11. If your organization uses more than one list, please make sure to include a description of the list so students know which to use. ==== ==== What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for Google Code-in 2010-11. If your organization uses more than one list, please make sure to include a description of the list so students know which to use. ====
-The best general mailing list to discuss project ideas on is freebsd-hackers@freebsd.org. You may also receive useful feedback on area specific lists such as freebsd-doc@freebsd.org for documentation, freebsd-net@freebsd.org for networking, or freebsd-ports@freebsd.org for ports collection related projects.+The best general mailing list to discuss project ideas on is <freebsd-hackers@freebsd.org>. You may also receive useful feedback on area specific lists such as <freebsd-doc@freebsd.org> for documentation, <freebsd-net@freebsd.org> for networking, or <freebsd-ports@freebsd.org> for ports collection related projects.
 ==== What is the main IRC channel for your organization? ==== ==== What is the main IRC channel for your organization? ====
 #freebsd-soc #freebsd-soc
 ==== Please provide a link to your task ideas page. This is much like the ideas page for Google Summer of Code but must include at least 5 tasks in all of the 8 categories sorted by difficulty level. ==== ==== Please provide a link to your task ideas page. This is much like the ideas page for Google Summer of Code but must include at least 5 tasks in all of the 8 categories sorted by difficulty level. ====
-http://wiki.freebsd.org/GoogleCodeIn/2011+[[GoogleCodeIn/2011Tasks]]
 ==== Please tell us about how your organization has prepared for Google Code-in, including what (and how many) mentors and organization administrators have agreed to help, what your schedule and response time will be during the holidays (and otherwise during the contest period) and how you plan to deal with unresponsive mentors ==== ==== Please tell us about how your organization has prepared for Google Code-in, including what (and how many) mentors and organization administrators have agreed to help, what your schedule and response time will be during the holidays (and otherwise during the contest period) and how you plan to deal with unresponsive mentors ====
 We have a high-quality idea list with 44 tasks. We have 12 mentors assigned to the tasks. Most of the mentors are very active %%FreeBSD%% contributors, largely responsible for %%FreeBSD%%-related projects, like: The %%FreeBSD%% Documentation Project. We expect these people will be responsive in the expected 36-hour turn-around time, since this is how quickly they typically answer on a daily basis. We have a high-quality idea list with 44 tasks. We have 12 mentors assigned to the tasks. Most of the mentors are very active %%FreeBSD%% contributors, largely responsible for %%FreeBSD%%-related projects, like: The %%FreeBSD%% Documentation Project. We expect these people will be responsive in the expected 36-hour turn-around time, since this is how quickly they typically answer on a daily basis.
  • googlecodein/application/2011.1320098098.txt.gz
  • Last modified: 2011/10/31 21:54
  • by WojciechKoszek