An update on our Google Code-In progress, the documentation tasks that are not code-related are still decidedly unpopular. The most popular tasks seem to be those that involve some coding, several fairly complicated projects have been done by students so far.
The available tasks: doc: Improve the wlan(4) manpage doc: Update Chapter 13 of the old handbook doc: Update Chapter 14 of the old handbook doc: Update Chapter 17 of the old handbook doc: Update Chapter 18 of the old handbook doc: Update Chapter 19 of the old handbook doc: Update Chapter 20 of the old handbook doc: Update Chapter 21 of the old handbook doc: Update Chapter 22 of the old handbook doc: Update Chapter 25 of the old handbook code: make du(1) show space used by historical data on the HAMMER filesystem Release benchmarking Document upgrading Tear out C/H/S disk reporting doc: Write some handbook entries on the device mapper (dm), lvm, cryptsetup, crypttab and initrd code: Change the display of iostat(8) Research: find out what functionality is missing in our udev/libdevattr to get Linux' applications using libudev to work How-To SAMBA Server Create a basic setup screencast Create a vkernel screencast Create a HAMMER screencast Document Hammer recovery Fix a compilation or runtime bug of a popular piece of open source software and submit a patch upstream Fix a compilation or runtime bug of a popular piece of open source software and submit a patch upstream Fix a compilation or runtime bug of a popular piece of open source software and submit a patch upstream Completed tasks: kernel/code: Convert struct klist from an SLIST to a TAILQ (Part 1) kernel/code: Convert struct klist from an SLIST to a TAILQ (Part 2) doc: Write an EXAMPLES section for the setitimer(2) manpage doc: Write an EXAMPLES section for the getsockopt(2)/setsockopt(2) manpage(s) doc: Write an EXAMPLES section for the socket(2)/accept(2)/bind(2)/connect(2) manpage(s) doc: Write an EXAMPLES section for the sendfile(2) manpage doc: Write an EXAMPLES section for the writev(2) manpage doc: Write an EXAMPLES section for the select(2) manpage doc: Write an EXAMPLES section for the poll(2) manpage doc: Write an EXAMPLES section for the fork(2) manpage doc: Write an EXAMPLES section for the send(2)/recv(2) manpage(s) doc: Write an EXAMPLES section for the mmap(2) manpage doc: Write an EXAMPLES section for the setjmp(3)/longmp(3) manpage(s) doc: Write an EXAMPLES section for the dladdr(3)/dlinfo(3)/dlopen(3) manpage(s) doc: Write an EXAMPLES section for the directory(3)/scandir(3) manpage(s) doc: Write an EXAMPLES section for the ucontext(3)/makecontext(3)/getcontext(3)/setcontext(3) manpage(s) doc: Write an EXAMPLES section for the msgctl(3)/msgget(3)/msgrcv(3)/msgsnd(3) manpage(s) doc: Write an EXAMPLES section for the glob(3) manpage(s) doc: Write an EXAMPLES section for the popen(3)/system(3) manpage(s) doc: Write an EXAMPLES section for the exec(3) manpage(s) doc: Write an EXAMPLES section for the tree(3) manpage(s) code: make hammer iostats display humanized output bugs.dragonflybsd.org layout Get to the desktop Regression test code: write a devattr tool code: write a libfsid code: Add usage() to vkernels doc/research: Describe all lwkt.* sysctl's that lack a description doc/research: Describe all debug.* sysctl's that lack a description doc/research: Describe all net.inet6.* sysctl's that lack a description doc/research: Describe all net.inet.* and net.local.* sysctl's that lack a description doc/research: Describe many vfs.* sysctl's that lack a description doc/research: Describe all vfs.nfs.* sysctl's that lack a description doc/research: Describe all vfs.hammer.* sysctl's that lack a description doc/research: Describe all vm.stats.* sysctl's that lack a description doc/research: Describe all kern.ipc.* sysctl's that lack a description code: Change default password hashing from md5 to SHA2 Create an installation video Porting FTP server documentation About half of these completed tasks are already committed, and most of the rest will be committed within the next several weeks. As you can see, our numbers of available tasks is dwindling to the point that almost all of those that are left are those larger documentation wrangling projects that have proven wholly unpopular. If you can think of anything applicable that needs doing please speak up so it can be added to the list. Best, Sam