---------- Forwarded message --------- From: Eyad Sharkawy <[email protected]> Date: Tue, Nov 3, 2026 at 8:19 PM Subject: Re: GSoC 2027 Backend Roadmap and Architectural Priorities To: Ádám Sághy <[email protected]>
Hi Ádám, Thank you for the detailed breakdown and ideas! The proposal to *move calculations and extensive business logic out of entities into dedicated domain services* stands out the most to me. Having worked on interest rate overrides in FINERACT-848 <https://issues.apache.org/jira/browse/FINERACT-848>, I experienced firsthand how tightly coupled calculation logic is to entity state, and how separating them would dramatically improve unit testability and maintainability. I’ll focus my attention here - starting by analyzing SavingsAccount and related deposit entities to identify calculation boundaries that can be decoupled safely into stateless services. Thanks again for the guidance, and I look forward to drafting an architectural proposal around this! Best regards, Eyad Sharkawy On Tue, Nov 3, 2026 at 2:11 PM Ádám Sághy <[email protected]> wrote: > Dear newcomer, > > we kindly request that you begin your onboarding by reviewing our curated, > helpful information under this link: > https://issues.apache.org/jira/browse/FINERACT-2135 > > Every contribution that enhances the codebase’s safety, effectiveness, or > readability is valuable! :) > > Considering your availability and willingness to contribute, there are > several areas where improvements are needed: > > Bug tickets > > https://issues.apache.org/jira/browse/FINERACT-2492?filter=-1&jql=project%20%3D%20%22Apache%20Fineract%22%20%20AND%20type%20%3D%20Bug%20%20%20AND%20resolution%20%3D%20Unresolved%20order%20by%20created%20DESC > > > Code maintainability / readability > We have a significant number of compilation warnings due to various > reasons. I believe at least half of these warnings could be easily fixed. > As we work on resolving these warnings, the codebase could become safer and > easier to maintain. > > All the rest of the stories > > https://issues.apache.org/jira/browse/FINERACT-2494?filter=-1&jql=project%20%3D%20%22Apache%20Fineract%22%20%20AND%20resolution%20%3D%20Unresolved%20order%20by%20created%20DESC > > > All the rest of the stories that are considered beginner friendly > > https://issues.apache.org/jira/browse/FINERACT-2489?filter=-1&jql=project%20%3D%20%22Apache%20Fineract%22%20and%20labels%20IN%20(beginner-friendly%2C%20beginner%2C%20begineer%2C%20beginners%2C%20Beginner)%20%20AND%20resolution%20%3D%20Unresolved%20order%20by%20created%20DESC > > And some of my ideas: > > I would say the below items would make our codebase better and serve the > community: > - modularisation: we started the work but many things are not at the righ > place still (loans, savings, core, charges,...). originally we had 1 module > (fineract-provider) and contained everything. now we have many modules but > still loan related stuff can be found in provider, core, etc. we should > move out as much from the provider as possible (loan related stuffs goes > into fineract-loan, fineract-progressive-loan or fineract-working-capital, > etc) For that we need to split services, introduce interfaces and so on... > so its not small task but can be really rewarding > > - if you are looking something smaller: split huge services into smaller > pieces based on functionality its providing. > > - moving calculations and extensive logic out of entities (entity should > contains only the logic to change its internal state) > > - Moving away from explicitly serializing the returning object to String > in the *ApiResource.java files (controller classes) > > > Hopefully, this gives you some ideas! > > P.S.: Before you pick up a story that describes a new feature to be > introduced, please send an email to the Fineract DEV email list to discuss > whether it’s something we really want to include in Fineract. > > Regards, > Adam > > > On Oct 30, 2026, at 9:54 AM, Eyad Sharkawy <[email protected]> > wrote: > > Hi everyone, > > My name is Eyad, and I am a thrid-year CS student looking to participate > in Google Summer of Code 2027 with Apache Fineract. > > Over the last few months, I have been familiarizing myself with the > Fineract backend and recently implemented FINERACT-848 > <https://issues.apache.org/jira/browse/FINERACT-848> (custom interest > rate overrides for deposit accounts - PR #6405 > <https://github.com/apache/fineract/pull/6405>) alongside its frontend UI > in the Mifos web-app (WEB-1358 > <https://mifosforge.jira.com/browse/WEB-1358>, PR #4169 > <https://github.com/openMF/web-app/pull/4169>). This gave me some great > exposure to the core calculation engine, database migrations, and domain > logic. > > Since the official GSoC 2027 ideas list isn't published yet, I wanted to > reach out to the community early. Are there any specific backend epics, > architectural modernization efforts, or roadmap priorities the core team is > currently focusing on? I would love to start researching those areas and > contributing to related tickets to build a strong foundation before > proposal season begins. > > Thank you for your time and guidance! > > Best regards, > > Eyad Sharkawy > > GitHub: Eyad-Sharkawy <https://github.com/Eyad-Sharkawy> > > >
