summerofcode2011application

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
summerofcode2011application [2011/03/04 03:01] – BrooksDavissummerofcode2011application [2021/04/26 04:45] (current) – Use MailTo macros. JethroNederhof
Line 50: 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.
Line 58: Line 58:
  
 === 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 78: Line 78:
 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 84: 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%%.  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.+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.
  
 ==== 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.1299207699.txt.gz
  • Last modified: 2011/03/04 03:01
  • by BrooksDavis