Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

Hi Ed, Yes, I have started looking deeper into how to eliminate the Category X dependencies. I have assigned this issues to myself and I'll share my approach to resolving these issues. Cheers, Isaac. On Mon, Oct 15, 2018 at 11:03 PM Ed Cable wrote: > Isaac, > > Have you or Awasum starting

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

Hi All - I believed I had enough lazy consensus to document what I *think* is the approach we are advocating. I took some liberties perhaps with the different phases, but hopefully this is good. If not, debate and comments welcome! Here are the key pages I changed and added content to on the

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

+1 ... I like the idea to start with a reduced set of services ... another way to look at it is ... all services are somewhat independent ... if we release the first set and bring all core libs to compliance ... we can decided piece by piece what to release and when. Cheers Markus On Wed, Oct

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

+1 > On October 17, 2018 at 8:06 PM James Dailey wrote: > > > Hi Myrle - > > I think the focus on a MVP (minimum viable product) is ideal. My list of > functionality in the email thread here was focused on that - although happy > to debate which are real MVP and which are nice to have (NTH). I

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

Hi Myrle - I think the focus on a MVP (minimum viable product) is ideal. My list of functionality in the email thread here was focused on that - although happy to debate which are real MVP and which are nice to have (NTH). I know you are focused on the building blocks on up and I am focused on

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

Hey all, Here's an alternative suggestion that I've been toying with: we could make our first release consist of just identity, provisioner, organization, accounting, customer, notifications, and of course fims-web-app and the supporting libraries. These pieces are enough to build a payment app

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

Isaac, Have you or Awasum starting looking into Section A any deeper - the elimination of Category X dependencies? Thanks, Ed On Mon, Oct 15, 2018 at 2:50 PM Isaac Kamga wrote: > Hello everyone, > > Thanks for your feedback Ed...it was very helpful. > > James, please could you edit the

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

Hello everyone, Thanks for your feedback Ed...it was very helpful. James, please could you edit the requirements you're suggesting into the Community roadmap . I'd like to encourage the community to add

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

Hi - I would like to suggest some key high level functional criteria for the formal release of Fineract-CN: 1. Use case orientation - that specific end-user roles and the steps that the end-user takes in interaction with Fineract-CN front end are written in a style that allows for both

[ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

Hello Fineracters, Hope this email finds you in good health. I was thinking about the survey on a product road map for Fineract CN which Ed Cable opened about half a year ago [0] and honestly it's time for us to break the silence around this discussion. Based on issues on our Jira issue tracker