Re: Fineract - Export Authorization

[Victor Manuel Romero Rodriguez]

Hi Myrle,

Thank you for your response. I'm looking for information too, and I 
would like to contribute in this point, right now customers in Mexico, 
which are now looking at the OSS projects like Fineract have this 
questions and if we can help, would be great.


I will come back with our 2 bucks.

Victor


El 21/03/18 a las 01:31, Myrle Krantz escribió:

Hi Victor,

To my knowledge, no committer or contributor has tried to figure out what
we need to do here. If you want to step in here, your contributions are
welcome!

I’m not sure how to find out the next steps, but I’d start by searching
through the mailing lists of projects that are in the incubator and on the
list you sent us.

Best Regards,
Myrle

On Tue 20. Mar 2018 at 20:36 Victor Manuel Romero Rodriguez <
victor.rom...@fintecheando.mx> wrote:


Hello Fineract Team,

Recently in Mexico as part of the FinTECH regulations our customers ask
us about the licenses I have the link of ASF about export licenses, but
I am unable to locate Fineract

http://www.apache.org/licenses/exports/

Is there any link/information related to the Export Authorization
License/compliance of Apache Fineract ?

Regards

Victor

Fineract CN Notification and GSoC 2018 interest

[Courage Angeh]

Hello Everyone,

I have implemented the minimum code required to send Email and SMS
Notification: https://github.com/Anh3h/fineract-cn-notification

on
Fineract CN.
I have not been able to properly test it because my machine lacks the
resources to run demo server. Please someone may help run it and let me
know.
I will be happy to get some feedback so I can improve the solution.
When it becomes ready and good enough I would like to contribute it as a
new Microservice when it's ready by the end of GSoC 2018.


Thanks,
Courage

Re: [VOTE] Apache Fineract 1.1.0

[Ippez Robert]

+1

On Wed, Mar 21, 2018 at 11:43 AM, Isaac Kamga  wrote:

> +1
>
> On Wed, Mar 21, 2018 at 12:12 AM, Nikhil Pawar  wrote:
>
> > Builds successfully.
> > +1 from my side.
> >
> > Regards,
> > Nikhil
> >
> > On Mon, Mar 19, 2018 at 5:05 PM, Avik Ganguly  wrote:
> >
> > > Hello Fineract community,
> > >
> > > We have created the Apache Fineract 1.1.0 release, with the artifacts
> > > below up for a vote.
> > >
> > > These are the goals of this release:
> > >
> > >- Share the new features & bugs fixes that have been developed so
> far,
> > >to give the community a good sense of the upcoming 1.1.0 release
> > >
> > > *For more information including release notes, please see:*
> > > https://cwiki.apache.org/confluence/display/FINERACT/1.
> > > 1.0+-+Apache+Fineract
> > >
> > > *Source & Binary files:*
> > > https://dist.apache.org/repos/dist/dev/fineract/1.1.0/
> > > Source:
> > > https://dist.apache.org/repos/dist/dev/fineract/1.1.0/
> > > apache-fineract-1.1.0-src.tar.gz
> > > Binary/War :
> > >  > > apache-fineract-1.1.0-binary.tar.gz>
> > > https://dist.apache.org/repos/dist/dev/fineract/1.1.0/
> > > apache-fineract-1.1.0-binary.tar.gz
> > >
> > > *Commit to be voted on:*
> > > https://git-wip-us.apache.org/repos/asf?p=fineract.git;a=
> > > commit;h=refs/heads/1.1.0
> > >
> > > *Source build verification steps can be found at:*
> > > Refer 'README.md' in apache-fineract-1.1.0-src.tar.gz
> > >
> > > *Binary Deployment steps can be found at:*
> > > https://cwiki.apache.org/confluence/display/FINERACT/
> > > Fineract+Installation+on+Ubuntu+Server
> > >
> > > *KEYS file containing PGP Keys we use to sign the release: *
> > > https://dist.apache.org/repos/dist/dev/fineract/KEYS
> > >
> > > Vote will be open for 72 hours.
> > >
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > > Let me know if there are any discrepancies in the signing process.
> > >
> > >
> > > Here's my +1
> > > Thanks,
> > > Avik.
> > >
> >
>



-- 
Ippez Roberts
Founder/C.E.O - Swift3 Technologies (U) Ltd
"Redefining Next Generation I/O Systems"
P.O.Box 155, Moyo
UGANDA.
Tel: +256788725408/770602630
Skype ID: ippez.robert1
Email: ippezrob...@gmail.com

Re: [VOTE] Apache Fineract 1.1.0

[Isaac Kamga]

+1

On Wed, Mar 21, 2018 at 12:12 AM, Nikhil Pawar  wrote:

> Builds successfully.
> +1 from my side.
>
> Regards,
> Nikhil
>
> On Mon, Mar 19, 2018 at 5:05 PM, Avik Ganguly  wrote:
>
> > Hello Fineract community,
> >
> > We have created the Apache Fineract 1.1.0 release, with the artifacts
> > below up for a vote.
> >
> > These are the goals of this release:
> >
> >- Share the new features & bugs fixes that have been developed so far,
> >to give the community a good sense of the upcoming 1.1.0 release
> >
> > *For more information including release notes, please see:*
> > https://cwiki.apache.org/confluence/display/FINERACT/1.
> > 1.0+-+Apache+Fineract
> >
> > *Source & Binary files:*
> > https://dist.apache.org/repos/dist/dev/fineract/1.1.0/
> > Source:
> > https://dist.apache.org/repos/dist/dev/fineract/1.1.0/
> > apache-fineract-1.1.0-src.tar.gz
> > Binary/War :
> >  > apache-fineract-1.1.0-binary.tar.gz>
> > https://dist.apache.org/repos/dist/dev/fineract/1.1.0/
> > apache-fineract-1.1.0-binary.tar.gz
> >
> > *Commit to be voted on:*
> > https://git-wip-us.apache.org/repos/asf?p=fineract.git;a=
> > commit;h=refs/heads/1.1.0
> >
> > *Source build verification steps can be found at:*
> > Refer 'README.md' in apache-fineract-1.1.0-src.tar.gz
> >
> > *Binary Deployment steps can be found at:*
> > https://cwiki.apache.org/confluence/display/FINERACT/
> > Fineract+Installation+on+Ubuntu+Server
> >
> > *KEYS file containing PGP Keys we use to sign the release: *
> > https://dist.apache.org/repos/dist/dev/fineract/KEYS
> >
> > Vote will be open for 72 hours.
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Let me know if there are any discrepancies in the signing process.
> >
> >
> > Here's my +1
> > Thanks,
> > Avik.
> >
>

Re: Fineract - Export Authorization

[Myrle Krantz]

Hi Victor,

To my knowledge, no committer or contributor has tried to figure out what
we need to do here. If you want to step in here, your contributions are
welcome!

I’m not sure how to find out the next steps, but I’d start by searching
through the mailing lists of projects that are in the incubator and on the
list you sent us.

Best Regards,
Myrle

On Tue 20. Mar 2018 at 20:36 Victor Manuel Romero Rodriguez <
victor.rom...@fintecheando.mx> wrote:

> Hello Fineract Team,
>
> Recently in Mexico as part of the FinTECH regulations our customers ask
> us about the licenses I have the link of ASF about export licenses, but
> I am unable to locate Fineract
>
> http://www.apache.org/licenses/exports/
>
> Is there any link/information related to the Export Authorization
> License/compliance of Apache Fineract ?
>
> Regards
>
> Victor
>

Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

[Sendoro Juma]

My comments below is related to item no.2 not 3

- Original Message -
From: "Sendoro Juma" 
To: "dev" 
Cc: "mifos-developer" 
Sent: Wednesday, March 21, 2018 8:07:34 AM
Subject: Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

Hello Ed, Dev

On item no. 3 on registration verification

I think mobile phone verification is even more important than email nowadays, 
so it can be both email and phone.. it should be added and I suggest to be a 
MUST.

Regards
Sendoro

- Original Message -
From: "Ed Cable" 
To: "dev" 
Cc: "mifos-developer" 
Sent: Wednesday, March 21, 2018 5:40:22 AM
Subject: Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

Hi all,

As a follow-up to this thread, Sundari has fleshed out some more details
supporting the use cases Nayan had proposed for a client-facing digital
credit app at

https://cwiki.apache.org/confluence/display/FINERACT/Digital+Credit+App

Markus, Myrle, or others - it'd be great to get your input as to how you'd
securely enable clients to access the data needed in such an app.

Ed

On Fri, Jan 26, 2018 at 6:20 PM, Ed Cable  wrote:

> Hi Markus,
>
> Thanks for your replies.
>
> For the rest of the community,
>
> While I know that with the previous iteration of self-service apps, we
> focused on implementing the back-end first and then allowing front-end use
> cases to follow, a good approach this time around would be to get some
> solid client-facing use cases identified and then design the back-end and
> integration with the data to support those use cases. Nayan from RuPie has
> shared some initial use cases he has. I'm working with a Mifos volunteer,
> Sundari Swami, to flesh these out further but wanted to share the initial
> use cases Nayan had presented to stimulate further discussion on what the
> best approach to supporting a client-facing app on Apache Fineract CN that
> would support adequately:
>
> From customer side
>
> UC 1. Client signup with basic data, and spot verification either with OTP
> to mobile number or Aadhaar verification
> UC 2. Customer can enter customer's other details like address, family,
> work, income/expense details, once this data is verified from back office,
> customer can't edit any of these data
> UC 3. Apply for loans
> UC 4. Repay EMI
> UC 5. Preclose his/her loans
> UC 6. Log support request
> UC 7. Upload documents like photo of electricity bills, voter id, passport
> etc, once documents are verified and accepted from back office customer
> cab't edit , delete the verified documents, but customer can upload new
> documents
>
> From organization point of view
>
> UC 1, Offer loan products based below criteria
>
>
>- Location ( Example, Bengaluru has P1 and P2 products where as jaipur
>has P2 and P3 products )
>- Based on customer work profile ( for salaried person offer personal
>loans, for business person offer working capital )
>- based gander, income etc
>
> UC 2. User management, (In Rupie's case they have around six thousand self
>  service users, need effective user management suite, search user, user
> activity tracking etc)
> - So user management has to be a lot more robust than user management from
> the perspective of staff users.
> UC 3.  Push ad-hoc/rule based/event based notification to users
>
> Ed
>
> On Tue, Jan 16, 2018 at 11:58 AM, Markus Geiss  wrote:
>
>> Dear Ed,
>>
>> We at Kuelap have no plans because believe we should never give members,
>> agents, or other third parties direct access to the financial
>> institution's
>> data.
>> Aside from any regulatory standpoint this is a huge flaw in the current
>> system.
>>
>> My company is working on two offline-first clients that we think are more
>> secure
>> architecture; one will provide a reduced set of functionalities for
>> employees
>> working in remote areas; The second one will provide mobile banking
>> functionalities for members of financial institutions.
>>
>> Once the company feels the time is right to share our work, we may propose
>> these apps or at least the secure architecture to the community, but we
>> are
>> not nearly far enough along to do that now.
>>
>> Cheers
>>
>> Markus
>>
>> .::Yagni likes a DRY KISS::.
>>
>>
>> On Tue, Jan 16, 2018 at 3:54 PM Ed Cable  wrote:
>>
>> > Markus, Mark or others who could best respond,
>> >
>> > What is the planned design for enabling third parties (i.e. non-staff)
>> such
>> > as clients, agents, etc to authenticate themselves and access data
>> within
>> > Apache Fineract CN.
>> >
>> > From what I recalled, you were planning to take a more secure approach
>> than
>> > simply providing a self-service API that has access to the full
>> production
>> > database but rather have a separate data layer for self-service 

Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

[Sendoro Juma]

Hello Ed, Dev

On item no. 3 on registration verification

I think mobile phone verification is even more important than email nowadays, 
so it can be both email and phone.. it should be added and I suggest to be a 
MUST.

Regards
Sendoro

- Original Message -
From: "Ed Cable" 
To: "dev" 
Cc: "mifos-developer" 
Sent: Wednesday, March 21, 2018 5:40:22 AM
Subject: Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

Hi all,

As a follow-up to this thread, Sundari has fleshed out some more details
supporting the use cases Nayan had proposed for a client-facing digital
credit app at

https://cwiki.apache.org/confluence/display/FINERACT/Digital+Credit+App

Markus, Myrle, or others - it'd be great to get your input as to how you'd
securely enable clients to access the data needed in such an app.

Ed

On Fri, Jan 26, 2018 at 6:20 PM, Ed Cable  wrote:

> Hi Markus,
>
> Thanks for your replies.
>
> For the rest of the community,
>
> While I know that with the previous iteration of self-service apps, we
> focused on implementing the back-end first and then allowing front-end use
> cases to follow, a good approach this time around would be to get some
> solid client-facing use cases identified and then design the back-end and
> integration with the data to support those use cases. Nayan from RuPie has
> shared some initial use cases he has. I'm working with a Mifos volunteer,
> Sundari Swami, to flesh these out further but wanted to share the initial
> use cases Nayan had presented to stimulate further discussion on what the
> best approach to supporting a client-facing app on Apache Fineract CN that
> would support adequately:
>
> From customer side
>
> UC 1. Client signup with basic data, and spot verification either with OTP
> to mobile number or Aadhaar verification
> UC 2. Customer can enter customer's other details like address, family,
> work, income/expense details, once this data is verified from back office,
> customer can't edit any of these data
> UC 3. Apply for loans
> UC 4. Repay EMI
> UC 5. Preclose his/her loans
> UC 6. Log support request
> UC 7. Upload documents like photo of electricity bills, voter id, passport
> etc, once documents are verified and accepted from back office customer
> cab't edit , delete the verified documents, but customer can upload new
> documents
>
> From organization point of view
>
> UC 1, Offer loan products based below criteria
>
>
>- Location ( Example, Bengaluru has P1 and P2 products where as jaipur
>has P2 and P3 products )
>- Based on customer work profile ( for salaried person offer personal
>loans, for business person offer working capital )
>- based gander, income etc
>
> UC 2. User management, (In Rupie's case they have around six thousand self
>  service users, need effective user management suite, search user, user
> activity tracking etc)
> - So user management has to be a lot more robust than user management from
> the perspective of staff users.
> UC 3.  Push ad-hoc/rule based/event based notification to users
>
> Ed
>
> On Tue, Jan 16, 2018 at 11:58 AM, Markus Geiss  wrote:
>
>> Dear Ed,
>>
>> We at Kuelap have no plans because believe we should never give members,
>> agents, or other third parties direct access to the financial
>> institution's
>> data.
>> Aside from any regulatory standpoint this is a huge flaw in the current
>> system.
>>
>> My company is working on two offline-first clients that we think are more
>> secure
>> architecture; one will provide a reduced set of functionalities for
>> employees
>> working in remote areas; The second one will provide mobile banking
>> functionalities for members of financial institutions.
>>
>> Once the company feels the time is right to share our work, we may propose
>> these apps or at least the secure architecture to the community, but we
>> are
>> not nearly far enough along to do that now.
>>
>> Cheers
>>
>> Markus
>>
>> .::Yagni likes a DRY KISS::.
>>
>>
>> On Tue, Jan 16, 2018 at 3:54 PM Ed Cable  wrote:
>>
>> > Markus, Mark or others who could best respond,
>> >
>> > What is the planned design for enabling third parties (i.e. non-staff)
>> such
>> > as clients, agents, etc to authenticate themselves and access data
>> within
>> > Apache Fineract CN.
>> >
>> > From what I recalled, you were planning to take a more secure approach
>> than
>> > simply providing a self-service API that has access to the full
>> production
>> > database but rather have a separate data layer for self-service users?
>> >
>> > Could you update the community on what the plans are for providing
>> access
>> > to enable these client-facing applications? Is it documented anywhere?
>> >
>> > One reason I ask is it that as the Mifos Initiative thinks about GSOC
>> 2018,
>> > I'd like to consider a project on building out an initial mobile banking
>> >