1.1.1. Use and improve the docs

• 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 have complaints about the documentation are encouraged to update its pages to improve it.

1.1.2. Report bugs or request feature enhancements

• 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 your own enhancement idea, it probably isn't realistic to think that it will be implemented unless it is generally recognized as a significant enhancement, or at least so recognized by a person who does have the skills to implement it. You might be interested in hiring a coder to do the implementation for you, if you think things are taking longer than you would need/like.

1.2.1. Respect the Environment

Tiki is both software and a community. The mix of the two, in the context of the Internet and "real life", is called The Environment. Any change in Tiki should take into account its effect on the entire Tiki Community and should allow for a balanced evolution with respect for the people that use it. Also, please make sure any code you commit respects the LGPL license and that you are allowed to share it.

1.2.2. Commit Early, Commit Often

Tiki's Subversion (SVN) repository is the central point in Tiki collaborative development. Commits should be frequent, even in the early stages, to offer the opportunity for 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

Tiki 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, and able to be tuned by the site administrator at least, via admin panels.