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.
committed to CURRENT in a not so distant future.
- Remove the sync USB with NetBSD entry. An import of a new USB subsystem
will soon happen.
- Extend the linuxulator and regression test entries.
- Move includes.nav*.sgml to share/sgml/navibar.ent and
<lang>/share/sgml/nabibar.l10n.ent.
- Move includes.sgml and includes.xsl to
share/sgml/common.ent, share/sgml/header.ent, <lang>/share/sgml/l10n.ent,
and <lang>?share/sgml/header.l10n.ent.
- Move most of XSLT libraries to share/sgml/*.xsl and
<lang>/share/sgml/*.xsl.
- Move news.xml and other *.xml files for the similar purpose
to share/sgml/*.xml and <lang>/share/sgml/*.xml.
- Switch to use a custom DTD for HTML document. Now we use
"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension", which is
HTML 4.01 + some entities previously pulled via
"<!ENTITY % includes SYSTEM "includes.sgml"> %includes;" line.
The location of entity file will be resolved by using catalog file.
- Add DOCTYPE declearation to XML documents. This makes the followings
possible:
* Use of &foo; entities for SGML in an XML file instead of defining
{$foo} as the same content.
* &symbolic; entities for Latin characters.
- Duplicated information between SGML and XML, or English and
translated doc, has been removed as much as possible.
- Add technical contacts for the Build options and COMPAT_TTY projects. [2]
- Add links to several HDA patches. This will hopefully reduce some "where
are the HDA patches?" noise on the mailing lists.
Submitted by: Daniel O'Connor <doconnor@gsoft.com.au> [1]
Submitted by: Gardner Bell <gbell72@rogers.com> [2]
- Sort everything alphabetically.
- Adjust, fix, and clean up a lot of descriptions.
- Update outdated/obsolete information.
- Remove a few entries from the list.
- Add ZFS to the list.
