Community of Mifos
Hi all -
So, it is good to see the effort by GF to engage the community of developers with the new strategy - the meeting
earlier tonight was good for that I think. More is needed, and not just for the developers who know what
Spring MVC is, but also for the constituency that is the eventual market. As an innovative open source
model, much still needs to be done to improve the community transparency - who is getting mifos working,
what are their challenges, how are they overcoming them, what is the future role of the GF/Mifos team?
When we dreamed up the Mifos concept with our friends at MFIs around the world, there seemed to be an appetite
to shoulder some of the effort themselves. That dream, where the end users are also the developers - at
least in the broad sense, should still be kept going. Those who have a vested interest make the best
participants long term and meeting their needs (developers within MFIs, external vendors, etc) is
paramount. They need to see a software solution constantly improve, and are best positioned to inform the
effort at GF or its successors.
Since I missed some of the early slides in the meeting this evening, and have no idea if these questions were
answered, I would like to ask:
* what makes the Mifos Chetah approach fundamentally different from the technology-strategy approach of
before? Beyond Spring and reworking the architecture, what does it say about the Mifos value
proposition?
* have you decided to reach 80% of the market with Software as a Service and what does that say about your
target customers? Small MFIs? Larger MFIs?
* what assumptions are you going to make about connectivity? and, how about those lightweight front ends
(Air, GoogleGears, etc) ?
* do you have accounting and transactional models at the core? or is the philosophy to leverage an existing
open source or other accounting system?
* will you enable (allow and encourage) a set of external and PRIVATE plugins to the framework to extend
functionality in a modular way?
* will you make data migration a part of your value proposition or at least make it easy to do?
Configurability, Approachability, Deployability, Extensibility - and since we love acronyms CADE -
this was the message that came out of our analysis of the original effort in 2006, we needed much much more of
CADE.
But, I would add something more - until Mifos has a solid core that the vendors around the world can make a
profit on, we won't get to a critical mass of participants/customers. Seeding that eco-system has been a
long and arduous task, but more frustrating perhaps for some supporters out there, is knowing when
certain elements of CADE will be available. I see the meeting tonight as a great step in that process and I
hope those supporters out there on the fence take note.
Before I sign off, Congrats on Version 1.1./Rhino - I can hear the thunder of hooves.
- James Dailey
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/