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 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 S > On Sep 28, 2026, at 1:33 PM, Jay Sharma <[email protected]> wrote: > > Hi Apache Fineract Community, > I hope you’re all doing well. > My name is Jay Sharma, and I’m a Java Backend Developer. I’m writing to > introduce myself to the community as an active contributor. > A bit about my background: > My Tech Stack: Java (17/21), Spring Boot, Spring Security, RESTful APIs, > MySQL, and AWS. > My Experience: I have backend experience in building applications, handling > database migrations, and configuring cloud infrastructure. > My contributions so far: > I’ve already started diving into the codebase and recently fixed a validation > bug in the post-dated checks processing module (FINERACT-2805). The fix > involved correcting core parameter evaluation logic by switching > misreferenced field variables from this.accountNo to this.checkNo to ensure > database validation accuracy. I really appreciate the module maintainers who > collaborated with me to test and merge the code! > Why Fineract, availability & mentorship: > Fineract is my very first experience working with a financial system, and I’m > highly motivated to learn core banking architectures inside out. I am > currently able to dedicate most of my day to consistently contributing to the > project. > Since I have experience in backend development—including database layer > optimizations (HikariCP, query tuning, DTOs, Interface projections, etc) and > security configurations.I would love to challenge myself with mid-level > backend problems where I can add real value. I would welcome any guidance or > mentorship from experienced contributors on core components so I can get up > to speed quickly and maximize the impact of the time I'm putting in. > Where I hope to help out: > Given my active daily schedule and backend background, I’m eager to pick up > tasks related to: > Data validation, core transaction logic, and API optimization/latency bugs. > Backend enhancements across Spring Boot, Spring Security, or the database > migration layer. > I’m keeping a close eye on the mailing list and the Apache Fineract Jira > Board. Please let me know if there are specific modules, ongoing tasks, or > mid-level bugs where I can get started. > Looking forward to collaborating and building with you all! > Best regards, > Jay
