You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »


## Description:  

At Apache Fineract, our mission is to build, maintain and enhance a cloud-ready core banking system for robust, scalable, and secure operations of financial institutions.  

We believe in financial services for everyone, including and especially for the unbanked and underbanked. 


## Issues:

  1. Trademark:  The project has been working to ensure that the Trademark policy is clear and to address potential issues.  
  2. Old releases:  We are working to encourage users to migrate to more recent versions.  Based on queries and other information, we are certain that a number of users are remaining on older versions or heavily forked code bases.  Upgrade paths have become problematic.  

We adopted a policy that only the last two releases will be listed on the main page and supported.  All users should migrate to those.  This is especially for bug or security fixes, of which there are a few.  We may revise to include a "stable long term release version".  

## Membership Data:

Apache Fineract was founded 2017-04-19 (6 years ago, contributed by Mifos.org)
There are currently 51 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 2 : 1     

Community changes, past quarter:

  • New Committer:  Bharath Gowda
  • New PMC Members:  Bharath Gowda, Javier Borkenztain, Victor Romero. 

## Project Activity:

  • The project added a Patch Release Process. 
  • The project released 1.8.2 and 1.7.2 on 28-November-2022, for a relatively minor issue and partly to further test the patch release process. 
  • We released 1.8.1 and 1.7.1 as patch releases on 25-November-2022 - covering the CVE below  - which was a first test of our patch release process. 
  • On August 22nd, the project released Fineract 1.8.0.  as covered in our last Board report. There is active development, and a new release (1.9) is anticipated in Q1 2023. Most of the contributions are coming in from commercial motivated interests.  
  • The project got a critical security vulnerability report. It was able to deliver a patch following the Apache process and issue the CVE-2022-44635 for the supported versions, and the community also got involved in creating patches for earlier versions. 
  • In November we conducted a Survey of the community.  We had 22 responses, which was probably not a sufficiently diverse sample, but nonetheless, we found useful insights.  The project continues to enjoy a generally positive impression, mostly unchanged from surveys in 2019 and 2021.  There are a larger number of people responding who found the project on the internet versus the connection to Mifos.org.  The domains covered by the production users covered digital wallets (70%), online lending (64%), payment accounts (60%),  traditional banking accounts (58%).  --> Survey Results 2022 November. 
  • In October we conducted an effort to close older issues. The decision was made by vote to close all issues that were older than 26 months and had no activity on them.  We ended up closing about 300 tickets but we still have a lot of stale issues.  2022-October-21: Jira Clean Up.  This remains an area of constructive dialog with some arguing to keep stale tickets visible.  
  • We began work on additional roadmap thinking in 2022, but have not completed this effort:  Roadmap Q4 2022 (PROPOSED) 
  • A more explicit Trademark policy was adopted: Fineract Trademarks Usage and Policy.   We communicated out the trademark policy on dev.  


## Community Health:

  • ApacheCON track 

PMC Chair  James Dailey


  • No labels