- Find a role.
- Suggest a translation.
- Help with the documentation.
- Help other users on the forums.
- Send a bugfix/patch.
- Test bug reports to confirm they are valid .
- Tell people why you like Tiki. (Have you seen Why Use Tiki?)
- Hang out on IRC and help people.
- Make a new theme.
- Suggest ideas for a new theme (at the Themes forum).
- Recommend Tiki to people as a solution, if appropriate (check Features and update their ratings).
- Respond (calmly) to unfounded/uninformed criticisms of Tiki.
- Participate at Tiki sites that are inviting members.
- Suggest ways to improve Tiki.
- Vote for Tiki.
- Become a regular code contributor.
- Help financially and donate to the Tiki Software Community Association.
Community members do their best to follow Tiki Social Contract.
Others expect you to read understand and do your best to follow the Tiki Social Contract.
In addition you are requested to follow these basic rules within Tiki Community:
- 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 complain about the documentation are welcome to update its pages to make it better.
- Report bugs or feature enhancement requests
- A bug only exists on record if it's reported in the bugtracker.
- When in doubt, file a bug report or request a feature/enhancement at http://dev.tiki.org/Make-a-wish.
- 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.
Please also see: How to Contribute to Open Source Without Coding
The traditional basic 3 rules for developers
- Respect Environment
- Commit early, Commit often
- Make it Optional