Fineract-CN running on mobile device - android/ios

[Stephen Agyepong]

I see mifosio/fims-web-app uses angular 2+, which I totally love.

My research shows 2 main ways to build an Angular app for mobile devices is
using (1) Ionic (hybrid/webview) or (2) NativeScript (native).

I was curious how you intend to build it to run on a mobile device or it is
meant for the browser?

Thanks

Re: Upping our truck factor

[Ed Cable]

Avik,

Sorry for the delay in replying to your questions. See my replies inline. I
know we also talked about some of this while in person at the Mentor Summit.



On Sun, Oct 1, 2017 at 8:57 AM, Avik Ganguly 
wrote:

> Hello everyone,
>
> 1) Context :- Last time I merged my organization's MifosX fork, I faced
> difficulties in deciding whether to rebase with MifosX or Fineract. On
> going through the commit history of both in details, I found MifosX had
> more assets related changes whereas Fineract had more liability and
> infrastructure related changes. (I went with Fineract in the end as the
> only thing we really wanted from MifosX was rescheduling which had open
> issues being addressed by Pramod at that time). Based on the commit
> history, I am still surprised that one set of client apps is able to
> support both platforms (which means API contracts has not diverged yet).
> Question :- Am I missing out on something or are the efforts of the
> community ending up in 2 similar codebases for some particular reason?
>

Avik - after we entered incubation at Apache, the mifosx
repository/codebase was deprecated. As you can see from the repo at
https://github.com/openMF/mifosx, the last commit to that codebase was in
February 2016. There shouldn't be any differences in terms of asset or
liability functionalities in Apache Fineract all the code (apart from
Pentaho reports libraries and Hibernate-related code) was moved into Apache
Fineract when mifosx repository was deprecated.

As I think you've already discovered, the main repo for Apache Fineract is
at https://github.com/apache/fineract/. We simply maintain a mirror of it
from openMF github. All pull requests and forking of the repo should be
from the apache/fineract repo.

All that being said, Mifos X the distribute/community release on top of
Apache Fineract maintained by the Mifos Initiative is still active. But it
merely consists of the .WAR file bundled with the web app that is built on
top of the latest stable release of Apache Fineract.

The blog post we made a while back tries to explain the infrastructure of
version control, communication, and issue tracking. I welcome any updates
to that page or incorporating this into the Apache Fineract wiki itself:
http://mifos.org/blog/infrastructure-apache-mifosx/


> 2) Is there any volunteering or dedicated QA engineer who certifies
> releases other than Santosh?  Jenkins making PRs breaking existing tests
> un-mergeable was part of MifosX; any reason for it not being part of
> Fineract?
>
>
Right now for Apache Fineract 1.0 and the Mifos X distribution and apps,
Santosh on contract from Conflux Technologies leads the role. However, over
the longterm and especially with Fineract-CN this has to be a community-led
effort by members of the PMC, individual partners, and volunteers.

Let's start a separate thread on getting continuous integration
successfully running for Apache Fineract. I'm not sure if there are any
restrictions from the Apache side.


> 3) Any particular reason why the release process is mentioned as a
> bottleneck? Is cherry-picking MifosX commits or MifosX picking Fineract
> commits somehow involved as part of release process? Is Nazeer contributing
> to both MifosX and Fineract releases?
>

What is most time-consuming (at least in the past) has been the back and
forth to get code up to community standards and get it generic enough for
shipping with the main release. Nazeer is the lead who guides both the
Apache Fineract release at the Apache level and he also guides the
packaging of the subsequent Mifos X distribution release on top of Apache
Fineract.


>
> Regards,
> Avik.
>
> On Sat, Sep 16, 2017 at 9:33 AM, vishwas 
> wrote:
>
> > Thanks Myrle !
> >
> > Regards,
> > Vishwas
> >
> >
> >
> > > On Sep 15, 2017, at 12:20 AM, Myrle Krantz  wrote:
> > >
> > > Ed and vishwas,
> > >
> > > I've filed an Infra ticket to request moderation privileges for both of
> > you.
> > >
> > > Here:
> > > https://issues.apache.org/jira/browse/INFRA-15089
> > >
> > > Moderation is done via a klugy email interface.  Instructions on how
> > > to use ezmlm to moderate once you have those privileges can be found
> > > here:
> > > https://reference.apache.org/pmc/ml
> > >
> > > Regards,
> > > Myrle
> > >
> > >
> > > On Thu, Sep 14, 2017 at 6:43 PM, vishwas
> > >  wrote:
> > >> Hello All,
> > >>
> > > 1.) Are you doing something that only you are doing, and that you
> > > believe should be shared more widely?
> > >>
> > >> No
> > >>
> > > 2.) What are the reasons why you aren't doing one of the activities
> > on
> > > our "bottleneck" list?
> > >>
> > >> I am currently focusing on a few other things I really want to do and
> > would not be able to take up time consuming activity like reviewing pull
> > requests.
> > >>
> > >> I would be happy to help with moderating lists though.
> > >>

Re: How to debug/run mifox on eclipse

[Stephen Agyepong]

Innocent,

I just went through your pain but it is easy.
You should note that because of an issue with OpenJpa you will not be able
to debug directly from Eclipse.
You run fineract and then attach the debugger to it.
I had luck debugging with Springsource Tool Suite (STS).

Setup and build fineract
$ cd \fineract-provider
$ ..\gradlew tomcatRunWar
Notice that gradlew.bat is at the base-directory but the build.gradle is
inside fineract-provider, that is why you need the ..\
When you run tomcatRunWar you will notice that it is listening on 8005 (if
you did not change this)
Now bring up fineract in STS and make sure there are no errors then
Run/Debug Debug Configuration
Create a Remote Java Application Configuration and point to port: 8005
Set your breakpoint and go at it.

see also:
https://mifosforge.jira.com/wiki/spaces/MDZ/pages/93093939/Eclipse+Setup

Happy Debugging


On Thu, Oct 19, 2017 at 7:45 AM, Innocent Marozva <
innoc...@taatconsulting.com> wrote:

> Hi Developers
>
>
>
> For the past days I have been trying to run/debug Mifos main() classes as
> Java Application locally without success, below are the classes I have
> tried and need help with:
>
>
>
> 1.   ServerWithMariaDB4jApplication how do I embed mariadb on eclipse
> here getting some errors here
>
> 2.   ServerApplication  tried the class to run as Java Application
> checked my localhost and db name and password everyting is fine but getting
> an error:
>
> 3.   SpringBootServerLoginTest when I run this class as Junit test I
> get just a green line
>
>
>
>
>
> Your help will greatly appreciated.
>
>
>
> Regards
>
>
>
> Innocent Marozva
>
>
>
> +263716634105 <+263%2071%20663%204105>
>
>
>
> Skype: innocent.morrison.marozva
>
>
>
> Taat Consulting
>
>
>

Re: [VOTE] Accept Mifos I/O code into the Apache Fineract project as Fineract CN

[Eugene Adjei-Djan]

+1 vote

On Thu, 19 Oct 2017 at 12:26 PM, Stephen Agyepong 
wrote:

> yes, +1 vote
>
> On Wed, Oct 18, 2017 at 5:29 AM, Myrle Krantz  wrote:
>
> > Please vote whether you wish to accept into the Fineract project all
> > of the repositories found at
> >
> > https://github.com/mifosio
> >
> > A yes vote means that we as Apache Fineract will:
> > * Begin the software grant process via the Apache Incubator and the
> > Mifos Initiative.
> > * Collect the necessary software grants, CLA's, and ICLA's from
> > companies and individual contributors to mifosio.
> > * Create Infra tickets to create repositories to move the code into
> > with a preference for gitbox repositories.
> > * Transfer the code to the new repositories.
> >
> > Please be aware that developers are still actively developing, so new
> > commits may come into those repositories during the voting process.
> > With apologies, but I believe this is better than keeping new code out
> > of those repositories for the duration of the vote and dumping it in
> > afterward.
> >
> > Further discussion/votes will be held before we release, make
> > adjustments to JIRA, or make any other significant requests to Infra.
> >
> > Voting will continue until 2/3's of committers have responded but for
> > at least 72 hours.  Non-committers are welcome to provide non-binding
> > votes as well.
> >
> > This is my +1 vote.
> >
> > Best Regards,
> > Myrle Krantz
> > Committer, Apache Fineract
> >
>

Re: [VOTE] Accept Mifos I/O code into the Apache Fineract project as Fineract CN

[Avik Ganguly]

+1

A bit doubtful though on maintaining separate repos for tests
(test-provisioner-identity-organization and
test-provisioner-rhythym-portfolio-accounting, fims e2e, test) and
utilities (service starter, default setup, demo server). Not sure but I
believe some private github account subscriptions has a limit on no. of
repositories which is a bit of concern for me personally if everything is
so granular.

On Oct 18, 2017 5:29 AM, "Myrle Krantz"  wrote:

> Please vote whether you wish to accept into the Fineract project all
> of the repositories found at
>
> https://github.com/mifosio
>
> A yes vote means that we as Apache Fineract will:
> * Begin the software grant process via the Apache Incubator and the
> Mifos Initiative.
> * Collect the necessary software grants, CLA's, and ICLA's from
> companies and individual contributors to mifosio.
> * Create Infra tickets to create repositories to move the code into
> with a preference for gitbox repositories.
> * Transfer the code to the new repositories.
>
> Please be aware that developers are still actively developing, so new
> commits may come into those repositories during the voting process.
> With apologies, but I believe this is better than keeping new code out
> of those repositories for the duration of the vote and dumping it in
> afterward.
>
> Further discussion/votes will be held before we release, make
> adjustments to JIRA, or make any other significant requests to Infra.
>
> Voting will continue until 2/3's of committers have responded but for
> at least 72 hours.  Non-committers are welcome to provide non-binding
> votes as well.
>
> This is my +1 vote.
>
> Best Regards,
> Myrle Krantz
> Committer, Apache Fineract
>

Re: Upping our truck factor

[Myrle Krantz]

Hey Avik,

Your questions are important and I wanted to approach those questions
that I can answer:

2.) With respect to MifosX, I cannot answer this question, but with
respect to Fineract CN, Kuelap has 2 dedicated QA engineers: Riana
Allen and Nina Delvos.  Once we've brought the code in (have you voted
yet? ; o), I hope that they will start writing their tickets on Apache
infrastructure rather than on our private infrastructure.

3.) The bigger problem with the release process is not how long it
takes to package a release (although maybe that too since we haven't
had a release since June).  The bigger problem is that if only one
person knows how to do it, as soon as that person stops work we no
longer have a release process.  You're right that calling that a
bottleneck is inaccurate.

Greets,
Myrle

On Sun, Oct 1, 2017 at 5:57 PM, Avik Ganguly  wrote:
> Hello everyone,
>
> I am not a Apache committer but I was wondering about some items discussed
> in this thread (in the non Fineract-CN context)
>
> 1) Context :- Last time I merged my organization's MifosX fork, I faced
> difficulties in deciding whether to rebase with MifosX or Fineract. On
> going through the commit history of both in details, I found MifosX had
> more assets related changes whereas Fineract had more liability and
> infrastructure related changes. (I went with Fineract in the end as the
> only thing we really wanted from MifosX was rescheduling which had open
> issues being addressed by Pramod at that time). Based on the commit
> history, I am still surprised that one set of client apps is able to
> support both platforms (which means API contracts has not diverged yet).
> Question :- Am I missing out on something or are the efforts of the
> community ending up in 2 similar codebases for some particular reason?
>
> 2) Is there any volunteering or dedicated QA engineer who certifies
> releases other than Santosh?  Jenkins making PRs breaking existing tests
> un-mergeable was part of MifosX; any reason for it not being part of
> Fineract?
>
> 3) Any particular reason why the release process is mentioned as a
> bottleneck? Is cherry-picking MifosX commits or MifosX picking Fineract
> commits somehow involved as part of release process? Is Nazeer contributing
> to both MifosX and Fineract releases?
>
> Regards,
> Avik.
>
> On Sat, Sep 16, 2017 at 9:33 AM, vishwas 
> wrote:
>
>> Thanks Myrle !
>>
>> Regards,
>> Vishwas
>>
>>
>>
>> > On Sep 15, 2017, at 12:20 AM, Myrle Krantz  wrote:
>> >
>> > Ed and vishwas,
>> >
>> > I've filed an Infra ticket to request moderation privileges for both of
>> you.
>> >
>> > Here:
>> > https://issues.apache.org/jira/browse/INFRA-15089
>> >
>> > Moderation is done via a klugy email interface.  Instructions on how
>> > to use ezmlm to moderate once you have those privileges can be found
>> > here:
>> > https://reference.apache.org/pmc/ml
>> >
>> > Regards,
>> > Myrle
>> >
>> >
>> > On Thu, Sep 14, 2017 at 6:43 PM, vishwas
>> >  wrote:
>> >> Hello All,
>> >>
>> > 1.) Are you doing something that only you are doing, and that you
>> > believe should be shared more widely?
>> >>
>> >> No
>> >>
>> > 2.) What are the reasons why you aren't doing one of the activities
>> on
>> > our "bottleneck" list?
>> >>
>> >> I am currently focusing on a few other things I really want to do and
>> would not be able to take up time consuming activity like reviewing pull
>> requests.
>> >>
>> >> I would be happy to help with moderating lists though.
>> >>
>> >> Regards,
>> >> Vishwas
>> >>
>> >>
>> >>
>> >>> On Aug 31, 2017, at 9:05 AM, Gaurav Saini 
>> wrote:
>> >>>
>> >>> Hello Myrle,
>> >>>
>> >>> Sorry for delayed reply. Below are my answers
>> >>>
>> >>> On Tue, Aug 29, 2017 at 6:57 PM, Myrle Krantz 
>> wrote:
>> >>>
>>  Hi Fineracters,
>> 
>>  There are 9 PMC members who have not responded (8 if we excuse
>>  Nazeer).  As a reminder, the questions are:
>> 
>>  1.) Are you doing something that only you are doing, and that you
>>  believe should be shared more widely?
>> 
>> >>>
>> >>> No
>> >>>
>> >>>
>>  2.) What are the reasons why you aren't merging PRs or helping out
>>  with releases?
>> 
>> 
>> >>> My main expertise was on frontend mainly, but recently after looking in
>> >>> Fineract CN I am really interested to get started with Fineract CN.
>> >>>
>> >>> Also, I saw that new Fineract CN has a frontend project based on
>> >>> typescript, material so I am really to interested to contribute on that
>> >>> right now also.
>> >>>
>> >>> Thanks
>> >>> Gaurav
>> >>>
>> >>>
>>  I would appreciate a response.  You might also want to say, "I'm too
>>  busy right now", or "I'm waiting for Fineract CN", or "I've lost
>>  confidence that the project can help me achieve my goals".  If that's
>>  the 

How to debug/run mifox on eclipse

[Innocent Marozva]

Hi Developers 

 

For the past days I have been trying to run/debug Mifos main() classes as
Java Application locally without success, below are the classes I have tried
and need help with:

 

1.   ServerWithMariaDB4jApplication how do I embed mariadb on eclipse
here getting some errors here 

2.   ServerApplication  tried the class to run as Java Application
checked my localhost and db name and password everyting is fine but getting
an error:

3.   SpringBootServerLoginTest when I run this class as Junit test I get
just a green line 

 

 

Your help will greatly appreciated.

 

Regards 

 

Innocent Marozva 

 

+263716634105

 

Skype: innocent.morrison.marozva

 

Taat Consulting 



 

Re: [VOTE] Accept Mifos I/O code into the Apache Fineract project as Fineract CN

[Help and Development Organization HDO]

+1



Regards

Khalid Javed Bhatti

Help and Development Organization

Pakistan



From: vish...@confluxtechnologies.com 
Sent: Thursday, October 19, 2017 2:32 PM
To: dev@fineract.apache.org
Subject: Re: [VOTE] Accept Mifos I/O code into the Apache Fineract project as 
Fineract CN

+1

Regards,
Vishwas

> On Oct 19, 2017, at 1:11 AM, Sharan Foga  wrote:
>
> +1
>
> Thanks
> Sharan
>
>> On 18/10/17 11:29, Myrle Krantz wrote:
>> Please vote whether you wish to accept into the Fineract project all
>> of the repositories found at
>>
>> https://github.com/mifosio
[https://avatars0.githubusercontent.com/u/14039122?s=200=4]

Mifos I/O · GitHub
github.com
GitHub is where people build software. More than 25 million people use GitHub 
to discover, fork, and contribute to over 69 million projects.


>>
>> A yes vote means that we as Apache Fineract will:
>> * Begin the software grant process via the Apache Incubator and the
>> Mifos Initiative.
>> * Collect the necessary software grants, CLA's, and ICLA's from
>> companies and individual contributors to mifosio.
>> * Create Infra tickets to create repositories to move the code into
>> with a preference for gitbox repositories.
>> * Transfer the code to the new repositories.
>>
>> Please be aware that developers are still actively developing, so new
>> commits may come into those repositories during the voting process.
>> With apologies, but I believe this is better than keeping new code out
>> of those repositories for the duration of the vote and dumping it in
>> afterward.
>>
>> Further discussion/votes will be held before we release, make
>> adjustments to JIRA, or make any other significant requests to Infra.
>>
>> Voting will continue until 2/3's of committers have responded but for
>> at least 72 hours.  Non-committers are welcome to provide non-binding
>> votes as well.
>>
>> This is my +1 vote.
>>
>> Best Regards,
>> Myrle Krantz
>> Committer, Apache Fineract
>

Re: [VOTE] Accept Mifos I/O code into the Apache Fineract project as Fineract CN

[vishwas]

+1

Regards,
Vishwas

> On Oct 19, 2017, at 1:11 AM, Sharan Foga  wrote:
> 
> +1
> 
> Thanks
> Sharan
> 
>> On 18/10/17 11:29, Myrle Krantz wrote:
>> Please vote whether you wish to accept into the Fineract project all
>> of the repositories found at
>> 
>> https://github.com/mifosio
>> 
>> A yes vote means that we as Apache Fineract will:
>> * Begin the software grant process via the Apache Incubator and the
>> Mifos Initiative.
>> * Collect the necessary software grants, CLA's, and ICLA's from
>> companies and individual contributors to mifosio.
>> * Create Infra tickets to create repositories to move the code into
>> with a preference for gitbox repositories.
>> * Transfer the code to the new repositories.
>> 
>> Please be aware that developers are still actively developing, so new
>> commits may come into those repositories during the voting process.
>> With apologies, but I believe this is better than keeping new code out
>> of those repositories for the duration of the vote and dumping it in
>> afterward.
>> 
>> Further discussion/votes will be held before we release, make
>> adjustments to JIRA, or make any other significant requests to Infra.
>> 
>> Voting will continue until 2/3's of committers have responded but for
>> at least 72 hours.  Non-committers are welcome to provide non-binding
>> votes as well.
>> 
>> This is my +1 vote.
>> 
>> Best Regards,
>> Myrle Krantz
>> Committer, Apache Fineract
> 

Re: [VOTE] Accept Mifos I/O code into the Apache Fineract project as Fineract CN

[Sharan Foga]

+1

Thanks
Sharan

On 18/10/17 11:29, Myrle Krantz wrote:

Please vote whether you wish to accept into the Fineract project all
of the repositories found at

https://github.com/mifosio

A yes vote means that we as Apache Fineract will:
* Begin the software grant process via the Apache Incubator and the
Mifos Initiative.
* Collect the necessary software grants, CLA's, and ICLA's from
companies and individual contributors to mifosio.
* Create Infra tickets to create repositories to move the code into
with a preference for gitbox repositories.
* Transfer the code to the new repositories.

Please be aware that developers are still actively developing, so new
commits may come into those repositories during the voting process.
With apologies, but I believe this is better than keeping new code out
of those repositories for the duration of the vote and dumping it in
afterward.

Further discussion/votes will be held before we release, make
adjustments to JIRA, or make any other significant requests to Infra.

Voting will continue until 2/3's of committers have responded but for
at least 72 hours.  Non-committers are welcome to provide non-binding
votes as well.

This is my +1 vote.

Best Regards,
Myrle Krantz
Committer, Apache Fineract