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 14, 2026, at 5:31 PM, Yash Goswami <[email protected]> wrote:
> 
> Hello Apache Fineract Team,
> 
> My name is Yash Goswami, and I am a B.Tech Computer Science student with a 
> strong interest in Java backend development.
> 
> I am excited to start contributing to Apache Fineract and become an active 
> member of the community. I am currently exploring the project, setting it up 
> locally, and understanding the codebase.
> 
> I would be grateful if you could guide me on a few points:
> 
> - Which issues would you recommend for a first-time contributor?
> - Are there any areas where contributors are currently needed?
> - Are there any contribution guidelines or coding practices that I should 
> follow beyond the official documentation?
> - Would someone be available to review my first pull request and provide 
> feedback?
> 
> My goal is to become a long-term contributor and continue learning through 
> real contributions. I also plan to participate in Google Summer of Code 
> (GSoC) in the future, so I would like to get involved with the project as 
> early as possible.
> 
> Thank you for your time and guidance. I look forward to contributing to 
> Apache Fineract.
> 
> Best regards,
> 
> Yash Goswami

Reply via email to