This is an old revision of the document!

This is a DRAFT of our Summer of Code 2009 application to be submitted at http://socghop.appspot.com/org_app/apply/google/gsoc2009 once application open.

If you aren't a SoC admin, please contact soc-admins@freebsd.org with comments rather than editing this directly.

• Link ID: freebsd
• Group Name: FreeBSD
• Home Page URL: http://www.freebsd.org/
• Public Email: soc-admins@freebsd.org
• Description
  • The FreeBSD Project is a large, mature, and yet relatively tightly knit organization. The FreeBSD Project began 15 years ago in 1993, but is based on the work at Berkeley CSRG with open source revision history going back 30 years to 1978. There are currently over 300 developers with write access to the main revision control system, and hundreds more with access to our Perforce servers for experimental and third party development (this is also where our summer of code students have worked in previous years). We have an active mentoring program to bring all new developers into our community, not just those that we introduce to FreeBSD through the GSoC. There are hundreds of mailing lists, forums, blogs, IRC channels, and user groups all detailed on our main website. FreeBSD offers a complete operating system in which students can work, not just a kernel or specific userland stack. This allows for interesting work that spans the userland/kernel boundary. In addition, FreeBSD has incubated the development of key pieces of infrastructure which are used by other open source projects including jemalloc, libarchive, and OpenBSM.

• Why is your group applying to participate? What do you hope to gain by participating?
  • First and formost, we hope to gain new developers for FreeBSD. Since we judge community members both on technical ability and ability to collaborate, GSoC offers an execellent form of introduction and evaluation. Secondly, we hope to gain new and improved functionality and a result of student contributions. Third, be participating in GSoC we increase our exposure to students and academia in general. Even student's who look at FreeBSD, but choose to apply to other projects will learn something about what FreeBSD is.

• What is the main public mailing list for your group?
  • FreeBSD has many mailing lists, hackers@FreeBSD.org is our largest, general development discussion list. questions@FreeBSD.org handles countless user questions.
  • XXX Submitted a bug about this one http://code.google.com/p/soc/issues/detail?id=297

• Where is the main IRC channel for your group?: N/A

• What criteria do you use to select the members of your group? Please be as specific as possible.
  • FreeBSD committers are selected based their technical contributions and their ability to work well with the project. Typically a contributer submits too many good changes and someone who has been working with them sponsors them for commit access. For source committers, the core team evaluates both their technical record and their record of interaction with the community through their own experience and the application submitted by the sponsor. In general we look for both technical and social maturity (we bring in a number of younger committers, but our average age is over 30). The portmgr and doceng teams perform similar functions for the ports collection and documentation projects respectively. In certain circumstances, community members who have performed extraordinary services to the project over time are also granted access to internal mailing lists.

• Has your group participated previously? If so, please summarize your involvement and any past successes and failures.
  • The FreeBSD project has participated in the Google Summer of Code since it's inception. We have had a total of XXX students XXX of whom have passed. Of those XXX have become committers and the work of many others has been incorporated into the FreeBSD source and ports trees.

• If your group has not previously participated, have you applied in the past? If so, for what sort of participation?: N/A

• What license does your organization use?: New and Simplified BSD licenses

• What is the URL to the ideas list of your organization?: http://www.freebsd.org/projects/ideas/

• What is the main development mailing list for your group?: hackers@freebsd.org

• What is the application template you would like contributors to your organization to use.: SummerOfCode2009Template (XXX: Finish this)

• What is your plan for dealing with disappearing contributors?
  • The first line of defense against disappearing contributeres will be regular, mandatory status reports. We aim to have students send status reports to a central list where they can help each other and mentors and other interested developers can keep tabs on them. Along with this we will require each contributor to negotiate a detailed specification of their work schedule with their mentor which will be provided to program administrators. We will uses this combination to detect problems. If problems appear to be occurring we will attempt to contact the contributors. If they can not be contacted in a reasonable period or do not have an acceptable explanation we will cut our losses and cease contact.

• What is your plan for dealing with disappearing members?
  • As with contributors, 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.

• What steps will you take to encourage contributors to interact with your 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.

• What will you do to ensure that your accepted contributors stick with the project after the program 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.

• Please select your backup group administrator (link_id): XXX: who is this going to be?