utility." cperciva acts as technical contact for the freebsd-update part of
the project, but it would be nice to have someone with experience from
writing GNOME/KDE applications as a technical contact/mentor as well.
Submitted by: cperciva, kris
extract ideas from the ideas list which include the class='soc'
attribute. Display the title of those projects which are deemed
suitable for summer of code projects and then link to the ideas page
for the full description, technical contacts, requirements, etc.
source and extract and display the projects listed here in multiple
ways. For example, those projects that are suitable for summer of
code can be designated with an attribute and then extracted to
automatically be displayed on the summer of code pages, so that we
only have to maintain one list instead of two.
Correct a typo in one of the idea descriptions while here.
Suggested by: rwatson
Discussed with: joel
- Port OpenBSD's sensors framework
- lint(1) improvements from OpenBSD
- Port prebind from OpenBSD
- Add hashed .db support to pkg_tools
Submitted by: netchild [1-3]
Submitted by: kris [4]
projects (based on discussions with netchild and rwatson):
- AutoFS: Adam Martin has been working on this since Google SoC 2006 and it
looks like we will see an implementation announced soon.
- Magic symlinks: Several implementations exists, so we don't need more
people looking at this right now.
- Tarfs: Eric Anderson is already working on this in p4.
- ZFS: No need to have this here, pjd has been hacking on ZFS for FreeBSD
for quite some time now.
- Cam layer locking: My understanding is that scottl is about to commit
his locking work to CVS soon.
- FPU subsystem overhaul: Not suitable as a Google SoC project.
- Linuxulator: We already have several committers (netchild, jkim, kib)
and past SoC students (Roman Divacky) working on this, so remove it
from the list.
- Process Checkpointing: Not suitable as a Google SoC project.
- Flight mode: Does not belong on the list. benjsc has implemented
this functionality (not yet committed though).
- Zeroconf: Already available on the Networking wiki page.
- NSS/LDAP/HESIOD/NIS/YP: Michael Bushkov did this as part of
Google SoC 2006 so this isn't suitable for Google SoC 2007. Not
committed yet.
More to come...
can help pjd with here, but they need to contact him first. We need to
decide if this item should still be on the TODO list.
Note that jb's work on dtrace is a significant work-in-progress so to
contact him. Does this need to be a todo item?
Note that the "use floating point in kernel rah rah rah" item requires
experimental validation -- the task isn't to hack code, but to decide if
the hacked code was a good idea. Does this need to be a todo item?
Note that the DFBSD process checkpointing facility is both experimental and
incomplete. Another "Don't just port this" sort of thing. Do we want this
to be a todo item?
In the Linuxulator update task, note that Roman is doing this. Do we need
this todo item anymore?
Add fine-grained locking to syscons task. Some of the items in this idea
are silly.
Note that the PXE HTTP idea requires someone to implement TCP in pxeboot,
add networking experience on the requirements list.
Add gnn to the TCP/IP regression suite idea, as he's working on such a
thing.
Make it clear in the distributed audit daemon task that portable C coding
is required.
+ Add a link to Unix System Administration course from OSU,
which would be useful for newbies as well.
Submitted by: James Marshall Brannan <marshall brannan gmail com>
