Welcome to Tiki Developers!
Welcome to our developers wiki, where you will find useful information about being a Tiki contributor. Please, grab a seat and make yourself at home.
Contribution Pathways
Hey, we are glad you are here. We have several areas where you could help us depending on your skill set. Want to hear more about it? Let's go then!
Fixing bugs and contributing to new features
Awesome, that's perfect. Before heading over to coding, you need to understand how Tiki works. I'll quickly guide you through what you may find while contributing to Tiki, but in case you want a longer read, please visit TikiDevNewbie
- Connect with us
Like most open source communities, we have several ways of keeping in touch, however we mainly use IRC (irc.freenode.net, #tikiwiki) and Mailing Lists. These communication channels suffer from high latency, which means that answers may not come immediately. Please stick around and we'll get back to you.
- Be Proficient
The more you use Tiki, the better you know how it works. Set up a local instance, play with it. Head over to this local instance installation guide.
- SVN
If you never contributed to open source projects, this may be the hardest step for you. SVN is a way to control software versioning, so that we can have this decentralized infrastructure. You may use any SVN client that you prefer. Visit Commiting changes via SVN for further instructions.
- Know your PHP
Tiki is written in PHP, thus having prior knowledge on the language is a must. DevTips has most of the must know facts about being a developer in the Tiki project. Please follow our naming conventions, indentation, commit messages, etc.
- Get commit access
We at Tiki encourage everyone to commit directly into the tree. We don't have a process of sendind a patch and someone will apply it to the code base. With this comes big responsibilities. Test your code locally, ask for feedback on the mailing list or IRC, check which branch you should commit to, etc. Check out Getting commit access for more information.
- Documentation
Last but not least, document your code. While nobody expects you to write a huge documentation, please provide a few inline comments on source code. By doing so, you're helping others to understand what that piece of code is doing and also lowering the barrier for newcomers.
Report bugs, request features
That's great! The more people reportings bugs, the better Tiki gets. Help us by sending bug reports on our tracker, or request new features/enhancements
Localization
You're Bilingual? Woohoo! Tiki is available in different languages, and each language is separated so that our contributors can target their efforts on a specific language. Let's see some useful resources.
- Per Language Status
At the Status Panel you can check how a specific language is doing. It's possible to identify the amount of translated/untranslated/total strings for that language.
- Take action
Register in order to be able to use our Interactive Translator which will allow you to translate strings on the go as you navigate through pages