osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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 <isaac.kamga@xxxxxxxxx> wrote:

> 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
> <
> https://cwiki.apache.org/confluence/display/FINERACT/Apache+Fineract+CN+Community+Roadmap
> >
> .
>
> I'd like to encourage the community to add items to the roadmap so that we
> move towards an initial release of Fineract CN.
>
> Given that some developers are working on issues on Fineract CN, I suggest
> we strike the items through ( like this strikethrough ) which have been
> closed on JIRA as I've started doing.
>
> Cheers,
> Isaac Kamga.
>
> On Wed, Jul 25, 2018 at 6:49 PM James Dailey <jamespdailey@xxxxxxxxx>
> wrote:
>
> > 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 "tests" and communication of
> the
> >    requirements.  For example:
> >       1. The User:BankStaff is able to login to see a recent history of
> all
> >       transactions by specific accounts, according to the permissions
> that
> > they
> >       have that mask certain transaction details.
> >       2. The User:Customer is able to login to a see current balances and
> >       recent activity on both debit and credit accounts with a total
> > showing for
> >       all of their accounts.
> >       3. The User:FieldAgent is able to login and see a list of payments
> by
> >       individuals for whom they are assigned to.
> >       4. and so on...
> >
> >       2. That security and configuration guides be included in the
> thinking
> >    from the beginning.  An open source project often faces the false
> > criticism
> >    that it is less secure so it is important to have ways of analyzing
> and
> >    addressing security holes from the beginning.  This may also take the
> > form
> >    of jira tickets that relate to ensuring that the logs are inviolable
> and
> >    that early detection mechanisms send alerts to the proper humans
> > defined in
> >    the configuration file - which may require thinking that through more.
> >    There are guides to how to secure infrastructure and I am sure other
> > Apache
> >    projects have had to deal with this - we should look to them for
> advice.
> >
> >    3. That the surface area of the release includes:
> >       1. Open an Account with at least two KYC levels
> >       2. Open a second account for the same person or entity
> >       3. Make a deposit
> >       4. Make a withdrawal
> >       5. Transfer funds within accounts held by the same person
> >       6. Enforce rules related to transfer amounts (subject to KYC
> limits)
> >       7. Have a simple approval process for a loan application (an agent
> >       can approve)
> >       8. Configure a loan product with min and max amounts and two
> methods
> >       of interest calc
> >       9. Transfer funds from a "lending department" to a customer
> >       10. Generate an expected payments schedule based on the product
> >       definition
> >       11. Write off the loan
> >       12. Close the account (put into one of several different states)
> >
> >       4. That there is sufficient test coverage for the release.
> >
> >
> > Thanks,
> > James
> >
> > On Wed, Jul 25, 2018 at 10:00 AM Ed Cable <edcable@xxxxxxxxx> wrote:
> >
> > > Isaac,
> > >
> > > Thanks for compiling the tickets and composing into a cohesive initial
> > > roadmap for our release candidate. Myrle - thank you as well for the
> > > feedback that you have provided thus far.
> > >
> > > Myrle and everyone else in the community,
> > >
> > > Can you please help define what an MVP is for the first demo-able
> > solution
> > > on top of the first official release of the framework? Namely, I want
> to
> > > know what if any additional microservices (i.e. reporting) need to be
> > > implemented in order to have an end to end solution on Fineract CN.
> This
> > > roadmap has a good focus on some of the key milestones around removing
> > > Category X dependencies, enabling local development, etc. but I think
> we
> > > need more visibility into the additional functionality that needs to be
> > > made available via the core set of microservices
> > >
> > > There is one ticket related to portfolio microservice and want to
> further
> > > discussion around what additional enhancements are needed around these
> > core
> > > microservcies to demonstrate a functional solution.
> > >
> > > I get that the use case will be limited (i.e. around individual loans,
> > etc)
> > > and not group lending but want us to establish what the bare minimum of
> > > microservices is to have in place such that others can come and extend
> > > through new microservices or new configurations or new enhancements to
> > > support other methodologies, other verticals, other processes like loan
> > > origination, etc.
> > >
> > > Ed
> > >
> > > On Wed, Jul 18, 2018 at 7:05 AM Isaac Kamga <isaac.kamga@xxxxxxxxx>
> > wrote:
> > >
> > > > 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 [1], I created some documentation [2] on Confluence to open
> the
> > > > discussion.
> > > >
> > > > It's important ( if not critical ) for community stakeholders to
> > discuss
> > > > and prioritize features they would like to enjoy on Fineract CN so we
> > > move
> > > > towards it's first release.
> > > >
> > > > I look forward to your opinions on this.
> > > >
> > > > At Your Service,
> > > > Isaac Kamga.
> > > >
> > > > [0]
> > > >
> > > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/fineract-dev/201802.mbox/%3CCAPnWRTh-o0G9Q6aKcs0BhhFK0ZbR-vO38MbMf=W+fyFjqhmKvg@xxxxxxxxxxxxxx%3E
> > > > [1] https://issues.apache.org/jira/browse/FINCN
> > > > [2]
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FINERACT/Apache+Fineract+CN+Community+Roadmap
> > > >
> > >
> > >
> > > --
> > > *Ed Cable*
> > > President/CEO, Mifos Initiative
> > > edcable@xxxxxxxxx | Skype: edcable | Mobile: +1.484.477.8649
> > > <(484)%20477-8649>
> > >
> > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> > > <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
> > >
> >
>


-- 
*Ed Cable*
President/CEO, Mifos Initiative
edcable@xxxxxxxxx | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>