Re: Code Committ Process for Fineract Committers

[Mexina Daniel]

Hello Steve

I managed to run integration test and only 7 were failing which i assume are 
the few left that you are looking at, thank you for the help

I was merging a PR #437 which does not relate with the failing tests, but when 
i push with my apache credentials it says "Invalid username or password" while 
the same credentials can login https://id.apache.org/.

Am i using the wrong credentials?

Regards

- Original Message -
From: "sconrad1" 
To: "dev" 
Cc: "Myrle Krantz" 
Sent: Tuesday, August 21, 2018 11:30:24 PM
Subject: Re: Code Committ Process for Fineract Committers

Hi all -

I have promoted some fixes for integration tests. There is still one test
that is failing that I am looking at, but this should help enable
contributors to run integration tests every time they promote a change.

A few tips on running integration tests:

1) Make sure that you drop and re-add the mifostenant-default database
before you run tests.
2) You should still be using MySQL 5.6 or turn off ONLY_FULL_GROUP_BY in
your MySQL 5.7 installation
3) You may need to set the timezone in your MySQL configuration (usually
/etc/mysql/my.cnf) to 'Asia/Kolkata' - if you don't do this, you may see
some failures with non-matching timestamps.

Please let me know if you have any issues with running integration tests.
And please make sure that tests are running cleanly with each commit you
make.

Thanks,
Steve

On Mon, Aug 20, 2018 at 9:31 AM Steve Conrad  wrote:

> Hi all -
>
> I am working this morning to get all of the integration tests back up and
> running, which will facilitate merging of open PRs. I will let you know
> when I have that done - hopefully today.
>
> Thanks,
> Steve
>
>
> On Mon, Aug 20, 2018 at 9:12 AM Mexina Daniel  wrote:
>
>> Hello Myrle
>>
>> Thank you for the more clarifications you have provided.
>>
>> For now, is it okay to merge the PRs i have tested and find they work
>> just fine in the application and there is no need to run integration tests?
>>
>> Because there are un-merged PRs that are needed in the community.
>>
>> Regards
>>
>> - Original Message -
>> From: "Myrle Krantz" 
>> To: "dev" 
>> Sent: Monday, August 20, 2018 3:36:03 PM
>> Subject: Re: Code Committ Process for Fineract Committers
>>
>> Hi Mexina,
>>
>> Coming back to your questions
>>
>> 1.) Theoretically we should be making sure all the integration tests
>> work before we merge a PR.  But we currently have no continuous
>> integration (CI) processes in place to build or run those integration
>> tests which means that it's up to individual developers to do it
>> themselves.  Hence it is possible for a committer to merge something
>> which breaks an integration test.  For this reason I suggest running
>> the integration tests on the changeset you want to merge your changes
>> with to get a baseline.  This is an area we need to do better in, and
>> I welcome anyone who wants to put in the time.
>>
>> By the way, the attachment you mentioned didn't reach the mailing
>> list.  A lot of people use pastebin and post links, but I'm not a fan
>> of that approach since that stuff doesn't get archived.  For pure text
>> files, you may be able to copy/paste out the interesting parts into
>> your email.  Whatever approach you chose, if you want to be sure that
>> what you sent also reached the mailing list, you can check the
>> archives here: https://lists.apache.org/list.html?dev@fineract.apache.org
>>
>> 2.) You've already found the answer to your question, but I wanted to
>> make sure it was clear.  The command you were looking for in the case
>> of pull request 444 was:
>> git pull https://github.com/wkk91193/incubator-fineract
>> extend-mifos-data-import-tool-branch-all-modules
>>
>> Basically you're telling git where to get the code from.  In this case
>> it's in the github account of the user who created the pull request.
>> This is not a standard case either since the its in a repo in that
>> account which has a slightly different name than the repo the pull
>> request was made to.  The second parameter to git pull is the name of
>> the branch within that repository being pulled from.
>>
>> I hope that helps.  I'm going to try to find a way to make this less
>> of a stumbling block.
>>
>> I'll be more responsive for the coming week.  If you want to ask me
>> questions on the list, now is a good time.
>>
>> Best Regards,
>> Myrle
>>
>> On Mon, Aug 6, 2018 at 2:35 PM Mexina Daniel  wrote:
>> >
>> > Hello Steve
>> >
>> > See the attachment, is the result i get when i run integrationTest
>> >
>> > What is a work around of this?
>> >
>> > Regards
>> >
>> > - Original Message -
>> > From: "Mexina Daniel" 
>> > To: "sconrad1" 
>> > Cc: "Myrle Krantz" , "Avik Ganguly" <
>> avikganguly...@gmail.com>, "edcable" , "Isaac Kamga" <
>> isaac.ka...@mifos.org>, "santosh" ,
>> "Nazeer Hussain Shaik" , "nayan ambali" <
>> nayan.amb...@gmail.com>, "shruthi" ,
>> "dev" 
>> > Sent: Thursday, August 2, 2018 10:16:39 AM
>> > Subject: Re: Code

Re: EVENT: Google Summer of Code Showcase Part 1 - August 16, 2018 at 1300GMT via GoToTraining

[Ebenezer Graham]

Works for me too

On Wed, 15 Aug 2018, 07:15 Ed Cable,  wrote:

> Hopefully you've seen all the great interactions of the Google Summer of
> Code interns spread across the Mifos and Apache Fineract communities.
> They've been hard at work all summer even though we only just formally
> introduced them on the Mifos blog at
> http://mifos.org/blog/meet-the-2018-gsoc-interns/
>
> They're ready to showcase and demo the product of their efforts in a series
> of showcases coming up over the course of the next two weeks. With a total
> of 18 interns (17 through GSOC and one independently), we have a lot of
> great work to highlight
>
> Part 1 will be Thursday August 16, 2018 at 1300GMT via GoToTraining.
>
> Please register at https://attendee.gototraining.com/r/5562581450304728065
>
> In this showcase, Abhay and Anwesh will cover our the rewrite of the Mifos
> X web app into Angular 6, Saksham will demo Mifos Mobile 3.0, Ankur will
> showcase he mobile wallet 2.0 project, Kumaranath will summarize
> performance enhancements to Fineract, Ebenezer will show off he new
> SMS/email microservice for Fineract CN, Lalit will share his
> scorecard-based machine learning, and Cabrel the bulk data import tool for
> Fineract CN.
>
> Part 2 will be Thursday August 23, 2018 at 1300 GMT via GoToTraining.
>
> Please register at https://attendee.gototraining.com/r/1497705654114562561
>
> In this showcase, Aksh will be demoing the The Android Field Operations App
> 5.0, Manish showcasing the first client-facing mobile banking app on
> Fineract CN, Mohak and Dilpreet highlighting, Fineract CN Mobile 2.0,
> Ruphine and Pembe sharing their implementation of group management on the
> back and front-end for Fineract CN, Dingfan demoing the Mifos Chatbot,
> Sanyam showcasing our Mifos payment gateway for mobile money integration,
> and Courage sharing her work on containerization for Fineract CN.
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>

CHANGE: Google Summer of Code Showcase Part 2 moved from August 23, 2018 at 1300GMT to August 24 via GoToTraining

[Ed Cable]

Hello all, I apologize for the last minute change in schedule. We had to
postpone today's showcase until the exact same time tomorrow.

Your registration will be updated.

Thank you for your flexibility.

Ed

On Tue, Aug 14, 2018, 20:14 Ed Cable  wrote:

> Hopefully you've seen all the great interactions of the Google Summer of
> Code interns spread across the Mifos and Apache Fineract communities.
> They've been hard at work all summer even though we only just formally
> introduced them on the Mifos blog at
> http://mifos.org/blog/meet-the-2018-gsoc-interns/
>
> They're ready to showcase and demo the product of their efforts in a
> series of showcases coming up over the course of the next two weeks. With a
> total of 18 interns (17 through GSOC and one independently), we have a lot
> of great work to highlight
>
> Part 1 will be Thursday August 16, 2018 at 1300GMT via GoToTraining.
>
> Please register at https://attendee.gototraining.com/r/5562581450304728065
>
> In this showcase, Abhay and Anwesh will cover our the rewrite of the Mifos
> X web app into Angular 6, Saksham will demo Mifos Mobile 3.0, Ankur will
> showcase he mobile wallet 2.0 project, Kumaranath will summarize
> performance enhancements to Fineract, Ebenezer will show off he new
> SMS/email microservice for Fineract CN, Lalit will share his
> scorecard-based machine learning, and Cabrel the bulk data import tool for
> Fineract CN.
>
> Part 2 will be Thursday August 23, 2018 at 1300 GMT via GoToTraining.
>
> Please register at https://attendee.gototraining.com/r/1497705654114562561
>
> In this showcase, Aksh will be demoing the The Android Field Operations
> App 5.0, Manish showcasing the first client-facing mobile banking app on
> Fineract CN, Mohak and Dilpreet highlighting, Fineract CN Mobile 2.0,
> Ruphine and Pembe sharing their implementation of group management on the
> back and front-end for Fineract CN, Dingfan demoing the Mifos Chatbot,
> Sanyam showcasing our Mifos payment gateway for mobile money integration,
> and Courage sharing her work on containerization for Fineract CN.
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>

Re: Code Committ Process for Fineract Committers

[Steve Conrad]

Hi Mexina -

That is strange - those credentials should be the correct ones. Ed or
Myrle, do you know who Mexina could contact at Apache to ensure that she
has permission to commit on the Fineract repo?

Thanks,
Steve


On Thu, Aug 23, 2018 at 2:30 AM Mexina Daniel  wrote:

> Hello Steve
>
> I managed to run integration test and only 7 were failing which i assume
> are the few left that you are looking at, thank you for the help
>
> I was merging a PR #437 which does not relate with the failing tests, but
> when i push with my apache credentials it says "Invalid username or
> password" while the same credentials can login https://id.apache.org/.
>
> Am i using the wrong credentials?
>
> Regards
>
> - Original Message -
> From: "sconrad1" 
> To: "dev" 
> Cc: "Myrle Krantz" 
> Sent: Tuesday, August 21, 2018 11:30:24 PM
> Subject: Re: Code Committ Process for Fineract Committers
>
> Hi all -
>
> I have promoted some fixes for integration tests. There is still one test
> that is failing that I am looking at, but this should help enable
> contributors to run integration tests every time they promote a change.
>
> A few tips on running integration tests:
>
> 1) Make sure that you drop and re-add the mifostenant-default database
> before you run tests.
> 2) You should still be using MySQL 5.6 or turn off ONLY_FULL_GROUP_BY in
> your MySQL 5.7 installation
> 3) You may need to set the timezone in your MySQL configuration (usually
> /etc/mysql/my.cnf) to 'Asia/Kolkata' - if you don't do this, you may see
> some failures with non-matching timestamps.
>
> Please let me know if you have any issues with running integration tests.
> And please make sure that tests are running cleanly with each commit you
> make.
>
> Thanks,
> Steve
>
> On Mon, Aug 20, 2018 at 9:31 AM Steve Conrad  wrote:
>
> > Hi all -
> >
> > I am working this morning to get all of the integration tests back up and
> > running, which will facilitate merging of open PRs. I will let you know
> > when I have that done - hopefully today.
> >
> > Thanks,
> > Steve
> >
> >
> > On Mon, Aug 20, 2018 at 9:12 AM Mexina Daniel 
> wrote:
> >
> >> Hello Myrle
> >>
> >> Thank you for the more clarifications you have provided.
> >>
> >> For now, is it okay to merge the PRs i have tested and find they work
> >> just fine in the application and there is no need to run integration
> tests?
> >>
> >> Because there are un-merged PRs that are needed in the community.
> >>
> >> Regards
> >>
> >> - Original Message -
> >> From: "Myrle Krantz" 
> >> To: "dev" 
> >> Sent: Monday, August 20, 2018 3:36:03 PM
> >> Subject: Re: Code Committ Process for Fineract Committers
> >>
> >> Hi Mexina,
> >>
> >> Coming back to your questions
> >>
> >> 1.) Theoretically we should be making sure all the integration tests
> >> work before we merge a PR.  But we currently have no continuous
> >> integration (CI) processes in place to build or run those integration
> >> tests which means that it's up to individual developers to do it
> >> themselves.  Hence it is possible for a committer to merge something
> >> which breaks an integration test.  For this reason I suggest running
> >> the integration tests on the changeset you want to merge your changes
> >> with to get a baseline.  This is an area we need to do better in, and
> >> I welcome anyone who wants to put in the time.
> >>
> >> By the way, the attachment you mentioned didn't reach the mailing
> >> list.  A lot of people use pastebin and post links, but I'm not a fan
> >> of that approach since that stuff doesn't get archived.  For pure text
> >> files, you may be able to copy/paste out the interesting parts into
> >> your email.  Whatever approach you chose, if you want to be sure that
> >> what you sent also reached the mailing list, you can check the
> >> archives here:
> https://lists.apache.org/list.html?dev@fineract.apache.org
> >>
> >> 2.) You've already found the answer to your question, but I wanted to
> >> make sure it was clear.  The command you were looking for in the case
> >> of pull request 444 was:
> >> git pull https://github.com/wkk91193/incubator-fineract
> >> extend-mifos-data-import-tool-branch-all-modules
> >>
> >> Basically you're telling git where to get the code from.  In this case
> >> it's in the github account of the user who created the pull request.
> >> This is not a standard case either since the its in a repo in that
> >> account which has a slightly different name than the repo the pull
> >> request was made to.  The second parameter to git pull is the name of
> >> the branch within that repository being pulled from.
> >>
> >> I hope that helps.  I'm going to try to find a way to make this less
> >> of a stumbling block.
> >>
> >> I'll be more responsive for the coming week.  If you want to ask me
> >> questions on the list, now is a good time.
> >>
> >> Best Regards,
> >> Myrle
> >>
> >> On Mon, Aug 6, 2018 at 2:35 PM Mexina Daniel 
> wrote:
> >> >
> >> > Hello Steve
> >> >
> >> > See th

Re: Code Committ Process for Fineract Committers

[Myrle Krantz]

Hey Mexina, Steve,

The best thing to do is to file a Jira ticket on the INFRA project, because
as a committer, Mexina *should* have access. If you need help with that,
let me know. But before you do that can you share with me the exact
commands you’re using, and how you’ve got the remotes on your local git
repo set up?

Thank you for your persistence,
Myrle

On Thu 23. Aug 2018 at 15:15 Steve Conrad  wrote:

> Hi Mexina -
>
> That is strange - those credentials should be the correct ones. Ed or
> Myrle, do you know who Mexina could contact at Apache to ensure that she
> has permission to commit on the Fineract repo?
>
> Thanks,
> Steve
>
>
> On Thu, Aug 23, 2018 at 2:30 AM Mexina Daniel  wrote:
>
>> Hello Steve
>>
>> I managed to run integration test and only 7 were failing which i assume
>> are the few left that you are looking at, thank you for the help
>>
>> I was merging a PR #437 which does not relate with the failing tests, but
>> when i push with my apache credentials it says "Invalid username or
>> password" while the same credentials can login https://id.apache.org/.
>>
>> Am i using the wrong credentials?
>>
>> Regards
>>
>> - Original Message -
>> From: "sconrad1" 
>> To: "dev" 
>> Cc: "Myrle Krantz" 
>> Sent: Tuesday, August 21, 2018 11:30:24 PM
>> Subject: Re: Code Committ Process for Fineract Committers
>>
>> Hi all -
>>
>> I have promoted some fixes for integration tests. There is still one test
>> that is failing that I am looking at, but this should help enable
>> contributors to run integration tests every time they promote a change.
>>
>> A few tips on running integration tests:
>>
>> 1) Make sure that you drop and re-add the mifostenant-default database
>> before you run tests.
>> 2) You should still be using MySQL 5.6 or turn off ONLY_FULL_GROUP_BY in
>> your MySQL 5.7 installation
>> 3) You may need to set the timezone in your MySQL configuration (usually
>> /etc/mysql/my.cnf) to 'Asia/Kolkata' - if you don't do this, you may see
>> some failures with non-matching timestamps.
>>
>> Please let me know if you have any issues with running integration tests.
>> And please make sure that tests are running cleanly with each commit you
>> make.
>>
>> Thanks,
>> Steve
>>
>> On Mon, Aug 20, 2018 at 9:31 AM Steve Conrad  wrote:
>>
>> > Hi all -
>> >
>> > I am working this morning to get all of the integration tests back up
>> and
>> > running, which will facilitate merging of open PRs. I will let you know
>> > when I have that done - hopefully today.
>> >
>> > Thanks,
>> > Steve
>> >
>> >
>> > On Mon, Aug 20, 2018 at 9:12 AM Mexina Daniel 
>> wrote:
>> >
>> >> Hello Myrle
>> >>
>> >> Thank you for the more clarifications you have provided.
>> >>
>> >> For now, is it okay to merge the PRs i have tested and find they work
>> >> just fine in the application and there is no need to run integration
>> tests?
>> >>
>> >> Because there are un-merged PRs that are needed in the community.
>> >>
>> >> Regards
>> >>
>> >> - Original Message -
>> >> From: "Myrle Krantz" 
>> >> To: "dev" 
>> >> Sent: Monday, August 20, 2018 3:36:03 PM
>> >> Subject: Re: Code Committ Process for Fineract Committers
>> >>
>> >> Hi Mexina,
>> >>
>> >> Coming back to your questions
>> >>
>> >> 1.) Theoretically we should be making sure all the integration tests
>> >> work before we merge a PR.  But we currently have no continuous
>> >> integration (CI) processes in place to build or run those integration
>> >> tests which means that it's up to individual developers to do it
>> >> themselves.  Hence it is possible for a committer to merge something
>> >> which breaks an integration test.  For this reason I suggest running
>> >> the integration tests on the changeset you want to merge your changes
>> >> with to get a baseline.  This is an area we need to do better in, and
>> >> I welcome anyone who wants to put in the time.
>> >>
>> >> By the way, the attachment you mentioned didn't reach the mailing
>> >> list.  A lot of people use pastebin and post links, but I'm not a fan
>> >> of that approach since that stuff doesn't get archived.  For pure text
>> >> files, you may be able to copy/paste out the interesting parts into
>> >> your email.  Whatever approach you chose, if you want to be sure that
>> >> what you sent also reached the mailing list, you can check the
>> >> archives here:
>> https://lists.apache.org/list.html?dev@fineract.apache.org
>> >>
>> >> 2.) You've already found the answer to your question, but I wanted to
>> >> make sure it was clear.  The command you were looking for in the case
>> >> of pull request 444 was:
>> >> git pull https://github.com/wkk91193/incubator-fineract
>> >> extend-mifos-data-import-tool-branch-all-modules
>> >>
>> >> Basically you're telling git where to get the code from.  In this case
>> >> it's in the github account of the user who created the pull request.
>> >> This is not a standard case either since the its in a repo in that
>> >> account which has a slightly diffe

Re: [Discussion] Fineract CN SMS & Email Notifications Project

[Ebenezer Graham]

Hi all,

@Markus: The ActiveMQ configuration worked :). I am now getting one
invocation. Thanks for the support,

However, the entity creation is still not working but I think Myrle's
feedback on my PR might do the trick.

@Myrle: I have updated the private cwiki page with the credentials, thanks.
Also, I have incorporated most of the feedback shared on the PRs
and added a few comments.
For the Domain objects, I have created tests for each of them. I will add
more rigorous tests to it after making significant progress with the
web-app interface
and the connection timeout problem when the system is up. More about the
issue below
The issue has to do with service timeouts. https://pastebin.com/f8UAkvsa
*N*
* B: *the email and SMS services are correctly configured and do send out
emails and SMS
in the component test. However, when I make an actual build the mail
connection times out even though it
has been invoked

@Awasum like you suggested, I have changed the JavaMail version to 1.4.1
RELEASE and it works fine. Thanks
I have created values in the ext.versions for the Twilio API and
JavaMail in the shared.gradle

My best guess is that there is something interrupting or inhibiting the
connection when the entire system is
up and running.

Looking forward to your feedback.

On 22 August 2018 at 16:03, Markus Geiss  wrote:

> Hey Ebenezer,
>
> hope this finds you well. (;
>
> looking at the two stack traces you've provided here is my take on it.
>
> The error while storing configuration is caused by a field in the database
> 'sender_number' being declared as not null, but no data is provided. In the
> create method of SMSConfiguration you are not handling the sender number at
> all. I would recommend to either use a builder pattern or just use plain
> getter/setter to create the instance.
>
> With regards to receiving multiple (3) events, this is caused by the way
> acitvemq is configured in your service. The default
> for activemq.concurrency is 3-10, if you set this to 1-1 it will only
> listen with 1 concurrent thread.
>
> Hope this helps.
>
> Cheers
>
> Markus
>
>
>
> On Wed, Aug 22, 2018 at 1:40 PM Ebenezer Graham 
> wrote:
>
> > Thanks myrle,
> >
> > I have already created a demo email account called
> > fineractcnnotificationd...@gmail.com and I created it for the sole
> purpose
> > of testing emails for this service and for other contributors to use.
> > Please advise me on this approach.
> >
> > Also, the password for ebenezergraha...@gmail.com and akyencorp@gmail
> are
> > no longer valid. I created app passwords and so I have already deleted
> > those app passwords for my live account and are no longer valid.
> >
> > *Error:*
> > In an attempt to store configurations from the repository I get this
> error:
> > https://pastebin.com/WqvRwXvB
> >
> > Please check: shouldCreateSMSConfigurationEntity()
> > https://github.com/ebenezergraham/fineract-cn-notifications/
> > blob/develop/component-test/src/main/java/org/apache/
> > fineract/cn/notification/TestSMSService.java
> >
> > I am able to retrieve stored configurations but I am unable to create a
> > configuration and store. Same issue for email repository
> >
> > Second Issue: https://pastebin.com/LKz7HcGy
> > I have managed to authenticate with identity and getting customer object,
> > however, when I trigger an invent from the fims web app, I get 3
> > invocations from the ActiveMQ. How can I resolve this issue? Are my
> > assumptions correct to begin with?
> >
> >
> > *At your service,*
> >
> > *Ebenezer Graham*
> >
> > *BSc (Hons) Computing*
> >
> >
> > [image: EmailSignature.png]
> >
> > African Leadership University,
> >
> > Power Mill Road, Pamplemousses,
> >
> > Mauritius.
> >
> >
> >
> > *skype*:
> > ebenezer.graham
> > GitHub  | LinkedIn
> >  | Twitter
> >  | Facebook
> > 
> > www.pactmart.com | Freelancing made easy.
> >
> >
> > *“Talk is cheap, show me the code.” *- *Linus Torvalds*
> >
> >
> >
> > On 22 August 2018 at 15:10, Ebenezer Graham 
> > wrote:
> >
> > > Thanks myrle,
> > >
> > > I have already created a demo email account called
> > > fineractcnnotificationd...@gmail.com and I created it for the sole
> > > purpose of testing emails for this service and for other contributors
> > > to use. Please advise me on this approach.
> > >
> > > Also, the password for ebenezergraha...@gmail.com and akyencorp@gmail
> > are
> > > not the real passwords. I created app passwords and so I have already
> > > deleted those app passwords for my live account and are no longer
> valid.
> > >
> > > *Error:*
> > > In an attempt to store configurations from the repository I get this
> > error:
> > >
> > > Please check: shouldCreateSMSConfigurationEntity()
> > >
> > https://github.com/ebenezergraham/fineract-cn-notifications/
> blob/develop/
> > > component-test/src/main/java/org/apache/fineract/cn/
> > > notific

Re: Code Committ Process for Fineract Committers

[Mexina Daniel]

Hello Myrle

Your question was an eye opener to my problem, the credentials was invalid 
because the repo i was working on was cloned from 
https://github.com/apache/fineract while i was to clone from 
https://git-wip-us.apache.org/repos/asf/fineract.git for merging PR.

Thank you and i was able to merge the PR.

Best Regards

- Original Message -
From: "Myrle Krantz" 
To: "sconrad1" 
Cc: "dev" , "Mexina Daniel" 
Sent: Thursday, August 23, 2018 4:58:10 PM
Subject: Re: Code Committ Process for Fineract Committers

Hey Mexina, Steve,

The best thing to do is to file a Jira ticket on the INFRA project, because
as a committer, Mexina *should* have access. If you need help with that,
let me know. But before you do that can you share with me the exact
commands you’re using, and how you’ve got the remotes on your local git
repo set up?

Thank you for your persistence,
Myrle

On Thu 23. Aug 2018 at 15:15 Steve Conrad  wrote:

> Hi Mexina -
>
> That is strange - those credentials should be the correct ones. Ed or
> Myrle, do you know who Mexina could contact at Apache to ensure that she
> has permission to commit on the Fineract repo?
>
> Thanks,
> Steve
>
>
> On Thu, Aug 23, 2018 at 2:30 AM Mexina Daniel  wrote:
>
>> Hello Steve
>>
>> I managed to run integration test and only 7 were failing which i assume
>> are the few left that you are looking at, thank you for the help
>>
>> I was merging a PR #437 which does not relate with the failing tests, but
>> when i push with my apache credentials it says "Invalid username or
>> password" while the same credentials can login https://id.apache.org/.
>>
>> Am i using the wrong credentials?
>>
>> Regards
>>
>> - Original Message -
>> From: "sconrad1" 
>> To: "dev" 
>> Cc: "Myrle Krantz" 
>> Sent: Tuesday, August 21, 2018 11:30:24 PM
>> Subject: Re: Code Committ Process for Fineract Committers
>>
>> Hi all -
>>
>> I have promoted some fixes for integration tests. There is still one test
>> that is failing that I am looking at, but this should help enable
>> contributors to run integration tests every time they promote a change.
>>
>> A few tips on running integration tests:
>>
>> 1) Make sure that you drop and re-add the mifostenant-default database
>> before you run tests.
>> 2) You should still be using MySQL 5.6 or turn off ONLY_FULL_GROUP_BY in
>> your MySQL 5.7 installation
>> 3) You may need to set the timezone in your MySQL configuration (usually
>> /etc/mysql/my.cnf) to 'Asia/Kolkata' - if you don't do this, you may see
>> some failures with non-matching timestamps.
>>
>> Please let me know if you have any issues with running integration tests.
>> And please make sure that tests are running cleanly with each commit you
>> make.
>>
>> Thanks,
>> Steve
>>
>> On Mon, Aug 20, 2018 at 9:31 AM Steve Conrad  wrote:
>>
>> > Hi all -
>> >
>> > I am working this morning to get all of the integration tests back up
>> and
>> > running, which will facilitate merging of open PRs. I will let you know
>> > when I have that done - hopefully today.
>> >
>> > Thanks,
>> > Steve
>> >
>> >
>> > On Mon, Aug 20, 2018 at 9:12 AM Mexina Daniel 
>> wrote:
>> >
>> >> Hello Myrle
>> >>
>> >> Thank you for the more clarifications you have provided.
>> >>
>> >> For now, is it okay to merge the PRs i have tested and find they work
>> >> just fine in the application and there is no need to run integration
>> tests?
>> >>
>> >> Because there are un-merged PRs that are needed in the community.
>> >>
>> >> Regards
>> >>
>> >> - Original Message -
>> >> From: "Myrle Krantz" 
>> >> To: "dev" 
>> >> Sent: Monday, August 20, 2018 3:36:03 PM
>> >> Subject: Re: Code Committ Process for Fineract Committers
>> >>
>> >> Hi Mexina,
>> >>
>> >> Coming back to your questions
>> >>
>> >> 1.) Theoretically we should be making sure all the integration tests
>> >> work before we merge a PR.  But we currently have no continuous
>> >> integration (CI) processes in place to build or run those integration
>> >> tests which means that it's up to individual developers to do it
>> >> themselves.  Hence it is possible for a committer to merge something
>> >> which breaks an integration test.  For this reason I suggest running
>> >> the integration tests on the changeset you want to merge your changes
>> >> with to get a baseline.  This is an area we need to do better in, and
>> >> I welcome anyone who wants to put in the time.
>> >>
>> >> By the way, the attachment you mentioned didn't reach the mailing
>> >> list.  A lot of people use pastebin and post links, but I'm not a fan
>> >> of that approach since that stuff doesn't get archived.  For pure text
>> >> files, you may be able to copy/paste out the interesting parts into
>> >> your email.  Whatever approach you chose, if you want to be sure that
>> >> what you sent also reached the mailing list, you can check the
>> >> archives here:
>> https://lists.apache.org/list.html?dev@fineract.apache.org
>> >>
>> >> 2.) You've already found the answer to

REMINDER: Google Summer of Code Demo Day 2 - August 24, 2018 at 1300GMT

[Ed Cable]

Hi all,

Just a reminder that GSOC Demo Day 2 is happening just about 6.5 hours at
1300GMT via GoToTraining. Register to attend at
https://attendee.gototraining.com/r/1497705654114562561

As discussed in last week's showcase, we will have a total of 3 showcases.

For this week's showcase, the agenda is as such:

Aksh will be demoing the The Android Field Operations App 5.0, Manish
showcasing the first client-facing mobile banking app on Fineract CN,
Anwesh continuing the demo of the Mifos X web app, Ruphine and Pembe
sharing their implementation of group management on the back and front-end
for Fineract CN, Kumaranath will summarize performance enhancements to
Fineract, and Courage sharing her work on containerization for Fineract CN.

For the GSOC Demo Day #3 on August 30, 2018 at 1300GMT:

Dingfan will demo the Mifos Chatbot, Sanyam will showcase our Mifos payment
gateway for mobile money integration,  Ebenezer will show off he new
SMS/email microservice for Fineract CN, and Mohak and Dilpreet will
highlight Fineract CN Mobile 2.0.

Please register at https://attendee.gototraining.com/r/4441364363687034625

Cheers,

Ed












On Thu, Aug 23, 2018 at 4:55 AM Ed Cable  wrote:

> Hello all, I apologize for the last minute change in schedule. We had to
> postpone today's showcase until the exact same time tomorrow.
>
> Your registration will be updated.
>
> Thank you for your flexibility.
>
> Ed
>
> On Tue, Aug 14, 2018, 20:14 Ed Cable  wrote:
>
>> Hopefully you've seen all the great interactions of the Google Summer of
>> Code interns spread across the Mifos and Apache Fineract communities.
>> They've been hard at work all summer even though we only just formally
>> introduced them on the Mifos blog at
>> http://mifos.org/blog/meet-the-2018-gsoc-interns/
>>
>> They're ready to showcase and demo the product of their efforts in a
>> series of showcases coming up over the course of the next two weeks. With a
>> total of 18 interns (17 through GSOC and one independently), we have a lot
>> of great work to highlight
>>
>> Part 1 will be Thursday August 16, 2018 at 1300GMT via GoToTraining.
>>
>> Please register at
>> https://attendee.gototraining.com/r/5562581450304728065
>>
>> In this showcase, Abhay and Anwesh will cover our the rewrite of the
>> Mifos X web app into Angular 6, Saksham will demo Mifos Mobile 3.0, Ankur
>> will showcase he mobile wallet 2.0 project, Kumaranath will summarize
>> performance enhancements to Fineract, Ebenezer will show off he new
>> SMS/email microservice for Fineract CN, Lalit will share his
>> scorecard-based machine learning, and Cabrel the bulk data import tool for
>> Fineract CN.
>>
>> Part 2 will be Thursday August 23, 2018 at 1300 GMT via GoToTraining.
>>
>> Please register at
>> https://attendee.gototraining.com/r/1497705654114562561
>>
>> In this showcase, Aksh will be demoing the The Android Field Operations
>> App 5.0, Manish showcasing the first client-facing mobile banking app on
>> Fineract CN, Mohak and Dilpreet highlighting, Fineract CN Mobile 2.0,
>> Ruphine and Pembe sharing their implementation of group management on the
>> back and front-end for Fineract CN, Dingfan demoing the Mifos Chatbot,
>> Sanyam showcasing our Mifos payment gateway for mobile money integration,
>> and Courage sharing her work on containerization for Fineract CN.
>>
>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>   
>>
>>

-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

Re: REMINDER: Google Summer of Code Demo Day 2 - August 24, 2018 at 1300GMT

[Dingfan Zhao]

Hello Ed,

Actually I think I can demo today after checking my schedule today. If the 
schedule is okay to update then please add me to the list of demos. Thanks a 
lot.

Regards,
Dingfan

> On 24 Aug 2018, at 2:27 PM, Ed Cable  wrote:
> 
> Hi all,
> 
> Just a reminder that GSOC Demo Day 2 is happening just about 6.5 hours at
> 1300GMT via GoToTraining. Register to attend at
> https://attendee.gototraining.com/r/1497705654114562561
> 
> As discussed in last week's showcase, we will have a total of 3 showcases.
> 
> For this week's showcase, the agenda is as such:
> 
> Aksh will be demoing the The Android Field Operations App 5.0, Manish
> showcasing the first client-facing mobile banking app on Fineract CN,
> Anwesh continuing the demo of the Mifos X web app, Ruphine and Pembe
> sharing their implementation of group management on the back and front-end
> for Fineract CN, Kumaranath will summarize performance enhancements to
> Fineract, and Courage sharing her work on containerization for Fineract CN.
> 
> For the GSOC Demo Day #3 on August 30, 2018 at 1300GMT:
> 
> Dingfan will demo the Mifos Chatbot, Sanyam will showcase our Mifos payment
> gateway for mobile money integration,  Ebenezer will show off he new
> SMS/email microservice for Fineract CN, and Mohak and Dilpreet will
> highlight Fineract CN Mobile 2.0.
> 
> Please register at https://attendee.gototraining.com/r/4441364363687034625
> 
> Cheers,
> 
> Ed
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Thu, Aug 23, 2018 at 4:55 AM Ed Cable  wrote:
> 
>> Hello all, I apologize for the last minute change in schedule. We had to
>> postpone today's showcase until the exact same time tomorrow.
>> 
>> Your registration will be updated.
>> 
>> Thank you for your flexibility.
>> 
>> Ed
>> 
>> On Tue, Aug 14, 2018, 20:14 Ed Cable  wrote:
>> 
>>> Hopefully you've seen all the great interactions of the Google Summer of
>>> Code interns spread across the Mifos and Apache Fineract communities.
>>> They've been hard at work all summer even though we only just formally
>>> introduced them on the Mifos blog at
>>> http://mifos.org/blog/meet-the-2018-gsoc-interns/
>>> 
>>> They're ready to showcase and demo the product of their efforts in a
>>> series of showcases coming up over the course of the next two weeks. With a
>>> total of 18 interns (17 through GSOC and one independently), we have a lot
>>> of great work to highlight
>>> 
>>> Part 1 will be Thursday August 16, 2018 at 1300GMT via GoToTraining.
>>> 
>>> Please register at
>>> https://attendee.gototraining.com/r/5562581450304728065
>>> 
>>> In this showcase, Abhay and Anwesh will cover our the rewrite of the
>>> Mifos X web app into Angular 6, Saksham will demo Mifos Mobile 3.0, Ankur
>>> will showcase he mobile wallet 2.0 project, Kumaranath will summarize
>>> performance enhancements to Fineract, Ebenezer will show off he new
>>> SMS/email microservice for Fineract CN, Lalit will share his
>>> scorecard-based machine learning, and Cabrel the bulk data import tool for
>>> Fineract CN.
>>> 
>>> Part 2 will be Thursday August 23, 2018 at 1300 GMT via GoToTraining.
>>> 
>>> Please register at
>>> https://attendee.gototraining.com/r/1497705654114562561
>>> 
>>> In this showcase, Aksh will be demoing the The Android Field Operations
>>> App 5.0, Manish showcasing the first client-facing mobile banking app on
>>> Fineract CN, Mohak and Dilpreet highlighting, Fineract CN Mobile 2.0,
>>> Ruphine and Pembe sharing their implementation of group management on the
>>> back and front-end for Fineract CN, Dingfan demoing the Mifos Chatbot,
>>> Sanyam showcasing our Mifos payment gateway for mobile money integration,
>>> and Courage sharing her work on containerization for Fineract CN.
>>> 
>>> 
>>> 
>>> --
>>> *Ed Cable*
>>> President/CEO, Mifos Initiative
>>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>> 
>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>>   
>>> 
>>> 
> 
> -- 
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> 
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>