Van,
Let me know when you've got that page up on the wiki. Once it's up we can
start a separate thread for open feedback/feature requests and then guide
people to document it there on the wiki and as you said put it in some more
formal tool over time.
A lot of the users and implementers I interact with have a feedback requests
and I will direct it through these channels.
Ed
On Thu, Jul 7, 2011 at 4:17 PM, Van Mittal-Henkle <
[email protected]> wrote:
> Ed,****
>
> ** **
>
> All sounds good to me.****
>
> ** **
>
> The project oriented approach is one I’ve thought about too. It seems like
> a good thing to try getting multiple people working together in the same
> area of the app. It should allow for taking on bigger projects and increase
> the chances of completion even if the time folks have available is
> variable. (should be more fun too J )****
>
> ** **
>
> The priority list that Binny emailed seems like a good starting point for a
> Mifos user requested feature list. I hope to get this list up on the wiki
> (if the wiki would cooperate) so that areas that need to be fleshed out can
> be added to. From there detailed information could flow into Jira as issues
> and summary information could flow to mifos.org, uservoice or a form that
> gives the Mifos community an easy way to express their interest and vote.*
> ***
>
> ** **
>
> --Van****
>
> ** **
>
> *From:* Ed Cable [mailto:[email protected]]
> *Sent:* Thursday, July 07, 2011 7:41 AM
> *To:* Mifos software development
> *Cc:* [email protected]; A good place to start for users or
> folks new to Mifos.
>
> *Subject:* Re: [Mifos-users] [Mifos-developer] Whats after Maya G?****
>
> ** **
>
> Van,****
>
> ** **
>
> In that first bucket of users in the community, that is actually
> implementers (including both our MFI user and our Specialist ecosystem).
> Our Specialist ecosystem ideally over time will blur the line between both
> communities both implementing and supporting Mifos users, capturing feedback
> and requirements for the product and ultimately contributing to development
> themselves as well. We already have a number of Specialists that want to
> begin to work more on development or have created modules/new functionality
> that could be incorporated or shared more openly.****
>
> ** **
>
> I completely agree with what you're saying about letting developers choose
> what they work on. My wording in previous email was wrong as I was trying
> to be realistic about only being able to get work done that we had
> volunteers for - not necessarily assigning volunteers certain places.****
>
> ** **
>
> I would like us to move towards more of a project-based model like OpenMRS
> does - we can come up with a stronger set of projects and then openly
> advertise these so potential contributors know they have a well-defined
> project in which they can add meaningful value. Given the transition, we
> can move towards more comprehensive projects but will have to spend the
> effort to divide up into workable tasks, etc. ****
>
> ** **
>
> Ed****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Mifos-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-users
