1.1.1. Use and improve the docs

Verbose mode:

• Search the documentation first and read the FAQ before asking questions.
• When asking questions, update the documentation when you get the answers.
  When answering questions, please reference the docs/FAQs/etc. This will increase the visibility (and maybe overall usage) a valuable resource.
• Those who complain about the documentation, update its pages to make it better.

1.1.2. Report bugs or feature enhancement requests

Verbose mode:

• A bug only exists if it's reported in the bugtracker
• When in doubt, file a bug report or request a feature/enhancement in the bugtracker
• If you can't code yourself your own enhancement ideas, don't expect that your request will be implemented in short, if ever. You might be interested in hiring a coder to do that for you, if you think that things are getting done much more slowly than you would need/like.

1.2.1. Preserve Environment

Tikiwiki is both software and a community. The mix of both, contextualized in the Internet and the real life, is called The Environment. Any change in Tikiwiki should take in account its effect on the entire Tiki community and should allow for a balanced evolution with respect for the humans that use it. Please make sure any code you commit respects the LGPL license and that you allowed to share it.

1.2.2. Commit early, Commit often

CVS (<1.9) and SVN (>1.10) are the central points in tikiwiki collaborative development. Commits should be frequent, even in the early stages, to offer an opportunity of interaction between contributors. Early commits provide more chances for feedback and for the community to start to assimilate the ideas you propose

1.2.3. Make it Optional

Tikiwiki is used in many smaller contexts and its modularity is key to adoption in those areas. Help preserve this flexibility by making your changes optional whenever possible, accessible for tuning to the admin at least, via admin panels.