Hi Aleks, Thanks for the update. It’s good to know the fineract-command module is already upstream and that the focus is now on reaching the 20-module milestone.
Since the earlier description mentioned starting with non-critical modules like Document Management, which is now completed, I wanted to check which modules are currently unassigned and suitable to work on. >From my initial review I was considering *Staff* and *Search*. Are these good modules to focus on, or would you recommend a different set? Best Regards Nidhi On Fri, Mar 13, 2026 at 5:20 PM Aleksandar Vidakovic <[email protected]> wrote: > Hi Leonardo, > > ... the proper repository is [email protected]:apache/fineract.git ... the > other one is my private fork where I do my work... you don't need to > checkout "feature/FINERACT-2169", because that first phase of development > is already done (aka creating a standalone module that contains all > mechanics for the new command processing; see build module > "fineract-command" in the upstream Git repository. This is where you'll > find all the files you are looking for including the JMH tests. > > > https://github.com/apache/fineract/blob/develop/fineract-command/src/test/java/org/apache/fineract/command/CommandPipelineBenchmark.java > > The Jira ticket FINERACT-2169 is kind of a collection of 20 or so > sub-tasks/tickets... each ticket relates to a "module"/package/feature that > will be (or was already) migrated. We did already around 10. Our first > milestone is reaching 20. Overall we have approx. 50 or so > "modules"/packages that need to be migrated. We started to migrate in > "ascending" order in terms of complexity/impact/priority, means we started > to migrate very simple and non-critical packages first (caching, > configuration, document management, notes...). > > Maybe someone else can jump in and point Leonardo to that list of beginner > friendly tickets that is somewhere out there... > > Cheers, > > Aleks > > On Thu, Mar 12, 2026 at 11:34 PM Leonardo Alunno < > [email protected]> wrote: > >> Hi Aleksandar and the Fineract community, >> >> My name is Leonardo, and I'm a student interested in applying for GSoC >> 2026. I've been looking at the project ideas and I'm very interested in >> tackling the "New command processing infrastructure" project. I have a >> strong background in Java and I'm eager to work on modernizing the >> architecture with Spring Web MVC, DTOs, and the new >> synchronous/asynchronous/non-blocking execution models. >> >> I was reading through the project description and wanted to test the >> initial JMH smoke tests to get a better understanding of the baseline >> performance. I followed the instructions provided in the document: >> >> git clone [email protected]:vidakovic/fineract.git >> >> git checkout feature/FINERACT-2169 >> >> However, as mentioned in the description, it seems the branch is still in >> a private repository (or hasn't been published as a PR yet), so I wasn't >> able to check it out locally. >> >> Is there any chance the PR has been published under a different branch >> name, or would it be possible to get access to the prototype so I can start >> exploring the code and run the ./gradlew :fineract-command:jmh >> benchmarks? >> >> In the meantime, I've successfully set up the main Fineract repository >> locally and I'm looking for a "good first issue" to get familiar with the >> codebase. >> >> Looking forward to your guidance! >> >> Best regards, Leonardo >> >
