A number of ways to contribute to the cshampoo project are outlined below. For the most part, they are in order by difficulty. If you find another way to help that isn't listed below, don't hesitate to contribute. The list below is just an outline of some ideas to get people thinking. In any case, if you'd like to make a contribution, simply write an e-mail to one of the developers with a patch attached.


Every application can use more testing. We have a test suite to run unit tests, but it doesn't provide 100% code coverage. We'd happily accept patches that add new tests. We'd also like bug reports and suggestions for improving the Quality Assurance check list.


Well written documentation is crucial to any successful project. Without documentation, no one would know how to use the cshampoo APIs. Documentation that is up to date is also key. In many cases, out dated documentation is worse than no documentation at all. We'd welcome contributions of web site changes and Doxygen documentation.

Distribution Packagers

We'd be happy (and our users would be happy) if cshampoo packages were available for different distributions and operating systems. We'd be even happier if it was included in different distributions. We have a packaging guide to help potential packagers.

Porting to other Operating Systems

The development team doesn't have the time or resources to port cshampoo to every operating system known to man. We can aim for the free OSes that run on x86 hardware (GNU/Linux, FreeBSD, NetBSD, OpenBSD, OpenSolaris, etc), but we need help with the more exotic/esoteric systems out there (GNU/Hurd, IRIX, HP/UX, etc). For a list of supported operating systems, check out the requirements page.