summerofcode2010application

Differences

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

Link to this comparison view

Next revision		 Previous revision
summerofcode2010application [2010/03/12 02:05] – BrooksDavissummerofcode2010application [2021/04/26 04:46] (current) – Use MailTo macros. JethroNederhof
Line 25: Line 25:
 The %%FreeBSD%% project has participated in the Google Summer of Code since its inception. We have had a total of 99 projects, 91 of which passed. In each year we have had more promising student proposals and willing mentors than spaces were allocated to us, and so we were able to be extremely picky and I think this is reflected in the high success rate of our students. The %%FreeBSD%% project has participated in the Google Summer of Code since its inception. We have had a total of 99 projects, 91 of which passed. In each year we have had more promising student proposals and willing mentors than spaces were allocated to us, and so we were able to be extremely picky and I think this is reflected in the high success rate of our students.
  
-At least 10 of our former students continue to work on %%FreeBSD%% as full fledged committers and the work of many others has become part of the source and ports trees. Many others are currently in Ph.D. programs, some pursuing a similar line of %%FreeBSD%% related research to their %%SoC%% projects. We've also had quite a few join industry such as Google, Cisco, Oracle, Slide, and VMWare and found startups based on open source technologies (rememberthemilk.com).  Various %%FreeBSD%% project members have attended past Summer of Code Mentor Summits including all three members of our current admin team (Brooks Davis, Tim Kientzle, and Robert Watson).+A 17 former students have become full fledged committers, several others are active contributors, and the work of many others has become part of the source and ports trees.  Many others are currently in Ph.D. programs, some pursuing a similar line of %%FreeBSD%% related research to their %%SoC%% projects. We've also had quite a few join industry such as Google, Cisco, Oracle, Slide, and VMWare and found startups based on open source technologies (rememberthemilk.com).  Various %%FreeBSD%% project members have attended past Summer of Code Mentor Summits including all three members of our current admin team (Brooks Davis, Tim Kientzle, and Robert Watson).
  
 ==== If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006. ==== ==== If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006. ====
Line 48: Line 48:
  
 ==== 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 GSoC 2010. 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 GSoC 2010. 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-fs@freebsd.org for file systems, 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-fs@freebsd.org> for file systems, <freebsd-net@freebsd.org> for networking, or <freebsd-ports@freebsd.org> for ports collection related projects.
  
 The full list of mailing lists can be found at http://lists.freebsd.org/mailman/listinfo. The full list of mailing lists can be found at http://lists.freebsd.org/mailman/listinfo.
Line 56: Line 56:
  
 === Comment === === Comment ===
-A relatively complete list of %%FreeBSD%% related IRC channels can be found at http://wiki.freebsd.org/IrcChannels.+A relatively complete list of %%FreeBSD%% related IRC channels can be found [[IRC/Channels|here]].
  
 ==== Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2010 site. ==== ==== Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2010 site. ====
Line 76: Line 76:
 We will provide contributors with a designated place to post their status reports and encourage contributors, mentors, and other community members to review and comment on their work as it progresses. This will be separate from the primary mailing lists because we have found that posting to the primary lists can be quite intimidating. By creating a separate area where expectations are set appropriately and interactions are policed by mentors and administrators we hope to achieve a higher level of participation. Once code reaches a more complete state, we will encourage contributors to seek review on the appropriate lists. We will provide contributors with a designated place to post their status reports and encourage contributors, mentors, and other community members to review and comment on their work as it progresses. This will be separate from the primary mailing lists because we have found that posting to the primary lists can be quite intimidating. By creating a separate area where expectations are set appropriately and interactions are policed by mentors and administrators we hope to achieve a higher level of participation. Once code reaches a more complete state, we will encourage contributors to seek review on the appropriate lists.
  
-We also create a personal space about each accepted project on http://wiki.freebsd.org and make blog posts and newsflash entries about the projects. We also solicit individual project updates for our bi-monthly developer status reports, where these projects are reported on in the same document as our other mainstream development projects.+We also create a personal space about each accepted project on Wiki and make blog posts and newsflash entries about the projects. We also solicit individual project updates for our bi-monthly developer status reports, where these projects are reported on in the same document as our other mainstream development projects.
  
 Our project ideas page lists potential mentors and encourages students to contact them before the program so that we can open communication channels early. Our project ideas page lists potential mentors and encourages students to contact them before the program so that we can open communication channels early.
  • summerofcode2010application.1268359541.txt.gz
  • Last modified: 2010/03/12 02:05
  • by BrooksDavis