Simplify Locale Configuration
Background
The method used by Mifos to provide locale-specific content is difficult to maintain and not customizable per-user. We seek to simplify the Mifos code by improving the locale configuration and runtime localization code.
Status - Available
Contact
Please email the mifos-developer list if you are interested in helping on this project.
Mentor
Current Volunteer(s)
N/A
Time Estimate
40+ hours
Prerequisite experience
Java, J2EE, SQL (especially MySQL).
Details
come up with a rough plan to incrementally fix MIFOS-2018 and allow per-user locales
if possible, consider following the locale-sensing pattern implemented in the Cheetah spike (see
cheetah/trunkin source control)
Steps
Read the Developer Kick Start page for information on contributing and getting set up. Follow the steps under
Introduce yourself to the community - Mailing Lists
Fill out the Contributor Agreement
Start by submitting a couple of small patches which demonstrate your skill and provide incremental steps towards completing this project
Create small patches against the latest trunk revision. Ideally, submit a small patch after every working session.
Every patch must be applicable to the trunk.
"mvn clean install" in the top-level directory of your Mifos working copy must succeed for every patch.
Post the patch on the mifos-developer mailing list.
Describe what changes you made and why, following the CommitLogGuide wiki page.
If the patch requires moving or deleting files or directories, mention this in your post.
Patches must meet or exceed all requirements on VettingPatches
If you are blocked, post questions (and an in-work patch, if applicable) to (a) the IRC channel ( http://pastey.net can be used for sharing patches) and/or (b) the mifos-developer mailing list.
If creating patches turns out to be too cumbersome in the long run, we are happy to provide a branch off the trunk in source control for you to work on.