Hello @Georgi Kolev, Please read the reply that I have just sent to Arnav.
"One line of code at a time" you should focus your initial contribution efforts on writing small, functional pieces of code and then gradually you will see progress in all your skills (experience) Regards Victor Romero El dom, 4 ene 2026 a las 9:01, Georgi Kolev (<[email protected]>) escribió: > Hi everyone, > > My name is Georgi Kolev and I am a university student interested in > backend development, particularly in financial technology systems. I > recently subscribed to this mailing list, and I’m excited to start > contributing to Apache Fineract. > > I have experience with Java and working with backend APIs, and I’d like to > begin by picking an open issue and working on it. Before I do that, I > wanted to confirm the right process: > > - > > Once I choose an issue, do I need to let someone know that I’m working > on it (for example by replying on the issue tracker), or is it fine to just > start working and open a PR when it’s ready? > - > > Is there anything I should read or complete before starting on my > first issue (developer guides, contribution rules, coding standards, etc.)? > - > > If I get stuck while working on an issue, is this mailing list the > best place to ask questions, or should I also try to join the Slack > community? I noticed that Slack requires an invite — please let me know the > best way to request one. > > My goal is to start with something small, learn the codebase, and then > tackle more complex issues. Any guidance on good first backend areas to > explore would also be much appreciated. > > Thanks, and I’m looking forward to working with you all. > > Best regards, > Georgi Kolev >
