DISCUSS: Fineract Significant Improvement Proposal: [FSIP-3] Continue Enhancing New Progressive Loan Module to Support Interest-Bearing Loans

[Ed Cable]

Hi all,

I wanted to open up a discussion thread related to the ongoing enhancements
that are occurring to the loan functionality within Fineract. There are
major changes being proposed which continuedto extend off the existing
enhancements that have gone into the new progressive loan calculations that
were delivered in Fineract 1.9.

The design and implementation of these changes at a technical level are
being driven by Adam Saghy and Marta Jankovics - long-term active members
of the community and the functional requirements by Bharath Gowda.

Please view the details of the proposed changes, the goals of these
changes, the alternatives that were considered and timeline for these
changes if the Significant Improvement Proposal gets approved. Thanks to
Adam for sharing a lot of the high-level technical details of our approach
that I incorporated in the proposal. We look forward to the discussion and
vote and will continue to share more documentation around the proposed
changes including new enhancements and gradual enhancement/refactoring of
the existing logic of the loan module.

This proposal will result in valuable net new functionality and substantial
progress on the much needed optimization of the loan module but it won't
fully address the complete refactoring of the legacy loan module so want to
get the community's input and give visibility into the near and long-term
impact this would have on the community as well as the way community can
get involved in future work.

https://cwiki.apache.org/confluence/display/FINERACT/FSIP-3%3A+Continue+Enhancing+New+Progressive+Loan+Module+to+Support+Interest-Bearing+Loans


Here's a brief summary of the proposal.

We are proposing to add support for interest-bearing loan products for
progressive loan schedule by continuing to develop on the recently merged
progressive loan handling changes and moving it into a new externalized
*fineract-progressive-loan* module.

These changes are in support of an enterprise customer that has been
sponsoring upstream contributions into Fineract to support the migration of
its BNPL and installment lending products onto a new loan management system
of record.

This new module will aim to re-use existing logic from the legacy loan
module by extracting it into separate methods or classes to reduce the
complexity and improve the reusability.

The legacy loan module is far too complicated to build these new loan
capabilities onto but we also have decided not to build a completely
separate and independent loan module that would lead to forked
implementations.

Our proposed approach will allow us to deliver a solution that meets the
customer requirements while not breaking any existing functionality for the
community. We will make substantial progress on the much-needed redesign
and refactoring of the loan module and gradually and iteratively over time
build out this enhanced loan module to ideally deprecate the legacy loan
module.

Thanks,

*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [Mifos-developer] Inter Operation APIs

[Ed Cable]

Mark and others,

It still didn't actually take place. Let me work with the technical team
and make sure I commit to actually having this.

In the meantime, you could take a look at demo David from Mifos recently
recorded of our GovStack implementation of Payment Hub EE as Payments
Building Block for government use cases like G2P Payments -
https://www.youtube.com/watch?v=RNwfwhlGt4Q

Ed

On Wed, May 8, 2024 at 11:00 AM Mark Nuttall-Smith <
nutt...@apolloagriculture.com> wrote:

> Hey Ed et al.,
> Just wondering if the payment hub demo every took place, and if a video is
> available perhaps? I'd love to see something to get a feel for how the
> system works!
> Thanks, Mark
>
>
> On Fri, 15 Mar 2024, 18:18 Ed Cable,  wrote:
>
>> I have not scheduled it yet but let me get it on calendar as soon as
>> possible aiming for within the next two weeks.
>>
>> Ed
>>
>> On Fri, Mar 15, 2024 at 3:24 AM Ippez Robert 
>> wrote:
>>
>>> Dear Mark,
>>>
>>> We haven't had the session yet.
>>> I believe preparations for this in terms of demo session, Getting
>>> Started documentations/Readme etc are in progress. Otherwise we're all
>>> looking forward to having this.
>>>
>>> Thanks and regards
>>>
>>
>>
>> --
>> *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
>> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>>
>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Insufficient GSoC project description

[Ed Cable]

Zeyad,

Per our ongoing discussion, we have updated the listing for the idea as it
was an oversight that the project wasn't updated to reflect current
progress and current focus.

It will draw upon these two tickets from JIRA:
https://issues.apache.org/jira/browse/FINERACT-2021 and
https://issues.apache.org/jira/browse/FINERACT-2022

Ed

On Wed, Mar 20, 2024 at 8:00 PM Zeyad Nasef 
wrote:

> Here's the doc link:
>
>
> https://docs.google.com/document/d/1w23pvpbWmWZVQUOKXcC_0zjfs-T1bSAagkW-XG2kgxE/edit?disco=Z5PWsLk
>
> On Thu, Mar 21, 2024, 4:11 AM Zeyad Nasef 
> wrote:
>
>> Hello everyone.
>>
>> Quick heads up regarding the Lombok & Mapstruct project: Noticed the
>> project description is identical for 2022, 2023, and 2024.
>>
>> While searching for past successful applications, I found this doc
>> suggesting phase 2 involves swapping GSON with Jakson and removing the
>> helper classes (not mentioned in the current description).
>>
>> This info needs a bit of investigation, which I'm short on time for since
>> my midterm starts in two days and runs until March 30th. Won't leave me
>> much room to craft a good proposal.
>>
>> If there's a more detailed breakdown of what's expected, that'd be very
>> helpful.
>>
>> Thanks,
>> Zeyad.
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [Mifos-developer] Inter Operation APIs

[Ed Cable]

I have not scheduled it yet but let me get it on calendar as soon as
possible aiming for within the next two weeks.

Ed

On Fri, Mar 15, 2024 at 3:24 AM Ippez Robert  wrote:

> Dear Mark,
>
> We haven't had the session yet.
> I believe preparations for this in terms of demo session, Getting Started
> documentations/Readme etc are in progress. Otherwise we're all looking
> forward to having this.
>
> Thanks and regards
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Summer Intern Programs for 2024 - GSOC & Code for GovTech - Mifos GSOC Ask Me Anything Session - March 7 at 1500GMT

[Ed Cable]

Hi all,

As many of you are aware, we're on the cusp of aspiring interns soon to be
submitting their applications for programs like Google Summer of Code.
Mifos Initiative has been selected as a mentoring org and will be guiding
the process to select and mentor interns across a range of projects
including the back-end as well as integrations and new modules, Mifos X web
and mobile apps for customers and staff, projects related to Payment Hub
EE, AI projects as part of our AI for All strategy and lastly projects
related to Digital Public Goods and supporting use cases like G2P Payments.

As is tradition, we're conducting an Ask Me Anything (AMA) session
this *Thursday
March 7 at 1500GMT via Zoom Webinar.* Prospective applicants should come
prepared with any questions that they have. Mentors should join to be able
to share their perspectives and respond to questions as they come in.

*Register
at 
https://us02web.zoom.us/webinar/register/4217090642705/WN_aSwYxKEASxSvaZNE84jWAg
<https://us02web.zoom.us/webinar/register/4217090642705/WN_aSwYxKEASxSvaZNE84jWAg>*

You can view our current list of ideas which are still being refined at
https://mifosforge.jira.com/wiki/spaces/RES/pages/3532095546/Google+Summer+of+Code+2024+Ideas

Also check out the Mifos blog for a glimpse into our areas of focus this
year and what we are seeking from our interns -
https://mifos.org/blog/google-summer-of-code-2024/

This process guided by Mifos is separate from Apache Software Foundation as
an umbrella mentoring org.

Mifos will also be participating in Code for GovTech this year and have a
number of projects related specifically to digital public goods and digital
public infrastructure that we're targeting through that program. It's very
similar in structure and timeframes to GSOC. Learn more at
https://www.codeforgovtech.in/c4gt-2024

If you haven't already expressed an interest in being a mentor, you can do
so by filling this form out at https://forms.gle/NN5BvbABTykNkbCf8

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [Mifos-developer] Inter Operation APIs

[Ed Cable]

Hello Floyd and Robert, let me try to pull together some of the
documentation and possibly a demo session for using Payment Hub EE for
inbound and outbound mobile money flows. It's being used in production for
a number of different mobile money APIs, namely Safaricom's MPesa. My goal
is that we can make the process for supporting additional mobile money APIs
more replicable and easy to implement nce we have the BPMN flows defined
for inbound and outbound flows defined and then it's merely building the
additional connector for that Momo API that uses those same BPMN flows.

Efforts are also afoot to ease the installation process and reduce resource
consumption of PH-EE to make it easier to install and run.

Thanks,

Ed

On Tue, Feb 27, 2024 at 10:41 PM Ippez Robert  wrote:

> Hello,
>
> This is a good topic, I have been also looking forward to seeing how this
> can be implemented for production especially mobile money sending and
> receiving. I believe the Fineract backend works with the payment hub which
> actually seems complicated setting up for either testing or production for
> some of us.
>
> Someone with good experience in deployment of the payment hub and Fineract
> interoperability module can help some of us who wish to extend and
> implement this for live production.
>
> Thanks and regards
> Robert
>
> On Wed, Feb 28, 2024, 9:35 AM Floyd Nickson 
> wrote:
>
>> Good Day
>> Dear Mailing List Members,
>>
>> I am interested in exploring the interoperable APIs on Fineract and how
>> they can be leveraged to send and receive money from mobile money channels.
>> I believe that these APIs could greatly benefit my current project and I
>> would like to understand how they work and how they can be integrated into
>> my application.
>>
>> If anyone has experience working with Fineract's interop APIs or has any
>> resources or information that could help me better understand and utilize
>> them, I would greatly appreciate your input.
>>
>> Thank you in advance for any assistance you can provide.
>>
>> Best regards,
>> Floyd Nick.
>>
> Mifos-developer mailing list
> mifos-develo...@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer



-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINERACT] [VOTE] ️ 1.9.0 for release

[Ed Cable]

Thank you Terence.

+1 Binding from my side..I have been pinging other committers to test the
build.

Ed

On Wed, Jan 17, 2024, 01:21 Terence Monteiro 
wrote:

> +1 (binding)
>
> I successfully built the JAR file
>
> Regards,
> Terence Monteiro.
>
>
> On Tue, Jan 16, 2024 at 9:58 PM James Dailey 
> wrote:
>
>> +1 (binding)  I did not build the project, and am relying on those that
>> have.
>>
>>
>> On Mon, Jan 15, 2024 at 9:35 AM VICTOR MANUEL ROMERO RODRIGUEZ <
>> victor.rom...@fintecheando.mx> wrote:
>>
>>> Hello,
>>>
>>> On the Fineract Dev List I have raised a query about Functional test and
>>> Anjil has given a reply about it.
>>>
>>> Regards
>>>
>>> El lun, 15 ene 2024 a las 9:16, James Dailey ()
>>> escribió:
>>>
 If you’re using it and can do some verification that is good, and no, I
 don’t think I’d expect 100%.  Thanks.


 On Mon, Jan 15, 2024 at 12:46 AM Kigred Developer <
 kigred.develo...@gmail.com> wrote:

> Good Morning James,
>
> Does verifying mean carrying out a functional test on ALL endpoints
> of  the release?
>
> I have verified a couple of endpoints and they are working fine. So I
> want your guidance on this.
>
> Regards.
> Wilfred.
>
>
>
> On Mon, 8 Jan 2024, 20:18 James Dailey,  wrote:
>
>> Thank you Aleks!   Very very grateful!
>>
>> As Victor noted, it is IMPORTANT for at least some of the people here
>> to build and test this per our process and the apache (ASF) norms.
>> If you VOTED +1 already, please indicate if you built and tested.
>> Ideally, we would have at least three independent reviews of a release.
>>
>>
>> Grateful,
>> James
>> PMC Chair
>>
>> Related -  this needs to be updated somewhat I think:
>>
>> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
>>
>>
>>
>> On Mon, Jan 8, 2024 at 8:43 AM Sifiso Mtetwa <
>> sif...@skyburgsystems.org> wrote:
>>
>>> Hi Aleks,
>>>
>>> Compliments of the season :-)
>>>
>>> The link https://dist.apache.org/repos/dist/dev/fineract/1.9.0/ is
>>> currently unavailable.
>>>
>>> The last release appearing is 1.8.3
>>>
>>>
>>> -Original Message-
>>> From: Aleksandar Vidakovic [mailto:al...@apache.org]
>>> Sent: Monday, 08 January 2024 10:29
>>> To: dev@fineract.apache.org
>>> Subject: [FINERACT] [VOTE] ️ 1.9.0 for release
>>>
>>> Hello everyone,
>>>
>>> ... we have created Apache Fineract 1.9.0 release, with the
>>> artifacts below up for a vote.
>>>
>>> It fixes the following issues:
>>> https://cwiki.apache.org/confluence/display/FINERACT/1.9.0+-+Apache+Fineract
>>>
>>> Source & Binary files :
>>> https://dist.apache.org/repos/dist/dev/fineract/1.9.0/
>>>
>>> Tag to be voted on (rc#):
>>> https://gitbox.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.9.0
>>>
>>> Fineract's KEYS containing the PGP key we used to sign the release:
>>> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>>>
>>> Note that this release contains source and binary artifacts.
>>>
>>> This vote will be open for 72 hours:
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>> Cheers,
>>>
>>> Aleksandar Vidakovic
>>>
>>>

Re: Customising Fineract

[Ed Cable]

Wilfred,

You can also utilize the new custom modules feature which helps to achieve
the goals that Mugabe outlined in his last post around being able implement
custom changes without leading to conflict and difficulty in maintaining
compatibility with upstream.

https://fineract.apache.org/docs/current/#_custom_modules

@Aleksandar Vidakovic  can share more details on
using the custom modules approach.

Thanks,

Ed

On Wed, Jan 3, 2024 at 2:31 PM Magezi Arthur  wrote:

> Hello Wilfred,
> Additionally you could add a module for holding all your custom changes
> and just override the core functionalities.
> This helps you properly isolate your customizations from the core modules,
> hence allowing you to always fetch the latest versions with limited or no
> conflicts.
>
> On the other hand, contributing back would be easy since your custom code
> won’t be too entangled with your core.
>
> Happy new year.
>
> *MUGABE MAGEZI ARTHUR*
> Software Developer and
> Process Management Consultant
> emails:
> *artmag...@gmail.com *
> Mob: +256704901261
> facebook: Magezi Arthur
> Skype: marthur26
>
> The Struggle the doesn't break you will make you, if you hold a little
> longer under that fire you  will certainly come out as Gold
>
>
> On Thu, 4 Jan 2024 at 01:14, VICTOR MANUEL ROMERO RODRIGUEZ <
> victor.rom...@fintecheando.mx> wrote:
>
>> Hello Wilfred,
>>
>> My response for suggesting the “best way”
>>
>> 1. Write a Jira ticket with the change/feature requested, socialize it on
>> this list and upstream your changes as a PR to the development branch of
>> Apache Fineract.
>>
>> If the feature is not shared or sent back to the community (and
>> technical, legal reasons for not doing this) the code could be out of sync
>> and rebased by changes in the development branch and everyone must agree on
>> this in order to maintain that legacy piece of code.
>>
>> Regards
>>
>> Victor
>>
>>
>> El mié, 3 ene 2024 a las 15:18, Kigred Developer (<
>> kigred.develo...@gmail.com>) escribió:
>>
>>> Hello Devs,
>>>
>>> Happy New Year.
>>>
>>> What is the best way to customize fineract and still be able to use new
>>> code updates without breaking one's customised code?
>>>
>>> For example I am trying to make changes that enable users to purchase
>>> shares using a clients savings funds (it essentially a transfer
>>> transaction) but I want to use the other modules just the way they are and
>>> also be able to pull changes when fineract 1.9 is release without losing my
>>> customisations.
>>>
>>> What is the best way to do this?
>>>
>>> Regards.
>>> Wilfred.
>>>
>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Urgent - fineract jar not starting (sos)

[Ed Cable]

Divyush,

You should be using the web app UI as that's been continually updated with
the most recent changes to back-end Fineract as Community App is being
deprecated.

Ed

On Wed, Nov 15, 2023 at 7:41 PM Divyush Raj  wrote:

> Yes, I guess the community app (UI for fineract) must also be refactored
> to include this change in the Fineract API.
> Please inform the concerned team of the community app to make the changes.
>
> Thanks and regards
> Divyush
>
> On Fri, Nov 10, 2023 at 10:34 PM Ádám Sághy  wrote:
>
>> It seems you are not providing the “transactionProcessingStrategyCode”.
>>
>> See below story -> it was slightly changed and instead of the “
>> transactionProcessingStrategyId”, you need to provide the code.
>>
>> *Example:*
>> - transactionProcessingStrategyCode: “mifos-standard-strategy"
>>
>> Fineract story: https://issues.apache.org/jira/browse/FINERACT-1783
>>
>> I hope it helps!
>>
>> Regards,
>> Adam
>>
>> On 9 Nov 2023, at 09:11, Divyush Raj  wrote:
>>
>> Hi Adam,
>> I have solved the issue of jar file not running.
>> I have successfully installed the fineract backed API and also the UI
>> (Community-app).
>>
>> The *latest issue* that i am facing is that.
>> I am getting this error while trying to create a loan product:
>>
>> *ERROR:*
>> error.msg.transactions.processing.strategy.code.invalid
>>
>> {
>>   "developerMessage" : "The requested resource is not available.",
>>   "httpStatusCode" : "404",
>>   "defaultUserMessage" : "The requested resource is not available.",
>>   "userMessageGlobalisationCode" : "error.msg.resource.not.found",
>>   "errors" : [ {
>> "developerMessage" : "Loan transaction processing strategy with code
>> null does not exist",
>> "defaultUserMessage" : "Loan transaction processing strategy with
>> code null does not exist",
>> "userMessageGlobalisationCode" :
>> "error.msg.transactions.processing.strategy.code.invalid",
>> "parameterName" : "id",
>> "args" : [ { } ]
>>   } ]
>> }
>>
>> Please look into this. Your help would be really appreciated.
>>
>> Thank and Regards
>> Divyush
>>
>>
>>
>> On Tue, Nov 7, 2023 at 5:55 PM Ádám Sághy  wrote:
>>
>>> Hi
>>>
>>> You havent shared too much information…
>>>
>>> Can you please describe what exactly your question regarding "starting
>>> the fineract jar file”?
>>>
>>> What do you try to achieve? What configurations you were using…etc.
>>>
>>> If you are facing some exception, please share that as well.
>>>
>>> In the meantime, please feel free to check the Readme of the Fineract:
>>> https://github.com/apache/fineract/blob/develop/README.md
>>> You might find the answer for your questions there.
>>>
>>> Regards,
>>> Adam
>>>
>>> On 7 Nov 2023, at 11:12, Divyush Raj  wrote:
>>>
>>> Hi,
>>> I need some urgent help with starting the fineract jar file.
>>> Could you please help me?
>>>
>>> Thanks and regards
>>> Divyush
>>>
>>>
>>>
>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Mifos and Google Summer of Code Final Showcase via Zoom Webinar Thursday September 14 at 1500GMT

[Ed Cable]

Summer of Code has already reached its final stages and all our interns are
ready to showcase the product of their efforts this past summer

Please join the Mifos Initiative in showcasing the efforts of our Mifos and
Google Summer of Code interns this upcoming Thursday September 14 at
1500GMT via Zoom.

The session should last about an hour and a half.

Please register here to attend here:
https://us02web.zoom.us/webinar/register/7216905105812/WN_LMVXmU0zRbqLfb3iQ1UnEA

Cheers,

Ed



-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Advanced payment allocation

[Ed Cable]

Thanks Mihaly for making the community aware. As you've noted this
functionality around configurable payment allocation logic is long-awaited.

It would be nice when we get the chance (even though it's not part of
Fineract itself) to include some screenshots which show how an admin user
from a reference UI can configure the payment allocation logic.

As James noted, it will also be critical that we reflect in the technical
and functional documentation how we define or classify each each of the
various portions of a payment that can be configured and allocated.

Ed

On Thu, Sep 7, 2023 at 8:05 AM James Dailey  wrote:

> Thanks for highlighting this upcoming contribution by our leading
> contributors .
>
> We should also make sure that documentation around this makes it into the
> asciidocs.
>
> James
>
>
> On Thu, Sep 7, 2023 at 2:28 PM Mihály Dallos  wrote:
>
>> Dear Community!
>>
>> We are about to make a huge step forward in making Fineract customizable.
>> We have started to work on a brand new payment allocation method. It is
>> going to be independent from the previous ones. It has to as it will allow
>> full customisation!
>>
>> How does it going to work?
>> When you choose Advanced payment allocation you will be able to define in
>> what order payments will be used. What does client pays off first...
>> charges? principal? Past due or current? It'll be up to you. You will be
>> able to set it differently for *each transaction type*!
>> The meanwhile we introduce furter customisation when future obligations
>> are payed. Will it be the last one getting your loan shorter? ... or
>> distributed amongst instalments? It will be up to you.
>>
>> Beware that this is going to be such a powerful improvement that the days
>> of the current payment strategies may get counted!
>>
>> If you wish to follow the development or you would leave a comment you
>> can with the Fineract issue FINERACT-1968
>> <https://issues.apache.org/jira/browse/FINERACT-1968>
>>
>> Enjoy!
>>
>> Mihaly
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Mifos & Google Summer of Code Midterm Showcase - Friday July 27 at 230pm GMT via Zoom

[Ed Cable]

Hi Mifos and Fineract communities,

We are about halfway through Google and Mifos Summer of Code for this year.
Our fourteen interns would like to give a glimpse into what they've been
working on and will be working on this summer during our midterm showcase
this Friday at 230pm GMT via Zoom Webinar.

Please register to attend:
https://us02web.zoom.us/webinar/register/7216905105812/WN_d9CTNSPoSqeYpJh-Xj50gQ

For those who can't attend live, the recording will be distributed
afterwards.

Notes from weekly check-ins for GSOC can be found here:
https://mifosforge.jira.com/wiki/spaces/RES/pages/3296657409/2023+Google+Summer+of+Code

All the best,

Ed

Re: Small proposal(& apologize) for refactoring Fineract

[Ed Cable]

Woony,

First off welcome to the Fineract community. I see you've already been
engaging with Adam Saghy on your pull requests. Your JIRA account request
has now been approved. It had remind in the queue as our PMC had no context
about who was requesting the account until your email provided that
necessary clarification.

Thanks for your contributions and addressing the feedback provided on the
pull request. We look forward to more contributions from your side.

Cheers,

Ed

On Mon, Jul 24, 2023 at 12:42 AM 김재운  wrote:

> Hello, everyone.
>
> I'm Woony Kim, a software engineer who is working in the Fintech industry
> and want to contribute to Fineract.
>
> First of all, I apologize for not following the Fineract community
> guidelines properly and posting a PR in advance... I recently raised PR
> about refactoring first (https://github.com/apache/fineract/pull/3315)
> without consulting the mailing list enough. I misunderstood the process.. I
> should have read them carefully.
>
> *Background of proposal*
> As my company uses Fineract, and I recently moved to the team responsible
> for the platform, I became interested in contributing to it.
>
> However, since I'm a newbie to Fineract, I thought it would be great if I
> could contribute something small that I could fix. Adding or changing
> features is still out of my league, but I figured I could do some small
> refactoring, like improving the readability of existing code. That's why I
> changed the code(SQLInjectionValidator).
>
> I feel that someone might think it's not quite important or necessary code
> in the codebase... If you have any opinion or suggestions, please let me
> know if it's okay to refactor or not.
>
> Also, If it's okay, could I get authority to create Jira account? As I
> already wrote on PR, I haven't be given the authority.
>
> Sincerely,
> Woony Kim
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [Mifos-users] FINERACT PENTAHO

[Ed Cable]

Thanks for clarifying this as well too.

As you can see from the last message that Victor sent, he removed the dev
list and kept the discussion just on the Mifos list. Thanks Victor for both
replying about the thread and isolating it to the right place.

Ed

On Tue, Jun 27, 2023, 09:07 James Dailey  wrote:

> It appears that this is not a FINERACT topic.
>
> Please see FAQ about separation of projects.
> If there is an issue that relates to the plug in concept at Fineract,
> please revert here.
>
> The Mifos project is not discussed here.
> If you think additional documentation at Fineract would help smooth this
> for all plug-ins, please also make those suggestions to the existing
> documentation at Fineract.  In a "diff" manner.
>
> Thanks.
>
>
> On Tue, Jun 27, 2023 at 12:07 AM Honest Chirozva <
> hon...@taatconsulting.com> wrote:
>
>> Thanks Ed,
>>
>>
>>
>> I am available to contribute to the project and make necessary
>> documentation. Below are the issues I think new users might face when
>> integration pentaho reports which the docs do not answer
>>
>>
>>
>>1. How to enable the pentaho plugin in fineract-provider jar
>>2. What about the war file?
>>3. The pentaho plugin pom fails to locate fineract-provider plain
>>jar. Should we maybe provide guideline on how to build the jars locally 
>> for
>>fineract-core, fineract-client and fineract-provider-plain.jar?
>>4. The plugin depends on multiple jars, do we have to manually
>>download the jars? Can’t we build the fineract-pentaho plugin as a fat jar
>>with its dependencies included?
>>5. My thinking is that you only need fineract-provider.jar,
>>fineract-pentaho.jar, and a zip folder with the reports. These three must
>>work together without one needing to re build any of the jars?
>>
>>
>>
>> Regards.
>>
>> Honest Chirozva
>> Technical Consultant
>>
>>
>>
>> *From: *Ed Cable 
>> *Sent: *Monday, 26 June 2023 17:00
>> *To: *dev@fineract.apache.org
>> *Subject: *Re: [Mifos-users] FINERACT PENTAHO
>>
>>
>>
>> Honest,
>>
>>
>>
>> Can you directly share the issues you are facing while doing the
>> build/install? You could also then help improve the documentation yourself
>> based on what additional guidance community members can give you.
>>
>>
>>
>> Ed
>>
>>
>>
>> On Mon, Jun 26, 2023 at 5:52 AM Honest Chirozva <
>> hon...@taatconsulting.com> wrote:
>>
>> I have tried to follow the guideline but no avail. Can someone just
>> explain to me what to do in simple terms?
>>
>>
>> Honest Chirozva
>> Technical Consultant
>>
>>
>>
>>
>>
>> *From: *Francis Guchie 
>> *Sent: *Monday, 26 June 2023 14:28
>> *To: *A good place to start for users or folks new to Mifos.
>> 
>> *Cc: *dev@fineract.apache.org
>> *Subject: *Re: [Mifos-users] FINERACT PENTAHO
>>
>>
>>
>> Dear Honest,
>>
>>
>>
>> Kindly follow the events here ==>
>> https://github.com/openMF/fineract-pentaho/issues this way we can follow
>> up on the challenges
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> My Kind Regards
>>
>>
>>
>>
>>
>> Francis Kirago Guchie
>>
>> *Mobile:*
>>
>> +232 79 194407
>>
>> +256 70  5011852
>>
>>
>>
>> *Skype:* francisguchie
>>
>> *twitter*: @francisguchie
>>
>> *Telegram: *232 79 19 44 07
>>
>> *Whatsapp: *232 79 19 44 07
>>
>> *LINKEDIN:* https://www.linkedin.com/in/francis-guchie-a4379617/
>>
>> *Website: *https://guchietech.com
>>
>>
>>
>>
>>
>> On Mon, Jun 26, 2023 at 12:07 PM Bharath Gowda  wrote:
>>
>> Hi Honest.
>>
>>  + Adding the Mifos community list to this thread as the fineract-pentaho
>> repo is currently managed under OpenMF Umbrella.
>>
>>
>>
>> you should be able to add the Pentaho plugin if you follow the
>> instructions under the readme here
>> https://github.com/openMF/fineract-pentaho
>>
>>
>>
>> feel free to post questions in the same thread if you hit any dead ends
>> during the plugin installation process
>>
>>
>>
>>
>> Regards,
>>
>> Bharath
>>
>> Lead Implementation Analyst | Mifos Initiative
>>
>> Skype: live:cbharath4| Mobile: +91.7019635592
>>
>> http://mifos.org  <http://facebook.com/mifos>
>> <http://www.twitter.com/mifos>
>>
>>
>>
>>
>>
>> On Mon, Jun 26, 2023 at 1:27 PM Honest Chirozva <
>> hon...@taatconsulting.com> wrote:
>>
>> Greetings community,
>>
>>
>>
>> Can someone guide me on how to build finerect pentaho plugin against the
>> latest fineract develop branch.
>>
>>
>>
>> Kind Regards!
>>
>> Honest Chirozva
>> Technical Consultant
>>
>>
>>
>> Mobile:  +263 718 795 908
>> Email: hon...@taatconsulting.com
>>
>> Web : www.taatconsulting.com
>>
>>
>>
>> ___
>> Mifos-users mailing list
>> mifos-us...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mifos-users
>>
>>
>>
>>
>>
>>
>> --
>>
>> *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
>> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>>
>>
>>
>>
>>
>

Re: [Mifos-users] FINERACT PENTAHO

[Ed Cable]

Honest,

Can you directly share the issues you are facing while doing the
build/install? You could also then help improve the documentation yourself
based on what additional guidance community members can give you.

Ed

On Mon, Jun 26, 2023 at 5:52 AM Honest Chirozva 
wrote:

> I have tried to follow the guideline but no avail. Can someone just
> explain to me what to do in simple terms?
>
>
> Honest Chirozva
> Technical Consultant
>
>
>
>
>
> *From: *Francis Guchie 
> *Sent: *Monday, 26 June 2023 14:28
> *To: *A good place to start for users or folks new to Mifos.
> 
> *Cc: *dev@fineract.apache.org
> *Subject: *Re: [Mifos-users] FINERACT PENTAHO
>
>
>
> Dear Honest,
>
>
>
> Kindly follow the events here ==>
> https://github.com/openMF/fineract-pentaho/issues this way we can follow
> up on the challenges
>
>
>
>
>
>
>
>
>
> My Kind Regards
>
>
>
>
>
> Francis Kirago Guchie
>
> *Mobile:*
>
> +232 79 194407
>
> +256 70  5011852
>
>
>
> *Skype:* francisguchie
>
> *twitter*: @francisguchie
>
> *Telegram: *232 79 19 44 07
>
> *Whatsapp: *232 79 19 44 07
>
> *LINKEDIN:* https://www.linkedin.com/in/francis-guchie-a4379617/
>
> *Website: *https://guchietech.com
>
>
>
>
>
> On Mon, Jun 26, 2023 at 12:07 PM Bharath Gowda  wrote:
>
> Hi Honest.
>
>  + Adding the Mifos community list to this thread as the fineract-pentaho
> repo is currently managed under OpenMF Umbrella.
>
>
>
> you should be able to add the Pentaho plugin if you follow the
> instructions under the readme here
> https://github.com/openMF/fineract-pentaho
>
>
>
> feel free to post questions in the same thread if you hit any dead ends
> during the plugin installation process
>
>
>
>
> Regards,
>
> Bharath
>
> Lead Implementation Analyst | Mifos Initiative
>
> Skype: live:cbharath4| Mobile: +91.7019635592
>
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
>
>
>
>
>
> On Mon, Jun 26, 2023 at 1:27 PM Honest Chirozva 
> wrote:
>
> Greetings community,
>
>
>
> Can someone guide me on how to build finerect pentaho plugin against the
> latest fineract develop branch.
>
>
>
> Kind Regards!
>
> Honest Chirozva
> Technical Consultant
>
>
>
> Mobile:  +263 718 795 908
> Email: hon...@taatconsulting.com
>
> Web : www.taatconsulting.com
>
>
>
> ___
> Mifos-users mailing list
> mifos-us...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mifos-users
>
>
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Fineract - Feature Request - Savings Account related Trensactions and Data Tables

[Ed Cable]

Thanks Bharath for creating those tickets on the Mifos UI side - I will see
how we can go about getting that work done so there continues to be a
balance between what's available in Fineract back-end also have a reference
user interface for it as well.

Ed

On Wed, Jun 14, 2023 at 1:27 AM Bharath Gowda  wrote:

> Hi All,
>
> Great to see some search query changes happening on the savings
> transaction level
>
> Have created Mifos UI tickets for the following tickets so that
> community users using Mifos UI will get benefited of these features
> https://issues.apache.org/jira/browse/FINERACT-1747
> https://issues.apache.org/jira/browse/FINERACT-1912
> https://issues.apache.org/jira/browse/FINERACT-1910
>
>
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> Skype: live:cbharath4| Mobile: +91.7019635592
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
>
>
> On Mon, Jun 12, 2023 at 9:14 PM James Dailey 
> wrote:
>
>> On this topic, there are some discussions around the current tickets and
>> at least one proposed PR.
>>
>> The idea of extending the functionality of the Savings Account (Current
>> Account) has long been on the roadmap, so it's good to see some progress.
>> As we move forward, let's keep in mind,
>> a) Incremental improvements are good (don't impact other users while
>> adding functionality in a smart design)
>> b) backwards API compatibility
>> c) performance
>>
>> Also, I note that although the Mifos UI projects do try to stay up to
>> date with the latest on Fineract, they are NOT part of this project, so the
>> behavior of the APIs can only be seen in postman or some other test tool.
>>
>>
>>
>> On Wed, Jun 7, 2023 at 7:53 AM James Dailey 
>> wrote:
>>
>>> Bringing to top of list
>>>
>>>
>>>
>>> -- Forwarded message -
>>> From: James Dailey 
>>> Date: Wed, Apr 5, 2023 at 9:30 AM
>>> Subject: Fwd: Fineract - Feature Request - Savings Account related
>>> Trensactions and Data Tables
>>> To: James Dailey , <
>>> amuthi...@korconnection.com>
>>>
>>>
>>> Art -  Would you please forward to your backend fineract people and make
>>> them aware of this effort?I want to ask you if they can be involved  in
>>> this mini-project to be delivered by mid-May.
>>>
>>>
>>>
>>>
>>> -- Forwarded message -
>>> From: James Dailey 
>>> Date: Wed, Apr 5, 2023 at 9:22 AM
>>> Subject: Re: Fineract - Feature Request - Savings Account related
>>> Trensactions and Data Tables
>>> To: 
>>>
>>>
>>> Thanks Peter.  These are very welcome from my perspective.  I hope
>>> others jump into the discussion and make suggestions or share their
>>> designs.
>>>
>>> TL;DR   Add data tables to transactions in savings account module and
>>> filtering of transactions.
>>>
>>> I think it fair to say that this relates to the conversation about a
>>> more robust “current account”
>>> https://lists.apache.org/list.html?dev@fineract.apache.org   ( misnomer
>>> "savings" account)
>>>
>>> Such improvements you’ve ticketed would be a first incremental step in
>>> expanding the functionality.
>>>
>>> +1
>>>
>>> Additionally, I think this would benefit from having a ticket that
>>> brings these tickets and others together.  So I've opened a parent ticket:
>>> https://issues.apache.org/jira/projects/FINERACT/issues/FINERACT-1917
>>>
>>>
>>>
>>>
>>> On Wed, Apr 5, 2023 at 6:39 AM Peter Santa  wrote:
>>> >
>>> > Dear Community,
>>> >
>>> > We have some requirements collected, regarding to Savings Account
>>> Transactions, Data Tables, and to their combination.
>>> >
>>> > Would someone consider it as useful for the Community, and pick it up
>>> for development? If yes, feel free to reach out for a discussion, to avoid
>>> misunderstandings, and to align the solution concept.
>>> >
>>> > The related, currently existing tickets:
>>> >
>>> > Transactions
>>> >
>>> > https://issues.apache.org/jira/browse/FINERACT-1912
>>> >
>>> > Data tables
>>> >
>>> > https://issues.apache.org/jira/browse/FINERACT-1747
>>> >
>>> > https://issues.apache.org/jira/browse/FINERACT-1910
>>> >
>>> > https://issues.apache.org/jira/browse/FINERACT-1916
>>> >
>>> > Transaction+data tables
>>> >
>>> > https://issues.apache.org/jira/browse/FINERACT-1911
>>> >
>>> > https://issues.apache.org/jira/browse/FINERACT-1915
>>> >
>>> > https://issues.apache.org/jira/browse/FINERACT-1916
>>> >
>>> >
>>> > Best Regards,
>>> >
>>> > Péter
>>> --
>>> Sent from Gmail Mobile
>>> --
>>> Sent from Gmail Mobile
>>>
>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: On Getting Started with Fineract

[Ed Cable]

Sorry I didn't catch up on the other thread "gpg gradle warnings"
discussing docs which makes my reply somewhat redundant. I do think it's
important that the README remains where it is and keeps housing the vital
information it currently does. I do agree that it should also be part of
the ASCII doc too but can we have the README be incorporated into that
ASCII doc without having to maintain both separately and have the risk of
the versions being out of sync.

Ed

On Tue, Jun 13, 2023 at 11:30 PM Ed Cable  wrote:

> Rob, I think where you've been at (especially the README) is still the
> best places for getting started instructions on your build and dev
> environment. Another area of recently maintained technical documentation
> around Fineract is the ASCII doc that gets maintained/updated with each
> release: https://fineract.apache.org/docs/current
>
> Ed
>
> On Tue, Jun 13, 2023 at 5:00 PM Petri Tuomola 
> wrote:
>
>> Hi Rob - can you share the build log/failures so we can see where this is
>> breaking?
>>
>> Thanks
>>
>> Regards
>> Petri
>>
>> On Wed, 14 Jun 2023 at 07:14, Rob Tompkins  wrote:
>>
>>> Hello,
>>>
>>> I have struggled to get the project to build and to figure out where to
>>> get a local developent environment started. I’ve started in the standard
>>> location one would start [1]. From there, I’m quickly pointed to [2]. From
>>> here I get the impression that I’m to run a local instance of MariaDB, and
>>> then run the gradle commands:
>>>
>>> ./gradlew createDB -PdbName=fineract_tenants
>>> ./gradlew createDB -PdbName=fineract_default
>>> ./gradlew bootRun
>>>
>>> however these seem to result in build failures. I’m using java-17
>>> locally on my mac (the amazon corretto model). My gradle --version prints
>>> out the following:
>>>
>>> chtompki@Robs-MacBook-Pro-2 ~ % gradle --version
>>>
>>> Welcome to Gradle 8.1.1!
>>>
>>> Here are the highlights of this release:
>>> - Stable configuration cache
>>> - Experimental Kotlin DSL assignment syntax
>>> - Building with Java 20
>>>
>>> For more details see https://docs.gradle.org/8.1.1/release-notes.html
>>>
>>>
>>> 
>>> Gradle 8.1.1
>>> 
>>>
>>> Build time:   2023-04-21 12:31:26 UTC
>>> Revision: 1cf537a851c635c364a4214885f8b9798051175b
>>>
>>> Kotlin:   1.8.10
>>> Groovy:   3.0.15
>>> Ant:  Apache Ant(TM) version 1.10.11 compiled on July 10 2021
>>> JVM:  17.0.7 (Amazon.com Inc. 17.0.7+7-LTS)
>>> OS:   Mac OS X 13.4 aarch64
>>>
>>>
>>> The difficulty to get started here is a bit frustrating - it’s quite
>>> hard to find the ins and outs of the project and get going. I am really
>>> hoping to spend a bit of my time polishing this up and the surrounding
>>> documentation (where’s that stored? the wiki?). Streamlining this process
>>> will allow us to get a larger number of contributors which is a priority,
>>> in my opinion.
>>>
>>> Thoughts, questions, concerns?
>>>
>>> Cheers,
>>> -Rob
>>>
>>>
>>>
>>> [1]
>>> https://cwiki.apache.org/confluence/display/FINERACT/Getting+Started+Docs
>>> [2] https://github.com/apache/fineract/blob/develop/README.md
>>>
>>
>
> --
> *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
> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: On Getting Started with Fineract

[Ed Cable]

Rob, I think where you've been at (especially the README) is still the best
places for getting started instructions on your build and dev environment.
Another area of recently maintained technical documentation around Fineract
is the ASCII doc that gets maintained/updated with each release:
https://fineract.apache.org/docs/current

Ed

On Tue, Jun 13, 2023 at 5:00 PM Petri Tuomola 
wrote:

> Hi Rob - can you share the build log/failures so we can see where this is
> breaking?
>
> Thanks
>
> Regards
> Petri
>
> On Wed, 14 Jun 2023 at 07:14, Rob Tompkins  wrote:
>
>> Hello,
>>
>> I have struggled to get the project to build and to figure out where to
>> get a local developent environment started. I’ve started in the standard
>> location one would start [1]. From there, I’m quickly pointed to [2]. From
>> here I get the impression that I’m to run a local instance of MariaDB, and
>> then run the gradle commands:
>>
>> ./gradlew createDB -PdbName=fineract_tenants
>> ./gradlew createDB -PdbName=fineract_default
>> ./gradlew bootRun
>>
>> however these seem to result in build failures. I’m using java-17 locally
>> on my mac (the amazon corretto model). My gradle --version prints out the
>> following:
>>
>> chtompki@Robs-MacBook-Pro-2 ~ % gradle --version
>>
>> Welcome to Gradle 8.1.1!
>>
>> Here are the highlights of this release:
>> - Stable configuration cache
>> - Experimental Kotlin DSL assignment syntax
>> - Building with Java 20
>>
>> For more details see https://docs.gradle.org/8.1.1/release-notes.html
>>
>>
>> 
>> Gradle 8.1.1
>> 
>>
>> Build time:   2023-04-21 12:31:26 UTC
>> Revision: 1cf537a851c635c364a4214885f8b9798051175b
>>
>> Kotlin:   1.8.10
>> Groovy:   3.0.15
>> Ant:  Apache Ant(TM) version 1.10.11 compiled on July 10 2021
>> JVM:  17.0.7 (Amazon.com Inc. 17.0.7+7-LTS)
>> OS:   Mac OS X 13.4 aarch64
>>
>>
>> The difficulty to get started here is a bit frustrating - it’s quite hard
>> to find the ins and outs of the project and get going. I am really hoping
>> to spend a bit of my time polishing this up and the surrounding
>> documentation (where’s that stored? the wiki?). Streamlining this process
>> will allow us to get a larger number of contributors which is a priority,
>> in my opinion.
>>
>> Thoughts, questions, concerns?
>>
>> Cheers,
>> -Rob
>>
>>
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/FINERACT/Getting+Started+Docs
>> [2] https://github.com/apache/fineract/blob/develop/README.md
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: SonarCube at Apache for fineract available

[Ed Cable]

Victor,

Can you comment on the above thread? I was pretty certain that sonarcloud
account that Petri helped migrate in Jan 2022 that you set up in October
2021 was through Apache infra but maybe I'm mistaken.

Thanks,

Ed

On Tue, Jun 13, 2023 at 5:05 PM James Dailey  wrote:

> We do have it there, however that is not through the Apache infra
> account.  It is somewhat expected that we use official infra accounts when
> it’s provided.
>
> And…If sonarcube wants to start charging us, we’d have no way to pay it
> officially.
>
>
>
>
>
>
> On Tue, Jun 13, 2023 at 5:00 PM Petri Tuomola 
> wrote:
>
>> Hi James
>>
>> I think we already have this? See
>> https://sonarcloud.io/project/overview?id=apache_fineract
>>
>> At least I remember migrating it when we moved from Travis to GitHub
>> Actions…
>>
>> Regards
>> Petri
>>
>> On Wed, 14 Jun 2023 at 07:14, James Dailey 
>> wrote:
>>
>>> The ASF (Apache Software Foundation) also has an account with SonarCube.
>>>
>>> Would it be a problem to add the configuration to our GitHub Actions?
>>>
>>> https://sonarcloud.io/project/configuration/GitHubActions?id=fineract
>>>
>>> This would require changes to the gradle build file and the .github
>>> build yaml
>>>
>>> We would then be listed here in this catalog of Apache projects
>>> https://sonarcloud.io/organizations/apache/projects
>>>
>>>
>>> james
>>>
>>> --
> Sent from Gmail Mobile
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: FW: Too many threads of type "SimpleAsyncTaskExecutor-" accumulating

[Ed Cable]

Your account should now be approved and active Anjil.

On Tue, May 30, 2023, 06:11 Anjil R Chinnapatlolla 
wrote:

> Thanks @Arnold Galovics .
>
>
>
> I have raised request for Jira account and will raise a ticket soon after
> its approved.
>
>
>
>
>
> Thanks & Regards,
>
> Anjil
>
> *From: *Arnold Galovics 
> *Date: *Tuesday, 30 May 2023 at 1:37 PM
> *To: *dev@fineract.apache.org 
> *Cc: *Ed Cable , VICTOR MANUEL ROMERO RODRIGUEZ <
> victor.rom...@fintecheando.mx>, Anjil R Chinnapatlolla <
> anchi...@in.ibm.com>, Adam Saghy 
> *Subject: *[EXTERNAL] Re: FW: Too many threads of type
> "SimpleAsyncTaskExecutor-" accumulating
>
> Moving the discussion back to the devlist. Hi Anjil, The numbering of the
> thread names is expected to increase, there's no issue with that. The fact
> that you're reporting a lot of threads being active based on your thread
> dump is definitely
>
> ZjQcmQRYFpfptBannerStart
>
> *This Message Is From an External Sender *
>
> This message came from outside your organization.
>
> ZjQcmQRYFpfptBannerEnd
>
> Moving the discussion back to the devlist.
>
>
>
> Hi Anjil,
>
>
>
> The numbering of the thread names is expected to increase, there's no
> issue with that.
>
>
>
> The fact that you're reporting a lot of threads being active based on your
> thread dump is definitely something to take care of. Probably at some
> places in Fineract the executors should be switched to be thread-pool based
> executors instead of simple ones.
>
>
>
> Can you pls file a ticket for this?
>
>
>
> Thanks.
>
> Best,
>
> Arnold
>
>
>
> On Tue, May 30, 2023 at 9:34 AM Anjil R Chinnapatlolla <
> anchi...@in.ibm.com> wrote:
>
> Hi All,
>
>
>
> There seems to be some issue with my below mail delivery to the community.
>
> Can you please review my below observation sent to community mailing list
> earlier and share your thoughts.
>
>
>
> Thanks & Regards,
>
> Anjil
>
>
>
> *From: *Anjil R Chinnapatlolla 
> *Date: *Thursday, 18 May 2023 at 1:51 PM
> *To: *dev@fineract.apache.org 
> *Subject: *[EXTERNAL] Too many threads of type "SimpleAsyncTaskExecutor-"
> accumulating
>
> Dear Dev community team, I got to observe too many threads of type
> “SimpleAsyncTaskExecutor-86046” getting accumulated while running Fineract
> with increased concurrent users (ranging from 200-1000 users at a time
> performing saving deposits
>
> ZjQcmQRYFpfptBannerStart
>
> *This Message Is From an External Sender *
>
> This message came from outside your organization.
>
> ZjQcmQRYFpfptBannerEnd
>
> Dear Dev community team,
>
>
>
> I got to observe too many threads of type “*SimpleAsyncTaskExecutor-86046*”
> getting accumulated while running Fineract with increased concurrent users
> (ranging from 200-1000 users at a time performing saving deposits across 5
> pod replication).
>
>
>
> When deployed in a Kubernetes environment with read/write pods separated,
> the accumulation of threads within the pods is causing the resource
> exhaustion and JVM freeze.
>
>
>
> From a quick java thread-dump walk-through, my understanding is that these
> threads are created in the process of business event notification post
> write commands (like savings deposit) and is required by design.  Raising
> this observation to see if it can be optimized anyway to reduce the number
> of threads getting generated per transaction.
>
>
>
> From one of the thread dumps of a pod, we observed 168 threads of type “
> *https-jsse-nio2-8443-exec-*“ and “*SimpleAsyncTaskExecutor-*“ were 320.
>
>
>
> Thanks & Regards,
>
> Anjil
>
>

Re: Kafka support with Apache Fineract1.x

[Ed Cable]

Anjil,

With the forthcoming 1.9 release, we have a much more reliable event
framework incorporated into Fineract. The design of it has been documented
at https://fineract.apache.org/docs/current/#_reliable_event_framework It's
currently being used with ActiveMQ but can be used with Kafka as well.

@Arnold Galovics  or @Adam Saghy
 can
you point Anjil to any other relevant documentation or speak to how it can
be configured to use Kafka?

Thanks,

Ed

On Thu, Apr 13, 2023 at 2:34 PM VICTOR MANUEL ROMERO RODRIGUEZ <
victor.rom...@fintecheando.mx> wrote:

> Angil,
>
> Which are the expected use cases of Kafka in Fineract?
>
> Regards
>
> Victor
>
> El jue, 13 abr 2023 a las 15:25, Anjil R Chinnapatlolla (<
> anchi...@in.ibm.com>) escribió:
>
>> Dear community members,
>>
>>
>>
>> Do we have Kafka streaming support with current released version (1.8.4)
>> of Fineract or have plans for adding it to the 1.9.0 or future versions?
>>
>> Also, do we have any other applications currently making use of
>> Fineract’s ActiveMQ (or Kafka if supported) messages.
>>
>>
>>
>>
>>
>> Thanks & Regards,
>>
>> Anjil
>>
>>
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINERACT][VOTE] 1.7.3 for maintenance release

[Ed Cable]

+1 Thank you to all who contributed!

Ed

On Fri, Mar 17, 2023 at 11:39 AM Manoj VM  wrote:

> +1
>
> Manoj
>
> On 15-Mar-2023, at 6:18 PM, Bharath Gowda  wrote:
>
> +1
>
> On Wed, Mar 15, 2023, 5:46 PM James Dailey  wrote:
>
>> +1  (binding)
>>
>> I’m relying on the testing and review by others.
>> Thank you for this patch release!
>>
>> Alberto- flyway migrations!
>>
>>
>> On Wed, Mar 15, 2023 at 4:06 PM Aleksandar Vidakovic 
>> wrote:
>>
>>> Hello everyone
>>>
>>> ... we have created Apache Fineract 1.7.3 maintenance release, with the
>>> artifacts below up for a vote.
>>>
>>> It fixes the following issues:
>>> https://cwiki.apache.org/confluence/display/FINERACT/1.7.3+-+Apache+Fineract
>>>
>>> Source & Binary files :
>>> https://dist.apache.org/repos/dist/dev/fineract/1.7.3/
>>>
>>> Tag to be voted on (rc#):
>>> https://gitbox.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.7.3
>>>
>>> Fineract's KEYS containing the PGP key we used to sign the release:
>>> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>>>
>>> Note that this release contains source and binary artifacts.
>>>
>>> This vote will be open for 24 hours:
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>> Cheers,
>>>
>>> Aleksandar Vidakovic
>>>
>> --
>> Sent from Gmail Mobile
>>
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: How to become an Apache Commiter

[Ed Cable]

Ahmad,

I'm glad that you're now connected with Rajan and he's helping go through
the PRs. I will discuss with the PMC granting committership so you can play
a more direct role in helping to maintain the apps.

Thanks,

Ed

On Thu, Mar 2, 2023 at 6:09 PM Maxim Solodovnik 
wrote:

> Hello Ahmad Jawid Muhammadi,
>
> I believe the most proper way is to contact Fineract dev@ mailing list
> (in CC)
> I hope you'll help from Fineract  devs ASAP :)))
>
> On Fri, 3 Mar 2023 at 02:25, Ahmad Jawid Muhammadi
>  wrote:
> >
> > Hello, dear Sanyam,
> >
> > I hope you are doing well. At GSoC 2020 I worked on a project called
> Fineract CN Mobile, and then I mentored that project in GSoC 2021. All
> efforts from 2020 and 2021 are pending, and none of the PRs has been
> merged. Rajan Mayura is the only one who I know has access to merge Pull
> Request but we never succeed to get in touch with him despite many emails
> and DM messages in Slack and other mediums.
> >
> > This year, Ed Cable invited me to be a mentor for that project and I
> would love to help contributors but due to the pending Pull Requests, we
> are completely blocked and can't go forward. I would like to know the
> process of being an Apache Committer and how can I get access to that
> project so that I can start reviewing those PRs and merge them. I do
> appreciate your guidance and assistance on this matter.
> >
> > Best regards,
> > Ahmad Jawid Muhammadi
>
>
>
> --
> Best regards,
> Maxim
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Fineract banking use cases for performance/scalability evaluation

[Ed Cable]

Thank you Anjil for the contributions you and the rest of the team are
making around performance/scalability evaluation. It will be nice to have
some recent evaluations of performance beyond just for lending/credit. I
will circulate your request from other implementers across the community.

Thanks,

Ed

On Tue, Feb 28, 2023 at 11:12 AM Anjil R Chinnapatlolla 
wrote:

> Dear community members,
>
>
>
> We are evaluating the performance of OCP (Openshift Container Platform)
> infrastructure with banking workloads on different hardware architectures.
> With Fineract as one of the banking workloads, we have built the load test
> suite with APIs covering below use cases (Majorly with Savings and Loan
> products).
>
>
>
> I request the community members and teams who have Fineract deployed in
> production or being evaluated, to suggest specific use-cases which are more
> challenging in nature (in latency and scalability perspective) that we
> should consider adding to below list while evaluating performance of the
> deployment infrastructure (which in turn covers the performance of
> Fineract).
>
>
>
>
>
> Setup Bank Environment
>
> Category
>
> Use case
>
> *Create Codes*
>
>
>
>
>
> Create client closure reason code
>
>
>
> Create payment type code
>
>
>
> Get payment type codes
>
> *Ledger Accounting*
>
>
>
>
>
> Create Asset Ledger Account
>
>
>
> Create Liability Ledger Account
>
>
>
> Create Revenue Ledger Account
>
>
>
> Create Expense Ledger Account
>
>
>
> List General Ledger Accounts
>
> *Financial Activity Accounting*
>
>
>
>
>
> Map Financial Activity Account
>
> *Define Savings Products*
>
>
>
>
>
> Create savings product
>
> *Define Loan Products*
>
>
>
>
>
> Create personal loan product
>
> *Setup Clients*
>
>
>
>
>
> Create client
>
> *Setup Savings Account*
>
>
>
>
>
> Submit savings account
>
>
>
> Approve savings account
>
>
>
> Activate savings account
>
> *Setup Loan Accounts*
>
>
>
>
>
> Submit loan application
>
>
>
> Approve loan application
>
>
>
>
>
> *Transactions*
>
> *Category*
>
> *Use case*
>
> *Clients*
>
>
>
>
>
> Get all clients
>
> *Deposits*
>
>
>
>
>
> Deposit to savings account
>
> *Withdrawals*
>
>
>
>
>
> Withdraw from savings account
>
> *Balance Enquiry*
>
>
>
>
>
> Balance enquiry with associations
>
>
>
> Balance Enquiry
>
> *Post Interest *
>
>
>
>
>
> Post Interest on savings account
>
> *Disburse Loans*
>
>
>
>
>
> Disburse loan application
>
>
>
> Undo disburse loan application
>
>
>
> Disburse loan to savings
>
> *List All Loans*
>
>
>
>
>
> List loans
>
> *Reporting *
>
>
>
>
>
> Report savings account dormancy
>
>
>
> Report client listing
>
>
>
> Retrieve a report
>
>
>
> List all reports and parameters
>
>
>
>
>
> Thanks & Regards,
>
> Anjil Reddy Chinnapatlolla
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Call for Mentors: 2023 Google Summer of Code for the Mifos Initiative

[Ed Cable]

Hello Mifos & Fineract communities,

It's that time of year again and the Mifos Initiative is looking to
participate in Google Summer of Code once more. This would be our eleventh
year of participation. Our application has been submitted and we're in the
process of refining our ideas list in case we do get selected. If we are
selected to participate this year, I want to be deeply cognizant of having
a committed set of mentors and backup mentors who will be available for the
duration of the program to mentor their students in an engaged fashion.

Last year, despite having a smaller number of projects than normal (just
ten) we struggled to provide the ideal mentoring experience for our interns
and some of our mentors had to take on extra capacity to guide their
interns. GSOC still represents a great way to attract highly talented
individuals and begin to pass the torch onto the next generation of
contributors so it's a great way for our more seasoned community members to
participate and give back.

We already have a strong set of mentors who have expressed their interest
and their commitment to mentor this year but we're still seeking more so we
can have redundancy and ensure we deliver our interns the enriching
experience and professional and personal growth they deserve.

While Apache Software Foundation is applying separately, under the umbrella
of the Mifos Initiative, we will focus on our suite of Mifos mobile and web
apps for staff and customers but also target projects for Fineract 1.x with
a primary focus on peripheral innovation on the edge or making progress on
ongoing refactoring, code stability, security improvements, testing
coverage growth, etc around the back-end. While we haven't refined the
ideas significantly, we will also target work on the Payment Hub, our AI
for All strategy, additional modules on top of Fineract, Open Banking and
3PPI APIs and G2P related efforts like OpenG2P.

With the project ideas we'll be targeting and focusing on, we'll aim for
those on the back-end and Fineract to not impact core development or put
overall quality of the platform at risk.

We'll hear back on the status of our application by Feb 22 and if accepted,
interns can begin applying March 20.

We'll be adding our mentors and refining our ideas list at:
https://mifosforge.jira.com/wiki/spaces/RES/pages/3296690177/Google+Summer+of+Code+2023+Ideas

If you have any questions please contact me or or other org admins @Rahul
Goel  and @Sanyam Goel 

To express interest in mentoring, please fill the form out at
https://forms.gle/7X5c138tDJnmKTzC9

If you have ideas you'd like to list, please reach out to me or the other
org admins and we'll help get them added to the wiki page.

Later on, I will schedule a community-wide Zoom meeting to have a
discussion on potential ideas and answer questions of prospective mentors

Most of the changes that took place in 2022 have carried over to the 2023
program. These major changes are listed below.

(1) Starting in 2022, the program will be *open to all newcomers of open
source* that are 18 years and older, *no longer focusing solely on
university students**.*
(2) GSoC Contributors will be able to choose from multiple size projects
~175 hour (medium) and 350 hour (large).
(3) Google is building increased flexibility around the timing of projects
- there is an option to extend the standard 12 week coding time frame to a
maximum of 22 weeks

More on the 2023 program can be found at
https://developers.google.com/open-source/gsoc/resources/downloads/GSoC2023Presentation.pdf

The program starts slightly earlier this year with the coding program
officially beginning May 29 and for the standard duration projects ending
on August 8 and for the extended duration projects November 6.


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Heads up... next release 1.9.0 around the corner...

[Ed Cable]

Thank you Aleks for initiating this process. I am looking forward to
getting this significant release out to the community!

Ed

On Thu, Jan 26, 2023 at 4:06 PM Aleksandar Vidakovic 
wrote:

> Hi everyone,
>
> ... just wanted to inform you that we are planning to start the release
> process for the upcoming version 1.9.0 of Fineract soon.
>
> There have been a ton of new features, improvements and fixes since our
> last significant release 1.8.0 back in November (security fixes, business
> events, date handling, Spring Batch jobs...).
>
> You have still 2 weeks from now (until Wednesday, 8 Feb 2023) to get your
> suggestions and pull requests in place to be included before we open the
> release branch and have the official code freeze.
>
> Note: this time we'll have official release candidates as part of the
> release process to get stable pre releases earlier than usual into your
> hands instead of waiting for the entire 2 weeks for the release to finish.
>
> Opening the release branch in two weeks will mark automatically release
> candidate 0 (1.9.0.RC0). How many of those release candidates we'll have
> depends also on you and how much feedback you give, but we hope that
> release candidates make it a bit easier for you to do your own testing and
> send us feedback.
>
> You'll find a Jira ticket for this release here:
> https://issues.apache.org/jira/browse/FINERACT-1874
>
> Please make sure to mark your Jira tickets for version 1.9.0 if you want
> them included in this release.
>
> Cheers,
>
> Aleks
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Fineract as a Digital Public Good

[Ed Cable]

Yes to add to James' last point that is indeed one of the areas within the
DPG space where we've tried to impart our knowledge around the Apache way.
Adoption of DPGs amongst governments is a first step in this journey and
the next step is ensuring governments adopt support and development
policies to deploy, contribute to and maintain the upstream codebase.

Ed

On Fri, Jan 20, 2023 at 8:07 AM James Dailey  wrote:

> To put it simply:
> "An open source software becomes a Digital Public Good when it serves (as
> in ingredient) to build digital platforms sustaining national and
> international development, i.e.the Digital infrastructure that is used by
> every citizen on the planet or will be."  paraphrasing Kosta Peric, 2022
>
> We covered some of the opportunities for the Fineract project at ApacheCON
> October 2022, which we will highlight on list as things go forward.
>
> Moreover, there is an opportunity for this nascent DPG and Digital Public
> Infrastructure movement to learn from the experience of the Apache Software
> Foundation in ensuring things like vendor neutrality and public benefit of
> each project.
>
>
> On Wed, Jan 18, 2023 at 8:26 PM Bruce  wrote:
>
>> This is great news. Thank you for the update.
>>
>> On Thu, Jan 19, 2023, 3:06 AM Ed Cable  wrote:
>>
>>> Community,
>>>
>>> In the most recent report of the Fineract PMC to the Apache Board, the
>>> PMC announced that Fineract has been recognized as a Digital Public Good.
>>> Myself, James Dailey and Steve Conrad are active participants in the
>>> Digital Public Goods Alliance and help to represent and maintain Fineract's
>>> standing as a DPG including participation in roundtables, giving feedback
>>> to movements being led by the Digital Public Goods Alliance like the DPG
>>> Charter, maintaining our DPG listing, and ensuring that the Fineract
>>> codebase and community norms adhere to the DPG Standard -
>>> https://digitalpublicgoods.net/standard/. We recently updated our
>>> listing as additional clarification was sought as to how Fineract helps to
>>> advance the UN SDGs 1, 16, and 17. The updated listed will be viewable in
>>> DPG registry which will soon be live once again at
>>> https://digitalpublicgoods.net/registry/.
>>>
>>> A major focus of Fineract's role as a DPG is ensuring representation and
>>> participation in public sector adoption of DPGs as part of Digital Public
>>> Infrastructure primarily around use cases like G2P (Government to Person)
>>> payment and social protection programs. Members of the Fineract PMC have
>>> been actively representing Fineract in cross-sectoral movements like the
>>> Digital Public Goods Alliance, Digital Convergence Initiative, GovStack,
>>> G2P Connect and OpenG2P. James and myself shed light on this broader
>>> movement by facilitating a couple of talks during ApacheCon in New Orleans
>>> including a discussion with Jake Watson from DIAL on GovStack and a talk
>>> providing an update on OpenG2P.
>>>
>>> James, myself and Steve will continue to keep the community informed of
>>> progress and participation in the Digital Public Goods space.
>>>
>>> Thanks,
>>>
>>> Ed
>>>
>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Fineract as a Digital Public Good

[Ed Cable]

Community,

In the most recent report of the Fineract PMC to the Apache Board, the PMC
announced that Fineract has been recognized as a Digital Public Good.
Myself, James Dailey and Steve Conrad are active participants in the
Digital Public Goods Alliance and help to represent and maintain Fineract's
standing as a DPG including participation in roundtables, giving feedback
to movements being led by the Digital Public Goods Alliance like the DPG
Charter, maintaining our DPG listing, and ensuring that the Fineract
codebase and community norms adhere to the DPG Standard -
https://digitalpublicgoods.net/standard/. We recently updated our
listing as additional clarification was sought as to how Fineract helps to
advance the UN SDGs 1, 16, and 17. The updated listed will be viewable in
DPG registry which will soon be live once again at
https://digitalpublicgoods.net/registry/.

A major focus of Fineract's role as a DPG is ensuring representation and
participation in public sector adoption of DPGs as part of Digital Public
Infrastructure primarily around use cases like G2P (Government to Person)
payment and social protection programs. Members of the Fineract PMC have
been actively representing Fineract in cross-sectoral movements like the
Digital Public Goods Alliance, Digital Convergence Initiative, GovStack,
G2P Connect and OpenG2P. James and myself shed light on this broader
movement by facilitating a couple of talks during ApacheCon in New Orleans
including a discussion with Jake Watson from DIAL on GovStack and a talk
providing an update on OpenG2P.

James, myself and Steve will continue to keep the community informed of
progress and participation in the Digital Public Goods space.

Thanks,

Ed

Re: Best practices to customise Fineract codebase

[Ed Cable]

Shashwat,

In case you didn't find it on the list. There is some documentation on the
"drop-in" approach to extend functionality by overriding default services
with custom services via our custom modules which Aleks had been working
on::

https://fineract.apache.org/docs/current/#_custom_modules

Ed

On Tue, Jan 10, 2023 at 9:13 PM Shashwat Srivastava 
wrote:

> Victor - Thank you for the prompt response. Great points, indeed.
>
> Yes, absolutely. We are committed as an organization to contributing to
> open source. We are in a very early stage of adopting fineract and still
> learning. Will definitely raise PRs for the changes that we make. The only
> concern was that all such changes might not be helpful to larger community.
> But I guess it is better to suggest those changes and see if they are
> incorporated/merged.
>
> James, thanks for throwing light on design approach. Build "on-top-of" is
> exactly what I am looking for. I was exploring to see if I could add new
> handlers or use custom drop-in classes by implementing existing interfaces
> but wasn't sure if this approach was the right one. Will check for the
> "drop-in" approach to extend functionality.
>
> On Wed, Jan 11, 2023 at 10:16 AM James Dailey 
> wrote:
>
>> Those are good comments Victor.  Absolutely!
>>
>> Shashwat -
>> In that vein… We also must have a design approach that isn’t “strongly
>> typed” to a single institutional set of requirements.  When modeling a
>> design change, gather all of related use cases so that it’s a truly
>> valuable contribution.
>>
>> I’m addition, one of our goals we have as a project is to make it
>> possible for specific implementations to build “on-top-of”.  There was
>> mention of a Java class “drop in” strategy in I think version 1.7?
>> (Whereby core release remains but you can instantiate specific “over rides”
>> ). Search the archives for that.  That may answer, but only under certain
>> circumstances.  It was imagined as a way to “extend” existing
>> functionality.   We should make sure that gets documented.
>>
>>
>>
>> On Tue, Jan 10, 2023 at 8:11 PM VICTOR MANUEL ROMERO RODRIGUEZ <
>> victor.rom...@fintecheando.mx> wrote:
>>
>>> If the organization is committed to open source, modify it and send it
>>> back to the community as PR, best practices and debate will go to the
>>> source code itself. By experience if you go to implement a new big feature
>>> or vice versa a small change, anyone in the community will implement it and
>>> then the code in the source code could be refactored leaving your code with
>>> conflicts or hard to upgrade, i.e. today morning someone was facing an
>>> issue about the MySQL/MariaDB database creation and now the PR is ready to
>>> be reviewed/merged. For sure it is better to send back the changes and
>>> receive feedback as soon as possible.
>>>
>>> If your organization has a lot of FTE working on new features, changes,
>>> improvements in your fork/branch... the same proportional effort (most of
>>> the time, effort is measured in hours) will be invested to do the
>>> merge/upgrade to a new Apache Fineract release.
>>>
>>> If there are intellectual property reasons or limitations by a regulator
>>> or authority then... create a plugin or another external microservice
>>> without touching the code base. I have written a lot of "if" because of a
>>> lack of details about the roadmap of your implementation.
>>>
>>> You can look at  https://www.apache.org/theapacheway/
>>>
>>> El mar, 10 ene 2023 a las 21:27, Shashwat Srivastava ()
>>> escribió:
>>>
>>>> Hi everyone,
>>>>
>>>> I have been going through the Fineract codebase for our organization
>>>> recently. And I had a fundamental question. If I want to customise specific
>>>> behaviour, for instance, add a new allocation priority order or change how
>>>> the repayment schedule is generated. Is there a recommended way of doing
>>>> such customisations to ensure that you don't modify the original codebase?
>>>> Is there any documentation around this? Please share.
>>>>
>>>> Cheers,
>>>> Shashwat
>>>>
>>>>
>>> --
>> Sent from Gmail Mobile
>>
>
>
> --
> Shashwat Srivastava
>
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

[ANNOUNCE] Welcome Bharath Gowda as New Apache Fineract Committer

[Ed Cable]

Hello all,

I am happy to announce Bharath Gowda as a new committer. Bharath has played
a valuable role over the years as one of the foremost functional experts of
the platform. He is an active presence across the mailing list and
throughout Jira helping to shape requirements and triage new issues as well
as on board new contributors to the community.

Please join us in welcoming Bharath as a committer.

Ed

Re: [FINERACT] [VOTE] ️ 1.7.2 for release

[Ed Cable]

+1 (binding).

On Tue, Nov 29, 2022 at 7:08 AM James Dailey  wrote:

> +1 (binding)
>
> I did not do a review.
>
> On Tue, Nov 29, 2022 at 7:04 AM Kigred Developer
>  wrote:
> >
> > +1
> >
> > On Tue, 29 Nov 2022, 14:32 Aleksandar Vidakovic, 
> wrote:
> >>
> >> Hello everyone,
> >>
> >> ... we have created Apache Fineract 1.7.2 release, with the artifacts
> below up for a vote.
> >>
> >> It fixes the following issues:
> https://cwiki.apache.org/confluence/display/FINERACT/1.7.2+-+Apache+Fineract
> >>
> >> Source & Binary files :
> https://dist.apache.org/repos/dist/dev/fineract/1.7.2/
> >>
> >> Tag to be voted on (rc#):
> https://gitbox.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.7.2
> >>
> >> Fineract's KEYS containing the PGP key we used to sign the release:
> https://dist.apache.org/repos/dist/dev/fineract/KEYS
> >>
> >> Note that this release contains source and binary artifacts.
> >>
> >> This vote will be open for 72 hours:
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove (and reason why)
> >>
> >> Cheers,
> >>
> >> Aleksandar Vidakovic
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINERACT] [VOTE] ️ 1.7.2 for release

[Ed Cable]

+1 binding

On Tue, Nov 29, 2022 at 6:21 AM Avik Ganguly  wrote:

> +1
>
> On Tue, Nov 29, 2022 at 5:02 PM Aleksandar Vidakovic 
> wrote:
>
>> Hello everyone,
>>
>> ... we have created Apache Fineract 1.7.2 release, with the artifacts
>> below up for a vote.
>>
>> It fixes the following issues:
>> https://cwiki.apache.org/confluence/display/FINERACT/1.7.2+-+Apache+Fineract
>>
>> Source & Binary files :
>> https://dist.apache.org/repos/dist/dev/fineract/1.7.2/
>>
>> Tag to be voted on (rc#):
>> https://gitbox.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.7.2
>>
>> Fineract's KEYS containing the PGP key we used to sign the release:
>> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>>
>> Note that this release contains source and binary artifacts.
>>
>> This vote will be open for 72 hours:
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Cheers,
>>
>> Aleksandar Vidakovic
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINERACT] [VOTE] ️ 1.8.2 for release

[Ed Cable]

+1 binding.

On Mon, Nov 28, 2022 at 11:04 AM Aleksandar Vidakovic 
wrote:

> Hello everyone,
>
> ... we have created Apache Fineract 1.8.2 release, with the artifacts
> below up for a vote.
>
> It fixes the following issues:
> https://cwiki.apache.org/confluence/display/FINERACT/1.8.2+-+Apache+Fineract
>
> Source & Binary files :
> https://dist.apache.org/repos/dist/dev/fineract/1.8.2/
>
> Tag to be voted on (rc#):
> https://gitbox.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.8.2
>
> Fineract's KEYS containing the PGP key we used to sign the release:
> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>
> Note that this release contains source and binary artifacts.
>
> This vote will be open for 72 hours:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Cheers,
>
> Aleksandar Vidakovic
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Survey Results November 2022

[Ed Cable]

Thanks for initiating this survey and circulating the feedback.

Ed

On Sun, Nov 27, 2022 at 10:52 PM James Dailey 
wrote:

> I have posted the results of a community survey conducted in November
> 2022.  The survey was advertised on D ev at
> fineract.apache and was open for 12 days.
>
>
> https://cwiki.apache.org/confluence/display/FINERACT/Survey+Results+2022+November
>
> <https://cwiki.apache.org/confluence/display/FINERACT/Survey+Results+2022+November>
>
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Intro to new person Navleen

[Ed Cable]

Navleen, do let us know if you face any challenges in getting your JIRA
credentials created.

Meta - the default open source front-end for Fineract is maintained by the
Mifos Initiative as a separate repository outside of ASF - you can learn
more about the needs for contribution to the web-app in the slack channel
#web-app which you can join at https://bit.ly/mifos-slack. There are
currently some ongoing efforts with i18n to help with migrating over the
translated message strings from the older community app to new web-app.

Ed

On Sun, Nov 27, 2022 at 10:04 PM Navleen Kaur 
wrote:

> Thanks for this information James.
> I have gone through the above link, and it's very helpful. I have asked
> for the access from the relevant team.
>
> *Navleen Kaur*
>
>
> *W:*
>
> www.indiagold.co
>
>
>
>
>
> On Sun, 27 Nov 2022 at 00:55, James Dailey  wrote:
>
>> Navleen - Did you pursue this further?
>>
>> If you have found an error and which to create a JIRA Ticket, the infra
>> team has created a process by which you could be granted such access.
>>
>> https://infra.apache.org/jira-guidelines.html
>>
>> As of November 2022, due to increasing spam accounts, Infra at apache
>> disabled public creation of jira accounts.
>>
>>
>>
>> On Tue, Nov 15, 2022 at 10:11 PM James Dailey 
>> wrote:
>>
>>> Navleen -
>>>
>>> First, welcome to the listserv and the Fineract project.
>>>
>>> It is customary to try to first gain an understanding of the project by
>>> reading the wiki and reviewing past emails
>>> https://lists.apache.org/list.html?dev@fineract.apache.org
>>>
>>> and the past Community Reports.
>>>
>>> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+PMC+Reports+to+Apache+Board
>>>
>>> You should have this page ==> https://fineract.apache.org/.
>>>
>>> and the FAQ
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327
>>>
>>> Note that this is completely public listserv and is neither confidential
>>> nor privileged: You may want to change your standard email signature.
>>>
>>> Please start by reading the docs and familiarizing yourself with the
>>> community.  I think you *may* have a problem with understanding how the
>>> application works.  There is a lack of good documentation unfortunately.
>>>
>>> It often takes a new person a few weeks or months to learn enough about
>>> the application to know how to do a common activity.  This is a complex
>>> banking application, and it will take time.  If you have an urgent need
>>> there are people who are willing to help but first put in the time to
>>> understand the application.
>>>
>>> Please DO NOT EXPECT someone to drop everything and respond to your
>>> specific calculation issue.   We are volunteers.   Read more about how we
>>> work...  https://www.apache.org/
>>>
>>> It is possible you have found an error.  There are hundreds of open
>>> tickets, and we may or may not have anyone here willing to fix it.  Before
>>> you create a ticket you should detail all of the very specific
>>> configurations and steps you did to create the scenario, then erase and
>>> repeat until it is "reproducible".
>>>
>>> *Lastly, please use a separate email thread for a different discussion.
>>> Your email is not about the survey.   *
>>>
>>> Jdailey
>>>
>>>
>>> On Tue, Nov 15, 2022 at 8:57 PM Navleen Kaur
>>>  wrote:
>>> >
>>> > Hi Team
>>> >
>>> > How can I get access to JIRA? I have observed an issue in Fineract
>>> which I posted in the slack channel as well.
>>> > Could you please help me with further steps, I'm new to Fineract.
>>> >
>>> >
>>>
>>
>
> The information contained in this e-mail and any attachment herein is
> confidential and privileged, belonging to Flat White Capital Pvt Ltd and is
> intended solely for the use of the intended recipient/addressee(s). Access,
> copying or re-use of the e-mail or any attachment or any information
> herein, by any other person is not authorized. If you are not the intended
> person/addressee(s) or have received this e-mail in error, please return
> this e-mail to the sender and delete it from your computer/system. Internet
> communications are not guaranteed to be secured or virus free. Although we
> attempt to sweep e-mail and attachments for virus, we do not guarantee that
> they are virus free and accept no liability for any damage or loss as a
> result of virus or from unauthorized access/usage. Any opinion or other
> information in this e-mail or its attachments that does not relate to the
> business of Flat White Capital Private Limited is personal to the sender
> and is not given or endorsed by Flat White Capital Private Limited.
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Addition to community

[Ed Cable]

Welcome Shobhit. Echoing what Aleks had to say - please don't hesitate if
you have any questions. Over the past year work has gone into a collateral
management module but the needs for gold and other asset-backed loans
continue to vary. You're welcome to discuss your requirements and we can
see how those might align with the roadmap being defined across the
community. If any gaps arise, we can help connect you with a provider to
extend Fineract to meet your functional needs and/or help your team in
building out independently and contributing it back upstream.

Cheers,

Ed

On Mon, Nov 28, 2022 at 6:49 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Welcome Shobhit... reach out if you have any questions and/or need some
> pointers.
>
> On Mon, 28 Nov 2022, 13:54 shobhit asai,  wrote:
>
>> Hi Team,
>>
>> Could you please add me to the community?
>>
>> I'm Shobhit Asai, work as a Product Manager for a fintech startup that is
>> helping people monetise their gold assets (jewellery) and provide loans
>> against it. We are exploring Mifos as a potential LMS.
>>
>> Thanks,
>> Shobhit.
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINERACT] [VOTE] ️ 1.7.1 for release

[Ed Cable]

+1 binding


On Wed, Nov 23, 2022 at 11:23 PM Kigred Developer <
kigred.develo...@gmail.com> wrote:

> +1
>
> On Thu, 24 Nov 2022, 09:22 Aleksandar Vidakovic,  wrote:
>
>> Hello everyone,
>>
>> ... we have created Apache Fineract 1.7.1 release, with the artifacts
>> below up for a vote.
>>
>> It fixes the following issues:
>> https://cwiki.apache.org/confluence/display/FINERACT/1.7.1+-+Apache+Fineract
>>
>> Source & Binary files :
>> https://dist.apache.org/repos/dist/dev/fineract/1.7.1/
>>
>> Tag to be voted on (rc#):
>> https://gitbox.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.7.1
>>
>> Fineract's KEYS containing the PGP key we used to sign the release:
>> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>>
>> Note that this release contains source and binary artifacts.
>>
>> This vote will be open for 72 hours:
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Cheers,
>>
>> Aleksandar Vidakovic
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINERACT] [PROPOSAL] Minor version release

[Ed Cable]

Thank you for working on this process and documentation with Aleks.

To clarify, I understand that voting is still required but this is a more
expedited process than a normal release because it doesn't require that 2
week freeze/soak period correct?

+1 from me.

Ed

On Sun, Nov 13, 2022 at 11:38 PM Bharath Gowda  wrote:

> Hi Manoj,
>
> I agree with you on the need for minor patch releases for the main release
> versions as it helps a lot for organizations that are already using that
> version in their live environment.
>
> +1 from my side
>
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> Skype: live:cbharath4| Mobile: +91.7019635592
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
>
>
> On Mon, Nov 14, 2022 at 5:01 AM Anu Omotayo 
> wrote:
>
>> Well done Manoj for this initiative, you have my +1 vote.
>>
>> Major versions supported and when support will end also needs to be
>> looked into e.g
>>
>> Major versions 1.6.X and 1.7.X are in use on production by some customers
>> 1.8.X has been released and is the current version
>>
>> When will support for 1.6.X and 1.7.X end?
>>
>> Regards
>> Anu Omotayo
>>
>>
>> On Sunday, November 13, 2022 at 10:31:29 PM GMT+1, Manoj VM <
>> ma...@fynarfin.io> wrote:
>>
>>
>> Hi Everyone,
>> ... this is a continuation of the discussionAleksandar Vidakovic  started
>> some time before related to minor version releases
>>
>> 1. As we are constantly improving the Fineract with technology and
>> functionality, each version is released with updates that take time
>> to upgrade for existing users who are already live with a previous version.
>> While they want to eventually move to the latest version they also want to
>> do it at their will. ie, it is difficult for a user to upgrade to the
>> latest version of Fineract just for minor fixes that are needed for their
>> production to be stable.
>> Hence it is a request from many Fineract users to have minor(patch)
>> version releases on top of a Fineract release.
>> For example, someone who is live on production with version 1.7.0 does
>> not wish to upgrade to 1.8.0 or later just for a hotfix that is needed on
>> version 1.7.0. It requires additional testing and effort and it is not
>> feasible at the essence of time. Hence the hotfix should be provided as a
>> patch ( minor) version release 1.7.1.
>>
>> 2. While we haven't done that before, it is not so difficult to have a
>> minor version release. I was discussing this with Aleks and we have come up
>> with the following approach to do the minor version release. The process
>> can be as given below:
>>  1. Minor version releases are not so different from normal releases,
>> just that the waiting period for changes discussion is less because it is a
>> minor change on top of an already approved release. The discussion on the
>> PR happens on GitHub.
>> 2. Voting is needed for the release.
>> 3. Create a release branch from the previous version, and ask patch
>> developers to send PRs to this branch. For example,  for minor version
>> release 1.8.1, the release branch 1.8.1 is created from the 1.8.0 tag
>> 4. Once the minor version is released, the Release Manager has to
>> merge this branch to develop to keep the develop branch updated, this can
>> be done by creating a merge branch.
>> 5. Sign and upload the minor version release to the Fineract website
>> /SVN
>> 6. Clean up by removing the branches created.
>>
>> Dear Members of the community, kindly vote for this process, and please
>> provide your valuable feedback and suggestions.
>>
>> Thanks and Regards,
>> Manoj
>>
>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [DISCUSS] User listserv

[Ed Cable]

+1 to option #1 but let's determine if we call it user or users - our
previous incarnation of a Fineract User Mailing lists was just singular in
u...@fineract.apache.org - if we kept it the same, could have same
historical archive (albeit with a 4 year gap since 2018.

Also, Mifos continues to maintain a #help channel in its slack workspace to
try to help with support and general user inquiries as well. The
mifos-users and mifos-developer lists still exist too given they cover
questions/topics related to usage/UI/etc which technically aren't part of
the Fineract 1.x solution stack.

E

On Fri, Oct 28, 2022 at 11:30 AM James Dailey 
wrote:

> Hi Devs -
>
> A few years ago we decided to collapse the Dev@fineract.apache.org and
> us...@fineract.apache.org listservs to have one place for discussions.
>
> This had the advantage of reducing the number of lists one needed to
> subscribe to.
>
> The disadvantage is that we may - from time to time - get users who simply
> want to know how to "run the software" and "how to use the software" rather
> than "how to set up the dev environment", "how to describe an issue in a
> ticket", "how to make a code contribution", or "go deep into technical
> discussion abc".
>
> I'd like to offer two proposals for discussion:
>
> 1)  Set up us...@fineract.apache.org and encourage users to move over
> there with questions - keep this separate; obviously can be viewed or
> subscribed to by anyone.
> Hold a regular "user meeting" to establish some good Q for users.  We
> would want to have a few Contributors on the list to answer questions and
> generally move that conversation along.
> Alongside  us...@fineract.apache.org would be some wiki pages to orient
> the users.
> With this, d...@fineract.org becomes more focused on development
> practices, tickets, commits, engineering design discussions.
>
> alternatively:
> 2) Direct newcomers and users to a page on the wiki where we link to
> various resources, including outside resources.  When a person signs up
> for the listserv, or shows up, we ask them to first go through those
> resources, and if they still have questions for Dev, then we encourage
> that.
>
> I believe that coming to the project cold can be quite baffling.
>
> This is a DISCUSS thread, meaning please comment.   Quick reactions could
> be:
> +1  Like it
> 0No opinion or neutral
> -1   Don't like it.
>
>
> Thanks,
> @jdailey
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

EVENT: 2022 Google Summer of Code Final Showcase - Friday Sept 30 at 1400GMT via Zoom Webinar

[Ed Cable]

Hi all,

The 2022 Google Summer of Code is wrapping up and the ten interns that
Mifos Initiative has been mentoring are eager to showcase the work that was
completed during this program. This year our interns worked on a mix of
projects including refactoring the Fineract 1.x back-end to reduce
boilerplate code, improvements to the Fineract SDK and Android Client,
enhancements to the credit scoring module, implementation of a mobile UI
library and set of common components for mobile apps to consume,
improving authentication within the payment hub and evolving our mobile
wallet and vision PPI apps.

The showcase is 90 minutes long on Friday September 30 at 1400GMT.

Please register to attend via Zoom:
https://us02web.zoom.us/webinar/register/4716642858974/WN_1kOiK5dnTH6GtK9oUJca5Q

All the best,

Ed

Re: Fineract CN current status and pointers

[Ed Cable]

Anjil,

The repositories for Fineract CN in Github are relatively up to date. There
are some potential contributions from one of our partners in Mexico that
might be contributed upstream but they were pending the release from the
customer they were built for.

I'd be happy to jump on a call with you to discuss your exact use cases
you're looking to support and which platform would be best option for you -
Fineract 1.x or Fineract CN. Based on that I can identify how best to
support you and connect you with resources active on Fineract and Fineract
CN.  Originally the goal of the community was to put a deeper focus on
Fineract CN for greater modularity and scalability but in practice the
community based on uptake of partners and customer adoption has decided to
continue focused development on Fineract 1.x and implementing a greater
degree of modularity and scalability on that codebase to help institutions
of all sizes run and operate Fineract 1.x-based solutions even at planet
scale.

There are a handful of users on Fineract CN including one that is on it's
own forked version and then another user in South Africa that is intending
to invest in active development of Fineract CN to help modernize it even
further.

Thanks,

Ed


On Mon, Sep 26, 2022 at 6:36 AM Anjil R Chinnapatlolla 
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,
>
> Anjil
>
>
>
>
>
>
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: ph-ee-operations-app deployment

[Ed Cable]

Danish,

Are you able to help Chantilly with his request?

Chantilly, you could also post your query in the #payment-hub slack channel
in the Mifos workspace.

Thanks,

Ed

On Tue, Sep 27, 2022 at 1:09 AM Chantilly Muyaya 
wrote:

> Hello Team,
>
> I'd like to know if anybody can help me, to deploy this app
>
> *"https://github.com/openMF/ph-ee-operations-app
> <https://github.com/openMF/ph-ee-operations-app>"*
>
> And connect it with Fineract 1.x
>
> The readme file inside this app contain nothing.
>
> Regards
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

State of Open Source in Financial Services Survey

[Ed Cable]

Hi all,

Our friends over at FINOS are conducting their annual State of Open Source
in Financial Services survey and I thought it would be great for members of
the Fineract community to lend their voice about the State of Open Source
at their respective organizations. Fintechs are somewhat unrepresented
within FINOS so i think our large subset of fintechs would provide a
valuable voice/perspective for this survey.

The original survey close date of August 30 was extended through late
September but I'm not sure when the actual survey closes so please take
time to submit a response when you can. It should only take about 10
minutes or so.

https://www.research.net/r/PNBKH9W

Thanks,

Ed Cable

Re: [ANNOUNCE] Apache Fineract 1.8.0 Release

[Ed Cable]

Great work Aleks! Have you already shared documentation on the community
point release strategy that this will enable?

Thanks,

Ed

On Sun, Aug 28, 2022 at 12:22 PM Bruce  wrote:

> This is awesome.Congratulations Community.
>
> On Sunday, August 28, 2022, Javier Borkenztain  wrote:
>
>> congratulations community!
>>
>> Thank you Aleks for driving this new release.
>>
>> Javier
>>
>> On Sun, Aug 28, 2022, 08:03 Aleksandar Vidakovic 
>> wrote:
>>
>>> The Apache Fineract project is pleased to announce
>>> the release of Apache Fineract 1.8.0.
>>> The release is available for download from
>>> https://fineract.apache.org/#downloads
>>>
>>> Fineract provides a reliable, robust, and affordable solution for
>>> entrepreneurs,
>>> financial institutions, and service providers to offer financial
>>> services to the
>>> world’s 2 billion underbanked and unbanked. Fineract is aimed at
>>> innovative mobile
>>> and cloud-based solutions, and enables digital transaction accounts for
>>> all.
>>>
>>> This release addressed 47 issues.
>>>
>>> Readme: https://github.com/apache/fineract/blob/1.8.0/README.md
>>>
>>> Release page:
>>> https://cwiki.apache.org/confluence/display/FINERACT/1.8.0+-+Apache+Fineract
>>>
>>> List of fixed issues:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351315=Html=12319420
>>>
>>> For more information on Apache Fineract please visit
>>> project home page: https://fineract.apache.org
>>>
>>> The Apache Fineract Team
>>>
>>
>
> --
> Think Abundance
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: QA and process overall

[Ed Cable]

+1 from my side and that time should work.

Not.to inflate the agenda, but it might also be good during that meeting to
brief the community properly on the current status of using cucumber for
expanding testing coverage and pointing to how others in the community
could contribute to those efforts.

Ed

On Thu, Aug 25, 2022 at 4:06 PM James Dailey  wrote:

> Devs -
>
> I'd like to have a discussion around code quality and process quality.
>
> @alexs remarked during the release process of 1.8 (in process) that he
> wasn't always able to find a related Jira ticket for the PR or commit.
> This is a big problem!
>
> We should, in my view, simply revert or remove any contribution that
> doesn't have the proper documentation of WHY it is there and HOW the
> developer came to a specific design or approach. Also PRs and commits must
> have the proper format and should not happen without a jira ticket.
>
> I understand that this happens sometimes because people are "on deadlines"
> and need the feature right away... but I also know that sometimes the
> discovery process, which is implied by the jira ticketing idea, gets to a
> different solution.  For example, perhaps there is a way to configure a
> consumer facing product that doesn't involve placing your specific
> requirement in the java data class. There are other built out mechanisms.
>
> This surfaces the second problem: maintainability of the code.
> Maintainability is a squishy concept but you know it when it fails -
> projects get harder to work on - code is not understandable, the reasons
> for the code changes are unclear or illogical, new features and
> functionality are harder and harder to add. Tests sometimes catch this, but
> often not.
>
> Fundamentally, quality, maintainability, and security are all "collective
> action". We all have to agree to do it and have high standards.  We need a
> new agreement.
>
> So, I invite some comments here and propose a quality alignment zoom
> meeting for any active projects using Fineract.  Fineract is being used in
> production so it is increasingly important that we ensure a quality
> mindset.  Then, we document the agreement and bring it back to the list and
> the wiki.  We can use this as a follow up on the previous QA and testing
> discussion:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=195730039
>
>
> Proposed Zoom call:
> 7am PDT next week on Wednesday , Aug 31st
> 9am CDT
> 4pm CEST
> 7:30pm IST
>
> I'll send out details if you want to attend.  Please contact me directly.
>
> Thanks,
> James
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINERACT] [VOTE] ️ 1.8.0 for release

[Ed Cable]

+1 (binding)

On Mon, Aug 22, 2022 at 10:35 AM Bharath Gowda  wrote:

> +1
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> Skype: live:cbharath4| Mobile: +91.7019635592
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
>
>
> On Mon, Aug 22, 2022 at 10:30 PM Avik Ganguly  wrote:
>
>> +1
>>
>> On Mon, 22 Aug, 2022, 10:05 pm Aleksandar Vidakovic, 
>> wrote:
>>
>>> Hello everyone,
>>>
>>> ... we have created Apache Fineract 1.8.0 release, with the artifacts
>>> below up for a vote.
>>>
>>> It fixes the following issues:
>>> https://cwiki.apache.org/confluence/display/FINERACT/1.8.0+-+Apache+Fineract
>>>
>>> Source & Binary files :
>>> https://dist.apache.org/repos/dist/dev/fineract/1.8.0/
>>>
>>> Tag to be voted on (rc#):
>>> https://gitbox.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.8.0
>>>
>>> Fineract's KEYS containing the PGP key we used to sign the release:
>>> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>>>
>>> Note that this release contains source and binary artifacts.
>>>
>>> This vote will be open for 72 hours:
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>> Cheers,
>>>
>>> Aleksandar Vidakovic
>>>
>>
>> Disclaimer:
>>
>> Privileged & confidential information is contained in this message
>> (including all attachments). If you are not an intended recipient of this
>> message, please destroy this message immediately and kindly notify
>> the sender by reply e-mail. Any unauthorised use or dissemination of this
>> message in any manner whatsoever, in whole or in part, is strictly
>> prohibited. This e-mail, including all attachments hereto, (i) is for
>> discussion purposes only and shall not be deemed or construed to be a
>> professional opinion unless expressly stated otherwise, and (ii) is not
>> intended, written or sent to be used, and cannot and shall not be used, for
>> any unlawful purpose. This communication, including any attachments, may
>> not be free of viruses, interceptions or interference, and may not be
>> compatible with your systems. You should carry out your own virus checks
>> before opening any attachment to this e-mail. The sender of this e-mail and
>> *Fynarfin Tech Private Limited* shall not be liable for any damage that
>> you may sustain as a result of viruses, incompleteness of this message, a
>> delay in receipt of this message or computer problems experienced.
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [COLLABORATE] August 2022 Fineract Board Report

[Ed Cable]

Thanks Aleks and Awasum. I added a few changes as I didn't realize today
was the submission date.

Ed

On Fri, Aug 12, 2022 at 8:31 AM Awasum Yannick  wrote:

> Thank you all very much especially Aleks for getting this over the link.
>
> We have now reviewed and submitted the report.
>
> On Tue, Aug 9, 2022 at 10:15 AM Awasum Yannick  wrote:
>
>> Hi All,
>>
>> We started writing the Fineract board report for August.
>>
>> Here is the link:
>> https://cwiki.apache.org/confluence/display/FINERACT/2022-08+August+Report
>>
>> We invite you all to contribute to the report based don't eh activities
>> that have been taking place over the past 4 months.
>>
>> We will complete this and assemble the report to submit on Friday 12th
>> August 2022.
>>
>>
>> Thanks.
>> Awasum Yannick
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [ANNOUNCE] Welcome Manoj Mohanan as New Apache Fineract Committer

[Ed Cable]

Congrats Manoj. Glad you'll be able to take a deeper and more active role
beyond the one you already have played in the community.

Ed

On Wed, Aug 10, 2022 at 1:00 PM Javier Borkenztain  wrote:

> congratulations Manoj!
>
> Doing more with less are the kind of things I love!
>
> Javier Borkenztain
>
>
> On Wed, Aug 10, 2022, 15:48 Awasum Yannick  wrote:
>
>> Hello Everyone,
>>
>> I am happy to announce that the Apache Fineract PMC recently voted to
>> add Manoj as a Fineract Committer and we are delighted to say that He has
>> accepted our invitation.
>>
>> Manoj has been a long-time contributor to Mifos and Apache Fineract over
>> the past years. He currently works for fynarfin.io where He leads a team
>> building on top of Apache Fineract.
>> He has contributed a lot of bug fixes and features around loans, savings,
>> etc, helping review changes by other developers on Github while also
>> testing a lot of the key features which have been rolled out over the past
>> year.
>>
>> We are very happy to have him as a Committer for Apache Fineract.
>>
>> Please join me in Congratulating Manoj on a well-deserved recognition.
>>
>>
>> Thanks
>> Awasum Yannick.
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Notification topic subscription feature abandoned?

[Ed Cable]

I'm cc'ing @Pranjal Goswami   who originally
designed the notifications framework.

Here's one of the original design docs on the notification storage and
topic subscription.

https://docs.google.com/presentation/d/1jzqEQxxRYa1ZvN_SXLRwDgXBux1cb3_IMBWbdS7rRV0/edit?usp=sharing

Once it's fully implemented, it will and has to date served as a
foundational component to generating both staff and customer facing
notifications which can be displayed in the Web UI as well as mobile apps.

As a bit more background and  context, I'm forwarding a previous thread
from 2020 in which we were trying to extend the notifications framework to
generate FCM notifications via mobile apps.

=

Email from July 2020
Pranjal, Courage, Nazeer and others

I'm responding on top of this thread as both Devansh and Shashank are
blocked in trying to move forward with the portions of their projects
related to consuming FCM notifications. From our previous meeting, we had
somehow concluded that the PR at
https://github.com/apache/fineract/pull/421 was
for FCM notifications support but in talking with Nazeer it was only for
SMS campaigns.

Nazeer - are you able to clarify on that PR. If it doesn' have the support
for FCM notifications, can we outline the work involved in providing
server-side support to generate the FCM notifications.

Thanks all. Once we come to more clarity i'll take this to the list. If a
call is quickest way to tackle this, let's get one scheduled.

Thanks,

Ed

On Fri, Jun 5, 2020 at 4:22 PM Ed Cable  wrote:

Hi all,

Just to follow up on the second leg of the meeting we had to discuss the
notifications sub-system being used for the Request to Pay API for the
mobile wallet as well as a general update about the mobile wallet use case
in the near term to have it work in the new lab environment.

https://us02web.zoom.us/rec/share/5-oyIZrd1mZLYNLutAL8avU5H9zPX6a8gClL-fEPyh5OYllEDFBX8_ENod_Zeup_?startTime=1591200315000

>From the discussion, it appears the current manner in which notifications are
generated and stored in Fineract 1.x will work for the request to pay API.
However we must ensure that the self-service users (which should be in the
same users table but just denoted as "self-service") are subscribed to this
topic to receive the notification.

All students working on the customer-facing apps for Fineract 1.x,
should familiarize themselves with the notifications system (see previous
design and how it works) as the client-side integration should also be
complete for mifos mobile and mobile wallet.  If you have any questions,
please share them publicly on the mifos and fineract dev list and discourse
forum as it's a valuable discussion for community.

@Ebenezer Graham  can we grab some time to
discuss integration with the Fineract CN notifications microservices.

We identified some small action items to take to make the current mobile
wallet work for the prior 2 Mojaloop use cases and soon the 3rd Mojaloop
use case in our lab environment.
We need to:

1) Provide Shivansh and Devansh with both the updated environment details
of the Fineract, Payment Hub instances in the new lab environment as well
as the updated API endpoints.
2) Confirm where the MSISDN is being stored as an additional attribute for
Fineract.
3) Ensure that the Interop users/customers that are created in the Fineract
instances have an associated self-service user account and to add these
credentials to the lab environment Google sheet.

https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit?usp=sharing

Once the above is in place, we should be able to have the initial 2
mojaloop use cases of peer to peer transfer and payment via QR code work
with actual authenticated self-service users (not just hard-coded JSON user
data).



On Tue, Jun 2, 2020 at 9:19 AM Ed Cable  wrote:

Hi everyone,
Thank you for those who were able to join, especially to Pranjal for
joining short notice. We made some good progress in the discussion but will
continue this conversation once Istvan can join during part of our call
tomorrow that was scheduled for Open Banking fintech app requirements.

Here's a summary of what we concluded and outstanding questions/next steps:
*Fineract 1.x*

   - Creation and Storage of Notifications on Back-End
   -
  - Per the design of Pranjal and implementation by Courage and
  Adhiyan, the notifications subsystem for creating and storing
  notifications through the publisher/subscriber/topic model is
  complete and more recently has been updated by Nazeer to work with FCM
  messaging
  -
 - Slides on Design of Notification Subsystem:
 
https://docs.google.com/presentation/d/1jzqEQxxRYa1ZvN_SXLRwDgXBux1cb3_IMBWbdS7rRV0/edit?usp=sharing
 - Link to PR updating notifications for Fineract -
 https://github.com/apache/fineract/pull/421
  - Receiving notifications through channel apps
   -
  - Working for 

Re: Spring Batch integration

[Ed Cable]

Arnold,

Thank you for sharing the in progress design documentation. I have been
forwarding it to some other individuals for their feedback.

@Pramod Nuthakki  had the following question regarding
jobs dependent on other jobs.

"Currently  few scheduled jobs have dependency on other  jobs like NPA
depends on arrears job, Accruals has dependency  on NPA jobs etc... Once we
move the jobs to batch processing then how the above mentioned dependency
will be addressed."

Thanks,

Ed


On Mon, May 16, 2022, 05:04 Arnold Galovics  wrote:

> Dear all,
>
> I'd like to introduce you to the idea of enhancing Fineract with the
> capability to handle high-volume batch jobs along with a few other things.
>
> As any financial system, Fineract also supports batch jobs but they're
> quite limited on the data volume it can handle. Currently a batch job is a
> single Java method with loading everything at once and processing that huge
> chunk of data in a single execution step/transaction.
>
> To make Fineract better, we need to alter this simplified framework a
> little bit and introduce something that's more battle-tested: the Spring
> Batch module is here to help.
>
> With introducing Spring Batch into the mix, we'll finally have a chance to
> decouple data reading, processing and data writing that'll finally bring us
> the benefit of making our batch jobs:
> - faster
> - reliable
> - being able to handle huge data volumes
>
> And I'm not gonna just stop there, with Spring Batch in place, we'll be
> able to distribute our batch job workloads into separate JVMs in a scenario
> where we want to run a cluster of Fineract instances to cope with the load.
>
> The next thing to the Spring Batch module integration is the introduction
> of a new batch job, Loan Close Of Business; that'll be the starting point
> of reworking the date handling in Fineract. This job will be simply
> responsible to "close" Loans on a daily basis making sure that
> interests/fees/etc are calculated properly. It's going to be the first
> full-fledged job that'll be able to run in a partitioned mode on a cluster
> of JVMs and multiple threads.
>
> The job will be rolled out as disabled by default so it won't interfere
> with any existing deployments but if somebody will need it's potential and
> business functionality, they can certainly enable it. Also, there's an
> extensive documentation I already wrote for this; right now it's in PR for
> some review and I'm gonna do a few additional modifications but you can
> check it out here: https://github.com/apache/fineract/pull/2326
>
> I don't want to repeat everything that's in the PR so if you're curious be
> sure to check it.
>
> TL;DR; Spring Batch is going to be integrated into Fineract. A new batch
> job called Loan Close Of Business will be created along with some
> additional functionality that's described in the PR above.
>
> Best,
> Arnold
>
>

Re: [FINERACT] [VOTE] ️ 1.7.0 for release

[Ed Cable]

+1

On Wed, May 11, 2022 at 7:57 AM Aleksandar Vidakovic 
wrote:

> Hello everyone,
>
> ... we have created Apache Fineract 1.7.0 release, with the artifacts
> below up for a vote.
>
> It fixes the following issues:
> https://cwiki.apache.org/confluence/display/FINERACT/1.7.0+-+Apache+Fineract
>
> Source & Binary files :
> https://dist.apache.org/repos/dist/dev/fineract/1.7.0/
>
> Tag to be voted on (rc#):
> https://gitbox.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.7.0
>
> Fineract's KEYS containing the PGP key we used to sign the release:
> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>
> Note that this release contains source and binary artifacts.
>
> This vote will be open for 72 hours:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Cheers,
>
> Aleksandar Vidakovic
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Mifos Initiative seeking Technical Writer for 2022 Google Season of Docs Project

[Ed Cable]

The Mifos Initiative is excited to have been selected for the second time
to participate in Google's Season of Docs.

As you've seen with all the progress and momentum on list going into the
recent and forthcoming releases, Mifos, in coordination with its customers
and their committment to contribute their enhancements into the upstream
repositories, has been able to introduce some immensely valuable
scalability and maintainability enhancements across the platform and
community collaboration infrastructure.

Our Season of Docs
<https://developers.google.com/season-of-docs/docs/participants> project
aims to build upon the documentation our developers have been including
with these major changes. The project, which we have received a grant to
hire a technical writer for, Update Platform and Collaboration
Documentation for Launch of Mifos X 3.0, will be a nice complement to last
year's Season of Docs project and the current work Aleks has been leading
to automate ASCII document generation with each release.  The project will
commence in mid-June and needs to be completed by late October.

The need and scope of the project is fully outlined at:
https://mifosforge.jira.com/wiki/spaces/RES/pages/3038248961/Season+of+Docs+-+2022#proposal

We welcome any technical writers in the community to apply and highly
encourage you to forward this opportunity to anyone in your network who
might be a good fit.

Please include your resume/CV and links to your portfolio and/or two
writing samples.

Applications are due by May 1.

Thanks,

*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Ed Cable]

Aleks,

I will check with Manoj and Avik from Fynarfin to see if there are any
changes that are being worked on that might be ready for inclusion into 1.7.

Ed

On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> @Victor Manuel Romero Rodriguez  your
> three tickets are included... FYI
>
> On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> @Victor Manuel Romero Rodriguez  ... no
>> problem, I'll add them right now
>>
>> On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
>> victor.rom...@fintecheando.mx> wrote:
>>
>>> Hello Aleks,
>>>
>>> Is it possible to include these PRs?
>>>
>>> FINERACT-1577 TLS support in fully managed serverless environments
>>> FINERACT-1576 GCP Cloud SQL Support
>>> FINERACT-1575 IPv6 workaround
>>>
>>> Regards
>>>
>>> El mié, 20 abr 2022 a las 16:17, Ed Cable ()
>>> escribió:
>>>
>>>> Thank you Aleks and glad to see all of the automation that you have
>>>> added to the release process.
>>>>
>>>> Ed
>>>>
>>>> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic 
>>>> wrote:
>>>>
>>>>> Hello everyone,
>>>>>
>>>>> Based on our "How to Release Apache Fineract" process documented at
>>>>> https://cwiki.apache.org/confluence/x/DRwIB:
>>>>>
>>>>> I will create a 1.7.0 branch off develop in our git repository at
>>>>> https://github.com/apache/fineract on Monday, April 25, 2022.
>>>>>
>>>>> The release tracking umbrella issue for tracking all activity in JIRA
>>>>> is FINERACT-1590 (https://issues.apache.org/jira/browse/FINERACT-1590)
>>>>> for this Fineract 1.7.0.
>>>>>
>>>>> If you have any work in progress that you would like to see included
>>>>> in this release, please add "blocking" links to the release JIRA issue.
>>>>>
>>>>> I am the release manager for this release.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Aleksandar Vidakovic
>>>>>
>>>>>
>>>>>
>>>>>  Powered by Fineract Release Plugin 
>>>>>
>>>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Ed Cable]

Thank you Aleks and glad to see all of the automation that you have added
to the release process.

Ed

On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic  wrote:

> Hello everyone,
>
> Based on our "How to Release Apache Fineract" process documented at
> https://cwiki.apache.org/confluence/x/DRwIB:
>
> I will create a 1.7.0 branch off develop in our git repository at
> https://github.com/apache/fineract on Monday, April 25, 2022.
>
> The release tracking umbrella issue for tracking all activity in JIRA is
> FINERACT-1590 (https://issues.apache.org/jira/browse/FINERACT-1590) for
> this Fineract 1.7.0.
>
> If you have any work in progress that you would like to see included in
> this release, please add "blocking" links to the release JIRA issue.
>
> I am the release manager for this release.
>
> Cheers,
>
> Aleksandar Vidakovic
>
>
>
>  Powered by Fineract Release Plugin 
>

Re: Call for Presentations now open, ApacheCon North America 2022

[Ed Cable]

I can help with reviewing track proposals if that doesn't preclude me from
also submitting ones too.

Ed

On Thu, Mar 31, 2022 at 7:22 AM Javier Borkenztain  wrote:

> Hello Fineracters!
>
>
> Again this year, we'll have our traditional Fintech track at ApacheCon
> North America. This year the event will be in New Orleans Sheraton from 
> October
> 3rd through 6th, 2022.
>
>
> The Call for Presentations is now open and will close at 00:01 UTC on May
> 23rd, 2022.
>
>
> You may apply here: https://cfp.apachecon.com/
>
>
> And please let me know if you're interested in participating in the
> Fintech track's reviewing process, and we will give you the proper
> credentials to do so.
>
>
> I am looking forward to a great track this year!
>
> Javier
>
>
> [image: Logo] <https://www.fiter.io>
> *Javier Borkenztain* *| CEO*
> *e:* jav...@fiter.io
> *w:* fiter.io <http://www.fiter.io>
> *m:* +598 97980801
> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>
> Sent via Superhuman <https://sprh.mn/?vip=jav...@fiter.io>
>
>
> -- Forwarded message --
> From: Rich Bowen 
> Date: Wednesday, March 30 2022 at 9:15 AM -03
> Subject: Call for Presentations now open, ApacheCon North America 2022
> To: memb...@apache.org
>
> ApacheCon draws participants at all levels to explore “Tomorrow’s
> Technology Today” across 300+ Apache projects and their diverse
> communities. ApacheCon showcases the latest developments in ubiquitous
> Apache projects and emerging innovations through hands-on sessions,
> keynotes, real-world case studies, trainings, hackathons, community events,
> and more.
>
> The Apache Software Foundation will be holding ApacheCon North America
> 2022 at the New Orleans Sheration, October 3rd through 6th, 2022. The
> Call for Presentations is now open, and will close at 00:01 UTC on May
> 23rd, 2022.
>
> We are accepting presentation proposals for any topic that is related to
> the Apache mission of producing free software for the public good. This
> includes, but is not limited to:
>
> Community
> Big Data
> Search
> IoT
> Cloud
> Fintech
> Pulsar
> Tomcat
>
> You can submit your session proposals starting today at
> https://cfp.apachecon.com/
>
> Rich Bowen, on behalf of the ApacheCon Planners
> apachecon.com
> @apachecon
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Next Steps as a Mifos Mentor for the 2022 Google Summer of Code

[Ed Cable]

Hi everyone,

I'm delighted to share the news that Mifos has been selected as a mentoring
org for the tenth time. We're eager to return back after a one-year hiatus
- this direct participation will allow us to onboard and interact with a
larger number of interns and take on projects across all of our codebases
and not just the Apache Fineract ones. Mifos' participation as a mentoring
org will be in addition to whatever interns Fineract can bring on under
Apache Software Foundation.

Thanks to all the mentors who have expressed willingness to be a mentor
thus far. If you haven't already expressed interest and would like to -
please fill out the form that's been shared previously -
https://forms.gle/sFsYKdk4DtnvWmFM9

If you meet our criteria for being a mentor, I'll invite you to register as
a mentor through the GSOC portal. We really need committed and engaged
mentors and will only seek out interns for projects where we have both a
primary and secondary mentor confirmed and committed.

@Sanyam Goel  and @Rahul Goel
 will be helping with Org Admin duties this year so
please collaborate with them on the following topics:

*Changes in 2022*
As a reminder, the program has some major changes this year:

(1) Starting in 2022, the program will be *open to all newcomers of open
source* that are 18 years and older, *no longer focusing solely on
university students**.*
(2) GSoC Contributors will be able to choose from multiple size projects
~175 hour (medium) and 350 hour (large).
(3) Google is building increased flexibility around the timing of projects
- there is an option to extend the standard 12 week coding time frame to a
maximum of 22 weeks

*2022 Project Scope*
Our projects will cut across our entire stack from the Fineract back-end to
our mobile and web apps for staff and customers. We will also be trying to
target some projects around OpenG2P and the Payment Hub EE this year as
well.

*Next Steps*
While the intern application period isn't open for submissions until April
4 to April 19. Up until then is a crucial period when we will hopefully be
inundated with interest from applicants and will need high involvement and
engagement from mentors as applicants interact with the community and share
pull requests which will be the most important part of their applications.

Here's our official student-facing page on the Google Summer of Code site:
https://summerofcode.withgoogle.com/programs/2022/organizations/the-mifos-initiative

I'll share a post to our blog soon too and we'll be hosting a Mifos GSOC
AMA (Ask Me Anything) for all aspiring interns on Friday April 1 at 1300GMT
- you can register here:
https://us02web.zoom.us/webinar/register/2016485166342/WN_ZW6Ij83gRxCueea85bjEwA

We need to finalize our list of projects and mentor assignments prior to
April 4 so I welcome any mentors to assist in this process and if you have
an idea that you haven't listed, do list it now -

We will have a meeting of all mentors this Thursday at 1300GMT via Zoom -
https://us02web.zoom.us/meeting/register/tZYsdu6grTspHtMTDGNWI1Stiz-PnPCfGupv

For now here a few items of homework to participate as a mentor:

1) *Join the meeting this Thursday at 1300GMT (*
https://us02web.zoom.us/meeting/register/tZYsdu6grTspHtMTDGNWI1Stiz-PnPCfGupv
)

2) *Learn what it means to mentor* - Read up on the GSOC mentors manual at
https://google.github.io/gsocguides/mentor/ and what we look for in
students and how we evaluate them in this video:
https://www.youtube.com/watch?v=mtxBX7Sbqv0

3) *Add yourself as a mentor on Google GSOC site*: Accept the invite to
mentor that you will be receiving soon.

4) *Join discussion group and slack channel* -  Most of you are already on
this from previous years. If not, confirm your subscription to our internal
discussion group for mentors - we'll use for sending communications amongst
mentors. You should receive an invite for this group at:
https://groups.google.com/a/mifos.org/forum/#!forum/gsoc-mentors. I will
invite you to #gsoc-mentors slack channel .

5)* Refine project ideas *- this is a critical step to refine the ideas,
remove ones we won't move forward with and definitely assign mentors to
ideas. I will be sending separate emails on this topic.
https://mifosforge.jira.com/wiki/spaces/RES/pages/3004891137/Google+Summer+of+Code+2022+Ideas

6)* Be active* - join our Gitter chatroom and Slack, respond to mailing
list inquiries, participate in community meetings!

*Cheers,*

*Ed*

Re: ApacheCon 2022

[Ed Cable]

I would try to attend in person as well and glad to hear of the broader
inclusive fintech track that will still allow Fineract to be showcase
itself and hopefully begin collaboration with other fintech-related
projects.

I look forward to helping plan the track and sessions - hopefully enabling
participation from our community and implementations in the Americas.

Ed

On Mon, Mar 28, 2022 at 6:16 AM Javier Borkenztain  wrote:

> Awesome James! I will see you there :)
>
> This year, I want to share that the track will be "Fintech powered by
> Apache."
>
> For this year's track, we will invite all the different Apache projects,
> including Fineract, that the financial industry uses the projects.
>
> It will be an opportunity to share with other Apache projects and
> communities how we can collaborate.
>
> Javier
>
> [image: Logo] <https://www.fiter.io>
> *Javier Borkenztain* *| CEO*
> *e:* jav...@fiter.io
> *w:* fiter.io <http://www.fiter.io>
> *m:* +598 97980801
> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>
> Sent via Superhuman <https://sprh.mn/?vip=jav...@fiter.io>
>
>
> On Sun, Mar 27, 2022 at 10:56 PM, James Dailey 
> wrote:
>
>> Resurfacing this.  I would be interested in travel to New Orleans.
>>
>>
>>
>>
>>
>> On Fri, Mar 11, 2022 at 3:58 AM Javier Borkenztain 
>> wrote:
>>
>>> Hello Fineracters!
>>>
>>> The Planners for ApacheCon are excited to be working on the next edition
>>> of ApacheCon, which will be held at the *Sheraton New Orleans in New
>>> Orleans, Louisiana, from **October 3**-7, 2022*! This will be our first
>>> live event since 2019, and the team is putting together a great event for
>>> attendees.
>>>
>>> We need to decide if we will hold a Fineract track or not,
>>> provided this year is a live event.
>>>
>>> If we can have a reasonable number of attendees from our community, it
>>> will make sense to hold the track.
>>>
>>> The event team is planning a potential live event after the live one,
>>> but it's unclear if it will happen.
>>>
>>> Without this being a commitment, just an initial poll, please help us
>>> define if we will have this track, by answering if you are interested in
>>> traveling to New Orleans in October to participate in the ApacheCon.
>>>
>>> Thank you,
>>> Javier
>>>
>>> [image: Logo] <https://www.fiter.io>
>>> *Javier Borkenztain* *| CEO*
>>> *e:* jav...@fiter.io
>>> *w:* fiter.io <http://www.fiter.io>
>>> *m:* +598 97980801
>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>
>>> Sent via Superhuman <https://sprh.mn/?vip=jav...@fiter.io>
>>>
>>> --
>> Sent from Gmail Mobile
>>
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [ANNOUNCE] Welcome Arnold Galovics as a new Apache Fineract committer

[Ed Cable]

Hats of to Arnold on becoming a committer and so happy he's been able to be
such a high-performing contributor in such a short period of time.

Ed

On Wed, Mar 23, 2022 at 4:22 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi all,
>
> I'm happy to inform you that the Apache Fineract PMC has voted to add
> Arnold Galovics as a Fineract committer and we are happy that he has
> accepted our invitation.
>
> Arnold started contributing to Fineract this year and in a very
> short period of time he managed to make some significant contributions like
> replacing Flyway database migrations with Liquibase, cleaning up all MySQL
> specific references in our code so that we can support PostgreSQL and
> finally he replaced our outdated JPA implementation (OpenJPA) with the well
> maintained EclipseLink library.
>
> Let's congratulate Arnold on becoming a Fineract committer.
>
> Cheers,
>
> Aleks
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Conventional Commits...

[Ed Cable]

+1 from my side. Thanks for driving on this aleks. it would be great to get
this standardization and automation in place.

Ed

On Fri, Mar 11, 2022 at 10:53 AM Aleksandar Vidakovic 
wrote:

> Hi everyone,
>
> ... as you know we already have some rules in place to ensure that we have
> a somewhat uniform process concerning pull requests etc. (e. g. PR title
> starts with Jira issue number, squashing before merging is imperative etc.).
>
> I would really like to go a step beyond that and try to "standardize" our
> commit messages even more. What I mean with that can be seen here:
> https://www.conventionalcommits.org/
>
> The goal would be to create git messages that we can actually include in a
> changelog (for release announcements, changelog file in git repo etc.)
> without manually intervention (or at least not much). Those messages -
> ideally - would also contain more context than just simple copy and pasting
> the Github commit template, e. g. we could inform about backwards
> incompatibilities, references to other PRs etc. etc. I think this would
> require only minimal additional effort of each PR author.
>
> Example: https://github.com/angular/angular/blob/master/CHANGELOG.md
>
> Also opened a Jira ticket in case you want to comment there:
> https://issues.apache.org/jira/browse/FINERACT-1527
>
> Cheers,
>
> Aleks
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [VOTE]: Arnold Galovics as an Apache Fineract Committer

[Ed Cable]

+1 from my side. Arnold has really demonstrated all the merits of an
effective upstream contributor and I think can have an even more outsized
impact once he's a committer and can help in guiding other upstream
contributions and being more hands-on with the release process as well.

Ed

On Tue, Feb 22, 2022 at 4:33 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi everyone,
>
> ... I guess one or the other among you saw Arnold Galovics' work around
> Fineract's Git repo, his pull requests and his messages here in the mailing
> list. Arnold added in a very short time not only a significant amount of
> pull requests (10), but he tackled some long overdue issues that all of us
> have already struggled:
>
>- transaction safety
>- database locks
>- ... and most prominently database independence (well, at least
>PostgreSQL support in addition to MySQL) by replacing Flyway with Liquibase
>and replacing all database (MySQL) dependent expressions with SQL standards
>
> He has already more improvements lined up; he'll certainly let us all know
> here on the mailing list about the details when he gets to it. I'm already
> looking to see these contributions.
>
> You'll see that one or the other pull request seems a bit larger than
> usual, but Arnold's still paid attention that his changes can be reviewed
> and that they are backward compatible (in itself already a major
> challenge).
>
> And finally, in this relatively small timeframe he somehow managed to be
> responsible for 19% of 2022's contributions.
>
> This is why I am proposing to add Arnold as a Fineract committer.
>
> Please reply with your vote to this message.
>
> Cheers,
>
> Aleks
>
> P.S.: +1
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: PostgreSQL support

[Ed Cable]

Thanks Arnold for driving these contributions and being so transparent and
deliberate in keeping the community informed.

It's a great model and example for all of us in the community on
contributing large changes upstream.

Ed

On Tue, Feb 22, 2022, 14:35 Petri Tuomola  wrote:

> Great work! Very excited to see these changes - it will be an excellent
> addition and should bring a lot of benefits wrt performance.
>
> Also with Postgres we do not need to worry about bundling the JDBC drivers
> as they are all BSD licensed.
>
> Thanks again for your contributions!
>
> Regards
> Petri
>
> On 21 Feb 2022, at 16:24, Aleksandar Vidakovic 
> wrote:
>
> ... looking forward to seeing these changes Arnold. Thanks again for all
> the work!
>
> On Mon, Feb 21, 2022 at 8:59 AM Arnold Galovics 
> wrote:
>
>> Dear Community,
>>
>> As I mentioned a couple of mails back, it would be awesome if Fineract
>> could support PostgreSQL because of the performance gain it could bring.
>>
>> The first milestone in this process was to make the database migrations
>> MySQL independent and switch from Flyway to Liquibase. That's done, thanks
>> for reviewing and merging the changes.
>>
>> Now, I'm planning to continue on this path slowly but surely. In the
>> upcoming days/weeks I'm going to be filing new PRs to make Fineract as
>> independent as possible from MySQL and rely on standard SQL tools. Just as
>> an example, MySQL supports the IFNULL function but PostgreSQL doesn't.
>> However, IFNULL can be easily replaced by the ANSI SQL COALESCE function
>> which is supported both by MySQL and PostgreSQL.
>>
>> The JIRA I'm using for creating the commits is FINERACT-984
>> .
>> Also, the first PR has landed already in develop: PR link
>> 
>>
>> Best,
>> Arnold
>>
>
>

Re: [VOTE] [APACHE FINERACT] 1.6.0 for release

[Ed Cable]

+1 [binding]

Kudos to Aleks for all his effort on this.

Ed

On Mon, Feb 21, 2022 at 11:21 AM ondur kiyelo  wrote:

> +1
>
> On Mon, Feb 21, 2022 at 10:07 PM Petri Tuomola 
> wrote:
>
>> +1
>>
>>
>> On Tue, Feb 22, 2022, 00:58 VICTOR MANUEL ROMERO RODRIGUEZ <
>> victor.rom...@fintecheando.mx> wrote:
>>
>>> +1
>>>
>>> El lun, 21 feb 2022 a las 6:10, Bharath Gowda ()
>>> escribió:
>>>
>>>> +1
>>>>
>>>> Regards,
>>>> Bharath
>>>> Lead Implementation Analyst | Mifos Initiative
>>>> Skype: live:cbharath4| Mobile: +91.7019635592
>>>> http://mifos.org  <http://facebook.com/mifos>
>>>> <http://www.twitter.com/mifos>
>>>>
>>>>
>>>> On Mon, Feb 21, 2022 at 1:24 PM James Dailey 
>>>> wrote:
>>>>
>>>>> +1 [binding]
>>>>>
>>>>> On Sun, Feb 20, 2022 at 11:51 PM Arnold Galovics <
>>>>> galovicsarn...@gmail.com> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> On Mon, Feb 21, 2022 at 6:37 AM Bruce  wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Mon, Feb 21, 2022, 5:56 AM Aleksandar Vidakovic <
>>>>>>> chee...@monkeysintown.com> wrote:
>>>>>>>
>>>>>>>> Hi everyone,
>>>>>>>>
>>>>>>>> We have created an Apache Fineract 1.6.0 release, with the
>>>>>>>> artifacts below up for a vote.
>>>>>>>>
>>>>>>>> It fixes the following issues:
>>>>>>>> https://cwiki.apache.org/confluence/display/FINERACT/1.6.0+-+Apache+Fineract
>>>>>>>>
>>>>>>>> Source & Binary files :
>>>>>>>> https://dist.apache.org/repos/dist/dev/fineract/1.6.0/
>>>>>>>>
>>>>>>>> Tag to be voted on (rc#):
>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.6.0
>>>>>>>>
>>>>>>>> Fineract's KEYS containing the PGP key we used to sign the release:
>>>>>>>> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>>>>>>>>
>>>>>>>> Note that this release contains source and binary artifacts.
>>>>>>>>
>>>>>>>> This vote will be open for 72 hours:
>>>>>>>>
>>>>>>>> [ ] +1 approve
>>>>>>>> [ ] +0 no opinion
>>>>>>>> [ ] -1 disapprove (and reason why)
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Aleks
>>>>>>>>
>>>>>>>> P.S.: I found a last minute minor cosmetic issue in the source
>>>>>>>> distribution; looks like we didn't include all Gradle wrapper files 
>>>>>>>> (JAR is
>>>>>>>> missing); I have a PR open at
>>>>>>>> https://github.com/apache/fineract/pull/2041; contains no
>>>>>>>> functional changes, just this rather small fix; I think we can still 
>>>>>>>> vote
>>>>>>>> on this release, wouldn't want to delay the release vote just for a
>>>>>>>> non-critical minor fix.
>>>>>>>>
>>>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Call for Mentors: 2022 Google Summer of Code for the Mifos Initiative

[Ed Cable]

The ideas list hasn't been updated but we are certainly going to have an
idea related to the machine learning credit scorecards, the chatbot,
potentially vision PPI, and our other mentor exploring potential other
projects.

Ed

On Sun, Feb 20, 2022 at 11:13 AM David Asem  wrote:

> Hi Ed,
>
> I went through the Idealist for GSoC 2022 and found only one AI-related
> project which is the Fineract Chatbot.
>
> Would more AI projects be added? Because I'm interested in working on one
> of those for GSoC 2022.
>
> Happy to learn more.
>
> Regards,
> David Asem
>
> On Sun, Feb 20, 2022 at 6:24 PM Ed Cable  wrote:
>
>> For those mentors that are inputting their ideas, the mentor guide has
>> some really good tips around framing a project appropriately:
>> https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list
>>
>>
>> I will categorize some of our projects like suggested below. We will also
>> categorize between easy, medium, hard.
>>
>> Low-hanging fruit: These projects require minimal familiarity with the
>> codebase and basic technical knowledge. They are relatively short, with
>> clear goals.
>>
>> Risky/Exploratory: These projects push the scope boundaries of your
>> development effort. They might require expertise in an area not covered by
>> your current development team. They might take advantage of a new
>> technology. There is a reasonable chance that the project might be less
>> successful, but the potential rewards make it worth the attempt.
>>
>> Fun/Peripheral: These projects might not be related to the current core
>> development focus, but create new innovations and new perspective for your
>> project.
>>
>> Core development: These projects derive from the ongoing work from the
>> core of your development team. The list of features and bugs is
>> never-ending, and help is always welcome.
>>
>> Infrastructure/Automation: These projects are the code that your
>> organization uses to get its development work done; for example, projects
>> that improve the automation of releases, regression tests and automated
>> builds. This is a category in which a GSoC contributor can be really
>> helpful, doing work that the development team has been putting off while
>> they focus on core development.
>>
>> The projects you propose will define the tone and scope of your
>> organization’s participation in GSoC. It is a key part of your
>> organization’s application. Further, it may be the first impression made on
>> a potential applicant.
>>
>> On Sun, Feb 20, 2022 at 9:51 AM Ed Cable  wrote:
>>
>>> Hi all,
>>>
>>> I have spoken to many of you directly already and we are finalizing our
>>> ideas list as our GSOC application is due tomorrow. I want to do one last
>>> reminder for any potential mentors to share their interest in mentoring
>>> by filling out this form at https://forms.gle/sFsYKdk4DtnvWmFM9
>>>
>>> Ed
>>> -- Forwarded message -
>>> From: Ed Cable 
>>> Date: Thu, Jan 6, 2022 at 5:22 PM
>>> Subject: Call for Mentors: 2022 Google Summer of Code for the Mifos
>>> Initiative
>>> To: Dev , Mifos software development <
>>> mifos-develo...@lists.sourceforge.net>, 
>>>
>>>
>>> Hello all,
>>>
>>> It's that time of year again and the Mifos Initiative is looking to
>>> participate in Google Summer of Code once more. While unfortunately last
>>> year Mifos Initiative was not selected due to the need to let in new orgs
>>> to the program, I'm optimistic we can get selected this year. Last year, we
>>> still were able to play a role in helping guide the five interns that were
>>> selected under the Apache Software Foundation but when we participate
>>> directly through Mifos it allows us to target a larger class across a wider
>>> variety of projects.
>>>
>>> This year we'd be having interns work on our Mifos X web and mobile
>>> apps, Fineract 1.x and Fineract CN, as well as more projects around our AI
>>> for All strategy, our Payment Hub EE and payments integration, our Open
>>> Banking layer, and for the first time projects related to OpenG2P.
>>>
>>> Google Summer of Code applications are due February 21. I will refine
>>> our application but need to ensure we have a committed group of mentors and
>>> a solid ideas list. I have already been discussing ideas with our past GSOC
>>> mentors and recent GSOC alum who will become mentors for the first time.
>>&

Re: Call for Mentors: 2022 Google Summer of Code for the Mifos Initiative

[Ed Cable]

For those mentors that are inputting their ideas, the mentor guide has some
really good tips around framing a project appropriately:
https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list


I will categorize some of our projects like suggested below. We will also
categorize between easy, medium, hard.

Low-hanging fruit: These projects require minimal familiarity with the
codebase and basic technical knowledge. They are relatively short, with
clear goals.

Risky/Exploratory: These projects push the scope boundaries of your
development effort. They might require expertise in an area not covered by
your current development team. They might take advantage of a new
technology. There is a reasonable chance that the project might be less
successful, but the potential rewards make it worth the attempt.

Fun/Peripheral: These projects might not be related to the current core
development focus, but create new innovations and new perspective for your
project.

Core development: These projects derive from the ongoing work from the core
of your development team. The list of features and bugs is never-ending,
and help is always welcome.

Infrastructure/Automation: These projects are the code that your
organization uses to get its development work done; for example, projects
that improve the automation of releases, regression tests and automated
builds. This is a category in which a GSoC contributor can be really
helpful, doing work that the development team has been putting off while
they focus on core development.

The projects you propose will define the tone and scope of your
organization’s participation in GSoC. It is a key part of your
organization’s application. Further, it may be the first impression made on
a potential applicant.

On Sun, Feb 20, 2022 at 9:51 AM Ed Cable  wrote:

> Hi all,
>
> I have spoken to many of you directly already and we are finalizing our
> ideas list as our GSOC application is due tomorrow. I want to do one last
> reminder for any potential mentors to share their interest in mentoring
> by filling out this form at https://forms.gle/sFsYKdk4DtnvWmFM9
>
> Ed
> -- Forwarded message -
> From: Ed Cable 
> Date: Thu, Jan 6, 2022 at 5:22 PM
> Subject: Call for Mentors: 2022 Google Summer of Code for the Mifos
> Initiative
> To: Dev , Mifos software development <
> mifos-develo...@lists.sourceforge.net>, 
>
>
> Hello all,
>
> It's that time of year again and the Mifos Initiative is looking to
> participate in Google Summer of Code once more. While unfortunately last
> year Mifos Initiative was not selected due to the need to let in new orgs
> to the program, I'm optimistic we can get selected this year. Last year, we
> still were able to play a role in helping guide the five interns that were
> selected under the Apache Software Foundation but when we participate
> directly through Mifos it allows us to target a larger class across a wider
> variety of projects.
>
> This year we'd be having interns work on our Mifos X web and mobile apps,
> Fineract 1.x and Fineract CN, as well as more projects around our AI for
> All strategy, our Payment Hub EE and payments integration, our Open Banking
> layer, and for the first time projects related to OpenG2P.
>
> Google Summer of Code applications are due February 21. I will refine our
> application but need to ensure we have a committed group of mentors and a
> solid ideas list. I have already been discussing ideas with our past GSOC
> mentors and recent GSOC alum who will become mentors for the first time.
>
> We'll be adding our mentors and refining our ideas list at:
> https://mifosforge.jira.com/wiki/spaces/RES/pages/3004891137/Google+Summer+of+Code+2022+Ideas
>
> I will schedule a community-wide Zoom meeting to have a discussion on
> potential ideas and answer questions of prospective mentors
>
> Once again as in 2021, there are some major exciting changes to the 2022
> GSOC program - the three major changes are listed below (with full details
> at the bottom of the email):
>
> (1) Starting in 2022, the program will be *open to all newcomers of open
> source* that are 18 years and older, *no longer focusing solely on
> university students**.*
> (2) GSoC Contributors will be able to choose from multiple size projects
> ~175 hour (medium) and 350 hour (large).
> (3) Google is building increased flexibility around the timing of
> projects - there is an option to extend the standard 12 week coding time
> frame to a maximum of 22 weeks
>
>
> The coding program officially begins June 13 and for the standard duration
> projects ends September 12 and for the extended duration projects November
> 13.
>
> 2020 was our biggest year of participation in GSOC to date with 17
> interns mentored by the Mifos Initiative. That high num

Re: Call for Mentors: 2022 Google Summer of Code for the Mifos Initiative

[Ed Cable]

Hi all,

I have spoken to many of you directly already and we are finalizing our
ideas list as our GSOC application is due tomorrow. I want to do one last
reminder for any potential mentors to share their interest in mentoring
by filling out this form at https://forms.gle/sFsYKdk4DtnvWmFM9

Ed
-- Forwarded message -
From: Ed Cable 
Date: Thu, Jan 6, 2022 at 5:22 PM
Subject: Call for Mentors: 2022 Google Summer of Code for the Mifos
Initiative
To: Dev , Mifos software development <
mifos-develo...@lists.sourceforge.net>, 


Hello all,

It's that time of year again and the Mifos Initiative is looking to
participate in Google Summer of Code once more. While unfortunately last
year Mifos Initiative was not selected due to the need to let in new orgs
to the program, I'm optimistic we can get selected this year. Last year, we
still were able to play a role in helping guide the five interns that were
selected under the Apache Software Foundation but when we participate
directly through Mifos it allows us to target a larger class across a wider
variety of projects.

This year we'd be having interns work on our Mifos X web and mobile apps,
Fineract 1.x and Fineract CN, as well as more projects around our AI for
All strategy, our Payment Hub EE and payments integration, our Open Banking
layer, and for the first time projects related to OpenG2P.

Google Summer of Code applications are due February 21. I will refine our
application but need to ensure we have a committed group of mentors and a
solid ideas list. I have already been discussing ideas with our past GSOC
mentors and recent GSOC alum who will become mentors for the first time.

We'll be adding our mentors and refining our ideas list at:
https://mifosforge.jira.com/wiki/spaces/RES/pages/3004891137/Google+Summer+of+Code+2022+Ideas

I will schedule a community-wide Zoom meeting to have a discussion on
potential ideas and answer questions of prospective mentors

Once again as in 2021, there are some major exciting changes to the 2022
GSOC program - the three major changes are listed below (with full details
at the bottom of the email):

(1) Starting in 2022, the program will be *open to all newcomers of open
source* that are 18 years and older, *no longer focusing solely on
university students**.*
(2) GSoC Contributors will be able to choose from multiple size projects
~175 hour (medium) and 350 hour (large).
(3) Google is building increased flexibility around the timing of projects
- there is an option to extend the standard 12 week coding time frame to a
maximum of 22 weeks


The coding program officially begins June 13 and for the standard duration
projects ends September 12 and for the extended duration projects November
13.

2020 was our biggest year of participation in GSOC to date with 17 interns
mentored by the Mifos Initiative. That high number of interns tested the
limits of our mentors so I want to emphasize this year that if you express
interest in being a mentor, know the commitment it takes. We will be very
deliberate in our selection of projects this year to ensure we have proper
mentor capacity given with last year's smaller class it was more manageable
and in the end a better overall experience with more attention for each
intern.

Mifos participation is in addition to whatever participation Apache
Fineract might do as part of the umbrella organization, Apache Software
Foundation.

*Developers!*
This program is one of our most impactful ways to extend our software but
most importantly grow our community over the long run. Our most active
volunteers, committers, and maintainers in the community have all been
former GSOC students so if you're a senior community member looking for a
great way to give back, this is it!

I gave a talk a couple years back  that explains how GSOC is truly the
lifeblood and organic growth engine for our community -
https://www.youtube.com/watch?v=mtxBX7Sbqv0

In case you forgot, here's a link to blogs about past GSOC programs at:
https://mifos.org/blog/tag/gsoc/

If interested please *fill out this form*
<https://forms.gle/sFsYKdk4DtnvWmFM9> and/or reply to this email thread. If
you know someone who would be a good mentor, don't hesitate to invite them.

*Partners & Users!*

Regarding our list of Ideas, this year we'll both revisit some of the ideas
that weren't picked up last year, continue evolving the apps that students
have worked on in the past and try to do more projects on Fineract 1.x and
its ongoing modularization, the Payment Hub and payment orchestration,
streamlining design and development of our mobile apps, our Open Banking
APIs, and OpenG2P.

As we did last year, the majority of ideas we'll submit for
our application will be related to Mifos X distribution powered by Apache
Fineract 1.0 including web app (Community App), mobile apps (field officer,
mobile banking, mobile wallet ), and other modules (data import tool, etc.)
powered by Apache Fineract as well as our pay

Re: Liquibase has landed...

[Ed Cable]

Thanks Arnold for getting this valuable enhancement into the upstream
codebase. Thank you Aleks for coordinating the release and ensuring the
team could make a smooth upstream contribution.

Community, stay tuned for valuable enhancements that are forthcoming which
will help Fineract support new volumes of scale and throughput that will
power much of the API-driven, digital first financial services innovation
that so many in the community are working on.

On Sun, Feb 20, 2022 at 1:59 AM Arnold Galovics 
wrote:

> Hi Aleks, the Community,
>
> Thanks. If you encounter any issues with Liquibase, let me know. I'm happy
> to help.
>
> Best,
> Arnold
>
> On Sat, Feb 19, 2022 at 11:06 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi everyone,
>>
>> ... just wanted to let everyone know that we have new database migration
>> mechanics in place... thanks to Arnold Galovics who took on the task and
>> got us one step closer to database independence (at least MySQL and
>> PostgreSQL).
>>
>> Liquibase migrations will work seamlessly for all upgrades starting
>> future release 1.7.0 and higher. Everyone who's using older Fineract
>> versions is advised to first upgrade to - upcoming - version 1.6.0 (which
>> is still based on Flyway) and later upgrade to release 1.7.x (with
>> Liquibase).
>>
>> Thanks again Arnold for this contribution.
>>
>> Cheers,
>>
>> Aleks
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Loan entity performance improvements

[Ed Cable]

Thanks James as I had mixed up the desired condition we want to enforce.
Lazy loading by default as opposed to eager loading.

Ed

On Fri, Feb 4, 2022, 12:55 James Dailey  wrote:

> Just to clarify, we want to only use Eager loading when absolutely
> required , otherwise lazy loading (and avoid database locks) so we want a
> way to test for this rule on all PRs
>
>
>
> On Fri, Feb 4, 2022 at 8:52 AM Ed Cable  wrote:
>
>> Aleks - were you still exploring introduction of Archunit
>> https://www.archunit.org/ as you had discussed as a means of providing a
>> way to check and enforce eager loading conditions, etc?
>>
>> Ed
>>
>> On Fri, Feb 4, 2022 at 8:33 AM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> ... I am currently working on 3 (integration-)test related PRs:
>>>
>>>- add Cucumber support to have better interaction between people
>>>that are less involved with the implementation side, but have great 
>>> domain
>>>specific knowledge (I'll explain a bit more when it's ready)
>>>- add JMH Microbenchmarking support; this is something that could
>>>actually help here (collateral management) to figure out any performance
>>>related regressions
>>>- add Gatling support; this one would improve visibility into our
>>>integration tests; at the moment they are only used to verify if the
>>>business logic is still working; with Gatling we could additionally get
>>>some hints about performance; it's not "real world" (everything runs on
>>>localhost), but big outliers should be visible and help avoid regressions
>>>
>>> ... JMH Microbenchmarking in the context of the collateral management
>>> module could really help finding any bottlenecks... and it's easy to write
>>> and run these tests.
>>>
>>> I can move this up my priority list if needed... just let me know.
>>>
>>> Cheers,
>>>
>>> Aleks
>>>
>>> On Fri, Feb 4, 2022 at 5:02 PM Ed Cable  wrote:
>>>
>>>> Welcome to the community Arnold and thanks for documenting clearly in
>>>> the JIRA ticket the extent of changes you would propose to ensure optimal
>>>> performance with the loan entity.
>>>>
>>>> Going forward, we want to ensure necessary automated checks are in
>>>> place for future pull requests to enforce eager versus lazy loading so we
>>>> can catch this before a contribution is merged and have a developer address
>>>> it accordingly. I believe Aleks is working on incorporating that into our
>>>> review process and the CI/CD and corresponding documentation will be
>>>> updated as those changes are made.
>>>>
>>>> I am tagging @Benura Abeywardena  as he was the
>>>> developer working on the collateral management module and hope that he has
>>>> some time to help complete the fixes you are suggesting and proposing.
>>>>
>>>> Ed
>>>>
>>>> On Fri, Feb 4, 2022 at 5:23 AM Bharath Gowda  wrote:
>>>>
>>>>> Hi Arnold,
>>>>>
>>>>> Thank you for surfacing this issue.
>>>>> Performance of the application is always an important aspect and any
>>>>> fix related to that is always welcome and good for the application's 
>>>>> growth
>>>>>
>>>>> Attaching the full Functional Documents and Video links of the
>>>>> Collateral Module to help understand the feature while fixing the
>>>>> Performance issue
>>>>>
>>>>> In Summary, Collateral Module is Divided into 3 Levels
>>>>>
>>>>> • Product Level
>>>>> • Client Level
>>>>> • Loan Level
>>>>>
>>>>> At the product level, the user defines the Collateral required for the
>>>>> organization
>>>>>
>>>>> At the client level, the user adds the collateral which the client
>>>>> agrees to pledge
>>>>>
>>>>> At the Loan level, the user attaches the collateral to the loan which
>>>>> the client has pledged to get a loan.
>>>>>
>>>>> When the loan is repaid the collateral would be released from that
>>>>> loan account and would be again available to pledge for another loan for
>>>>> that client
>>>>>
>>>>>
>>>>>

Re: Loan entity performance improvements

[Ed Cable]

Aleks - were you still exploring introduction of Archunit
https://www.archunit.org/ as you had discussed as a means of providing a
way to check and enforce eager loading conditions, etc?

Ed

On Fri, Feb 4, 2022 at 8:33 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> ... I am currently working on 3 (integration-)test related PRs:
>
>- add Cucumber support to have better interaction between people that
>are less involved with the implementation side, but have great domain
>specific knowledge (I'll explain a bit more when it's ready)
>- add JMH Microbenchmarking support; this is something that could
>actually help here (collateral management) to figure out any performance
>related regressions
>- add Gatling support; this one would improve visibility into our
>integration tests; at the moment they are only used to verify if the
>business logic is still working; with Gatling we could additionally get
>some hints about performance; it's not "real world" (everything runs on
>localhost), but big outliers should be visible and help avoid regressions
>
> ... JMH Microbenchmarking in the context of the collateral management
> module could really help finding any bottlenecks... and it's easy to write
> and run these tests.
>
> I can move this up my priority list if needed... just let me know.
>
> Cheers,
>
> Aleks
>
> On Fri, Feb 4, 2022 at 5:02 PM Ed Cable  wrote:
>
>> Welcome to the community Arnold and thanks for documenting clearly in the
>> JIRA ticket the extent of changes you would propose to ensure optimal
>> performance with the loan entity.
>>
>> Going forward, we want to ensure necessary automated checks are in place
>> for future pull requests to enforce eager versus lazy loading so we can
>> catch this before a contribution is merged and have a developer address it
>> accordingly. I believe Aleks is working on incorporating that into our
>> review process and the CI/CD and corresponding documentation will be
>> updated as those changes are made.
>>
>> I am tagging @Benura Abeywardena  as he was the
>> developer working on the collateral management module and hope that he has
>> some time to help complete the fixes you are suggesting and proposing.
>>
>> Ed
>>
>> On Fri, Feb 4, 2022 at 5:23 AM Bharath Gowda  wrote:
>>
>>> Hi Arnold,
>>>
>>> Thank you for surfacing this issue.
>>> Performance of the application is always an important aspect and any fix
>>> related to that is always welcome and good for the application's growth
>>>
>>> Attaching the full Functional Documents and Video links of the
>>> Collateral Module to help understand the feature while fixing the
>>> Performance issue
>>>
>>> In Summary, Collateral Module is Divided into 3 Levels
>>>
>>> • Product Level
>>> • Client Level
>>> • Loan Level
>>>
>>> At the product level, the user defines the Collateral required for the
>>> organization
>>>
>>> At the client level, the user adds the collateral which the client
>>> agrees to pledge
>>>
>>> At the Loan level, the user attaches the collateral to the loan which
>>> the client has pledged to get a loan.
>>>
>>> When the loan is repaid the collateral would be released from that loan
>>> account and would be again available to pledge for another loan for that
>>> client
>>>
>>>
>>> Full Functional Video of the feature is available here
>>> <https://drive.google.com/file/d/1r8Dxbf7ebzk4k1NR4a-rObz6LLAY3qqZ/view?usp=sharing>to
>>> view
>>>
>>>
>>>
>>> Regards,
>>> Bharath
>>> Lead Implementation Analyst | Mifos Initiative
>>> Skype: live:cbharath4| Mobile: +91.7019635592
>>> http://mifos.org  <http://facebook.com/mifos>
>>> <http://www.twitter.com/mifos>
>>>
>>>
>>> On Fri, Feb 4, 2022 at 4:03 PM Arnold Gálovics 
>>> wrote:
>>>
>>>> Hi everybody,
>>>>
>>>> Wanted to bring attention to the ticket I've just created on potential
>>>> performance improvements when it comes to Loans.
>>>> https://issues.apache.org/jira/browse/FINERACT-1496
>>>>
>>>> I've tried to write everything down into the ticket but let me try to
>>>> sum it up here.
>>>> Turns out the Loan entity has an EAGER relationship to the
>>>> LoanCollateralManagement entity which goes on and on and on. The full
>>>>

Re: Loan entity performance improvements

[Ed Cable]

Welcome to the community Arnold and thanks for documenting clearly in the
JIRA ticket the extent of changes you would propose to ensure optimal
performance with the loan entity.

Going forward, we want to ensure necessary automated checks are in place
for future pull requests to enforce eager versus lazy loading so we can
catch this before a contribution is merged and have a developer address it
accordingly. I believe Aleks is working on incorporating that into our
review process and the CI/CD and corresponding documentation will be
updated as those changes are made.

I am tagging @Benura Abeywardena  as he was the
developer working on the collateral management module and hope that he has
some time to help complete the fixes you are suggesting and proposing.

Ed

On Fri, Feb 4, 2022 at 5:23 AM Bharath Gowda  wrote:

> Hi Arnold,
>
> Thank you for surfacing this issue.
> Performance of the application is always an important aspect and any fix
> related to that is always welcome and good for the application's growth
>
> Attaching the full Functional Documents and Video links of the Collateral
> Module to help understand the feature while fixing the Performance issue
>
> In Summary, Collateral Module is Divided into 3 Levels
>
> • Product Level
> • Client Level
> • Loan Level
>
> At the product level, the user defines the Collateral required for the
> organization
>
> At the client level, the user adds the collateral which the client agrees
> to pledge
>
> At the Loan level, the user attaches the collateral to the loan which the
> client has pledged to get a loan.
>
> When the loan is repaid the collateral would be released from that loan
> account and would be again available to pledge for another loan for that
> client
>
>
> Full Functional Video of the feature is available here
> <https://drive.google.com/file/d/1r8Dxbf7ebzk4k1NR4a-rObz6LLAY3qqZ/view?usp=sharing>to
> view
>
>
>
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> Skype: live:cbharath4| Mobile: +91.7019635592
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
>
>
> On Fri, Feb 4, 2022 at 4:03 PM Arnold Gálovics 
> wrote:
>
>> Hi everybody,
>>
>> Wanted to bring attention to the ticket I've just created on potential
>> performance improvements when it comes to Loans.
>> https://issues.apache.org/jira/browse/FINERACT-1496
>>
>> I've tried to write everything down into the ticket but let me try to sum
>> it up here.
>> Turns out the Loan entity has an EAGER relationship to the
>> LoanCollateralManagement entity which goes on and on and on. The full
>> relationship chain is Loan -> LoanCollateralManagement ->
>> ClientCollateralManagement -> CollateralManagementDomain ->
>> ApplicationCurrency
>>
>> These are all eagerly loaded relationships which definitely hurts the
>> performance to some degree.
>> I'm proposing that we shall take a look at it and potentially switch from
>> EAGER fetching to LAZY fetching hence making sure that the data gets loaded
>> only when it's required.
>>
>> Let me know your thoughts.
>>
>> Best,
>> Arnold
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Questions regarding Production-Readiness of Fineract Client

[Ed Cable]

Chinmay and Danish,

There is some interest and inquiry coming from users in the
community regarding the Fineract Client.

I was hoping you all along with some of the past contributors to this
project like @Aleksandar Vidakovic  and @Michael
Vorburger  could help me with some of the
below questions:

3. What is the difference between these 2 clients:
https://github.com/openMF/fineract/tree/develop/fineract-client
https://github.com/openMF/fineract-client

Are either of these client’s considered production ready?

4. Is
https://github.com/openMF/fineract-client/blob/master/swagger-api-spec-file.json
hand
coded or generated?

5. We have noticed that both fineract-clients only have fullname field
supported when creating a Fineract Client (the database entity). This has
led to the conclusion that neither are based off the Fineract-provider
JAX-RS but are probably hand coded. We are wondering which one is best
supported now and into the future, or if we should hand code our own client.

6. Have either client been used in high volume use cases?

Improving Fineract Unit Testing Coverage

[Ed Cable]

Back in December we had a good community-wide meeting discussing improving
unit testing coverage across Fineract. We had a productive discussion on
the approach to take and identified next steps that Aleks has begun to
execute on as evident from the other emails he's been sending to the list.

Raw notes can be found on the wiki at:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=195730039

I wanted to outline key decisions and next steps around implementing
cucumber as test framework and leveraging community efforts to identify
test cases to be created and begin implementing those test cases.

We should also align this with previous discussion on creation of postman
collections for test cases Michael and others have led at
https://markmail.org/thread/unn6rnwypqu5fgpi and improving integration
tests at https://issues.apache.org/jira/browse/FINERACT-713,
https://issues.apache.org/jira/browse/FINERACT-985,
https://issues.apache.org/jira/browse/FINERACT-949


Key decisions that were made:

*Selection of Test Framework*

   - Cucumber was chosen as it enables business-driven test design and
   behavior-driven development where semi and non-technical individuals with
   more domain knowledge can easily write test cases.
  - Cucumber is good because you can use keywords and prose for test
  case definition and someone else can simply go in and fill in gaps with
  conditions to run test cases
  - Good deal of familiarity with it across members of the community.
  - Synchronizes well with JIRA through plug-in like
  
https://marketplace.atlassian.com/apps/1221264/cucumber-for-jira-bdd-natively-in-jira?tab=overview=cloud

*Implementation of Cucumber Framework*

   - Aleks to implement changes he made to build scripts to improve
   developer experience into upstream
   - Cucumber framework to then be implemented (Aleks)
   - In future can implement test containers for integration tests.
   - Ongoing changes that Petri and Aleks are working on with the REST API
   layer can happen in parallel


*Creation of Test Cases*

   - Identify and separate out failing integration tests that should be in
   unit test cases. (Aleks)
   - Convert a few existing integration tests to unit tests as examples
   - Define the expected code coverage we'd want at a functional module
   leve (i.e. module should have at least 80% unit testing coverage)
  - Let's think about how we improve our existing integration tests
  (see https://issues.apache.org/jira/browse/FINERACT-949) and what's
  balance we want between integration tests and unit tests.
   - Identify which unit test cases to focus on and ultimately have a wiki
   page with five categories, each category having 100 to 200 test cases and
   red or green tick mark to show if we have coverage.
  - Near-term step to having this page is for individuals like Nayan
  and Istvan based on the test cases their teams have implemented to input
  into a Google Sheet at least the categories and ideally the test
cases that
  were implemented so these can be focused on.
  - We can use this Google Sheet as a starting point:
  
https://docs.google.com/spreadsheets/d/1aGTcPV_bBhyri-pEFIoKph9NKFgu4cErhCb4tvWU-rY/edit?usp=sharing
   - Create a test data set (No owner yet)
   - Create a replicable cookbook for creation of test cases using DBUnit
   for setting up the database and providing a few examples for others to
   follow. Test cases can be set up with simple CSV files.
   - In future can generate Jacoco and other reports for test coverage.
   - We can reference some previous test cases that were documented at
   
https://drive.google.com/drive/folders/1T5MlVh0KWC6bQmqiZwEmoI73Q-0cuaxr?usp=sharing


*Documentation*
In parallel we need to:

   - Update documentation on testing
   - Update our strategy and guidance on what tests (unit and/or
   integration) are required for PR to be contributed.
  - It is still outstanding if test should be part of the PR or separate
  - Don't want to add too much friction to developers by requiring too
  many test to be created
  - Could put skeleton of test in place in Cucumber, mark as ignore
  test and then set up Github Actions to create a todo list of
ignored tests
  that other volunteers could work on.

Call for Mentors: 2022 Google Summer of Code for the Mifos Initiative

[Ed Cable]

Hello all,

It's that time of year again and the Mifos Initiative is looking to
participate in Google Summer of Code once more. While unfortunately last
year Mifos Initiative was not selected due to the need to let in new orgs
to the program, I'm optimistic we can get selected this year. Last year, we
still were able to play a role in helping guide the five interns that were
selected under the Apache Software Foundation but when we participate
directly through Mifos it allows us to target a larger class across a wider
variety of projects.

This year we'd be having interns work on our Mifos X web and mobile apps,
Fineract 1.x and Fineract CN, as well as more projects around our AI for
All strategy, our Payment Hub EE and payments integration, our Open Banking
layer, and for the first time projects related to OpenG2P.

Google Summer of Code applications are due February 21. I will refine our
application but need to ensure we have a committed group of mentors and a
solid ideas list. I have already been discussing ideas with our past GSOC
mentors and recent GSOC alum who will become mentors for the first time.

We'll be adding our mentors and refining our ideas list at:
https://mifosforge.jira.com/wiki/spaces/RES/pages/3004891137/Google+Summer+of+Code+2022+Ideas

I will schedule a community-wide Zoom meeting to have a discussion on
potential ideas and answer questions of prospective mentors

Once again as in 2021, there are some major exciting changes to the 2022
GSOC program - the three major changes are listed below (with full details
at the bottom of the email):

(1) Starting in 2022, the program will be *open to all newcomers of open
source* that are 18 years and older, *no longer focusing solely on
university students**.*
(2) GSoC Contributors will be able to choose from multiple size projects
~175 hour (medium) and 350 hour (large).
(3) Google is building increased flexibility around the timing of projects
- there is an option to extend the standard 12 week coding time frame to a
maximum of 22 weeks


The coding program officially begins June 13 and for the standard duration
projects ends September 12 and for the extended duration projects November
13.

2020 was our biggest year of participation in GSOC to date with 17 interns
mentored by the Mifos Initiative. That high number of interns tested the
limits of our mentors so I want to emphasize this year that if you express
interest in being a mentor, know the commitment it takes. We will be very
deliberate in our selection of projects this year to ensure we have proper
mentor capacity given with last year's smaller class it was more manageable
and in the end a better overall experience with more attention for each
intern.

Mifos participation is in addition to whatever participation Apache
Fineract might do as part of the umbrella organization, Apache Software
Foundation.

*Developers!*
This program is one of our most impactful ways to extend our software but
most importantly grow our community over the long run. Our most active
volunteers, committers, and maintainers in the community have all been
former GSOC students so if you're a senior community member looking for a
great way to give back, this is it!

I gave a talk a couple years back  that explains how GSOC is truly the
lifeblood and organic growth engine for our community -
https://www.youtube.com/watch?v=mtxBX7Sbqv0

In case you forgot, here's a link to blogs about past GSOC programs at:
https://mifos.org/blog/tag/gsoc/

If interested please *fill out this form*
<https://forms.gle/sFsYKdk4DtnvWmFM9> and/or reply to this email thread. If
you know someone who would be a good mentor, don't hesitate to invite them.

*Partners & Users!*

Regarding our list of Ideas, this year we'll both revisit some of the ideas
that weren't picked up last year, continue evolving the apps that students
have worked on in the past and try to do more projects on Fineract 1.x and
its ongoing modularization, the Payment Hub and payment orchestration,
streamlining design and development of our mobile apps, our Open Banking
APIs, and OpenG2P.

As we did last year, the majority of ideas we'll submit for
our application will be related to Mifos X distribution powered by Apache
Fineract 1.0 including web app (Community App), mobile apps (field officer,
mobile banking, mobile wallet ), and other modules (data import tool, etc.)
powered by Apache Fineract as well as our payment integration tools
including payment hub and mobile money integrations.

You can start adding ideas to our very early stage 2022 ideas page at
https://mifosforge.jira.com/wiki/spaces/RES/pages/3004891137/Google+Summer+of+Code+2022+Ideas
That page is still to be updated for current ideas.

We especially need more functional use cases of what the mobile apps should
support - if you would like to see new innovation and more development -
this is your chance to have your feedback be heard!

-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...

Re: Fineract-CN-Portfolio microservice issue

[Ed Cable]

Welcome to the community! Glad that you have gotten so far in your setup. @Jose
Hernandez  and @Victor Manuel Romero
Rodriguez  given you and your team have a
good depth of experience with Fineract CN can you give any pointers or
guidance to Enkhnaran?

Thanks,

Ed

On Wed, Jan 5, 2022 at 5:39 PM Enkhnaran Galsandorj <
enhnaran.galsand...@gmail.com> wrote:

> Dear devs,
>
> I'm in awe of this amazing complex project.
>
> I have set up my CN project on my CentOS machine and used docker compose
> project to set everything up. Everything works perfectly, except for the
> portfolio microservice. I've tried searching in the mail archive but found
> only one mail questioning the same issue.
> https://www.mail-archive.com/dev@fineract.apache.org/msg06234.html
> I have exactly the same problem with the same error messages. I have not
> found any workaround/solution for this. Are there any methods to work
> around this that I'm not aware of?
>
> Your response will be highly appreciated. Thank you in advance.
>
> Kind regards
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Fineract project in SonarCloud

[Ed Cable]

@Yannick Awasum  @Victor Manuel Romero Rodriguez
 I know you were involved in setting this up
- do you have admin rights to the Fineract project in SonarCloud?

@Petri Tuomola  Thanks for focusing on this.

SonarQube is now compatible with Github Actions? As I think in November you
were blocked due to lack of ability to store the secrets anywhere)

Ed

On Wed, Jan 5, 2022 at 3:01 PM Petri Tuomola 
wrote:

> Hi all
>
> Who has the admin rights to the fineract project in SonarCloud? I’d like
> to migrate this to use Github Actions so that we can decommission the
> Travis build script altogether, but for this I’d need admin rights to
> generate a new project key. I have access to SonarCloud but not to the
> fineract project.
>
> Not sure who set this up originally - but if anyone has any idea on how to
> get added as admin, it would be great to hear from you…
>
> Regards
> Petri
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Incubator Release Notes

[Ed Cable]

Michael, I think that's because I restored those pages. Prior to Avik's
request, they were just showing up as in the trash.

On Wed, Dec 29, 2021, 14:19 Michael Vorburger  wrote:

> Avik,
>
> On Wed, Dec 29, 2021 at 6:21 PM Avik Ganguly  wrote:
>
>> Hello everyone,
>>
>>
 https://mail-archives.apache.org/mod_mbox/www-announce/201701.mbox/%3CCAOSe2yuhJTNPENs_A3g8OYGM6ymN5tz-kg2NusSwt6=sgpf...@mail.gmail.com%3E
>>>
>>> The release notes can be found here:
>>>
>>> https://cwiki.apache.org/confluence/display/FINERACT/0.6.0-incubating+Release-+Apache+Fineract
>>
>> The above link for incubator fineract release notes is dead. When
>> Fineract graduated, did the incubator release notes move to somewhere else
>> or did it get removed altogether? Can a Confluence space admin perhaps
>> restore the incubator release notes in case they were removed during
>> graduation?
>>
>
> I'm probably misunderstand what you are asking, but for me on
> https://cwiki.apache.org/confluence/display/FINERACT/0.6.0-incubating+Release-+Apache+Fineract
> it currently does still show the following, is this not the incubator
> release notes you were hoping to see:
>
> 0.6.0-incubating Release- Apache Fineract
> 
>
>- Created by Nazeer Shaik
>, last
>modified by Myrle Krantz
> on Jan 09, 2017
>
> 
>
>
> Scope
>
> There are main goals of this release
>
>- Addressing some of Apache Fineract 0.5.0-incubating review comments
>-
>
>Share the new feature(s) & bug fixes that have been developed so far,
>to give the community a good sense of the upcoming 0.6.0 release.
>
> Release Artifacts
>
> Download the 0.6.0-incubating release
> 
>
> This release contains both Source & Binary artifacts.
> Release Notes
>
> New Features & Improvements
>
>- Workflow implementation with entity data tables
>- Updating readme.md with relevant user manuals
>- Added instructions in readme.md about how to run RAT
>
> Bugs
>
>- FINERACT-288 - Client's Image Uploaded Not Showing on UI in Amazon S3
>- FINERACT-260 - Validation need to be added if the client charge is
>applied before client activation date
>- FINERACT-267 - Foreclosure Issue: Loan with Installment fee status
>is overpaid
>- FINERACT-309 - Editing 'Product Mix' Not Working
>-
>
>FINERACT-361 - Getting
>error.msg.loanschedule.emi.amount.must.be.greter.than.interest on loan
>submit
>-
>
>Fix to charge fees when total amount changed during approval
>-
>
>Remove unnecessary checking for missing joined date
>
>
>
> With best regards,
>> Avik Ganguly.
>>
>> Disclaimer:
>>
>> Privileged & confidential information is contained in this message
>> (including all attachments). If you are not an intended recipient of this
>> message, please destroy this message immediately and kindly notify
>> the sender by reply e-mail. Any unauthorised use or dissemination of this
>> message in any manner whatsoever, in whole or in part, is strictly
>> prohibited. This e-mail, including all attachments hereto, (i) is for
>> discussion purposes only and shall not be deemed or construed to be a
>> professional opinion unless expressly stated otherwise, and (ii) is not
>> intended, written or sent to be used, and cannot and shall not be used, for
>> any unlawful purpose. This communication, including any attachments, may
>> not be free of viruses, interceptions or interference, and may not be
>> compatible with your systems. You should carry out your own virus checks
>> before opening any attachment to this e-mail. The sender of this e-mail and
>> *Fynarfin Tech Private Limited* shall not be liable for any damage that
>> you may sustain as a result of viruses, incompleteness of this message, a
>> delay in receipt of this message or computer problems experienced.
>>
>

Re: Incubator Release Notes

[Ed Cable]

I restored those incubator release notes for 0.4, 0.5 and 0.6

Ed

On Wed, Dec 29, 2021 at 9:21 AM Avik Ganguly  wrote:

> Hello everyone,
>
>
>>> https://mail-archives.apache.org/mod_mbox/www-announce/201701.mbox/%3CCAOSe2yuhJTNPENs_A3g8OYGM6ymN5tz-kg2NusSwt6=sgpf...@mail.gmail.com%3E
>>
>> The release notes can be found here:
>>
>> https://cwiki.apache.org/confluence/display/FINERACT/0.6.0-incubating+Release-+Apache+Fineract
>
> The above link for incubator fineract release notes is dead. When Fineract
> graduated, did the incubator release notes move to somewhere else or did it
> get removed altogether? Can a Confluence space admin perhaps restore the
> incubator release notes in case they were removed during graduation?
>
> With best regards,
> Avik Ganguly.
>
> Disclaimer:
>
> Privileged & confidential information is contained in this message
> (including all attachments). If you are not an intended recipient of this
> message, please destroy this message immediately and kindly notify
> the sender by reply e-mail. Any unauthorised use or dissemination of this
> message in any manner whatsoever, in whole or in part, is strictly
> prohibited. This e-mail, including all attachments hereto, (i) is for
> discussion purposes only and shall not be deemed or construed to be a
> professional opinion unless expressly stated otherwise, and (ii) is not
> intended, written or sent to be used, and cannot and shall not be used, for
> any unlawful purpose. This communication, including any attachments, may
> not be free of viruses, interceptions or interference, and may not be
> compatible with your systems. You should carry out your own virus checks
> before opening any attachment to this e-mail. The sender of this e-mail and
> *Fynarfin Tech Private Limited* shall not be liable for any damage that
> you may sustain as a result of viruses, incompleteness of this message, a
> delay in receipt of this message or computer problems experienced.
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Critical RCE Vulnerability: log4j - CVE-2021-44228

[Ed Cable]

Thank you Airsay for raising this to the community and their Aleks and
Michael for clarifying in the exposure and impact for the Fineract
community.

Ed

On Sun, Dec 12, 2021, 08:12 Isaac Kamga  wrote:

> Thanks for the reassurance Michael.
>
> On Sat, Dec 11, 2021 at 09:16 Michael Vorburger  wrote:
>
>> Independently confirming this - relax everyone! (As in, you can relax for
>> Fineract. Don't relax for anything else you are responsible for - do check
>> any other code you have, this security vulnerability is as bad they can
>> get; the Internet is rightfully on fire about this.)
>>
>> https://spring.io/blog/2021/12/10/log4j2-vulnerability-and-spring-boot
>> (which I found while working on
>> https://github.com/vorburger/MariaDB4j/issues/509) has some related
>> background; TL;DR: *"The log4j-to-slf4j and log4j-api jars that we
>> include in spring-boot-starter-logging cannot be exploited on their own.
>> Only applications using log4j-core and including user input in log messages
>> are vulnerable."*
>>
>> Or, more technically:
>>
>> $ ./gradlew fineract-provider:dependencies | grep log4j
>> |||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
>> ||||\--- org.apache.logging.log4j:log4j-api:2.14.1
>> |||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
>> ||||\--- org.apache.logging.log4j:log4j-api:2.14.1
>> |||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
>> ||||\--- org.apache.logging.log4j:log4j-api:2.14.1
>> |||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
>> ||||\--- org.apache.logging.log4j:log4j-api:2.14.1
>> |||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
>> ||||\--- org.apache.logging.log4j:log4j-api:2.14.1
>> |||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
>> ||||\--- org.apache.logging.log4j:log4j-api:2.14.1
>>
>> $ ./gradlew fineract-provider:dependencies | grep log4j-core
>> (nothing)
>>
>> Hope this helps everyone to sleep well... ;-)
>>
>>
>> On Sat, Dec 11, 2021 at 10:28 AM AirsayLongCon 
>> wrote:
>>
>>> Hello Aleks
>>> Thank you for the clarification
>>>
>>> On Sat, Dec 11, 2021, 10:17 AM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 Hi,

 ... we are using SLF4J to abstract all the different logging frameworks
 (Commons Logging, Log4J etc.). Under the hood logging in Fineract is done
 by Logback and not Log4j. The only Log4j dependencies we have are those
 that "redirect" the logging to Logback.

 Here's also a vulnerability report for that specific dependency
 ("org.apache.logging.log4j:log4j-to-slf4j"):

 https://snyk.io/vuln/maven:org.apache.logging.log4j:log4j-to-slf4j

 FYI

 Cheers,

 Aleks

 On Sat, Dec 11, 2021 at 2:10 AM AirsayLongCon 
 wrote:

> Hello community,
> Are we are of the RCE reportedly affecting log4j
>
> If your organization uses the log4j library, you should upgrade
> to log4j-2.1.50.rc2 immediately.
>
>
> https://www.huntress.com/blog/rapid-response-critical-rce-vulnerability-is-affecting-java
>

[ANNOUNCE] Victor Romero as new Apache Fineract Committer

[Ed Cable]

Hi All,

It is with great pleasure that I'm able to announce that Victor Romero was
recently voted in as an Apache Fineract committer and he has accepted the
invitation to become an Apache Fineract Committer.

You should probably recognize Victor from the mailing lists as he has been
actively contributing to the community in a variety of ways since 2017.
Victor extensively shares his expertise in in-depth discussions on the
mailing lists he's participated in around scalability, security, and most
recently idempotency. He's also always immediate in responding to fellow
community members to assist with their queries. He's made a number of
contributions to both Fineract and Fineract CN and also has additional
contributions to Fineract CN planned. Victor has mentored for Google Summer
of Code on a number of occasions and is now working on helping get some
community devops infrastructure in place.

Join us in formally welcoming Victor as a committer. We look forward to his
ongoing contribution and his continued growth on his journey as a committer.

Thanks,

Ed Cable
Apache Fineract PMC

Re: Standing Instructions For Loans Loan Installments

[Ed Cable]

Wilfred,

As James pointed out if you did a search on Google, you should find the
user manual section on configuring standing instructions to repay loan
installments.

Did this topic answer your question?
https://docs.mifos.org/user-manual/for-operational-users-mifos-x-web-app/accounts-and-transactions/loan-accounts/how-to-make-repayments-on-a-client-loan-account

Ed

On Sun, Oct 24, 2021 at 1:24 PM James Dailey  wrote:

> Hi Wilfred -
>
> That's great.
>
> Hopefully you have read the FAQ which lays out what component is where?
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327
>
> I mention this because there are other open source projects, outside of
> fineract, that are publishing UIs and native apps, so there are starting
> points for you to look at. ICYMI.
>
> The strategy of Fineract is to allow you to build your own front end
> experience, based on the APIs, and to ask for your help in contributing
> back core code - i.e. code that is needed in Fineract to support the use
> cases in the various front ends that are out there.  There are many active
> discussions about the roadmap for Fineract.
>
> James
>
>
> James Dailey
> skype: jdailey
>
>
> On Sun, Oct 24, 2021 at 11:31 AM Kigred Developer <
> kigred.develo...@gmail.com> wrote:
>
>> Thanks for guidance James.
>> I am building a user interface to work with Fineract 1.X. I will try to
>> follow your instructions here.
>>
>> Regards.
>>
>> On Sun, Oct 24, 2021 at 8:21 PM James Dailey 
>> wrote:
>>
>>> Hi Wilfred -
>>>
>>> Welcome to the list and the community.  I've noticed you pointed out a
>>> broken link (which I took out) and want to thank you for participating.
>>> Can you tell us more about what you are working on?
>>>
>>> On the standing instructions topic, and in general (and this is a
>>> reminder for everyone on list), the way to proceed is to:
>>>
>>>1. Do the Initial Research -
>>>   1. see if there is documentation on the wiki about this.
>>>   2. check out the listserv for discussion that may have happened [
>>>   https://lists.apache.org/list.html?dev@fineract.apache.org ]
>>>   3. check out the swagger documented API on the hosted
>>>   fineract.dev site (APIs map to available features)
>>>2. If the feature of functionality is not present, then please:
>>>   1. spell out the requirements in some detail in an email
>>>   2. and open up a Jira Ticket with the requirements
>>>   3. and on the listserv, explain what you hope to change in the
>>>   code and how you'd like to add the feature
>>>   4. And get some discussion and AGREEMENT, or at least non
>>>   objection (on listserv)
>>>3. Raise a Pull Request with your code changes including acceptance
>>>tests, documentation, etc.
>>>4. Work the process through to acceptance of your PR
>>>
>>> If you are new to an open source project, it may be useful to hang out
>>> on the list and read past posts for many weeks or months to get a feel for
>>> the community, to work on an existing ticket that needs fixing, or to help
>>> with a priority task that the community has already identified.
>>>
>>> And yes, we probably NEED better documentation, including around the
>>> existing Standing Instructions functionality on our wiki, and/or a deeper
>>> dive into what is needed and what may be missing.   Yes, it exists, and you
>>> may find the documentation on the MifoX website gives you better info (the
>>> Mifos project maintains the front end and contributed the core MifosX which
>>> became Fineract1.x).
>>>
>>> Thank you
>>>
>>>
>>>
>>> On Sun, Oct 24, 2021, 1:12 AM Kigred Developer <
>>> kigred.develo...@gmail.com> wrote:
>>>
>>>> Hello Devs,
>>>>
>>>> I am considering migration of sacco operations to Fineract 1.X.
>>>> I know it is possible to create loans whose installments date back to
>>>> 2019 but is it possible to have installments settled using standing
>>>> instructions?
>>>>
>>>> Regards.
>>>> Wilfred
>>>>
>>>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [Mifos-developer] Merge Strategy for Android Client

[Ed Cable]

Chinmay,

I know you likely don't have cycles to help with Fineract CN Mobile but you
and @Shashank Priyadarshi  share your strategy
and plan that we were going to execute on soon to merge the android-client
PRs and create a release?

Thanks,

Ed

On Sat, Oct 23, 2021 at 4:35 AM Awasum Yannick  wrote:

> This is still the case this year. So many unmerged PRs on the Fineract
> CN mobile project. We need mobile developers to help review them.
>
>
> Chinmay, do you want to help us review some of these PRs?
> https://github.com/apache/fineract-cn-mobile as well?
>
>
> On Sat, Nov 21, 2020 at 4:42 PM Michael Vorburger 
> wrote:
> >
> > On Sat, 21 Nov 2020, 12:00 Chinmay Kulkarni, 
> wrote:
> >>
> >> Hi,
> >> For android-client, we currently have 159 Open Pull Requests
> >
> >
> > Phew! That's... a lot.
> >
> >> addressing various kinds of issues. Out of these, some are approved, a
> couple of them are awaiting changes and the remaining ones are yet to be
> reviewed.
> >>
> >> We need to get these PRs merged into the codebase as soon as possible
> for the next release of Android Client. Also, after this new contributors
> could work on new issues and features.
> >>
> >> For the approved PRs, I wanted to ask what merge strategy do we follow?
> Do we start merging the latest PRs first and old ones later or vice versa?
> It would be helpful if anyone can shed some light on this.
> >
> >
> > Older ones first could be more"fair", I guess.
> >
> >> Thanks,
> >> Chinmay
> >> Mifos-developer mailing list
> >> mifos-develo...@lists.sourceforge.net
> >> Unsubscribe or change settings at:
> >> https://lists.sourceforge.net/lists/listinfo/mifos-developer
> >
> > Mifos-developer mailing list
> > mifos-develo...@lists.sourceforge.net
> > Unsubscribe or change settings at:
> > https://lists.sourceforge.net/lists/listinfo/mifos-developer
>


-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Using Swagger CodeGen to Generate a Client Library.

[Ed Cable]

Chinmay, Michael, and Manthan,

We were running into some questions regarding the swagger definitions. Are
they generated from source code and can be used to generate client
libraries? If so, does it currently cover all of the APIs within Fineract
1.x?

We have been reviewing the fineract-client email threads
http://mail-archives.apache.org/mod_mbox/fineract-commits/202010.mbox/%3c20201019210057.5d32981...@gitbox.apache.org%3E
and gist report

https://gist.github.com/Grandolf49/f79537436a467dac0baa9458a38290c5

but still had some doubts.

@adam.sa...@dpc.hu  Can you share what additional
questions you have?

Thanks,

Ed

Re: Open source on Financial Services

[Ed Cable]

Thanks Javier for sharing. Just to clarify Javier, Angela is a "she". :)

For more context, here is the keynote that Angela gave at the inaugural
Fintech DevCon sponsored by Moov. I helped give her some background on
Mifos in preparation of her talk.

She spends about two minutes talking about Mifos/Fineract and includes the
Paul Ramsey quote I've used to highlight the virtuous cycle.

You should listen to the whole talk but the Mifos mention is at about 20:35
in: https://youtu.be/fJQF93zL9PA

I will be doing a blog post soon noting our ongoing interactions with Angel
and a16z and this strong endorsement/recognition of mifos/fineract.

Ed

On Mon, Oct 18, 2021 at 4:16 AM Javier Borkenztain  wrote:

> A great milestone to be mentioned by the Fintech guru Angela Strange from
> A16Z on his blog post and conference.
>
> Full article here:
> https://future.a16z.com/open-source-financial-services/
>
> And Mifos and Apache  mentioned here:
>
>
> "*The Mifos Initiative, leaders of the Mifos X platform, now an Apache
> project, is an open source banking core. Developers can access free open
> source libraries and benefit from the expertise of a global community to
> build cost-effective banking applications for microfinance institutions and
> QR-based payments for micro merchants. These new solutions focus on the
> underserved bottom of the socioeconomic pyramid*."
>
> [image: Logo] <https://www.fiter.io>
> *Javier Borkenztain* *| CEO*
> *e:* jav...@fiter.io
> *w:* fiter.io <http://www.fiter.io>
> *m:* +598 97980801
> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>
> Sent via Superhuman <https://sprh.mn/?vip=jav...@fiter.io>
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Invitation to Contribute to the October 2021 Fineract Board Report

[Ed Cable]

Great suggestion Kevin. I'll connect up again with sally. A good way to
close the loop on the conversation I'd begun that you had previously
initiated.

On Thu, Oct 14, 2021, 11:02 Kevin A. McGrail  wrote:

> Based on the way the board operates and pre-approves reports from
> projects, unless this was something with an ask for the board to do
> something, I don't think it would achieve anything. What I would suggest
> instead is emailing this to press at Apache.org. it's a great human
> interest story and perhaps something that Sally can make some suggestions
> about.
>
> On Thu, Oct 14, 2021, 09:29 Ed Cable  wrote:
>
>> Awasum,
>>
>> It would be good and appropriate to note what Ankit has referenced above.
>> Now that the contributors have safely made it out of Afghanistan, they and
>> Open Collective have been able to shed more light on the efforts to assist
>> them in this blog post:
>>
>>
>> https://blog.opencollective.com/helping-open-source-contributors-escape-afghanistan/
>>
>> The campaign was organized by Lukasz Gornicki and Fran Méndez and was
>> really a great story for how an open source community can come together to
>> assist individuals in need. I was able to help indirectly promote it to
>> individual ASF and Apache Fineract community members who were able to
>> assist in a very small manner in making donations. Words can't express how
>> much Lukasz and Fran really did to literally help the contributors escape -
>> it was a harrowing journey and they were actively in touch at each step of
>> the way to help the contributors get to their destination.
>>
>> Ankit is right in that our Fineract contributor (who is named in the blog
>> post) is an exceptionally talented mobile developer (including being an
>> Apache Fineract mentor for this years' GSOC) who is in need of support in
>> helping to get a job as his previous placement was disrupted because of the
>> crisis in Afghanistan.
>>
>> Awasum, please include what you feel would be appropriate from the blog
>> above and if you would like to include a link to the resume of the
>> contributor, I can share that as well.
>>
>> Ed
>>
>> On Thu, Oct 14, 2021 at 1:57 AM Muellners ApS 
>> wrote:
>>
>>> During this quarter, this community stood besides and supported the
>>> young talented human lives to escape from Afghanistan when the government
>>> collapsed, with fund raising by open source members elsewhere and visa
>>> application support by Denmark based Non for Profit Muellners Foundation,
>>> to which I am an advisor also.
>>>
>>> Please help me decide whether we should add this detail in this report
>>> or not. The PMC should take privacy consent from the contributor or
>>> individuals or Foundation mentioned, whose information is shared on the
>>> report.
>>>
>>> I believe this can help the young community member to gain recognition &
>>> perhaps a job.
>>>
>>>
>>>
>>> On Thu, 14 Oct 2021 at 09.38, Benura Abeywardena 
>>> wrote:
>>>
>>>> Thanks Ed !
>>>>
>>>> On Thu, 14 Oct 2021, 09:43 Ed Cable,  wrote:
>>>>
>>>>> I added a few notes to the report.
>>>>>
>>>>> Ed
>>>>>
>>>>> On Wed, Oct 13, 2021 at 2:45 PM Benura Abeywardena 
>>>>> wrote:
>>>>>
>>>>>> Thanks @awasum
>>>>>>
>>>>>> On Thu, Oct 14, 2021 at 2:55 AM Awasum Yannick 
>>>>>> wrote:
>>>>>>
>>>>>>> Permission Granted to benuraab.
>>>>>>>
>>>>>>> On Wed, Oct 13, 2021 at 10:06 PM Benura Abeywardena <
>>>>>>> benur...@gmail.com> wrote:
>>>>>>>
>>>>>>>> It's 'benuraab'.
>>>>>>>>
>>>>>>>> On Thu, Oct 14, 2021 at 2:21 AM Awasum Yannick 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Yes. You can add changes to the doc but make sure you don't delete
>>>>>>>>> any information. What is your Confluence ID so that I give you 
>>>>>>>>> permission
>>>>>>>>> to that document?
>>>>>>>>>
>>>>>>>>> On Wed, Oct 13, 2021 at 9:26 PM Benura Abeywardena <
>>>>>>>>> benur...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>

Re: Invitation to Contribute to the October 2021 Fineract Board Report

[Ed Cable]

Awasum,

It would be good and appropriate to note what Ankit has referenced above.
Now that the contributors have safely made it out of Afghanistan, they and
Open Collective have been able to shed more light on the efforts to assist
them in this blog post:

https://blog.opencollective.com/helping-open-source-contributors-escape-afghanistan/

The campaign was organized by Lukasz Gornicki and Fran Méndez and was
really a great story for how an open source community can come together to
assist individuals in need. I was able to help indirectly promote it to
individual ASF and Apache Fineract community members who were able to
assist in a very small manner in making donations. Words can't express how
much Lukasz and Fran really did to literally help the contributors escape -
it was a harrowing journey and they were actively in touch at each step of
the way to help the contributors get to their destination.

Ankit is right in that our Fineract contributor (who is named in the blog
post) is an exceptionally talented mobile developer (including being an
Apache Fineract mentor for this years' GSOC) who is in need of support in
helping to get a job as his previous placement was disrupted because of the
crisis in Afghanistan.

Awasum, please include what you feel would be appropriate from the blog
above and if you would like to include a link to the resume of the
contributor, I can share that as well.

Ed

On Thu, Oct 14, 2021 at 1:57 AM Muellners ApS  wrote:

> During this quarter, this community stood besides and supported the young
> talented human lives to escape from Afghanistan when the government
> collapsed, with fund raising by open source members elsewhere and visa
> application support by Denmark based Non for Profit Muellners Foundation,
> to which I am an advisor also.
>
> Please help me decide whether we should add this detail in this report or
> not. The PMC should take privacy consent from the contributor or
> individuals or Foundation mentioned, whose information is shared on the
> report.
>
> I believe this can help the young community member to gain recognition &
> perhaps a job.
>
>
>
> On Thu, 14 Oct 2021 at 09.38, Benura Abeywardena 
> wrote:
>
>> Thanks Ed !
>>
>> On Thu, 14 Oct 2021, 09:43 Ed Cable,  wrote:
>>
>>> I added a few notes to the report.
>>>
>>> Ed
>>>
>>> On Wed, Oct 13, 2021 at 2:45 PM Benura Abeywardena 
>>> wrote:
>>>
>>>> Thanks @awasum
>>>>
>>>> On Thu, Oct 14, 2021 at 2:55 AM Awasum Yannick 
>>>> wrote:
>>>>
>>>>> Permission Granted to benuraab.
>>>>>
>>>>> On Wed, Oct 13, 2021 at 10:06 PM Benura Abeywardena <
>>>>> benur...@gmail.com> wrote:
>>>>>
>>>>>> It's 'benuraab'.
>>>>>>
>>>>>> On Thu, Oct 14, 2021 at 2:21 AM Awasum Yannick 
>>>>>> wrote:
>>>>>>
>>>>>>> Yes. You can add changes to the doc but make sure you don't delete
>>>>>>> any information. What is your Confluence ID so that I give you 
>>>>>>> permission
>>>>>>> to that document?
>>>>>>>
>>>>>>> On Wed, Oct 13, 2021 at 9:26 PM Benura Abeywardena <
>>>>>>> benur...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Awasum,
>>>>>>>>
>>>>>>>> As a former GSOC intern, are we allowed to add contributions to the
>>>>>>>> report? If so, shall I add contributions under the "Contributions" 
>>>>>>>> section?
>>>>>>>>
>>>>>>>> Thanks & Regards,
>>>>>>>> Benura
>>>>>>>>
>>>>>>>> On Thu, Oct 14, 2021 at 1:43 AM Awasum Yannick 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>>
>>>>>>>>> I am making final edits and additions to the board report. The
>>>>>>>>> deadline is today but I am going to wait for a day and submit the 
>>>>>>>>> report
>>>>>>>>> tomorrow evening as the board meeting will take place in 7 days time. 
>>>>>>>>> The
>>>>>>>>> board will hopefully still have time to review them before the meeting
>>>>>>>>> proper.
>>>>>>>>>
>>>>>>>>> On Wed, Oct 6, 2021 at 8:15 PM Awasum Yannic

Re: Invitation to Contribute to the October 2021 Fineract Board Report

[Ed Cable]

I added a few notes to the report.

Ed

On Wed, Oct 13, 2021 at 2:45 PM Benura Abeywardena 
wrote:

> Thanks @awasum
>
> On Thu, Oct 14, 2021 at 2:55 AM Awasum Yannick  wrote:
>
>> Permission Granted to benuraab.
>>
>> On Wed, Oct 13, 2021 at 10:06 PM Benura Abeywardena 
>> wrote:
>>
>>> It's 'benuraab'.
>>>
>>> On Thu, Oct 14, 2021 at 2:21 AM Awasum Yannick 
>>> wrote:
>>>
>>>> Yes. You can add changes to the doc but make sure you don't delete any
>>>> information. What is your Confluence ID so that I give you permission to
>>>> that document?
>>>>
>>>> On Wed, Oct 13, 2021 at 9:26 PM Benura Abeywardena 
>>>> wrote:
>>>>
>>>>> Hi Awasum,
>>>>>
>>>>> As a former GSOC intern, are we allowed to add contributions to the
>>>>> report? If so, shall I add contributions under the "Contributions" 
>>>>> section?
>>>>>
>>>>> Thanks & Regards,
>>>>> Benura
>>>>>
>>>>> On Thu, Oct 14, 2021 at 1:43 AM Awasum Yannick 
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I am making final edits and additions to the board report. The
>>>>>> deadline is today but I am going to wait for a day and submit the report
>>>>>> tomorrow evening as the board meeting will take place in 7 days time. The
>>>>>> board will hopefully still have time to review them before the meeting
>>>>>> proper.
>>>>>>
>>>>>> On Wed, Oct 6, 2021 at 8:15 PM Awasum Yannick 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> We have started writing the Fineract Board report for October 2021.
>>>>>>> You are all invited to contribute here:
>>>>>>> https://cwiki.apache.org/confluence/display/FINERACT/2021-10+October+Report
>>>>>>>
>>>>>>> GSoC Interns and Mentors, you can contribute by summarizing your
>>>>>>> projects. Ed, would you like to help again here?
>>>>>>>
>>>>>>> Javier, James and others, would you like to write something about
>>>>>>> ApacheCon? I have been hearing important things.
>>>>>>>
>>>>>>> Contributors, put in a few words about the wonderful work you do.
>>>>>>>
>>>>>>> We will combine all of these points and submit the report on Tuesday
>>>>>>> 12 October 2021.
>>>>>>>
>>>>>>>
>>>>>>> Thanks.
>>>>>>> Awasum Yannick.
>>>>>>> PMC Chair, Apache Fineract.
>>>>>>>
>>>>>>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: ApacheCon @2021 Fineract track videos available on Youtube

[Ed Cable]

cies*
>>> <https://mailtrack.io/trace/link/7fe6cd9b80612cd8303a096117315078ec082d47?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNSnnPD52k5k%26list%3DPLU2OcwpQkYCwZfTRhACzyM6QT1qPijPFw%26index%3D152=6675149=0fdf58097c3a3dc5>
>>>
>>> James Dailey
>>>
>>> Central Bank Digital Currencies (CBDCs) are an emerging set of
>>> blockchain and cryptographic enabled solutions that taken together forms a
>>> national cryptocurrency. It has the support of the International Bank of
>>> Settlement (IBS) as a promising area of innovation. Can CBDCs challenge the
>>> status quo of banking systems? How does the CBDC allow the Central Bank to
>>> do clearing and settlements across different assets class better? What
>>> would a global architecture look like? What would cause Central Banks to
>>> adopt CBDCs? How does this relate to one basic-account-per-person provide
>>> for an economy? This is survey of the current discussion and speculation on
>>> the future of CBDCs.
>>>
>>> *CEOs Panel: How the business sees the platform*
>>> <https://mailtrack.io/trace/link/1f5e1100930317688bb7f01fb21ba3d366f17a8c?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DcFyy14-5Dng%26list%3DPLU2OcwpQkYCwZfTRhACzyM6QT1qPijPFw%26index%3D152=6675149=926d084bce4caa37>
>>>
>>> Juan Esteban Saldarriaga, Uzoma Dozie, Javier Borkenztain
>>>
>>> During this panel, the CEOs of two successful fintech companies in
>>> Colombia and Nigeria will take us through their companies journey in
>>> implementing Fineract.
>>>
>>> Why did they choose Fineract as the engine to implement core banking
>>> software? What challenges did they face and how Fineract flexibility
>>> allowed them to sort them? How is the software scalability going along with
>>> the companies growth? His view on how Fineract can support all types of
>>> fintech projects?
>>>
>>> *Extending Fineract Accounting using Odoo ERP*
>>> <https://mailtrack.io/trace/link/000acb44a07961ac17a00a94be32914f0b4537dc?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DWPMKCZYXAvE%26list%3DPLU2OcwpQkYCwZfTRhACzyM6QT1qPijPFw%26index%3D150=6675149=405023084bbde43b>
>>>
>>> John Ruhiu
>>>
>>> As bigger and more complex organizations adopt Fineract as their core
>>> banking system it's becoming necessary to enhance many features to cope
>>> with the requirements of these organizations.
>>>
>>> The accounting module available out of the box is designed to cater to
>>> transaction-related journal entries. This is not sufficient for larger
>>> organizations that require other accounting modules such as asset
>>> management, payroll, branch accounting, and richer analysis and reporting.
>>>
>>> One option is to extend the accounting module in Fineract to include
>>> these features. The other option is to integrate with a mature ERP that has
>>> these features. After some analysis, it turned out that the second option
>>> is far better.
>>>
>>> In this presentation, we are going to look at how we successfully
>>> integrated with Odoo. The challenges, wins, and opportunities.
>>>
>>> *OpenG2P one year on*
>>> <https://mailtrack.io/trace/link/197143a0145d03c0c9772c60e0837d60600f8ecf?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxI1txdaBHDs%26list%3DPLU2OcwpQkYCwZfTRhACzyM6QT1qPijPFw%26index%3D149=6675149=9326efac90bbff77>
>>>
>>> Ed Cable, Jill Shemin, James Dailey, Karina Lizeth Ortiz Muñoz, Raul
>>> Salomon Almeraya Sibaja
>>>
>>> In ApacheCon@Home 2020 we introduced this new effort and this year we
>>> report back on challenges and progress made:
>>>
>>> OpenG2P is a digital public good digitizing large scale cash transfers
>>> with open source building blocks, recently designated by Digital Public
>>> Goods Alliance. Meanwhile GovStack is a global effort to define a set of
>>> building blocks, especially open source, for governments to leverage when
>>> building new systems.
>>>
>>> These efforts, underway just in the last two years, are starting with
>>> the requirements for government services and building out open APIs between
>>> components. This discussion will be about the various architectural
>>> decisions, lessons learned and next phases of the project.
>>>
>>> *From Monolith to Microservices: Modularizing Fineract 1.x*
>>> <https://mailtrack.io/trace/link/a23cebb79032dc4ae1ab1dda0def6554f7529cd0?url=https%3A%2F%2Fwww.youtube

Re: State of the Project

[Ed Cable]

oject"
>>> talk at ApacheCON next week and I would like your input into that.
>>> ApacheCON is the annual conference that this year is again online.
>>> https://www.apachecon.com/acah2021/tracks/.  Register today!
>>>
>>>
>>>
>>> To help me with my REPORT OUT:  Please feel free to share observations,
>>> criticisms, concerns, as well as compliments to specific contributors.
>>> Please either respond on list, or email me directly.
>>>
>>>
>>>
>>> If you or your company is engaged in developing new features and wants
>>> to be mentioned, I would like to highlight that.
>>>
>>>
>>>
>>> There is much to celebrate and I am very grateful to all of the
>>> contributors this past year.
>>>
>>>
>>>
>>> Thank you,
>>>
>>> - James
>>>
>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

EVENT: Final Google Summer of Code Showcase - August 31 at 1300GMT

[Ed Cable]

We are coming to the tail end of the 2021 Google Summer Code program with
our five interns through the Apache Software Foundation. All have been
productive and successful with their projects around a mobile wallet for
Fineract CN, Android SDK enhancements, Fineract CN Mobile Field Ops App
improvements, the collateral module, and machine learning credit scorecard
module.

Demos and showcases of their efforts will be on August 31 at 1300GMT via
Zoom.

Register and attend here:
https://us02web.zoom.us/webinar/register/1916294885738/WN_8fMaEYKGQv29q45M6-GlNg

Thanks,

Ed

Re: Help required regarding datable

[Ed Cable]

Danish, sharing my answer here too:

You can do that by configuring that in entity checks for data tables. To
configure via the UI, you can go to Admin > Org > Entity Data Table Checks
and then create a new one where you can select "Client" for entity,
"Create" for status, and then select the Data table from the drop down to
associate and attach to Create Client stage of workflow. User Manual for
how to do through UI is here:
https://docs.mifos.org/user-manual/for-administrators-mifos-x-platform/administration/organization/entity-data-table-checks
and API docs are here:
https://demo.mifos.io/api-docs/apiLive.htm#entitydatatablechecks

On Mon, Aug 9, 2021, 07:23 Danish Jamal  wrote:

> Does anyone have idea on how to associate a datable with specific api. For
> example I have a datatable created named Client Beneficiary information
> and I want to associate with client, so that whenever client creates a new
> client this datatables is need to be filled..
>
> Regards,
> Danish Jamal
> Github  | LinkedIn
> 
>
>

Re: Running Fineract in Kubernetes

[Ed Cable]

Hello William,

Welcome to the community! I'm cc'ing on this email @Victor Manuel Romero
Rodriguez  from Fintecheando as he and his
team have been contributing in a number of different ways to help with
containerization of Fineract.

I'd love to chat further about LakeHub and how to accelerate your efforts.
As President of the Mifos Initiative, it's one of my key priorities to
better engage with incubators like yourself to grow our ecosystem.
Mifos/Fineract provides a set of open source core banking building blocks
that provide an ideal solution for embedded finance enabling fintechs to
easily embed financial services in their solutions freeing them up to focus
on customer-facing innovation.

We are also kicking off a working group on savings-led financial inclusion
along with others who have been digitizing savings groups. If you'd like to
be a part of that please join our slack channel at
https://join.slack.com/share/zt-tw2wt2mv-byFOuFH51N9cc1FLafj3hg

Best wishes,

Ed



On Fri, Aug 6, 2021 at 7:00 PM William Ondenge 
wrote:

> Hello Community,
>
> I'm looking for help around the plumbing involved in deploying Apache
> Fineract in a Kubernetes Cluster.  I'm conversant with Docker and K8s at a
> high level.
>
> I currently support developers and entrepreneurs who are trying to come up
> with social enterprises for greater good and impact. We are having
> conversations around our community on how to leverage the Fineract
> Platform for last mile payments for the informal savings group in rural
> parts of Kenya. I was looking for some coaching, support and mentorship
> sessions so that I can do knowledge transfer to these amazing and resilient
> innovators who want to make a difference.
>
> Any help would be greatly appreciated.
>
>
> --
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

REMINDER: Apache Fineract GSOC Midterm Showcase Tuesday July 27 at 1300GMT

[Ed Cable]

Hi community,

We're about midway through GSOC and we'd like to showcase the efforts of
our five Apache Fineract GSOC interns thus far. Join us for a webinar on
Zoom this Tuesday July 27 at 1300GMT at
https://us02web.zoom.us/webinar/register/6016268741005/WN_K1nimxU9QiqJgEr5NQ2CjQ

You can see the progress on follow their daily updates on our
#gsod-daily-processes on the Mifos slack (https://bit.ly/mifos-slack)

* Android SDK and Android Field Operations App integration led by Danish
Jamal
* Mobile Wallet for for Fineract CN led by Kinar Sharma - see Gist at
https://gist.github.com/EGOR-IND/e13db2d9bcbb221d46741ec3644e800c
* Fineract CN Mobile enhancements by Varun Jain see Gist at
https://gist.github.com/varsvat/2eb968ede92c774b099b6663ded23837
* Collateral Module led by Benura Abeywardena - see Gist at
https://gist.github.com/BLasan/bd21154ab9cc69e996a9e5aa0395cc03
* Machine Learning Credit Scorecard Module Productization by Nasser Yemdijh



-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Contribute to Fineract Board Report for July 2021

[Ed Cable]

My updates are now in there Yannick - including points on the Fineract 1.5
release, backlog planning and GSOC, and ApacheCon.

Ed

On Sun, Jul 18, 2021 at 2:24 PM Ed Cable  wrote:

> Sorry Yannick I missed the last couple emails on this. I will add my
> updates during the next 24 hours
>
> Ed
>
> On Sun, Jul 18, 2021 at 10:09 AM Awasum Yannick  wrote:
>
>> We will be completing this and submitting within the next 24 hours.
>>
>> On Mon, Jul 12, 2021, 18:00 Awasum Yannick  wrote:
>>
>>> Hello Everyone,
>>>
>>> We have started writing the Fineract Board report for July 2021.
>>>
>>> Here is the link:
>>> https://cwiki.apache.org/confluence/display/FINERACT/2021-07+July+Report
>>>
>>> We invite you all to update this document with all the wonderful work
>>> you have been doing over the past 2 or 4 months. Everything around the
>>> Fineract Open Source Software.
>>>
>>> I know GSoC is going on and it will be wonderful to get updates on what
>>> our current interns have been working on during the past 6 weeks.
>>>
>>> We will submit this report by Friday this week.
>>>
>>>
>>> Thanks.
>>> Awasum
>>>
>>
>
> --
> *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
> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Contribute to Fineract Board Report for July 2021

[Ed Cable]

Sorry Yannick I missed the last couple emails on this. I will add my
updates during the next 24 hours

Ed

On Sun, Jul 18, 2021 at 10:09 AM Awasum Yannick  wrote:

> We will be completing this and submitting within the next 24 hours.
>
> On Mon, Jul 12, 2021, 18:00 Awasum Yannick  wrote:
>
>> Hello Everyone,
>>
>> We have started writing the Fineract Board report for July 2021.
>>
>> Here is the link:
>> https://cwiki.apache.org/confluence/display/FINERACT/2021-07+July+Report
>>
>> We invite you all to update this document with all the wonderful work you
>> have been doing over the past 2 or 4 months. Everything around the Fineract
>> Open Source Software.
>>
>> I know GSoC is going on and it will be wonderful to get updates on what
>> our current interns have been working on during the past 6 weeks.
>>
>> We will submit this report by Friday this week.
>>
>>
>> Thanks.
>> Awasum
>>
>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [GitHub] [fineract-cn-mobile-wallet] EGOR-IND closed pull request #2: Domain layer

[Ed Cable]

That would be more appropriate Awasum. How does one change that setting? I
think I didn't set it properly when initializing the repository as it
required a mailing list to be selected and I had forgotten commits@

Do you now how to modify this for an existing repo? I'm only familiar
with the process during creation. Is it just by opening an infra ticket or
is it a self-guided process?

Thanks,

Ed

On Mon, Jul 12, 2021 at 10:08 AM Awasum Yannick  wrote:

> Maybe these updates should go to the
> https://lists.apache.org/list.html?comm...@fineract.apache.org
> mailing address ?
>
> On Sun, Jul 11, 2021 at 7:26 AM GitBox  wrote:
>
>>
>> EGOR-IND closed pull request #2:
>> URL: https://github.com/apache/fineract-cn-mobile-wallet/pull/2
>>
>>
>>
>>
>>
>> --
>> This is an automated message from the Apache Git Service.
>> To respond to the message, please log on to GitHub and use the
>> URL above to go to the specific comment.
>>
>> To unsubscribe, e-mail: dev-unsubscr...@fineract.apache.org
>>
>> For queries about this service, please contact Infrastructure at:
>> us...@infra.apache.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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Mifos and Fineract highlighted in Digital Public Goods Alliance Final Report on Digital Public Infrastructure for Financial Inclusion

[Ed Cable]

We have had the privilege of collaborating and participating with other
projects like Mojaloop, MOSIP, OpenCRVS, X-Road, and OpenG2P as part of the
Financial Inclusion Community of Practice convened by the Digital Public
Goods Alliance

The Digital Public Goods Alliance is formally announcing their five year
strategy to help shift global focus to digital public goods and catalyzing
the ecosystems supporting them. They're highlighting this strategy at a
webinar this Tuesday June 29 and have also published their final report and
technical assessment on the Digital Public Goods and Digital Public
Infrastructures of which Mifos and Fineract have been recognized.

Learn more and download the full strategy and report at

https://mifos.org/blog/digital-public-good-alliance-launch/

*About the Digital Public Goods Alliance*
*The DPGA is a globally distributed, multi-stakeholder alliance working to
accelerate the attainment of the sustainable development goals in low- and
middle-income countries by facilitating the discovery, development, use of,
and investment in digital public goods. The Secretariat of the Digital
Public Goods Alliance is co-hosted by the Norwegian Agency for Development
Cooperation (Norad) and UNICEF and governed by an Interim Strategy Group
consisting of: iSPIRT; The Government of Norway; The Government of Sierra
Leone; and UNICEF.*

Welcome to our 2021 Google Summer of Code Interns for Apache Fineract

[Ed Cable]

It's that time of year again and we're proud to announce our class of 2021
Google Summer of Code interns. Regrettably Mifos was not selected as a
mentoring org this year but we were fortunately able to  participate under
the umbrella of the Apache Software Foundation and have selected 5 interns
to contribute back to Fineract-related projects this summer.

Mifos along with mentors from the community will be guiding them through
our traditional communication and check-in protocols for GSOC. Community
members are welcome t j

Join us in welcoming our interns, Danish Jamal, Kinar Sharam, Varun Jain,
from India, Yemdjih Nasser, from Cameroon, and Benura Abeywardena from Sri
Lanka. You can learn more about their professional background and their
projects in our official welcome blog post at
*https://mifos.org/blog/gsoc-2021/
*. Below are links to the project plans
for each intern.

Stay tuned for Part 2 of our Welcome Blog Post with Fun Facts next week.

Already they're off to a great start so say congrats and welcome them to
the community!

Community members are welcome to join our weekly check-ins via Zoom at
1300GMT on Tuesdays if they'd like: https://us02web.zoom.us/j/84551680441

Projects

   - *Danish Jamal*
  - Android SDK & Fineract Client
  

  - Mentor(s): Chinmay Kulkarni & Shashank Priyadarshi
   - *Kinar Sharma *
  - Mobile Wallet – Fineract-CN
  
  - Mentor(s): Devansh Aggarwal, Garvit Agarwal, Victor Romero,
  Shivansh Tiwari


   - *Varun Jain*
  - Fineract CN Mobile app
  
  - Mentor(s): Ahmad Jawid Muhammadi and Rajan Maurya


   - *Yemdjih Nasser*
  - Machine Learning Credit Scorecards
  
  - Mentor(s): Lalit Mohan, Aaashish Sawhney, Abhijit Ramesh, Jeremy
  Engelbrecht and Rahul Goel
   - *Benura Abeywardena*
  - Fineract Backlog & Collateral Management Module
  
  - Mentor(s): Bharath Gowda, Chaitanya Nuthalapati, Manthan Surkar,
  Sanyam Goel

Re: [VOTE] [APACHE FINERACT] 1.5.0 for release

[Ed Cable]

Thanks Petri for taking on this duty this release cycle.

+1 (Binding)

Ed

On Mon, May 24, 2021 at 2:42 AM Awasum Yannick  wrote:

> +1
>
> On Sat, May 22, 2021 at 5:29 PM MR. UGONNA UGWAH 
> wrote:
>
>> +1
>>
>> On Sat, 22 May 2021, 3:28 pm Aleksandar Vidakovic, <
>> chee...@monkeysintown.com> wrote:
>>
>>> +1
>>>
>>> On Sat, May 22, 2021 at 3:10 PM Petri Tuomola 
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> We have created Apache Fineract 1.5.0 release, with the artifacts below up 
>>>> for a vote.
>>>>
>>>> It fixes the following issues: 
>>>> https://cwiki.apache.org/confluence/display/FINERACT/1.5.0+-+Apache+Fineract
>>>>
>>>> Source & Binary files: 
>>>> https://dist.apache.org/repos/dist/dev/fineract/1.5.0/
>>>> Tag to be voted on (rc#): 
>>>> https://git-wip-us.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.5.0
>>>> Fineract's KEYS containing the PGP key we used to sign the release: 
>>>> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>>>> Note that this release contains source and binary artifacts.
>>>>
>>>> This vote will be open for 72 hours:
>>>>
>>>> [ ] +1 approve
>>>> [ ] +0 no opinion
>>>> [ ] -1 disapprove (and reason why)
>>>>
>>>>
>>>> Let me know if you find any problems with any of the artifacts / links etc 
>>>> - it’s my first time doing this...
>>>>
>>>> Thanks,
>>>> Petri
>>>>
>>>>
>>>>
>>>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Fineract 1.5.0 release branch

[Ed Cable]

Petri,

Thanks for stepping up to help Aleks and the rest of the Fineract
community. Given the imperative in getting this release out, it would be
great if you can continue to proceed ahead with the steps for releasing as
you've been following at

https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract

I think next up will be Step 5 from that list in freezing JIRA, creating
release tag, building distribution, digitally signing it, uploading it to
dist/dev (staging), and calling for the PMC vote which we'll need to have
open for at least 72 hours or at least 3 +1s from the PMC.

Ed

On Thu, May 20, 2021 at 4:36 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi Petri,
>
> ... thanks for stepping in... I got a bit side-tracked, because my main
> dev machine went up in flames and unfortunately I forgot to make a backup
> of my GPG keys. At least I have a new machine; the last thing I need to do
> is retrieve my keys from an nvme ssd (can't believe how difficult it is to
> get an external casing for that). I should be back on track by Monday...
> I'll sync with you to see how I can help out again.
>
> Cheers,
>
> Aleks
>
>
> On Fri, May 21, 2021 at 12:39 AM Petri Tuomola 
> wrote:
>
>> Hello all - hope you are staying safe and healthy
>>
>> For a number of reasons, I think it is important that we get the next
>> release - Fineract 1.5.0 - out as soon as possible. I know Aleks was
>> working on this - not sure how far you got with this Aleks?
>>
>> However, I’d be happy to help get this over the line. So unless someone
>> else wants to do this, or has any objections, I will create a 1.5.0 branch
>> off develop in our git repository at https://github.com/apache/fineract
>> on Saturday 22nd May. I will also then create a release tracking umbrella
>> issue for tracking all activity in JIRA.
>>
>> If you’d prefer another approach, or if you’d like to take care of this
>> (or have already started working not this), please drop me a note before
>> tomorrow so we don’t duplicate any work.
>>
>> Thanks everyone
>>
>> Regards
>> Petri
>>
>>
>>

-- 
*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [FINCN Blocker] New API deployed on an existing database results in 404

[Ed Cable]

Thanks Robert for your help.

On Tue, May 11, 2021, 08:51 Manoj VM  wrote:

> Dear Robert,
>
> Thank you very much for the API details.
>
> With this API we are able to update roles with new permissions.
> Now the new endpoints are populated properly in the JWT token.
>
> New endpoints are working fine now.
>
> Thanks again.
>
> Thanks and Regards,
> Manoj
> fynarfin.io
>
>
> On Mon, May 10, 2021 at 7:37 PM Robert Elles 
> wrote:
>
>> Hi Manoj,
>>
>> Yes, that sounds like some progress, good!
>>
>> You need to send a put request with the updated administrator role
>> containing your new permission group id in the permission list as payload
>> to the /identity/v1/roles/administrator endpoint. See
>> the RoleRestController in the identity project.
>>
>> Best,
>> Robert Elles
>>
>> Head of Global Product Development
>>
>> Kuelap, Inc.
>> +4915788460030
>> robert.el...@kuelap.io
>> www.kuelap.io
>> Pappelallee 78-79, 10437 Berlin, Germany
>> [image: linkedin] 
>>
>> Kuelap GmbH - Geschäftsführer: Craig Chelius | Registergericht:
>> Amtsgericht Charlottenburg (Berlin) | HBR 201125 B
>>
>>
>> On Mon, May 10, 2021 at 12:20 PM Manoj VM  wrote:
>>
>>> Dear Robert,
>>>
>>> Thanks a lot for your help
>>>
>>> First we were trying with an existing group Id in @Permitable
>>> annotation, after your suggestions we tried creating new group ids for our
>>> new endpoints.
>>>
>>> Now, the new group Ids are populated in isis_permitable_groups table in
>>> Cassandra. Yet we are not getting them in the permission list for
>>> administrator(operator). Also the new end points are not present in the JWT
>>> token created while logingin as administrator (operator).
>>>
>>> Could you please tell us how to assain these permissions to the role?
>>>
>>> I have a feel that we are in right direction, but still miles to go.
>>>
>>> Thanks,
>>> Manoj
>>>
>>> On Mon, 10 May, 2021, 14:10 Robert Elles, 
>>> wrote:
>>>
 Hello Avik,

 the gradle task publishApiToMavenLocal if for publishing the api
 artefact of the current projekt to the local maven repository but does not
 relate to permissions.

 In your cassandra instance you can also check the
 isis_permittable_groups table. If you see your new endpoints under the
 permittable group id then you know that the assign application worked. In
 the @Permittable did you set a new group id or did you use an existing one?
 With a new one you also need to assign the new permission to the user's
 role with whom you call the endpoint. With an existing group id there
 might  be still a bug that you can not create new endpoints under an
 existing permittable group id.

 Best regards,
 Robert

 On Sat, May 8, 2021 at 8:40 AM Avik Ganguly  wrote:

> Hi Robert, Community,
>
> Description : The APIs auto register only on a completely fresh new
> database.
>
> Thank you for the quick response on this issue.
>
> I suspect the issue you see is due to permissions not updated. After
>> you add a new API endpoint to a micro service you need to call the assign
>> application endpoint of provisioner so that the auth-system is made aware
>> of the new endpoint. Your rest controller endpoints must be annotated 
>> with
>> @Permittable with the proper parameters.
>
>
> The end points we have created are already annotated with
> @Permittable, however we tried changing the group name  to test whether 
> the
> new group name will force the permission creation, but it doesn't.
>
> And yes, every time we deploy a new end point, we call the
> provisioner  Assign api , which runs migration scripts, but doesn't add 
> new
> permissions.
>
> What can we be missing out on?
>
> Perhaps there is a need for one more  API in the initial API
> collection which does permission creation, as we could see APIs in 
> identity
> service for creating permissions.
> Also we found a gradle task for publishApiToMavenLocal, but running
> the task did not change anything.
>
> With best regards,
> Avik.
>
> Disclaimer:
>
> Privileged & confidential information is contained in this message
> (including all attachments). If you are not an intended recipient of this
> message, please destroy this message immediately and kindly notify
> the sender by reply e-mail. Any unauthorised use or dissemination of
> this message in any manner whatsoever, in whole or in part, is strictly
> prohibited. This e-mail, including all attachments hereto, (i) is for
> discussion purposes only and shall not be deemed or construed to be a
> professional opinion unless expressly stated otherwise, and (ii) is not
> intended, written or sent to be used, and cannot and shall not be used, 
> for
> any unlawful purpose. This communication, including any 

Mifos Initiative seeking a Technical Writer for Season of Docs to refine and consolidate our developer documentation

[Ed Cable]

The Mifos Initiative is excited to have been selected for the first time to
participate in Google's Season of Docs.

The project which we have received a grant to hire a technical writer for,
Consolidate Documentation into Mifos Developer Portal will greatly benefit
both the Fineract and Mifos communities as it will re-organize and unify
our current documentation, update relevant technical documentation, and
provide a more end to end overview of how the open source stack fits
together and how one can orient themselves across the various projects.

The need and scope of the project is fully outlined at
https://mifosforge.jira.com/wiki/spaces/RES/pages/2428043320/Season+of+Docs#proposal

We welcome any technical writers in the community to apply and highly
encourage you to forward this opportunity to anyone in your network who
might be a good fit.

Applications are due by May 1.

Thanks,


*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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>