That's exactly the kind of stuff I had in mind. Something like a "contributor's guide". Ken Perry writes: > It would also be nice if someone created a short documentation with > steps of what maintainers want for changes like table changes. Also > what maintainers want for changes in the c code. For example a small > document showing a table change,, what words it was for, example test > cases added to the automated tests for the change, and anything else > you guys are expecting like the news change. . This should be laid > out in a step by step example form so that we can just follow it and > make your job easier in that you would just have to read through the > commit log and if all steps were followed accept it. For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com