Since Caudium is a community effort, we will gladly accept patches, fixes, new modules and more. You can submit code using our SourceForge Patch manager. Even though it is titled as patch manager, you can also use it to submit new code. After submitting code, please send a mail to the general Caudium mailing list. We will look at your code and if it is valid and useful, we will commit it. For simplicity, you would have to agree that any code you submit becomes part of Caudium. You are also required to place any and all code under The GNU General Public License version 2 or later, and assign any and all copyrights to The Caudium Group. Please be assured that the license will never change from GPL - it is not even possible since Caudium is based on GPL code not copyrighted by The Caudium Group.

Documentation is a very important part of any major project, and sadly something open source projects often lack. Caudium is not an exception here. Although there are Roxen 1.3 docs that work well overall, we do need a lot of docs written. So if you are interested, let us know. Here are some examples on what needs to be done:

• Moving external tag documentation into the source code of the file defining the tag (source is in modules/tags/doc).
• Documentation of core functions, primarily well used API functions in files like caudiumlib.pike and cache.pike. The secondary goal is to document every core function in the server. The main reason behind this is to help developers to make modules and understand the core of the server. Also, a complete source documentation will help in cleaning up the code.
• Non-reference documentation with anything from basic administration and more advanced RXML examples to module programming. Other related documentation might include extending Pike with modules written in C and advanced Pike programming.
• HOWTO type documents on various subjects like building PHP for Caudium, converting from Apache etc.
• Checking existing documentation for spelling, grammatical and documentation errors.

If you are interested in helping with documentation, it is a good idea to discuss what you want to do on the mailing list. This way we can help avoiding duplicate work.