Update this page for Summer 2006:
* Add a new section on "Proposal Guidelines" borrowed heavily from the Perl Foundation open source proposal HOWTO. * Begin the example proposal ideas section with a pointer to the general ideas page as an additional source of projects that need developers. * Add 3 project ideas proposed by David Malone last year: inode versioning, ipv6 stack vulnerability audit, and ipv6 feature parity. * Add generic input device subsystem project proposed by philip. * Add gnn@ as a potential mentor for other unlisted networking projects. * Add ssouhlal@ as a potential mentor for other unlisted filesystem/vm projects. * Add a FAQ entry with a pointer to the summerofcode-2005.html page with last year's successful projects listed. Note that none of these projects are written in stone. If you think a particular project idea is bogus and shouldn't be worked on this summer please contact the proposed mentor.
This commit is contained in:
Murray Stokely
parent
c13ab6a014
commit
afe4105ca7
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=27515
1 changed files with 90 additions and 12 deletions
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
||||
<!ENTITY base CDATA "..">
|
||||
<!ENTITY date "$FreeBSD: www/en/projects/summerofcode.sgml,v 1.32 2005/09/29 11:13:18 joel Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/projects/summerofcode.sgml,v 1.33 2005/10/04 19:43:49 hrs Exp $">
|
||||
<!ENTITY title "FreeBSD Summer Projects">
|
||||
<!ENTITY % navincludes SYSTEM "../includes.navdevelopers.sgml"> %navincludes;
|
||||
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
|
||||
|
|
@ -12,7 +12,7 @@
|
|||
|
||||
<p>The FreeBSD Project is excited to take part in the Google <a
|
||||
href="http://code.google.com/summerofcode.html">Summer of Code
|
||||
2005</a>. This project endeavors to fund students to contribute to
|
||||
2006</a>. This project endeavors to fund students to contribute to
|
||||
an open source project over the summer break.</p>
|
||||
|
||||
<ul>
|
||||
|
|
@ -26,12 +26,17 @@
|
|||
</ul>
|
||||
</li>
|
||||
<li><a href="#mentors">Possible Mentors</a></li>
|
||||
<li><a href="#proposals">Proposal Guidelines</a></li>
|
||||
<li><a href="#faq">Frequently Asked Questions</a></li>
|
||||
</ul>
|
||||
|
||||
<a name="ideas"></a>
|
||||
<h2>Example Proposal Ideas</h2>
|
||||
|
||||
<p>In addition to the student project ideas listed below, the FreeBSD
|
||||
Project maintains a list of general projects looking for volunteers <a
|
||||
href="&base;/projects/ideas/index.html">here</a>.</p>
|
||||
|
||||
<a name="p-userland"></a>
|
||||
<h3>Userland / Installation Tools</h3>
|
||||
|
||||
|
|
@ -101,7 +106,7 @@
|
|||
the tests on, a database to store results in, and software to
|
||||
extract interesting results and display them. Solving the whole
|
||||
problems is probably beyond the scope of one summer's work, but an
|
||||
interesting subset should be managable. <a
|
||||
interesting subset should be manageable. <a
|
||||
href="mailto:brooks@FreeBSD.org">&a.brooks;</a> is the coordinator.</li>
|
||||
|
||||
</ul>
|
||||
|
|
@ -110,6 +115,13 @@
|
|||
<h3>Filesystem</h3>
|
||||
|
||||
<ul>
|
||||
<li><strong>inode versioning</strong>: Introduce an inode version
|
||||
number into UFS, so we can store inodes in different formats. As
|
||||
an example of how to use this, introduce a new inode format that
|
||||
has a 32 bit link count field. <a
|
||||
href="mailto:dwmalone@freebsd.org">&a.dwmalone;</a> is the
|
||||
coordinator.</li>
|
||||
|
||||
<li><strong>UFS Journaling</strong>: Add transaction journaling and
|
||||
playback to the UFS filesystem. The goal is to increase the reliability
|
||||
of the filesystem and greatly reduce the need for a full 'fsck' after
|
||||
|
|
@ -149,6 +161,19 @@
|
|||
<h3>Networking</h3>
|
||||
|
||||
<ul>
|
||||
|
||||
<li><strong>IPv6 stack vulnerabilities</strong>: Review the last few
|
||||
years worth of IP stack vulnerabilities. Check that these have been
|
||||
fixed in the IPv6 stack too. Fix ones that haven't been fixed. <a
|
||||
href="mailto:dwmalone@freebsd.org">&a.dwmalone;</a> is the
|
||||
coordinator.</li>
|
||||
|
||||
<li><strong>IPv6 feature parity</strong>: Review new features that
|
||||
have been added to the IP stack (hostcache, TCP MD5 checksums,
|
||||
...). Check if these include IPv6 support. Implement if it
|
||||
hasn't. <a href="mailto:dwmalone@freebsd.org">&a.dwmalone;</a> is
|
||||
the coordinator.</li>
|
||||
|
||||
<li><strong>Network Disk Device</strong>: Add the ability to
|
||||
remotely access devices from one system to another. The goal is
|
||||
to allow remote access to resources such as disks, sound devices,
|
||||
|
|
@ -272,6 +297,15 @@
|
|||
<h3>Kernel</h3>
|
||||
|
||||
<ul>
|
||||
|
||||
<li><strong>Generic Input Device Subsystem</strong>: Some work has
|
||||
been done in Perforce that begins to replace the ancient
|
||||
psm->moused->syscons codepath into something more pleasant.
|
||||
There's still a lot of duplication between psm and moused, however
|
||||
and even more work is necessary to get syscons to be happy with
|
||||
the new world order. <a
|
||||
href="mailto:philip@FreeBSD.org">&a.philip;</a> is coordinating.</li>
|
||||
|
||||
<li><strong>Update the Linuxulator</strong>: FreeBSD provides Linux
|
||||
binary compatibility through a Linux system call table that is
|
||||
invoked when Linux ELF binaries are executed. This implementation
|
||||
|
|
@ -352,10 +386,14 @@
|
|||
<ul>
|
||||
<li><strong>Networking</strong>:
|
||||
<a href="mailto:alfred@FreeBSD.org">&a.alfred;</a>,
|
||||
<a href="mailto:gnn@FreeBSD.org">&a.gnn;</a>,
|
||||
<a href="mailto:brooks@FreeBSD.org">&a.brooks;</a>, and
|
||||
<a href="mailto:sam@FreeBSD.org">&a.sam;</a></li>
|
||||
|
||||
<li><strong>Filesystems</strong>: <a
|
||||
href="mailto:scottl@FreeBSD.org">&a.scottl;</a>, <a href="mailto:alfred@FreeBSD.org">&a.alfred;</a></li>
|
||||
href="mailto:scottl@FreeBSD.org">&a.scottl;</a>, <a
|
||||
href="mailto:alfred@FreeBSD.org">&a.alfred;</a>, <a
|
||||
href="mailto:ssouhlal@FreeBSD.org">&a.ssouhlal;</a></li>
|
||||
<li><strong>GEOM</strong>: <a
|
||||
href="mailto:phk@FreeBSD.org">&a.phk;</a></li>
|
||||
<li><strong>Release Engineering / Integration</strong>: <a
|
||||
|
|
@ -367,13 +405,53 @@
|
|||
and <a href="mailto:bruno@FreeBSD.og">&a.bruno;</a>.</li>
|
||||
<li><strong>Sound</strong>: <a
|
||||
href="mailto:matk@FreeBSD.org">&a.matk;</a>.</li>
|
||||
<li><strong>Virtual Memory</strong>: <a
|
||||
href="mailto:ssouhlal@FreeBSD.og">&a.ssouhlal;</a>.</li>
|
||||
</ul>
|
||||
|
||||
|
||||
<p>If your project is not selected for funding by Google, but you
|
||||
still think you have a feasible project proposal, then please email
|
||||
<a href="mailto:proposals@FreeBSD.org">proposals@FreeBSD.org</a>.</p>
|
||||
|
||||
<a name="proposals"></a>
|
||||
<h2>Proposal Guidelines</h2>
|
||||
|
||||
<p>Students are responsible for writing a proposal and submitting it
|
||||
to Google before the application deadline. The following outline
|
||||
was adapted from the Perl Foundation <a
|
||||
href="http://www.perlfoundation.org/gc/grants/proposals.html">open
|
||||
source proposal HOWTO</a>. A strong proposal will include:</p>
|
||||
|
||||
|
||||
<ul>
|
||||
<li><strong>Name</strong></li>
|
||||
|
||||
<li><strong>Email</strong></li>
|
||||
|
||||
<li><strong>Project Title</strong></li>
|
||||
|
||||
<li><strong>Benefits to the FreeBSD Community</strong> - a good
|
||||
project will not just be fun to work on, but also generally
|
||||
useful to others.</li>
|
||||
|
||||
<li><strong>Deliverables</strong> - It is very important to list
|
||||
quantifiable results here e.g.
|
||||
<ul>
|
||||
<li>"Improve X modules in ways Y and Z."</li>
|
||||
<li>"Write 3 new man pages for the new interfaces."</li>
|
||||
<li>"Improve test coverage by writing X more unit/regression
|
||||
tests."</li>
|
||||
<li>"Improve performance in FOO by X%."</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li><strong>Project Schedule</strong> - How long will the project
|
||||
take? When can you begin work?</li>
|
||||
|
||||
<li><strong>Bio</strong> - Who are you? What makes you the best
|
||||
person to work on this project?</li>
|
||||
</ul>
|
||||
|
||||
<a name="faq"></a>
|
||||
<h2>Frequently Asked Questions</h2>
|
||||
|
||||
|
|
@ -384,16 +462,16 @@
|
|||
href="http://code.google.com/summfaq.html">Participant FAQ</a>
|
||||
for all questions about eligibility.</p></li>
|
||||
|
||||
<li><p><strong>How do I write a proposal?</strong></p>
|
||||
|
||||
<p>The Perl Foundation has a nice <a
|
||||
href="http://www.perlfoundation.org/gc/grants/proposals.html">HOWTO</a>
|
||||
that describes how to write an open source proposal.</p></li>
|
||||
|
||||
<li><p><strong>When is the proposal deadline?</strong></p>
|
||||
|
||||
<p>Proposals must be received by Google by June 14.</p></li>
|
||||
<p>Please check back soon for the proposal deadline.</p></li>
|
||||
|
||||
<li><p><strong>What projects were completed successfully by students
|
||||
last summer?</strong></p>
|
||||
|
||||
<p>Please see the <a href="summerofcode-2005.html">2005 FreeBSD
|
||||
Summer of Code</a> page for a list of the completed projects
|
||||
from last year.</p></li>
|
||||
</ul>
|
||||
|
||||
&footer;
|
||||
|
|
|
|||
Loading…
Reference in a new issue