• Created by Unknown User (jdailey), last updated on Jan 07, 2025 3 minute read 
## Description:
The mission of Apache Fineract is the creation and maintenance of software 
related to a core banking platform that provides a reliable, robust, and 
affordable solution for entrepreneurs, financial institutions, and service 
providers to offer financial services to the world's underbanked and unbanked.

## Project Status:
Current project status: Stable. 
Issues for the board: Nothing urgent to highlight.  

## Membership Data:
Apache Fineract was founded 2017-04-18 (8 years ago) There are currently 54
committers and 24 PMC members in this project. The Committer-to-PMC ratio ~
2:1 if the math is right.

Community changes, past quarter:
- No new PMC members. Last addition was Adam Saghy on 2023-07-10.
- Marta Jankovics was added as committer on 2024-10-14

## Project Activity:
1.10.1 was released on 2024-12-31.
1.9.0 was released on 2024-01-12.

## Community Health:
A drop in listserv traffic is probably indicative of better help available
from outside resources, including the newly launched Fineract-Academy.com by
PMC member Adam Saggy.  This was approved by the PMC.

Message from PMC chair Dec 31st, 2-24: 
https://lists.apache.org/thread/1799o3xx9n6f9nmxfqkryjcf2cdqslb7 Today, our
software is in use in organizations large and small around the world, reaching
- according to some vendors - at least 65 million end users, and by dozens of
vendors and maybe hundreds of direct providers.  I suspect this under-counts
our use...and impact.

Some highlights and things to do:  In 2024, we reworked the docker hub target
and got that working again.  We continue to see a lot of downloads there.

We released 1.9.0 in January 2024, version 1.10.1 on Dec 31st, 2024.

In 2025, we intend to make the release process easier such that this can
happen more frequently.

As part of this we may decide (after discussion) to do away with back porting
of security patches and only have one official current release.  If you want
to earn karma by back porting recent security fixes or have an issue to
report, send to security @ Fineract .apache.org

In 2025, I'd also like to propose the following:
* Readme and asciidoc documentation is improved and versioned with each
  release, with wiki content streamlined to project management.
* Builds improvements as discussed in this dev thread
  https://lists.apache.org/thread/9l46b7p6bxt7c475o94wrg3k2wc54zdv
* Progress on each of the FSIPs as outlined at https://cwiki.apach
  e.org/confluence/display/FINERACT/Fineract+Significant+Improvement+Proposals

In a virtuous cycle of innovation, we continue to need the "roadmap" of items
like those on the FSIPs as well as a set of "anti-roadmap" items, aka much
later priority roadmap items. The roadmap is defined by the community not by
any one Vendor, but contributions drive that roadmap. We have to ask “what is
being planned?” Or “what would you like to add?” And discuss.

Our assumed anti-roadmap currently includes "we will not embed complex
reporting" and "we will not build the front end", as it is useful in defining
where outside users and vendors can develop additional value-adds with some
predictability.

The philosophy of commercial open source requires companies ("vendors") making
money such that they can contribute to the core code, and always exist
upstream on the codebase because it is strategic for them.

"You get what you develop, you get what they develop, you get what everyone
 develops."  In terms of patterns, as has been pointed out recently, we need
 to push back on "Endless feature expansion".  We don't do a good job of
 pruning features, which makes the process of development more complex than it
 needs to be. We may need a more frank discussion in 2025 about backwards
 compatibility and feature limitations.
+1 on "look left and right" when touching the code. We should make sure that
 we develop cleanly and with sufficient documentation and consistency.  More
 eyeballs are needed on the reviews.  Subscribe to the feed and start
 following.  In 2025, we should clear out old jira tickets and focus on the
 real needs and errors of today. Is this something you can help with?

Full end of 2024 message is here ==> 
https://lists.apache.org/thread/1799o3xx9n6f9nmxfqkryjcf2cdqslb7



  • No labels