Dear newcomer, we kindly request that you begin your onboarding by reviewing our curated, helpful information here: https://issues.apache.org/jira/browse/FINERACT-2135
Every contribution that enhances the codebase’s safety, effectiveness, or readability is valuable! :) Depending on 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 for various reasons. I believe at least half of these warnings could be fixed relatively easily. As we work on resolving these warnings, the codebase becomes safer and easier to maintain. All remaining open 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 Beginner-friendly stories: 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! So my advice would be: don’t be afraid to get involved. The community is welcoming and friendly. Go ahead and get your feet wet freely: whether through documentation, testing, PR review, smaller fixes, code hygiene improvements, or identifying new issues as you become more familiar with the project. And of course, if you are unsure whether something is a good first contribution, feel free to ask in the channel. That is exactly what the community is there for. P.S. Before picking up a story that introduces a new feature, please send an email to the Fineract DEV mailing list first, so the community can discuss whether it is something we really want to include in Fineract. P.S.2: We have now Matrix room as well: https://matrix.to/#/%23apache-fineract-dev:matrix.org Regards, Adam > On Jul 16, 2026, at 3:52 AM, Kaushal Shriyan <[email protected]> wrote: > > Dear Apache Fineract Community, > > I am interested in contributing to the Apache Fineract project as an > open-source contributor. > > I have experience working with Linux, DevOps, cloud technologies, and > deploying Apache Fineract. While I am new to Java development, I am eager to > learn and contribute to the project. I believe contributing to Apache > Fineract will be an excellent way for me to improve my Java skills while > giving back to the community. > > I would appreciate your guidance on the following: > > * What Java topics should I focus on to become an effective Apache Fineract > contributor? > * Are there any beginner-friendly issues or “good first issues” that you > would recommend? > * Are there any coding standards, documentation, or contribution guides that > I should follow before submitting my first pull request? > * Are there any community meetings or mentoring opportunities for new > contributors? > > I am committed to learning and contributing consistently, and I look forward > to becoming an active member of the Apache Fineract community. > > Thank you for your time and guidance. > > Best regards, > > Kaushal
