This page should give some ideas of how you can contribute to the WackoWiki project.
I get the question of “Where should I start?” fairly often and my advice is just don’t even ask that question. It’s more like if you’re not interested enough in one particular area that you already know what you want to try to do, don’t do it. Just let it go and then when you hit something where you say, “I could do this better” and you actually feel motivated enough that you go from saying that to doing that, you will have answered that question yourself. — Linus Torvalds
1. you are a ...
- Contribute ideas
- Give feedback
- Translate the documentation to your language -> /Doc
- Translate message sets to your language -> /Dev/Translations
- Share your theme -> /Dev/Themes
WackoWiki is an open source project, which means that the program is maintained and developed by volunteers. If you're interested in contributing work to the project, see our developer page for further information on how you may contribute.
You can help with the development of the engine by using and testing the development version and providing patches for bugfixes, minor enhancements and documentation.
- Sign up in our development infrastructure
- Download and test the last development release
- Checkout the latest code
- Create bug patches
- Create feature patches
- Contribute new functionality
- Contribute how-tos to our blog
- Contribute to the community Wiki
Fork it, fix it, we'll pull it
Go wild, fork the project, and prove your point. Show everybody that you can make improvements.
There are couple of preferred ways to submit your changes for inclusion:
- pull request from your personal clone
- Mercurial bundle files
- patch files – in Mercurial patch format to keep the author info etc.
Pull request from your personal clone (in Bitbucket or other public server) is the easiest and fastest way to get your changes included.
WackoWiki recognizes contributions from volunteers by adding their names to the list of contributors in the release notes for each version and in the Team page.
2. Reporting Bugs
Report every single bug that you encounter or know about into our bugs system.
If the bug is already reported, please add a comment to the bug report that it affects you too.
Giving us more information about which bugs are really important for us to fix. More information will help us make better decisions about how and when a bug should be fixed.
Anonymous users may
Registered users may
- create tickets (bug reports or enhancement requests)
- add comments to existing tickets
- edit the wiki
3. Institutional Involvement
Organizations can play an active role in the community by sponsoring the project.