I want to help
From Koha Wiki
Helping out with Koha is easy: the community is friendly and there is good documentation.
This page will guide you through all the information you need to make the most of our community resources.
If you have a bit more experience already then you can always come back here to use this page as a reference guide.
First steps into the community
We mostly talk to each other in 2 ways: by email or by IRC chat.
It's best if you set up tools for both, so you won't have to worry about how to get in touch with us when you need help. And you will need help, because we all do, all the time!
You can sign up to the mailing lists by following these instructions.
You can then find out how to come and say hello in the Koha IRC channel.
Finally, to figure out how we make decisions and how we decide when to release a new version of Koha.
Voilá, you can now start contributing to Koha!
Documenting & translating Koha: using your language skills for good
If you are a linguistic wizard, or still a novice, then improve the world by writing our manual, or by joining the translation team.
Improving our manual
A piece of software is only as good as its manual, and people who are good at writing those are worth their weight in gold.
Follow the steps on this page to land your first contributions to our manual.
Becoming a translator
Koha thrives of being an international project. Koha is available in many different languages, thanks to the ongoing work of our talented translators.
If you are great at your native language and good at English, help us out by becoming a translator!
Once you have stepped through that document, get cracking at http://translate.koha-community.org!
Going on a bug hunt…
I've found a bug! What do I do?
Report the bug! Bug reports help us to improve improve Koha; good bug reports are possibly the single-best way to help us improve Koha!
Find out how to submit *great* bug reports!
Testing bug fixes
Koha has a stringent quality assurance workflow to ensure we mostly only release code that works.
Anyone can contribute a fix for a reported bug. But not all fixes will become part of Koha. Fixes are vetted by our QA (quality assurance) team, before our RM (release manager) pushes them into the produce. But before our QA team can vet a fix it needs to be tested and signed off by Koha users.
Testing bug fixes is this first and essential step.
Finally, if you run into difficulties, remember chat! Bug testing is an art; mastering it is hard — but the great artists are held in great esteem!
Fixing bugs: submitting patches
Of course we also welcome contributions in code!
We have an ever evolving Developer handbook that might be your first point of call, or reference guide. Outside of this, you can follow our crash course in Koha hacking or learn how to set up a dedicated testing and hacking environment.
If you're looking for some inspiration of code contributions you could work on, read on!
Low hanging fruit
- Trivial or string change patches needing signoff
- Answering questions on the mailing list
- Tidy up the wiki
- Add a cookie, fudge or ice cream recipe
- Merging our SIP2 changes back into the upstream OpenNCIP project
- Minor bugs needing patches
- Small patches needing signoff
This is just getting silly
- Work on database independence
- Large Patches needing signoff
- Major severity bugs
- Update POD, add missing POD
- Integrate ElasticSearch as a search engine