Standards for Hacks

Oooo, sounds all official and everything, eh? Well, right now, it’s not. As part of the documentation effort, and the overall effort to create a great product like WordPress and to add value to WP through extensions, hacks, mods, plug-ins, or whatever you choose to call them, I have some proposals for discussion purposes. For the sake of making this post less wordy, I’m going to call everything a “mod.”
Items which are already defined by the developers:
1. Coding style rules have been published and all mods must adhere to this style.
2. Refer to the Hack Guidelines for other information.
My proposals:
3. All coding must validate to the minimum XHTML standard that WP validates to, and that is XHTML Transitional.
4. Unless otherwise stated by the developers, individual mod support falls on the mod developer with the help of the WP community members who are willing and able to help.
5. Mods must be documented fully, including date, author, version number, target WP version, and mod Title. Instructions should be included on how to install and implement the code. The documentation should also include a listing of the features the mod offers. What I am looking for here is a mod product that would stand up to the standard which WP will be setting for itself.
6. It would be desirable to have mod authors host a page on their own sites where community members could obtain the necessary code and documentation.
7. WordPress is published under the GNU General Public License and authors of all mods should document fully what copyright restrictions they wish to place on the code submitted as mods.
I think that this is basically it, in terms of documentation stuff. I invite your comments and ideas. Thanks…
Craig.