The Mifos Save Mobile Application is an open-source digital banking app that helps financial institutions manage group-based financial services. This project adds support for Group Banking and Village Savings and Loan Associations ( VSLA), enabling field officers to manage Centers, Groups, members, savings, loans, attendance, meetings, and collection activities. It also introduces JLG, GLIM, GSIM, and VSLA features to streamline community banking operations and improve financial inclusion.
Note
We're moving towards to Jira for issue tracking. Please
use Jira for issue tracking.
And Join our slack community
channel mifos-save-mobile-app to discuss all things about the project development. Please keep discussions
focused and avoid cross-posting across channels.
Access the demo credentials on our Jira Wiki page.
Thank you for your interest in contributing to the Mifos Save project by Mifos! We welcome all contributions and encourage you to follow these guidelines to ensure a smooth and efficient collaboration process. To get started, please refer to the Contribution Guide for detailed instructions on how to contribute to the project.
For development purposes, always pull from the dev branch, as all contributions and updates are merged into this branch. Upon completion of development, changes are subsequently merged into the master branch, which represents the stable and bug-free version of the code.
Please refer to the Development Setup Guide for detailed instructions on configuring the development environment.
After making changes in your local repository, you will need to commit them to your GitHub repository. If you are unfamiliar with the process of committing changes, please refer to the Committing Your Changes guide.
To ensure a clean and organized Git history, contributors are encouraged to squash their commits before merging. Instructions on how to squash commits can be found in the Squashing Your Commits guide.
Occasionally, merge conflicts may arise when your pull request is being reviewed. These conflicts need to be resolved manually. To learn how to resolve merge conflicts, please refer to the Solving Merge Conflicts guide
Mifos has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.
Please visit our Wiki page for a detailed overview of the project's architecture and guidelines. Explore further to gain a deeper understanding of our project.
This project is licensed under the open source MPL-2.0.
Special thanks to the incredible code contributors who continue to drive this project forward.