4 This page shall serve as a common place to look if you're in search of a DragonFly related project. It's also the place to check if someone else is already working on it (to prevent project collision) or should be contacted.
15 * Correct [mailing lists page](http://www.dragonflybsd.org/community/mail.cgi) and [news page](http://www.dragonflybsd.org/community/news.cgi) to better describe the content of each list.
18 * Create layout for http://bugs.dragonflybsd.org that matches the main site.
21 * Check through all the [DragonFly mirrors](http://www.dragonflybsd.org/community/download.cgi) and report on any that aren't working
24 * Create short list of tasks for a new DragonFly user (this information is all available elsewhere, but it's buried in a lot of other data):
27 * how to upgrade the operating system
30 * how to get to a working desktop
33 * and where and how to report issues.
37 ## Documentation projects
40 * Check all chapters of the handbook and do the following:
43 * Check if the content applies to DragonFly. If not, change it.
46 * Add new content and enhance the previous chapters
49 * Check for syntax error, typos and wiki errors.
52 * Add prev/next buttons to all pages.
55 * Reorder `/usr/src/UPDATING` to put more relevant information at top; remove data no longer relevant.
58 * Help out in http://bugs.dragonflybsd.org (try to reproduce, diagnose, propose fixes ...)
61 * Organize, contribute to, and finish the C book project.
68 * Bring in BSD-licensed versions of some text tools like `grep`, `diff` and `sort`. The Open***BSD guys already did some work related to that. If you manage to bring the tools to DragonFly, check if everything works as expected (e.g. rc.d scripts, make world runs, ...). Of course the new tools need to have at least all the features of the old GNU tools.
71 * Update the [contributed software](ContribSoftware) which is out-of-date.
74 * Remove `NOINET6` build option
77 * `WARN` corrections to utilities
80 * Clean our code to make it [style(9)](http://leaf.dragonflybsd.org/cgi/web-man?command#style§ionANY) compatible. Compile and test your changes. Verify that the checksum (sha(1)) of the unmodified object matches the checksum of the cleaned object. Check also with strip(1)+sha(1)
83 * Bring in code from other *BSDs:
86 * smbfs changes from FreeBSD
89 * pf changes from OpenBSD
92 * Randomize mmap() offsets as described in http://www.openbsd.org/papers/ven05-deraadt/index.html
95 * Add extended slice support to `fdisk`
98 * Install Coverity and fix the FreeBSD bugs that were uncovered by Coverity, but do not just blindly pull over the FreeBSD patches. Make sure that you first understand what the patch does.
101 * C99 Standards Conformance. The todo list is on http://wiki.dragonflybsd.org/index.cgi/StandardsConformanceProject (original http://www.in-nomine.org/~asmodai/df/conformance/).
104 * Setup a regression testing machine/system to register and find problems and new improvements..
107 * Networking performance scalability
110 * scalability (algorithmic performance) - ideas: http://bulk.fefe.de/scalability/ and http://bulk.fefe.de/lk2006/talk.pdf
116 * also check HowToStressTest
119 * Add lwp support to ptrace/gdb/core dumps.
125 * Linuxulator update (Free***BSD did a lot of work in this area. Look [here](http://wiki.freebsd.org/linux-kernel),
128 * Bringing in version 2.0 of the BSD Installer
131 * Build a Live CD with a DragonFly-specific X desktop, integrated into nrelease build. Check ongoing LiveDVD project: [LiveDVD for Google SoC](LiveDVDGSoC)
134 * UTF8 support in the console
137 * Write a tool to monitor changes in other code bases such as FreeBSD, NetBSD, OpenBSD. corecode is busy with this one (http://oly.corecode.ath.cx/~corecode/cgi-bin/crosscgi.py) (svn repository (https://fortunaty.net/svn/crossref/)).
143 * ptrace/gdb follow-fork-mode support and more (peek at linux)
146 * Change the build to create one libbfd for gdb and binutils
149 * Separate RPC code from NFS into separate library.
156 * Make our sound system support surround sound
159 * Port the BSDL OSS code to DragonFly
162 * Complete Path MTU Discovery by adding a host route to remember the Path MTU and setting a timer to expire old host routes. See netinet/if_ether.c for an example of this mechanism as used by ARP. Periodically increase MTU of hosts that have had its MTU decreased.
165 * Look for places in the kernel that can benefit from Solaris-style caching of preconstructed slab allocator objects. If we can find enough of these uses, we can add this functionality to the kernel memory allocator.
168 * Implement `sem_open()`, `sem_close()`, and `sem_unlink()`.
171 * Clean our code to make it [style(9)](http://leaf.dragonflybsd.org/cgi/web-man?command#style§ionANY) compatible. Compile and test your changes. Verify that the checksum (sha(1)) of the unmodified object matches the checksum of the cleaned object. Check also with strip(1)+sha(1)
174 * Setup a regression testing machine/system to register and find problems and new improvements..
177 * Networking performance scalability
180 * scalability (algorithmic performance) - ideas: http://bulk.fefe.de/scalability/ and http://bulk.fefe.de/lk2006/talk.pdf
186 * also check HowToStressTest
189 * fix `APIC_IO` on SMP
192 * Port drivers from other systems. (Being able to support most of the wireless adapters out there would be nice.)
195 * Port TMPFS. Look [here](http://wiki.freebsd.org/TMPFS) for the work the Free***BSD guys did.
198 * Port ZFS. Look [here](http://wiki.freebsd.org/ZFS) for the work the Free***BSD guys did.
201 * Port NFSv4. [This mail](http://leaf.dragonflybsd.org/mailarchive/kernel/2008-01/msg00065.html) is a good starting point.
204 * Port/sync the following from FreeBSD:
207 * PCI code (to take advantage of power saving features)
213 * netgraph modules. Contact joerg.
216 * Bring in support for UFS2, just the changes to extend the width of some fields from 32 bits to 64 bits.
222 * Port/sync the following from OpenBSD:
225 * Add support for the NoExecute bit as described in http://www.openbsd.org/papers/auug04/index.html.
228 * After that, make user stacks and data heaps non-executable. (W^X)
231 * hardware drivers, specially wireless.
234 * Import/Update DRM from the DRM git repository (http://dri.freedesktop.org/wiki/DRM).
237 * CPU scheduler work:
240 * Design & implement a run-time switchable scheduler framework. (see Luigi's FreeBSD4 scheduler framework at http://info.iet.unipi.it/~luigi/ps_sched.20020719a.diff)
243 * The next step is to add a Solaris-like dispatcher framework that can handle more than one installed scheduling policy, all running on top of the base fixed lwkt priorities.
246 * I/O scheduler work:
249 * factor out, and make the IO scheduler plugabble.
252 * start with a "NOP" scheduler for RAM based devices
255 * implement a anticipatory scheduler (see documentation about the linux anticipatory scheduller)
258 * implement a Fair Queuing scheduler (even out the access to IO between competing processes/users)
261 * Work relating LWKT (LightWeightKernelThreading)
264 * Implement lazy IPI cross-processor lwkt message passing.
267 * Add timeout functionality to lwkt_waitmsg().
270 * Write man pages for the lwkt message passing API.
273 * A real slab allocator. Contact corecode for patches.
276 * clean up buildworld/kernel compilation warnings
279 * Make the kernel more robust. Do this by removing any cases causing a kernel panic on memory allocation failure. Contact Devon H. O'Dell for information and ideas about how this might work.
282 * Port XFS. (Contact joerg)
285 * Computer Architecture related:
288 * Port DragonFly over to Xen.
291 * Port DragonFly over to amd64 (look [here](http://www.dragonflybsd.org/cgi-bin/cvsweb.cgi/src/README.amd64) for more information).
300 * Xen support as domU and dom0 platform
303 * DistributedFileSystem
307 [[SimonsTODOs]] contain some more or less important things of various sizes and colors