Quality Control

Although the MiscKit administrator will compile and run your code to make sure it at least superficially appears to work, quality control is the responsibility of the submitter/maintainer of a MiscKit resource. Be sure to thoroughly test your code before you submit it. If code is untested, say so in the documentation so that people don't waste too much time scratching their heads when things are broken. It is preferred that you simply submit code that works, of course.

If your code generates warnings when compiled (or compile time errors) it will probably not be folded into the MiscKit until the warnings and/or errors are eliminated unless there is no reasonable way to do so and they are shown to be inconsequential to the functioning of your code. (In other words, a harmless warning that is impossible to get rid of is acceptable.) Remember that each warning requires an entry in the README.rtf explaining that it is an "OK" warning--and that file is too long already.