Another name for this page might be: "we've got a long road ahead, but check out what we've done along the way!".
These are problems keeping Mifos from being truly awesome. Some of them have corresponding issues in our issue tracker. If you agree that they need to be fixed, please vote for them!
A fast compile/fix cycle is essential for making code changes in a timely manner.
Fast, useful feedback.
MIFOS-4921
Migration to Spring MVC and Freemarker in progress!
We need to cull or pull out non-core functionality into plugins/extensions
PPI source data is currently in many separate Word documents and Excel spreadsheets. Store it in a standard format that can be used to generate printed surveys as well as reports used by Mifos BI software.
Eliminate exclusivity of batch jobs and OLTP activities
Fix MIFOS-2018, others.
The HTTP session is used much more than is really necessary.
These are issues I was particularly concerned about that have since been resolved. Yay!
Done! Thank you, Michael Vorburger!
See MIFOSADMIN-54.
Done by Kojo during the Google Summer of Code 2010. Yay!!
See MIFOS-2896.
Done June 2010. Yay!!
We currently use both JIRA and Mingle.
Done mid-May, 2010. Thank you, Git!
This is a huge win during development. Thank you to Adam Feuer and others for making it so that Mifos can be run without first building and deploying a war
Thank you, OpenNMS!
Thank you, BackupPC!
We realized many benefits after moving from Ant to Maven
Also, we moved from Bamboo to Hudson for our continuous integration server. Awesome!
Moving our Subversion repository to SourceForge.net was a huge win after months of abuse from an unreliable repository at java.net. The next step is moving to distributed version control.
With sf.net, we gained
Thank you, Atlassian!
Done! See FixFirefoxBugs.
Almost every Mifos release is now on schedule or early.
Done! See UpgradeHibernate.
Done! See AutomatePseudolocalization or MIFOS-2445.
Marked "wont fix". It seems acceptable that Mifos requires table/column name case insensitivity.
See MIFOS-1513.
The original development platform was likely one where filenames are case-insensitive. On these platforms, MySQL allows referring to tables (and columns?!) in a case-insensitive way. This is a gotcha for Linux and OS X deployments, see issue 1513 for details.
Update: we ran into a problem using EC2: their RDS service only supports case-sensitive databases! Thanks to Udai, MIFOS-1513 is now fixed!
Mifos used to require JBoss. We've found Tomcat
Thank you, Freenode!
All customers now operate on known, frozen versions of released software that we have tested.