India

IST (GMT +5:30)

IndiaUSA

IST PST(GMT +5-8:3000)

GMT

USA

PST(GMT -8:00)

To run any business successfully, you need the insight of the business and that is possible when you have information system in which you can get the information in the format your business analysis team needs. And in current world business are very much market adaptive and market scenarios changes very rapidly. To cope up with that  good MIS need to have Ad-hoc report builder.

Easy-to-use, drag-and-drop report designer builds crosstabs, tables, and chart-based reports using a standard browser.

In 2014, we began the Saiko integration and this project would serve as a continuation of that.

The ad hoc reporting will be based on a logical mapping of Mifos data elements to business entities (like customer, loan account, savings account, loan transactions, savings transactions etc.) and business attributes (like loan approved date, loan amount, loan outstanding amount etc.). An end user will be able to configure and generate reports based on these business entities and business attributes.

Reporting fields and reporting criteria will support basic derived fields like "days overdue", "amount overdue", "customer total outstanding amount", "customer total relationship value" etc.

The reporting will support basic functions like summing up totals, sorting based on different fields and grouping based on different fields.

http://community.pentaho.com/faq/waqr_faq.php

For better usability system needs to have notifications to the logged in user about actions he/she needs to perform in the application.

Build real time notification system in application to notify to users about pending/new actions she/he needs to take. Example if branch manager login to the application and 3 new loans are created and pending for approval then system should notify him/her about the pending actions.

This involves both invoking and triggering these notifications based on these actions or activities as well as the extension of the user interface to support the display of the notifications as well as the ability of the user to take action upon the notifications.

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.

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's goal is to create an Amazon Cloud formation template for Mifos deployments at large Organisations. We would measure how we scale, with concrete scenarios and hard numbers, and produce documentation about this helping organization who are evaluating Mifos.

We would also try to identify and fix performance bottlenecks in the MifosX and the community app codebase

You would be creating a Cloud formation template on AWS for a sample high performance Mifos setup. The setup would include

• Approximately 5 web servers (Apache) on medium EC2 instances fronted with a load balancer
• Approximately 5 Tomcats servers on large EC2 instances fronted with a load balancer
• Multi Az extra Large RDS
• Distributed in memory cache environment

You would then use Jmeter (or a tool of your choice) to create realistic data and run and benchmark performance on this setup. Based on the figures, we would make fixes to either to the MifosX / Community app codebases to fix any identified performance bottlenecks and then carry out multiple iterations of tweaking the Cloud formation template to achieve best performance.

http://twitter.github.io/iago/

http://www.loadui.org (by the good people behind SOAPui)

Selenium WebDriver

https://jmeter.apache.org/

http://grinder.sourceforge.net/

http://opensta.org/

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.

Initial version of Mifos X was not designed to be database agnostic. Goal of this project is to make it so, and test this out in practice by running it locally on Oracle, make sure our test suite runs against Oracle as well as mysql, and well documenting how this can be set up by end-user clients, if they wish to go for this deployment.

To make this possible, all business logic has to be concentrated in the middle tier with the database being as dumb as possible. This means the platform does not rely on any database specific stored procedures or on the database to generate unique keys. And also application heavily use prepared statements (Spring jdbctemplate) for retrieving data and need to make sure all these queries use full JOIN syntax, and bracket the JOINs so that each join is between a single table and bracketed expression.

MFI with large client base can use the application with Oracle or any other commercial databases.

Mifos has abstraction from underlying database using:

• Hibernate as ORM (must have good experience with Hibernate)
• Liquibase as Database refactoring tool
• DbUnit as test dataset maintenance

 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)

Mifos X today is typically used on Tomcat (with Jetty known to work). For a certain class of users, testing it on "Enterprise Stack" application servers (meaning IBM WebSphere and Oracle WebLogic) is desirable - this project would properly test Mifos X on these configurations, make any adaptations to the code which may be required, and produce easy to follow documentation or even small tools helping future users how to go about this.

This project could be combined with and taken up by the same candidate as the Enterprise database project.

Java, Application Server configuration, WAS classloading crap tricks, documentation writing.

Use Cargo, Arquillian etc. for automated testing against WAS & WLS containers?

Vendor pages

The Mifos X platform as of today is a well structure but monolithic code base - one Git repo, one build, one WAR. This has worked out well for us, but as we grow, it could be interesting to introduce a proper SDK and plug-in concept, allowing contributors to build individual JARs that can be dropped into a certain directory of Mifos X to augment the core platform on well defined extension points and hooks. These modules would be loaded at run-time, not require rebuilding Mifos X, and would remain compatible when a customer upgrades their core platform version.

We currently see the SDK as something more relevant to the Java back-end, so in this project you would likely work less on our AngularJS UI (barring some configuration UI for the plug-ins probably); but if you do have any ideas how to make the front-end more modular and extensible as well, we would love to hear from you.

This project will have three axis/phases: 1. platform infrastructure framework kind of work, based on a very simple or fictitious example extension; 2. identifying the functionally which could require / be sensible to extend in Mifos X, extracting clear and documented Java APIs from it, and then make changes to existing functional platform services to make them extensible by plug-ins; 3. well document this - such plugins will only be written if it's easy and clear how to do this. Note that the more technical part 1. should only take about 1/4 of your project, the focus will have to be putting the "theory" from 1. into "practice" in phases 2. & 3.

For better usability system needs to have notifications to the logged in user about actions he/she needs to perform in the application.

Build real time notification system in application to notify to users about pending/new actions she/he needs to take. Example if branch manager login to the application and 3 new loans are created and pending for approval then system should notify him/her about the pending actions.

This involves both invoking and triggering these notifications based on these actions or activities as well as the extension of the user interface to support the display of the notifications as well as the ability of the user to take action upon the notifications.

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.

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's goal is to create an Amazon Cloud formation template for Mifos deployments at large Organisations. We would measure how we scale, with concrete scenarios and hard numbers, and produce documentation about this helping organization who are evaluating Mifos.

We would also try to identify and fix performance bottlenecks in the MifosX and the community app codebase

You would be creating a Cloud formation template on AWS for a sample high performance Mifos setup. The setup would include

• Approximately 5 web servers (Apache) on medium EC2 instances fronted with a load balancer
• Approximately 5 Tomcats servers on large EC2 instances fronted with a load balancer
• Multi Az extra Large RDS
• Distributed in memory cache environment

You would then use Jmeter (or a tool of your choice) to create realistic data and run and benchmark performance on this setup. Based on the figures, we would make fixes to either to the MifosX / Community app codebases to fix any identified performance bottlenecks and then carry out multiple iterations of tweaking the Cloud formation template to achieve best performance.

http://twitter.github.io/iago/

http://www.loadui.org (by the good people behind SOAPui)

Selenium WebDriver

https://jmeter.apache.org/

http://grinder.sourceforge.net/

http://opensta.org/

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)

Mifos X today is typically used on Tomcat (with Jetty known to work). For a certain class of users, testing it on "Enterprise Stack" application servers (meaning IBM WebSphere and Oracle WebLogic) is desirable - this project would properly test Mifos X on these configurations, make any adaptations to the code which may be required, and produce easy to follow documentation or even small tools helping future users how to go about this.

This project could be combined with and taken up by the same candidate as the Enterprise database project.

Java, Application Server configuration, WAS classloading crap tricks, documentation writing.

Use Cargo, Arquillian etc. for automated testing against WAS & WLS containers?

Vendor pages

At present MIfos X platform is shipped with Community-App (SPA) as default UI, but initial load time of the application high. And for users on narrow bandwidth internet it takes a considerable amount of time to load the app.

Instead of loading the app every time, we can convert the Community-App into a Chrome App and user can download them once and install it ion the machine, and it can used as thick client.

Community-App is completely developed on top of JavaScript, CSS and HTML. And Chrome apps are also written in same stack. Using grunt we should be able to repackage Community-App(SPA) into Community-App(Chrome App)

Users with slow internet connectivity can use this app (Installed on the machine) instead of loading Community-App (SPA) on the browser. Users will also have a continually updated app. This will also allow MFIs to potentially use Chromebooks as field-based devices for their branches.

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/