Hi Victor - I appreciate your contributions and hope that given your expertise in leveraging the FineractCN code base, that we get you more involved here in a positive discussion.
Could you describe what you think should be the roadmap for FineractCN? Currently the code is sitting in an official status of not-released at Apache. There is a formal release process as you know ==> https://www.apache.org/legal/release-policy.html Given community progress in updating Fineract1.x and making it more scalable, and the idea of using Fineract1.x as its own “microservice”, I think that the FineractCN strategy needs updating. We are considering Fineract1.x as almost a Microservice and also a strategy of breaking Fineract1.x into different jars and thus making it more composable. Thus perhaps we want to consider fineractCN within that context? I would propose that we collectively define the Minimal Viable Release as a running instance that can be leveraged by outside firms. This is more of a framework concept with the ability to register new microservices within that framework. Do you think we should modify the description of FineracCN on the wiki? It does create some potential points of confusion for people coming to the project. I understand you’re still trying to get code contributions approved by partner orgs. While that is ongoing is there a framework idea and approach we can move forward on? If I’ve misunderstood, please let me know. Thanks , Jdailey On Mon, Sep 26, 2022 at 6:36 AM Anjil R Chinnapatlolla <[email protected]> wrote: > Dear Fineract community members, > > > > Looking for exploring the current version of Fineract CN and possible > opportunities to contribute to the project. > > Can someone please help me point to the relevant material related to > Fineract-CN’s current status and if it is being considered for active > development. > > > > > > Thanks&Regards, > > Anjil > > > > > > >
