We love having you here. But before you start, to ensure everyone has a good experience, we ask everyone that interacts with our community and staff to read our code of conduct.
There are many ways to get involved with Ushahidi, and some of them are great for first time contributors. If you never contributed to Open Source Software before, or need more guidance doing it, please join the community in one of the channels listed here.
If you find an area of the Ushahidi platform that could use better docs, we would love to hear from you in an issue, and would be seriously excited if you send a Pull Request. This is a great way to get involved, and one of the highest impact changes you can make at the moment. You can choose to work on user documentation, fix typos, or add new sections for discussion and collaboration with the community. Every little bit helps.
If you found an issue/bug, please report it here. Someone on the team will jump in to check it, try to help, and prioritize it for future development depending on the issue type.
If you think you have found a security issue, please follow this link where we explain our disclosure and reporting policies.
If you want to contribute a fix for a bug you or someone else found, we will be happy to review your PR and provide support. You can find our issues here:
Before you start coding, read through the Development & Code section to get started and to get help setting up your environment!
Feature development is generally driven by our product and engineering team members, but if you have a great idea or found a user need that we haven't covered, you are more than welcome to make a suggestion in the form of a GitHub issue here, or reach out to Ushahidi staff in Gitter.
If you are a designer and want to contribute to Ushahidi, please contact the Ushahidi design team at firstname.lastname@example.org or through the Join the Ushahidi community section of these docs. While you are waiting for us to reply, start reading through our Design-docs.
If you are interested in helping us QA and test new releases, please send an email to email@example.com or through the Get in Touch section of these docs to request access to the test environment. While you are waiting for us to reply, start reading trough the QA & Testing docs.
Help us make the platform available in as many languages as possible.
Translations live in our Transifex repository
You are welcome and encouraged to jump in and help other members of the community, either by responding to issues in GitHub or jumping into our community channels to answer questions. Read more here how to join the community channels.
We encourage community development workers, international development workers, activists and volunteers to join in and contribute with their knowledge and experience. Check out the section Encouraging contribution from non-developers to learn more how you can get involved.