summerofcode2011application

Differences

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

Link to this comparison view

Next revision		 Previous revision
summerofcode2011application [2011/03/04 02:37] – Start a 2011 application page with the contents of the 2010 application BrooksDavissummerofcode2011application [2021/04/26 04:45] (current) – Use MailTo macros. JethroNederhof
Line 23: Line 23:
  
 ==== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ==== ==== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ====
-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 117 projects, 105 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.
  
 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). 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. ====
 +2010: 16/18
 +
 2009: 17/20 2009: 17/20
  
Line 39: Line 41:
  
 === Comment === === Comment ===
-total: 91/99+total: 107/117
  
 ==== If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? ==== ==== If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? ====
Line 48: Line 50:
  
 ==== 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.
  
 ==== What is the main IRC channel for your organization? ==== ==== What is the main IRC channel for your organization? ====
-What is the main IRC channel for your organization?+#freebsd-soc
  
 === 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 71: Line 73:
  
 ==== What is your plan for dealing with disappearing mentors? ==== ==== What is your plan for dealing with disappearing mentors? ====
-As with students, finding the problem is the most important thing. We will encourage mentors to interact with their contributors in a public or semi-public venue so we can keep tabs on them. We will also ask them to provide their schedules so we know when we can expect to see them interacting with contributors. We will attempt to provide a backup mentor for each project. Backup mentors may be oversubscribed, but will be expected to be aware of the project status. Additionally we will poll students periodically about their mentor contact. If it is inadequate we will ask the backup mentor to take a greater role or to take over. Additionally, we will take care to select mentors who we believe have the time and personality necessary to be effective mentors.+As with students, finding the problem is the most important thing. We will encourage mentors to interact with their contributors in a public or semi-public venue so we can keep tabs on them. We will also ask them to provide their schedules so we know when we can expect to see them interacting with contributors. We will attempt to provide a backup mentor for each project. Backup mentors may be oversubscribed, but will be expected to be aware of the project status. Additionally we will poll students periodically about their mentor contact. If it is inadequate we will ask the backup mentor to take a greater role or to take over. Additionally, we will take care to select mentors who we believe have the time and personality necessary to be effective mentors.  We have been fortunate to have few problems with mentors during out time with %%GSoC%%.
  
 ==== What steps will you take to encourage students to interact with your project's community before, during and after the program? ==== ==== What steps will you take to encourage students to interact with your project's community before, during and after the program? ====
 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 the 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.
Line 82: Line 84:
 We invite all gsoc participants to attend BSD conferences and developer summits, and thanks to The %%FreeBSD%% Foundation, are able to offer travel support to them. This allows them to present their work to the community, meet the people they've seen on the lists (and their mentor), as well as network with the community and potential employers. We invite all gsoc participants to attend BSD conferences and developer summits, and thanks to The %%FreeBSD%% Foundation, are able to offer travel support to them. This allows them to present their work to the community, meet the people they've seen on the lists (and their mentor), as well as network with the community and potential employers.
  
-After the program is over we profile many of the successful projects on our website and provide the tools and support necessary for them to continue working should they desire. We retain system accounts for students that are still working on %%FreeBSD%%. +After the program is over we profile many of the successful projects on our website and provide the tools and support necessary for them to continue working should they desire.  We retain system accounts and email addresses for students who are still working on %%FreeBSD%%.  We will also to remind mentors to propose successful students as committers before the end of the evaluation period.  While not every successful project will reflect an ideal committer, many do and we want to capture as many of those as possible.
- +
-==== What will you do to ensure that your accepted students stick with the project after GSoC concludes? ==== +
-While there have been exceptions, the best predictor of contributors sticking with the project so far has been getting their code into the tree during or shortly after their project is completed. We plan to encourage contributors and mentors to set schedules that produce integratiable code as early and often as the project permits. We also intend remind mentors to propose successful students as committers before the end of the evaluation period. While not every successful project will reflect an ideal committer, many do and we want to capture as many of those as possible. +
- +
-We will also continue to support the infrastructure necessary for the student to continue working.  Students can keep their freebsd.org email forward, Perforce account, wiki account, and if necessary, login access to project compute resources to enable them to continue working.+
  
 ==== Is there anything else you would like to tell the Google Summer of Code program administration team? ==== ==== Is there anything else you would like to tell the Google Summer of Code program administration team? ====
 Thank you for allowing us to participate in %%GSoC%% over the years.  It has been an honor to have mentored nearly 100 students and we've produced both some excellent code and some new contributors both of which have helped move the project in useful directions. Thank you for allowing us to participate in %%GSoC%% over the years.  It has been an honor to have mentored nearly 100 students and we've produced both some excellent code and some new contributors both of which have helped move the project in useful directions.
  
  • summerofcode2011application.1299206229.txt.gz
  • Last modified: 2011/03/04 02:37
  • by BrooksDavis