Our AngularJS Community App is the standard application on the Mifos X platform that provides all the core functionality for the most common methods of financial inclusion and products and services. It's also the starting point for any partners looking to customize or extend the UI. It's constantly being improved based on user feedback, better performance, and to integrate new design standards and AngularJS refactoring.

The project will involve the following:

• Performance improvements by introducing on demand loading
• Implement Material Design and Redesign pages and areas of the application needing improvement:
  • Log-in page, chart of accounts, permissions, data tables, collection sheet, etc.
• Upgrade to latest version of http://angular-ui.github.io/bootstrap/

Enable two factor authentication for certain types of transactions - for example transfers initiated, need to be confirmed via a One-Time-Password generated by Mifos and sent via SMS to client's mobile number.

We have recently released a full set of client-facing APIs to enable self-service channels for clients to interact with their own data and transact in a self-service manner. Previously all Mifos operations were performed by back office staff. Now clients can authenticate themselves, view and edit their account details. and make repayments or transactions between their own accounts.

It is now possible for them to have direct banking apps that they can utilize including smartphone-based mobile banking, USSD-based mobile banking, and online banking via a web app.

Provides more security for clients especially during loan disbursements and savings withdrawals or transfersAllows a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood.

Customer Self Service

Customer Self Service - Phase 2

We have recently released a full set of client-facing APIs to enable self-service channels for clients to interact with their own data and transact in a self-service manner. Previously all Mifos operations were performed by back office staff. Now clients can authenticate themselves, view and edit their account details. and make repayments or transactions between their own accounts.

It is now possible for them to have direct banking apps that they can utilize including smartphone-based mobile banking, USSD-based mobile banking, and online banking via a web app.

The focus of this project would be designing and implementing a clean and simple AngularJS application that can be used as a reference web app for financial institutions to directly deploy and offer to their customers or for our our support partners to customize and enhance to the local needs of their market.

Allows a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood.

Customer Self Service

Customer Self Service - Phase 2

We have recently released a full set of client-facing APIs to enable self-service channels for clients to interact with their own data and transact in a self-service manner. Previously all Mifos operations were performed by back office staff. Now clients can authenticate themselves, view and edit their account details. and make repayments or transactions between their own accounts.

It is now possible for them to have direct banking apps that they can utilize including smartphone-based mobile banking, USSD-based mobile banking, and online banking via a web app.

The focus of this project would be designing and implementing a clean and simple AngularJS application that can be used as a reference web app for financial institutions to directly deploy and offer to their customers or for our our support partners to customize and enhance to the local needs of their market.

Allows a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood.

Customer Self Service

Customer Self Service - Phase 2

This has Agent Banking has become a key new delivery channel to increase reach, lower cost, and broaden the depth of services available. We will be taking over the Egalite codebase that's being donated to the Mifos Initiative by BFSI Consulting - it's a fully functional Android-based app for agents that works with any core banking system. This project would involved extending the application so it fully integrates with and works on top of the Mifos X platform

The current codebase is stand-alone and can integrate with any core banking system. This project will involve converting it to work on top of Mifos X by leveraging the Mifos X APIs for all functionalities that exist in Mifos X and adding in APIs for the functionalities that aren't present in Mifos X but in Egalite.

By enabling branchless banking, the costs of serving the poor are dramatically lowered, outreach can be extended to rural offerings, and brand new products and services that are more relevant can be delivered.

This has a dependency on the Self-Service backend API's being available 

Allows a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood.

Agent Banking has become a key new delivery channel to increase reach, lower cost, and broaden the depth of services available. We will be taking over the Egalite codebase that's being donated to the Mifos Initiative by BFSI Consulting - it's a fully functional Android-based app for agents that works with any core banking system. This project would involved extending the application so it fully integrates with and works on top of the Mifos X platform

The current codebase is stand-alone and can integrate with any core banking system. This project will involve converting it to work on top of Mifos X by leveraging the Mifos X APIs for all functionalities that exist in Mifos X and adding in APIs for the functionalities that aren't present in Mifos X but in Egalite.

By enabling branchless banking, the costs of serving the poor are dramatically lowered, outreach can be extended to rural offerings, and brand new products and services that are more relevant can be delivered.

Enable two factor authentication for certain types of transactions - for example transfers initiated, need to be confirmed via a One-Time-Password generated by Mifos and sent via SMS to client's mobile number.

Provides more security for clients especially during loan disbursements and savings withdrawals or transfers.

In outbound SMS notification MFI decides when and what information need to be sent to client, but as part of client protection, client has complete rights to request for information about her/his account details(any time any where). Using inbound SMS client can query for her account details such loan amount, status of new loan application, outstanding loan amount.

Transparency and client protection.

See SMS Integration and Outbound SMS

• Hooks
• Showcase of sending event-based SMS

Right now Mifos X contains core client management functionalities including tracking basic demographic information, know your customer information, document management, and survey collection through data tables. As financial institutions serving the poor begin to offer a more in-depth and diverse range of financial inclusion products, the need for more robust client management and in-depth client understanding has grows. Their core system needs to provide more and more CRM-type functionality that complement the portfolio management and financial/social reporting the Mifos X provides.

This project will work to deliver the initial set of customer relationship management functionalities including a module for tracking inquiries, complaints

This module will have a request management functionality. A request can be of 2 types: Complaints and Service Requests. Each request must be against a customer and optionally against an account of the customer. Each request will go through a simple workflow.

Actions that can be performed on a request:

Assign -> will change status to "assigned"

Start Work --> will change status to "in progress"

Close --> will change status to "closed" (with a sub-reason code)

At each step user can enter comments.

The customer summary screen will have a link to view the requests of the customer - along with a summary and current status - with option to click-through to get the complete history of each request.

Deepening the client relationship and ensuring fair, responsible, and transparent financial services to the poor is a core piece of the industry's roadmap for financial inclusion. Providing customers the ability to voice their concerns and feedback about the services they're receiving provides a simple yet powerful tool to protect the client. Empowering the financial institution with the ability to track these inquiries and overall maintain a more holistic relationship tracking entire lifecycle of their clients gives them a much better ability to understand their clients and respond to their needs with appropriately designed services and products.

We believe the Mifos X platform is super secure and impenetrable. Your mission, should you choose to accept it, is to prove us wrong, and help close gaps you may find.

Beyond a one time exercise, you should integrate (some of) the tools you've used into our build chain so that, even after you've gone, tools flag up future newly introduced potential vulnerabilities.

Integrate MifosX with an opensource Point of Sale (POS) called JPOS.

Use case would be to get a debit transaction (cash withdraw from checking account) thru the POS device /local runtime with 2FA.  In India, the ability to get cash out through a point of sale network is provided for under RBI regulations. In production there will likely need to be an intermediate "Merchant Acquisition" or "Payment Processor" in between a single POS and MifosX Instance, but this could be abstracted out as a payment gateway only (primarily data mapping). The implementation target is the ability to do a 2 factor authentication on a POS device running JPOS (emulator ok), input account number (via some simple method), then be able to do a (cash-out) account withdrawal in real time to the MifosX account. Additional use cases would be to implement a transaction for payment for goods. i.e. enter specific goods, then do payment from MifosX account to Merchant Account (probably also in Mifos).

Familiarity with API work. Understanding of transactional flows.

Java.

Two-factor authentication - see other project idea .

https://github.com/jpos/jPOS/

This project would seek to create one unified ID/login and profile for community members similar to the OpenMRS ID. It would achieve the following two primary objectives:

1. One unified profile and identity for community members in which they can share with the community who they are and also build reputation and recognition. This ability to discover and self-identify with other community members is difficult when we have so many different tools and profiles to maintain.
2. Single Sign On for our various collaboration and community infrastructure tools listed below.

1. Identifying a single sign-on authentication protocol that ties together authentication of our various community collaboration tools: 1) Atlassian Studio - JIRA, Confluence, JIRA Agile, 2) Social Q&A - AnswerHub 3) Mailing Lists - Mailman (administered through SourceForge 4) Source Code Version Control - GitHub 5) Continuous Integration - Jenkins 6) General Community Website (mifos.org) - Wordpress 7) Partner Directory
   1. This could be built out independently, tie into some OpenID protocol, or leverage one of our existing tools for this authentication - Atlassian Studio/Crowd or AnswerHub or another common OpenID protocol. 
2. Design and implement a dashboard to handle the creation of this unified ID
3. Design and create a common profile tied to this ID with basic information and photos that is searchable by the community.

Design a profile

Extra Credit:

• Gamification/Reputation Building - Tie into Open Badge system like Mozilla Open Badges http://openbadges.org/ or Ushahidi Badges: http://ushahidi.github.io/Badges/

Impact is two-fold:

• Common unified profile and identity can help to grow collaboration and participation in the community. By being able to simply share who you are or discover who's in your community, we can deepen the bonds of community which motivates each member to participate more often and invest personally in the health of the community. Building reputation and recognizing efforts of each type of community member (users, partners, volunteers, etc) in a tangible way also helps to increase participation.
• Single sign-on will it make much easier for community members to collaborate and communicate. Right now there is often a high barrier to signing up for the various tools - SSO will make that process easier but also encourage others to more regularly be involved.

 Create a POC of a scalable MifosX implementation (with load balanced tomcats and percona servers) on an openstack setup on a public cloud. Also publish a whitepaper with details of Openstack setup

 Mifosx was built to be cloud ready from the ground up. One of the most popular deployment environments for MifosX has been on Amazon EC2, however due to country specific regulation, many implementors are forced to seek alternative models that can scale as effectively

The aim of this project is two-fold

We believe the Mifos X platform is super secure and impenetrable. Your mission, should you choose to accept it, is to prove us wrong, and help close gaps you may find.

Beyond a one time exercise, you should integrate (some of) the tools you've used into our build chain so that, even after you've gone, tools flag up future newly introduced potential vulnerabilities.

https://www.owasp.org/index.php/Main_Page

https://code.google.com/p/zaproxy/

http://wapiti.sourceforge.net

Run FindBugs & related tools for some serious static code analysis

http://en.wikipedia.org/wiki/Penetration_test

This project would seek to create one unified ID/login and profile for community members similar to the OpenMRS ID. It would achieve the following two primary objectives:

1. One unified profile and identity for community members in which they can share with the community who they are and also build reputation and recognition. This ability to discover and self-identify with other community members is difficult when we have so many different tools and profiles to maintain.
2. Single Sign On for our various collaboration and community infrastructure tools listed below.

1. Identifying a single sign-on authentication protocol that ties together authentication of our various community collaboration tools: 1) Atlassian Studio - JIRA, Confluence, JIRA Agile, 2) Social Q&A - AnswerHub 3) Mailing Lists - Mailman (administered through SourceForge 4) Source Code Version Control - GitHub 5) Continuous Integration - Jenkins 6) General Community Website (mifos.org) - Wordpress 7) Partner Directory
   1. This could be built out independently, tie into some OpenID protocol, or leverage one of our existing tools for this authentication - Atlassian Studio/Crowd or AnswerHub or another common OpenID protocol. 
2. Design and implement a dashboard to handle the creation of this unified ID
3. Design and create a common profile tied to this ID with basic information and photos that is searchable by the community.

Design a profile

Extra Credit:

• Gamification/Reputation Building - Tie into Open Badge system like Mozilla Open Badges http://openbadges.org/ or Ushahidi Badges: http://ushahidi.github.io/Badges/

Impact is two-fold:

• Common unified profile and identity can help to grow collaboration and participation in the community. By being able to simply share who you are or discover who's in your community, we can deepen the bonds of community which motivates each member to participate more often and invest personally in the health of the community. Building reputation and recognizing efforts of each type of community member (users, partners, volunteers, etc) in a tangible way also helps to increase participation.
• Single sign-on will it make much easier for community members to collaborate and communicate. Right now there is often a high barrier to signing up for the various tools - SSO will make that process easier but also encourage others to more regularly be involved.

 Create a POC of a scalable MifosX implementation (with load balanced tomcats and percona servers) on an openstack setup on a public cloud. Also publish a whitepaper with details of Openstack setup

 Mifosx was built to be cloud ready from the ground up. One of the most popular deployment environments for MifosX has been on Amazon EC2, however due to country specific regulation, many implementors are forced to seek alternative models that can scale as effectively

The aim of this project is two-fold

• Propose a scalable deployment model for Mifos (includes load balanced tomcats, percona mysql server etc ) on OpenStack. The POC would be on a public cloud provider (Rackspace?)
• Publish a whitepaper of the same, which can be used as a reference for local implementors (who would additionally take care of provisioning their own hardware)

While the Mifos X Community App front-end UI based on AngularJS-based currently does already have some JS unit tests, we lack a full UI level web tests which continually non-regression test common scenarios. We believe having this could add value in terms of quality, including ensuring automated cross browser testing.

Possibly building upon a extremely limited small scale existing POC (if you find it to be a useful starting point), your mission, should you chose to accept it, would be to build out comprehensive UI walk through scenario test coverage for the Mifos X UI. If you can build more such tests faster and more maintainable (= less code) by using any of the existing frameworks listed below or others you know of / will find, or build useful such infrastructure yourself as part of this code, we're eager to hear from you! Keep in mind that the main deliverable of this project is not (only) a foundation framework, but must actually include an extensive suite of running tests integrated into the Mifos build.

Integrate MifosX with an opensource Point of Sale (POS) called JPOS.

Use case would be to get a debit transaction (cash withdraw from checking account) thru the POS device /local runtime with 2FA.  In India, the ability to get cash out through a point of sale network is provided for under RBI regulations. In production there will likely need to be an intermediate "Merchant Acquisition" or "Payment Processor" in between a single POS and MifosX Instance, but this could be abstracted out as a payment gateway only (primarily data mapping). The implementation target is the ability to do a 2 factor authentication on a POS device running JPOS (emulator ok), input account number (via some simple method), then be able to do a (cash-out) account withdrawal in real time to the MifosX account. Additional use cases would be to implement a transaction for payment for goods. i.e. enter specific goods, then do payment from MifosX account to Merchant Account (probably also in Mifos).

Familiarity with API work. Understanding of transactional flows.

Java.

Two-factor authentication - see other project idea .

unit tests, we lack a full UI level web tests which continually non-regression test common scenarios. We believe having this could add value in terms of quality, including ensuring automated cross browser testing.

Possibly building upon a extremely limited small scale existing POC (if you find it to be a useful starting point), your mission, should you chose to accept it, would be to build out comprehensive UI walk through scenario test coverage for the Mifos X UI. If you can build more such tests faster and more maintainable (= less code) by using any of the existing frameworks listed below or others you know of / will find, or build useful such infrastructure yourself as part of this code, we're eager to hear from you! Keep in mind that the main deliverable of this project is not (only) a foundation framework, but must actually include an extensive suite of running tests integrated into the Mifos build.

http://docs.seleniumhq.org/projects/webdriver/

https://github.com/vorburger/mifosx-ui-selenium-webdriver-tests

https://github.com/vorburger/webdriver-runner

https://saucelabs.com or https://browserling.com

https://github.com/FluentLenium/FluentLenium

http://www.gebish.org

http://www.thucydides.info