From: justin Date: Fri, 29 Oct 2010 02:19:43 +0000 (-0700) Subject: Adding Google Code-In tags X-Git-Url: https://gitweb.dragonflybsd.org/ikiwiki.git/commitdiff_plain/b1b401e0e2d8dd273860bba6c698e72635233a80 Adding Google Code-In tags --- diff --git a/docs/developer/ProjectsPage.mdwn b/docs/developer/ProjectsPage.mdwn index 0cf932ac..91ae343f 100644 --- a/docs/developer/ProjectsPage.mdwn +++ b/docs/developer/ProjectsPage.mdwn @@ -2,25 +2,28 @@ 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. +Projects that can be clearly used for Google Code-In are marked with their category, where applicable. Some unmarked items may be eligible; it depends on how the student wants to tackle the project. + [[!toc levels=3 ]] ## Website projects ### One-liners -* Add traffic report, especially to lists requests that cause 404s -* Add the mail archive to the search index -* Download link right on the main page. +* Add traffic report, especially to lists requests that cause 404s (GCI:Research) +* Add the mail archive to the search index (GCI:Documentation) +* Download link right on the main page. * Fix RSS feed to have correct links -* Create layout for http://bugs.dragonflybsd.org that matches the main site. +* Create layout for http://bugs.dragonflybsd.org that matches the main site. (GCI:User Interface) * Create short list of tasks for a new DragonFly user -* how to upgrade the operating system -* how to get to a working desktop -* and where and how to report issues. +* How to upgrade the operating system (GCI:Training) +* How to get to a working desktop (GCI:Training) +* and where and how to report issues.(GCI:Documentation) ### Post papers in the proper locations on the website * Format conversion may be necessary * Aggelos's papers from [http://leaf.dragonflybsd.org/~aggelos/] (http://leaf.dragonflybsd.org/~aggelos/) (netmp-paper.pdf and netmp.pdf) to Presentations * ["A Peek at the vKernel" article](http://cvsweb.dragonflybsd.org/cvsweb/site/data/docs/articles/vkernel/vkernel.shtml?rev=1.3&content-type=text/x-cvsweb-markup) from old site +(GCI:Documentation) ## Documentation projects @@ -32,40 +35,41 @@ This page shall serve as a common place to look if you're in search of a DragonF ### Handbook maintenance * Check if the content applies to DragonFly. If not, change it. * Add new content and enhance the previous chapters -* Check for syntax error, typos and wiki errors. -* Add prev/next buttons to all pages. +* Check for syntax error, typos and wiki errors. +* Add prev/next buttons to all pages. (GCI:User Interface) + ### Write manpages -* sysref +* sysref (GCI:Documentation or Research) ## Userland projects ### One-liners * Update the [[contributed software|docs/user/ContribSoftware]] which is out-of-date. * Remove `NOINET6` build option -* `WARN` corrections to utilities +* `WARN` corrections to utilities (GCI:Code) * Bring in code from other *BSDs: -* smbfs changes from FreeBSD +* smbfs changes from FreeBSD (GCI:Code) * Add extended slice support to `fdisk` * 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. -* C99 Standards Conformance. The todo list is on [[/docs/developer/StandardsConformanceProject]] -* Setup a regression testing machine/system to register and find problems and new improvements.. -* Networking performance / scalability -* [[RegressionTest|/docs/developer/RegressionTest]] -* also check [[HowToStressTest|/docs/developer/HowToStressTest]] +* C99 Standards Conformance. The todo list is on [[/docs/developer/StandardsConformanceProject]] (GCI:Code) +* Setup a regression testing machine/system to register and find problems and new improvements. (GCI:Quality Assurance) +* Networking performance / scalability ((GCI:Research) +* [[RegressionTest|/docs/developer/RegressionTest]] (GCI:Research) +* also check [[HowToStressTest|/docs/developer/HowToStressTest]] (GCI:Research) * Add lwp support to ptrace/gdb/core dumps. * Bringing in version 2.0 of the BSD Installer * UTF8 support in the console -### Scalability (algorithmic performance) -* [http://bulk.fefe.de/scalability/](http://bulk.fefe.de/scalability/) +### Scalability (algorithmic performance) (GCI:Research) +* [http://bulk.fefe.de/scalability/](http://bulk.fefe.de/scalability/) * [http://bulk.fefe.de/lk2006/talk.pdf](http://bulk.fefe.de/lk2006/talk.pdf) -### Clean our code to make it [style(9)](http://leaf.dragonflybsd.org/cgi/web-man?command#style§ionANY) compatible. +### Clean our code to make it [style(9)](http://leaf.dragonflybsd.org/cgi/web-man?command#style§ionANY) compatible. (GCI:Code) * 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) +* Verify that the checksum (sha(1)) of the unmodified object matches the checksum of the cleaned object. Check also with strip(1)+sha(1) -### Port BSD-licensed tools (ex: `grep`, `diff` and `sort`) +### Port BSD-licensed tools (ex: `grep`, `diff` and `sort`) (GCI:Code) * The OpenBSD 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, ...). * The new tools need to have at least all the features of the old GNU tools. @@ -86,17 +90,17 @@ This page shall serve as a common place to look if you're in search of a DragonF * Add to natacontrol (see NetBSD's atactl?) * Add to camcontrol -### Disk scheduling rc scripts +### Disk scheduling rc scripts (GCI:Code) * Create a rc script to manage the disk/io scheduling system * Perhaps 1 entry to "enable" it, and all disks will have mode set to "auto", in auto mode smart inquiries and other heuristics could attempt to determine the best i/o scheduler * Per-device and device class or similar defaults should be definable in rc.conf also * The bulk of this functionality could be implemented in a resurrected "dschedctl" utility and exposed through the rc interface using just a thin wrapper, allowing hotplug scripts and etc. an easier option to use the same facilities. -### Add usage() to vkernels +### Add usage() to vkernels (GCI:Code) * Most userspace applications have a (traditionally) usage() routine which prints helpful information when passed -h or -? or any unknown command line argument or incorrect syntax. * Add a usage() to the vkernel's argument parsing. -### libHAMMER +### libHAMMER * HAMMER has the capability to expose very rich information to userland through ioctl's. * Currently the hammer(8) utility makes use of this information in an ad-hoc manner. * Port this core functionality into a public libhammer library so that other base and third party utilities may take advantage of it. @@ -107,9 +111,9 @@ This page shall serve as a common place to look if you're in search of a DragonF * Port the BSDL OSS code to DragonFly * 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. * 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. -* Implement [`sem_open()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_open.html), [`sem_close()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_close.html), and [`sem_unlink()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_unlink.html). +* Implement [`sem_open()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_open.html), [`sem_close()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_close.html), and [`sem_unlink()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_unlink.html). (GCI:Code) * 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) -* Setup a regression testing machine/system to register and find problems and new improvements.. +* Setup a regression testing machine/system to register and find problems and new improvements. (GCI:Research) * Port or update drivers from other systems. * Port NFSv4. [This mail](http://leaf.dragonflybsd.org/mailarchive/kernel/2008-01/msg00065.html) is a good starting point. * clean up buildworld/kernel compilation warnings @@ -118,8 +122,8 @@ This page shall serve as a common place to look if you're in search of a DragonF ### Code to port/sync from FreeBSD * PCI code (to take advantage of power saving features) -* Bring in support for UFS2, just the changes to extend the width of some fields from 32 bits to 64 bits. -* hardware drivers. +* Bring in support for UFS2, just the changes to extend the width of some fields from 32 bits to 64 bits. (GCI:Code) +* hardware drivers. ### Code to port/sync from OpenBSD * Add support for the NoExecute bit as described in [http://www.openbsd.org/papers/auug04/index.html](http://www.openbsd.org/papers/auug04/index.html). @@ -134,7 +138,7 @@ This page shall serve as a common place to look if you're in search of a DragonF * A pluggable kernel I/O scheduler already exists * Implement additional disk scheduling policies -### Modify firmware framework +### Modify firmware framework * We currently use the firmware(9) FreeBSD also uses * It would be more appropriate to avoid future problems with redistribution problems, etc, to adapt the wifi firmware stuff to use the firmware(9) we used to have before, which was able to load firmware files from userland (/etc/firmware). * See "firmware discussion" thread on kernel@ mailing list, March-May 2010. @@ -179,7 +183,7 @@ This page shall serve as a common place to look if you're in search of a DragonF * This can be very easy, or can be very unwieldy * Convert all of these cases to ktr's, while slightly less easy they are far easier to wield in all cases. -### Tear out C/H/S disk reporting +### Tear out C/H/S disk reporting (GCI:Research) * Cylinders/Heads/Sectors are an outdated concept and the system doesn't rely on them anymore. * Verify the assumption that we don't rely on them in any way, shape or form. * Tear the reporting out of the kernel/installer/etc.