# Contributors' Guide
We are glad that you are considering becoming a part of the Mojaloop community.
Based on the current phase of the Mojaloop project, we are looking for one of the following types of contributors:
# Types of contributors
# Individual Contributors
These individuals are those that want to start contributing to the Mojaloop community. This could be a software developer or quality assurance person that wants to write new code or fix a bug. This could also be a business, compliance or risk specialist that wants to help provide rules, write documentation or participate in requirements gathering.
# Hub Operators
Typically these or organizations or individuals or government agencies that are interested in setting up their own Mojaloop Switch to become part of the ecosystem.
# Implementation Teams
Implementation teams can assist banks, government offices, mobile operators or credit unions in deploying Mojaloop.
# How do I contribute?
- Review the Mojaloop Deployment (opens new window) Guide and the Onboarding Guide (opens new window).
- Browse through the Repository Overview (opens new window) to understand how the Mojaloop code is managed across multiple Github Repositories.
- Get familiar with our Standards for contributing to this project.
- Go through the New Contributor Checklist, and browse through the project board and work on your good first issue (opens new window)
- Review the Roadmap and contribute to future opportunities.
- Familiarize yourself with our Community Code of Conduct.
# What work is needed?
Work is tracked as issues in the mojaloop/project (opens new window) repository GitHub. You'll see issues there that are open and marked as bugs, stories, or epics. An epic is larger work that contains multiple stories. Start with any stories that are marked with "good first issue (opens new window)". In addition, anything that is in the backlog and not assigned to someone are things we could use help with. Stories that have owners are in someone's backlog already, though you can always ask about them in the issue or on Slack.
There's a roadmap that shows larger work that people could do or are working on. It has some main initiatives and epics and the order, but lacks dates as this work is community driven. Work is broken down from there into issues in GitHub.
In general, we are looking for example implementations and bug fixes, and project enhancements.
# Where do I get help?
Join the Mojaloop Slack Discussions (opens new window) to connect with other developers.
Also checkout the FAQ (opens new window)
# What is the current release?
See the Mojaloop Slack Announcements (opens new window) to find out information on the latest release.
# What's here and what's not?
This is free code provided under an Apache 2.0 license (opens new window).
The code is released with an Apache 2.0 license but the Specification documents under the 'mojaloop-specification' documents are published with CC BY-ND 4.0 License
We don't provide production servers to run it on. That's up to you. You are free (and encouraged!) to clone these repositories, participate in the community of developers, and contribute back to the code.
We are not trying to replace any mobile wallet or financial providers. We provide code to link together new and existing financial providers using a common scheme. There are central services for identifying a customer's provider, quoting, fulfillment, deferred net settlement, and shared fraud management. Each provider can take advantage of these services to send and receive money with others on the system and there's no cost to them to onboard new providers. We provide code for a simple example mobile money provider to show how integration can be done, but our example DFSP is not meant to be a production mobile money provider.
# Where do I send bugs, questions, and feedback?
For bugs, see Reporting bugs (opens new window).