You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Akash Nadar <ak...@gmail.com> on 2024/11/24 07:38:28 UTC

Guidance Request for Contribution to Apache Fineract

Hi everyone,

I’m Akash, a new contributor to Apache Fineract. I have experience with
Java, Spring Boot, and building REST APIs. I’ve successfully set up the
project locally, including database connections, and have explored the
Swagger documentation.

I couldn’t find any "good first issues" or beginner-friendly tasks on the
GitHub Issues page. Could someone please suggest a task or guide me on how
I can get started with my first contribution? I’m particularly interested
in working on APIs or improving existing features.

Looking forward to your guidance!

Thanks and regards,
Akash

Re: Guidance Request for Contribution to Apache Fineract

Posted by Mark Salter <ma...@protonmail.com.INVALID>.
Outdoor interest and for future starters are you able to share what was wrong
and how you got it going?

\--  
Mark Salter

  
  
\-------- Original Message --------  
On 29/11/2024 03:59, Oluwafemi Oluwatuyi  wrote:  

> Hi,
>
> I was able to identify the issue. It's working now.
>
> Thanks!
>
>  
>
>
> On Thu, Nov 28, 2024, 9:25 PM Oluwafemi Oluwatuyi
> <[oluwafemioluwatuyi8@gmail.com](mailto:oluwafemioluwatuyi8@gmail.com)>
> wrote:  
>
>

>> Hi Akash Nadar,  
> Thanks! It is working now.  
>  
> But the issue I am facing now is testing the endpoints. Most of the errors I
> am getting are similar to the attached file below.
>>

>>  
>
>>

>>  
>
>>

>> On Wed, Nov 27, 2024 at 4:23 PM Akash Nadar
<[akashnadar14@gmail.com](mailto:akashnadar14@gmail.com)> wrote:  
>
>>

>>> Hi Oluwafemi,

>>>

>>> Follow this below given documentation , this helped me to set up the
project locally .

>>>

>>>  
>
>>>

>>> <https://fineract-academy.com/how-to-build-fineract-with-intellij-
idea.html>  
>
>>>

>>>  
>
>>>

>>> Thanks and Regards,

>>>

>>> Akash  
>
>>>

>>>  
>
>>>

>>> On Wed, Nov 27, 2024 at 6:30 PM Oluwafemi Oluwatuyi
<[oluwafemioluwatuyi8@gmail.com](mailto:oluwafemioluwatuyi8@gmail.com)> wrote:  
>
>>>

>>>> Hi,

>>>>

>>>> I'm experiencing an issue with my Gradle build, where it gets stuck at
98% when I run the command `./gradlew bootRun`, the build process gets stuck
at 98%. I've tried:

>>>>

>>>> -Cleaning and rebuilding the project,  
>  -Checking for any errors or warnings in the build output
>>>>

>>>> However, none of these solutions have worked. I'd greatly appreciate any
guidance or advice on how to resolve this issue.

>>>>

>>>> Thanks in advance for your help.  
>
>>>>

>>>>  
>
>>>>

>>>> On Tue, Nov 26, 2024, 4:26 PM James Dailey
<[jdailey@apache.org](mailto:jdailey@apache.org)> wrote:  
>
>>>>

>>>>> As a reminder, this is a public listserv that goes to many hundreds of
people globally.

>>>>>

>>>>> It is archived and searchable - for example, this thread is found at:

>>>>>

>>>>> <https://lists.apache.org/thread/q2o2lsghj2rr4plnwk7747gs9smf925k>

>>>>>

>>>>>  
>
>>>>>

>>>>> Please note.

>>>>>

>>>>>  
>
>>>>>

>>>>> I probably would encourage you to contact each other privately and
perhaps use discord or slack for side conversations.

>>>>>

>>>>>  
>
>>>>>

>>>>>  
>
>>>>>

>>>>>  
>
>>>>>

>>>>> On Tue, Nov 26, 2024 at 7:13 AM Oluwafemi Oluwatuyi
<[oluwafemioluwatuyi8@gmail.com](mailto:oluwafemioluwatuyi8@gmail.com)> wrote:  
>
>>>>>

>>>>>> Hello Akash and Sarthak,

>>>>>>

>>>>>> I also want to be part of this. I have sent a friend request @sarthak
via LinkedIn.

>>>>>>

>>>>>> Below is my social profile

>>>>>>

>>>>>> <https://www.linkedin.com/in/oluwafemioluwatuyi>

>>>>>>

>>>>>> Best regards,  
>  Oluwafemi  
>
>>>>>>

>>>>>>  
>
>>>>>>

>>>>>> On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar
<[deokarsarthak05@gmail.com](mailto:deokarsarthak05@gmail.com)> wrote:  
>
>>>>>>

>>>>>>> Hello Akash,  
>  
> here are my social profiles  
>  
>
>>>>>>>

>>>>>>> Regards,

>>>>>>>

>>>>>>> Sarthak Deokar

>>>>>>>

>>>>>>>  
>
>>>>>>>

>>>>>>> Linkdin

>>>>>>>

>>>>>>>  
>
>>>>>>>

>>>>>>> <https://www.linkedin.com/in/sarthak-deokar/>

>>>>>>>

>>>>>>>  
>
>>>>>>>

>>>>>>> Instagram

>>>>>>>

>>>>>>>  
>
>>>>>>>

>>>>>>>
<https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6>

>>>>>>>

>>>>>>>  
>
>>>>>>>

>>>>>>>  
>
>>>>>>>

>>>>>>> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar
<[akashnadar14@gmail.com](mailto:akashnadar14@gmail.com)> wrote:  
>
>>>>>>>

>>>>>>>> Hi James and Sarthak,  
>  
> Thank you for the detailed guidance and warm welcome!  
>  
> James, I’ll start by reviewing existing PRs and validating old Jira tickets
> to familiarize myself with the project. I’ll also explore areas for
> documentation and test coverage improvements. Your suggestions are very
> helpful!  
>  
> Sarthak, let’s connect and collaborate on these tasks together. We can
> divide work or brainstorm how to approach it. Let me know how you’d like to
> proceed.  
>  
> Thanks,  
> Akash  
>
>>>>>>>>

>>>>>>>>  
>
>>>>>>>>

>>>>>>>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala
<[mandalavijaysuryaopensource@gmail.com](mailto:mandalavijaysuryaopensource@gmail.com)>
wrote:  
>
>>>>>>>>

>>>>>>>>> Hey James,  
>  
>  Thank you for sharing these "first-steps" to contribute to this  
>  project. Although I wasn’t directly tagged in this email, I greatly  
>  appreciate the steps you’ve outlined for understanding the codebase  
>  and contributing meaningfully.  
>  Your advice is incredibly helpful for someone like me who is eager to  
>  contribute effectively.  
>  
>  -Vijay  
>  
>  
>  On Mon, Nov 25, 2024 at 4:20 AM James Dailey
> <[jdailey@apache.org](mailto:jdailey@apache.org)> wrote:  
>  >  
>  > Akash and Sarthak - thanks for your interest and welcome.  
>  >  
>  > Because Fineract is a large code base used in production at regulated
> financial institutions, it is essential that new contributors start with
> understanding the code base rather than trying to add new features.  
>  > There is a tendency for devs to want to do the "next cool thing" when
> really what is needed is more documentation, more test coverage, more
> detailed tickets, more reviews of changes.  
>  >  
>  > As a first step, you can review the existing PRs that are coming in. Do
> they make sense to you? Can you follow the logic? Are the details in the
> Jira ticket sufficient? You might want to try that for a week or two or
> five.  
>  > Following project activity is a very important first step. You might even
> have some clarifying questions that could help the project become better.
> That is also a contribution.  
>  >  
>  > Secondly, look for areas that are not well covered. On many open source
> projects, too many devs are writing too much code with too little
> documentation. That is true here as well. Once you understand the features
> and functions and the structure of the code, can you help with some small
> piece of documentation? ... we need people digging into specific areas that
> are in the code and documenting what is there. That might also involve more
> test coverage in Cucumber (Gherkin files).  
>  >  
>  > Third, you might look at the really old jira tickets, and validate one by
> one that the tickets are still needing to be fixed. We have hundreds of old
> tickets that have creation dates before 2022 and I strongly suspect 90% are
> no longer valid. This is tedious work, but is needed. Pick a ticket, read
> it, determine if it seems real, put a comment that "yes, verified as of
> github checkpoint xxxx-xxxx" that the issue still exists" or "no, verified
> as of ... that the bug ticket is no longer valid".  
>  >  
>  > Generally, contributors should come with very modest aims at first. This
> is a very complex project.  
>  >  
>  > James  
>  >  
>  > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar
> <[deokarsarthak05@gmail.com](mailto:deokarsarthak05@gmail.com)> wrote:  
>  >>  
>  >> Hi,  
>  >>  
>  >> I am also suffering the same issues hope we could connect and work
> together  
>  >>  
>  >> Regards,  
>  >> Sarthak Deokar  
>  >>  
>  >> On Sun, Nov 24, 2024, 13:08 Akash Nadar
> <[akashnadar14@gmail.com](mailto:akashnadar14@gmail.com)> wrote:  
>  >>>  
>  >>> Hi everyone,  
>  >>>  
>  >>> I’m Akash, a new contributor to Apache Fineract. I have experience with
> Java, Spring Boot, and building REST APIs. I’ve successfully set up the
> project locally, including database connections, and have explored the
> Swagger documentation.  
>  >>>  
>  >>> I couldn’t find any "good first issues" or beginner-friendly tasks on
> the GitHub Issues page. Could someone please suggest a task or guide me on
> how I can get started with my first contribution? I’m particularly
> interested in working on APIs or improving existing features.  
>  >>>  
>  >>> Looking forward to your guidance!  
>  >>>  
>  >>> Thanks and regards,  
>  >>> Akash  
>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Oluwafemi Oluwatuyi <ol...@gmail.com>.
Hi James,

Thanks! I will consult those resources for better understanding.

On Fri, Dec 6, 2024 at 2:58 AM James Dailey <ja...@gmail.com> wrote:

> Those APIs will be Deprecated
>
> https://cwiki.apache.org/confluence/display/FINERACT/Securing+Fineract
>
> https://lists.apache.org/thread/rrmvywcd1qrgnmyp93ngo9ozxgol76yg
>
>
>
> On Thu, Dec 5, 2024 at 12:11 AM Oluwafemi Oluwatuyi <
> oluwafemioluwatuyi8@gmail.com> wrote:
>
>> Hi,
>>
>> I’m facing an issue with the self-service API endpoints. While
>> self-authorization is working correctly, the following endpoints are
>> returning an "Unauthorized" error:
>>
>>    - /self/userdetails
>>    - /self/loans
>>    - /self/savingsaccounts
>>
>> I have verified that the user credentials are correct and authentication
>> is properly configured. However, the endpoints remain inaccessible.
>>
>> Below is the attached screenshot of one of the responses I got.
>>
>>
>>
>> On Thu, Nov 28, 2024 at 11:29 PM Oluwafemi Oluwatuyi <
>> oluwafemioluwatuyi8@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I was able to identify the issue. It's working now.
>>>
>>> Thanks!
>>>
>>> On Thu, Nov 28, 2024, 9:25 PM Oluwafemi Oluwatuyi <
>>> oluwafemioluwatuyi8@gmail.com> wrote:
>>>
>>>> Hi Akash Nadar,
>>>> Thanks! It is working now.
>>>>
>>>> But the issue I am facing now is testing the endpoints. Most of the
>>>> errors I am getting are similar to the attached file below.
>>>>
>>>>
>>>> On Wed, Nov 27, 2024 at 4:23 PM Akash Nadar <ak...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Oluwafemi,
>>>>> Follow this below given documentation , this helped me to set up the
>>>>> project locally .
>>>>>
>>>>>
>>>>> https://fineract-academy.com/how-to-build-fineract-with-intellij-idea.html
>>>>>
>>>>> Thanks and Regards,
>>>>> Akash
>>>>>
>>>>> On Wed, Nov 27, 2024 at 6:30 PM Oluwafemi Oluwatuyi <
>>>>> oluwafemioluwatuyi8@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I'm experiencing an issue with my Gradle build, where it gets stuck
>>>>>> at 98% when I run the command `./gradlew bootRun`, the build process gets
>>>>>> stuck at 98%. I've tried:
>>>>>>
>>>>>> -Cleaning and rebuilding the project,
>>>>>> -Checking for any errors or warnings in the build output
>>>>>>
>>>>>> However, none of these solutions have worked. I'd greatly appreciate
>>>>>> any guidance or advice on how to resolve this issue.
>>>>>>
>>>>>> Thanks in advance for your help.
>>>>>>
>>>>>> On Tue, Nov 26, 2024, 4:26 PM James Dailey <jd...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> As a reminder, this is a public listserv that goes to many hundreds
>>>>>>> of people globally.
>>>>>>> It is archived and searchable - for example, this thread is found
>>>>>>> at:
>>>>>>> https://lists.apache.org/thread/q2o2lsghj2rr4plnwk7747gs9smf925k
>>>>>>>
>>>>>>> Please note.
>>>>>>>
>>>>>>> I probably would encourage you to contact each other privately and
>>>>>>> perhaps use discord or slack for side conversations.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Nov 26, 2024 at 7:13 AM Oluwafemi Oluwatuyi <
>>>>>>> oluwafemioluwatuyi8@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hello Akash and Sarthak,
>>>>>>>>
>>>>>>>> I also want to be part of this. I have sent a friend request
>>>>>>>> @sarthak via LinkedIn.
>>>>>>>>
>>>>>>>> Below is my social profile
>>>>>>>>
>>>>>>>> https://www.linkedin.com/in/oluwafemioluwatuyi
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Oluwafemi
>>>>>>>>
>>>>>>>> On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar <
>>>>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hello Akash,
>>>>>>>>>
>>>>>>>>> here are my social profiles
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Sarthak Deokar
>>>>>>>>>
>>>>>>>>> Linkdin
>>>>>>>>>
>>>>>>>>> https://www.linkedin.com/in/sarthak-deokar/
>>>>>>>>>
>>>>>>>>> Instagram
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <
>>>>>>>>> akashnadar14@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi James and Sarthak,
>>>>>>>>>>
>>>>>>>>>> Thank you for the detailed guidance and warm welcome!
>>>>>>>>>>
>>>>>>>>>> James, I’ll start by reviewing existing PRs and validating old
>>>>>>>>>> Jira tickets to familiarize myself with the project. I’ll also explore
>>>>>>>>>> areas for documentation and test coverage improvements. Your suggestions
>>>>>>>>>> are very helpful!
>>>>>>>>>>
>>>>>>>>>> Sarthak, let’s connect and collaborate on these tasks together.
>>>>>>>>>> We can divide work or brainstorm how to approach it. Let me know how you’d
>>>>>>>>>> like to proceed.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Akash
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
>>>>>>>>>> mandalavijaysuryaopensource@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hey James,
>>>>>>>>>>>
>>>>>>>>>>> Thank you for sharing these "first-steps" to contribute to this
>>>>>>>>>>> project. Although I wasn’t directly tagged in this email, I
>>>>>>>>>>> greatly
>>>>>>>>>>> appreciate the steps you’ve outlined for understanding the
>>>>>>>>>>> codebase
>>>>>>>>>>> and contributing meaningfully.
>>>>>>>>>>> Your advice is incredibly helpful for someone like me who is
>>>>>>>>>>> eager to
>>>>>>>>>>> contribute effectively.
>>>>>>>>>>>
>>>>>>>>>>> -Vijay
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>> >
>>>>>>>>>>> > Akash and Sarthak - thanks for your interest and welcome.
>>>>>>>>>>> >
>>>>>>>>>>> > Because Fineract is a large code base used in production at
>>>>>>>>>>> regulated financial institutions, it is essential that new contributors
>>>>>>>>>>> start with understanding the code base rather than trying to add new
>>>>>>>>>>> features.
>>>>>>>>>>> > There is a tendency for devs to want to do the "next cool
>>>>>>>>>>> thing" when really what is needed is more documentation, more test
>>>>>>>>>>> coverage, more detailed tickets, more reviews of changes.
>>>>>>>>>>> >
>>>>>>>>>>> > As a first step, you can review the existing PRs that are
>>>>>>>>>>> coming in.  Do they make sense to you?   Can you follow the logic?  Are the
>>>>>>>>>>> details in the Jira ticket sufficient?   You might want to try that for a
>>>>>>>>>>> week or two or five.
>>>>>>>>>>> > Following project activity is a very important first step.
>>>>>>>>>>> You might even have some clarifying questions that could help the project
>>>>>>>>>>> become better.  That is also a contribution.
>>>>>>>>>>> >
>>>>>>>>>>> > Secondly, look for areas that are not well covered.  On many
>>>>>>>>>>> open source projects, too many devs are writing too much code with too
>>>>>>>>>>> little documentation.  That is true here as well.  Once you understand the
>>>>>>>>>>> features and functions and the structure of the code, can you help with
>>>>>>>>>>> some small piece of documentation?   ... we need people digging into
>>>>>>>>>>> specific areas that are in the code and documenting what is there.  That
>>>>>>>>>>> might also involve more test coverage in Cucumber (Gherkin files).
>>>>>>>>>>> >
>>>>>>>>>>> > Third, you might  look at the really old jira tickets, and
>>>>>>>>>>> validate one by one that the tickets are still needing to be fixed.  We
>>>>>>>>>>> have hundreds of old tickets that have creation dates before 2022 and I
>>>>>>>>>>> strongly suspect 90% are no longer valid.  This is tedious work, but is
>>>>>>>>>>> needed.  Pick a ticket, read it, determine if it seems real, put a comment
>>>>>>>>>>> that "yes, verified as of github checkpoint xxxx-xxxx" that the issue still
>>>>>>>>>>> exists" or "no, verified as of ... that the bug ticket is no longer valid".
>>>>>>>>>>> >
>>>>>>>>>>> > Generally, contributors should come with very modest aims at
>>>>>>>>>>> first.  This is a very complex project.
>>>>>>>>>>> >
>>>>>>>>>>> > James
>>>>>>>>>>> >
>>>>>>>>>>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>>>>>>>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>>>>>>> >>
>>>>>>>>>>> >> Hi,
>>>>>>>>>>> >>
>>>>>>>>>>> >> I am also suffering the same issues hope we could connect and
>>>>>>>>>>> work together
>>>>>>>>>>> >>
>>>>>>>>>>> >> Regards,
>>>>>>>>>>> >> Sarthak Deokar
>>>>>>>>>>> >>
>>>>>>>>>>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <
>>>>>>>>>>> akashnadar14@gmail.com> wrote:
>>>>>>>>>>> >>>
>>>>>>>>>>> >>> Hi everyone,
>>>>>>>>>>> >>>
>>>>>>>>>>> >>> I’m Akash, a new contributor to Apache Fineract. I have
>>>>>>>>>>> experience with Java, Spring Boot, and building REST APIs. I’ve
>>>>>>>>>>> successfully set up the project locally, including database connections,
>>>>>>>>>>> and have explored the Swagger documentation.
>>>>>>>>>>> >>>
>>>>>>>>>>> >>> I couldn’t find any "good first issues" or beginner-friendly
>>>>>>>>>>> tasks on the GitHub Issues page. Could someone please suggest a task or
>>>>>>>>>>> guide me on how I can get started with my first contribution? I’m
>>>>>>>>>>> particularly interested in working on APIs or improving existing features.
>>>>>>>>>>> >>>
>>>>>>>>>>> >>> Looking forward to your guidance!
>>>>>>>>>>> >>>
>>>>>>>>>>> >>> Thanks and regards,
>>>>>>>>>>> >>> Akash
>>>>>>>>>>>
>>>>>>>>>>

Re: Guidance Request for Contribution to Apache Fineract

Posted by James Dailey <ja...@gmail.com>.
Those APIs will be Deprecated

https://cwiki.apache.org/confluence/display/FINERACT/Securing+Fineract

https://lists.apache.org/thread/rrmvywcd1qrgnmyp93ngo9ozxgol76yg



On Thu, Dec 5, 2024 at 12:11 AM Oluwafemi Oluwatuyi <
oluwafemioluwatuyi8@gmail.com> wrote:

> Hi,
>
> I’m facing an issue with the self-service API endpoints. While
> self-authorization is working correctly, the following endpoints are
> returning an "Unauthorized" error:
>
>    - /self/userdetails
>    - /self/loans
>    - /self/savingsaccounts
>
> I have verified that the user credentials are correct and authentication
> is properly configured. However, the endpoints remain inaccessible.
>
> Below is the attached screenshot of one of the responses I got.
>
>
>
> On Thu, Nov 28, 2024 at 11:29 PM Oluwafemi Oluwatuyi <
> oluwafemioluwatuyi8@gmail.com> wrote:
>
>> Hi,
>>
>> I was able to identify the issue. It's working now.
>>
>> Thanks!
>>
>> On Thu, Nov 28, 2024, 9:25 PM Oluwafemi Oluwatuyi <
>> oluwafemioluwatuyi8@gmail.com> wrote:
>>
>>> Hi Akash Nadar,
>>> Thanks! It is working now.
>>>
>>> But the issue I am facing now is testing the endpoints. Most of the
>>> errors I am getting are similar to the attached file below.
>>>
>>>
>>> On Wed, Nov 27, 2024 at 4:23 PM Akash Nadar <ak...@gmail.com>
>>> wrote:
>>>
>>>> Hi Oluwafemi,
>>>> Follow this below given documentation , this helped me to set up the
>>>> project locally .
>>>>
>>>>
>>>> https://fineract-academy.com/how-to-build-fineract-with-intellij-idea.html
>>>>
>>>> Thanks and Regards,
>>>> Akash
>>>>
>>>> On Wed, Nov 27, 2024 at 6:30 PM Oluwafemi Oluwatuyi <
>>>> oluwafemioluwatuyi8@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I'm experiencing an issue with my Gradle build, where it gets stuck at
>>>>> 98% when I run the command `./gradlew bootRun`, the build process gets
>>>>> stuck at 98%. I've tried:
>>>>>
>>>>> -Cleaning and rebuilding the project,
>>>>> -Checking for any errors or warnings in the build output
>>>>>
>>>>> However, none of these solutions have worked. I'd greatly appreciate
>>>>> any guidance or advice on how to resolve this issue.
>>>>>
>>>>> Thanks in advance for your help.
>>>>>
>>>>> On Tue, Nov 26, 2024, 4:26 PM James Dailey <jd...@apache.org> wrote:
>>>>>
>>>>>> As a reminder, this is a public listserv that goes to many hundreds
>>>>>> of people globally.
>>>>>> It is archived and searchable - for example, this thread is found at:
>>>>>> https://lists.apache.org/thread/q2o2lsghj2rr4plnwk7747gs9smf925k
>>>>>>
>>>>>> Please note.
>>>>>>
>>>>>> I probably would encourage you to contact each other privately and
>>>>>> perhaps use discord or slack for side conversations.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Nov 26, 2024 at 7:13 AM Oluwafemi Oluwatuyi <
>>>>>> oluwafemioluwatuyi8@gmail.com> wrote:
>>>>>>
>>>>>>> Hello Akash and Sarthak,
>>>>>>>
>>>>>>> I also want to be part of this. I have sent a friend request
>>>>>>> @sarthak via LinkedIn.
>>>>>>>
>>>>>>> Below is my social profile
>>>>>>>
>>>>>>> https://www.linkedin.com/in/oluwafemioluwatuyi
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Oluwafemi
>>>>>>>
>>>>>>> On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar <
>>>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hello Akash,
>>>>>>>>
>>>>>>>> here are my social profiles
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Sarthak Deokar
>>>>>>>>
>>>>>>>> Linkdin
>>>>>>>>
>>>>>>>> https://www.linkedin.com/in/sarthak-deokar/
>>>>>>>>
>>>>>>>> Instagram
>>>>>>>>
>>>>>>>>
>>>>>>>> https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <
>>>>>>>> akashnadar14@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi James and Sarthak,
>>>>>>>>>
>>>>>>>>> Thank you for the detailed guidance and warm welcome!
>>>>>>>>>
>>>>>>>>> James, I’ll start by reviewing existing PRs and validating old
>>>>>>>>> Jira tickets to familiarize myself with the project. I’ll also explore
>>>>>>>>> areas for documentation and test coverage improvements. Your suggestions
>>>>>>>>> are very helpful!
>>>>>>>>>
>>>>>>>>> Sarthak, let’s connect and collaborate on these tasks together. We
>>>>>>>>> can divide work or brainstorm how to approach it. Let me know how you’d
>>>>>>>>> like to proceed.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Akash
>>>>>>>>>
>>>>>>>>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
>>>>>>>>> mandalavijaysuryaopensource@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hey James,
>>>>>>>>>>
>>>>>>>>>> Thank you for sharing these "first-steps" to contribute to this
>>>>>>>>>> project. Although I wasn’t directly tagged in this email, I
>>>>>>>>>> greatly
>>>>>>>>>> appreciate the steps you’ve outlined for understanding the
>>>>>>>>>> codebase
>>>>>>>>>> and contributing meaningfully.
>>>>>>>>>> Your advice is incredibly helpful for someone like me who is
>>>>>>>>>> eager to
>>>>>>>>>> contribute effectively.
>>>>>>>>>>
>>>>>>>>>> -Vijay
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>> >
>>>>>>>>>> > Akash and Sarthak - thanks for your interest and welcome.
>>>>>>>>>> >
>>>>>>>>>> > Because Fineract is a large code base used in production at
>>>>>>>>>> regulated financial institutions, it is essential that new contributors
>>>>>>>>>> start with understanding the code base rather than trying to add new
>>>>>>>>>> features.
>>>>>>>>>> > There is a tendency for devs to want to do the "next cool
>>>>>>>>>> thing" when really what is needed is more documentation, more test
>>>>>>>>>> coverage, more detailed tickets, more reviews of changes.
>>>>>>>>>> >
>>>>>>>>>> > As a first step, you can review the existing PRs that are
>>>>>>>>>> coming in.  Do they make sense to you?   Can you follow the logic?  Are the
>>>>>>>>>> details in the Jira ticket sufficient?   You might want to try that for a
>>>>>>>>>> week or two or five.
>>>>>>>>>> > Following project activity is a very important first step.  You
>>>>>>>>>> might even have some clarifying questions that could help the project
>>>>>>>>>> become better.  That is also a contribution.
>>>>>>>>>> >
>>>>>>>>>> > Secondly, look for areas that are not well covered.  On many
>>>>>>>>>> open source projects, too many devs are writing too much code with too
>>>>>>>>>> little documentation.  That is true here as well.  Once you understand the
>>>>>>>>>> features and functions and the structure of the code, can you help with
>>>>>>>>>> some small piece of documentation?   ... we need people digging into
>>>>>>>>>> specific areas that are in the code and documenting what is there.  That
>>>>>>>>>> might also involve more test coverage in Cucumber (Gherkin files).
>>>>>>>>>> >
>>>>>>>>>> > Third, you might  look at the really old jira tickets, and
>>>>>>>>>> validate one by one that the tickets are still needing to be fixed.  We
>>>>>>>>>> have hundreds of old tickets that have creation dates before 2022 and I
>>>>>>>>>> strongly suspect 90% are no longer valid.  This is tedious work, but is
>>>>>>>>>> needed.  Pick a ticket, read it, determine if it seems real, put a comment
>>>>>>>>>> that "yes, verified as of github checkpoint xxxx-xxxx" that the issue still
>>>>>>>>>> exists" or "no, verified as of ... that the bug ticket is no longer valid".
>>>>>>>>>> >
>>>>>>>>>> > Generally, contributors should come with very modest aims at
>>>>>>>>>> first.  This is a very complex project.
>>>>>>>>>> >
>>>>>>>>>> > James
>>>>>>>>>> >
>>>>>>>>>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>>>>>>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>>>>>> >>
>>>>>>>>>> >> Hi,
>>>>>>>>>> >>
>>>>>>>>>> >> I am also suffering the same issues hope we could connect and
>>>>>>>>>> work together
>>>>>>>>>> >>
>>>>>>>>>> >> Regards,
>>>>>>>>>> >> Sarthak Deokar
>>>>>>>>>> >>
>>>>>>>>>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <
>>>>>>>>>> akashnadar14@gmail.com> wrote:
>>>>>>>>>> >>>
>>>>>>>>>> >>> Hi everyone,
>>>>>>>>>> >>>
>>>>>>>>>> >>> I’m Akash, a new contributor to Apache Fineract. I have
>>>>>>>>>> experience with Java, Spring Boot, and building REST APIs. I’ve
>>>>>>>>>> successfully set up the project locally, including database connections,
>>>>>>>>>> and have explored the Swagger documentation.
>>>>>>>>>> >>>
>>>>>>>>>> >>> I couldn’t find any "good first issues" or beginner-friendly
>>>>>>>>>> tasks on the GitHub Issues page. Could someone please suggest a task or
>>>>>>>>>> guide me on how I can get started with my first contribution? I’m
>>>>>>>>>> particularly interested in working on APIs or improving existing features.
>>>>>>>>>> >>>
>>>>>>>>>> >>> Looking forward to your guidance!
>>>>>>>>>> >>>
>>>>>>>>>> >>> Thanks and regards,
>>>>>>>>>> >>> Akash
>>>>>>>>>>
>>>>>>>>>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Oluwafemi Oluwatuyi <ol...@gmail.com>.
Hi,

I’m facing an issue with the self-service API endpoints. While
self-authorization is working correctly, the following endpoints are
returning an "Unauthorized" error:

   - /self/userdetails
   - /self/loans
   - /self/savingsaccounts

I have verified that the user credentials are correct and authentication is
properly configured. However, the endpoints remain inaccessible.

Below is the attached screenshot of one of the responses I got.



On Thu, Nov 28, 2024 at 11:29 PM Oluwafemi Oluwatuyi <
oluwafemioluwatuyi8@gmail.com> wrote:

> Hi,
>
> I was able to identify the issue. It's working now.
>
> Thanks!
>
> On Thu, Nov 28, 2024, 9:25 PM Oluwafemi Oluwatuyi <
> oluwafemioluwatuyi8@gmail.com> wrote:
>
>> Hi Akash Nadar,
>> Thanks! It is working now.
>>
>> But the issue I am facing now is testing the endpoints. Most of the
>> errors I am getting are similar to the attached file below.
>>
>>
>> On Wed, Nov 27, 2024 at 4:23 PM Akash Nadar <ak...@gmail.com>
>> wrote:
>>
>>> Hi Oluwafemi,
>>> Follow this below given documentation , this helped me to set up the
>>> project locally .
>>>
>>>
>>> https://fineract-academy.com/how-to-build-fineract-with-intellij-idea.html
>>>
>>> Thanks and Regards,
>>> Akash
>>>
>>> On Wed, Nov 27, 2024 at 6:30 PM Oluwafemi Oluwatuyi <
>>> oluwafemioluwatuyi8@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm experiencing an issue with my Gradle build, where it gets stuck at
>>>> 98% when I run the command `./gradlew bootRun`, the build process gets
>>>> stuck at 98%. I've tried:
>>>>
>>>> -Cleaning and rebuilding the project,
>>>> -Checking for any errors or warnings in the build output
>>>>
>>>> However, none of these solutions have worked. I'd greatly appreciate
>>>> any guidance or advice on how to resolve this issue.
>>>>
>>>> Thanks in advance for your help.
>>>>
>>>> On Tue, Nov 26, 2024, 4:26 PM James Dailey <jd...@apache.org> wrote:
>>>>
>>>>> As a reminder, this is a public listserv that goes to many hundreds of
>>>>> people globally.
>>>>> It is archived and searchable - for example, this thread is found at:
>>>>> https://lists.apache.org/thread/q2o2lsghj2rr4plnwk7747gs9smf925k
>>>>>
>>>>> Please note.
>>>>>
>>>>> I probably would encourage you to contact each other privately and
>>>>> perhaps use discord or slack for side conversations.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Nov 26, 2024 at 7:13 AM Oluwafemi Oluwatuyi <
>>>>> oluwafemioluwatuyi8@gmail.com> wrote:
>>>>>
>>>>>> Hello Akash and Sarthak,
>>>>>>
>>>>>> I also want to be part of this. I have sent a friend request @sarthak
>>>>>> via LinkedIn.
>>>>>>
>>>>>> Below is my social profile
>>>>>>
>>>>>> https://www.linkedin.com/in/oluwafemioluwatuyi
>>>>>>
>>>>>> Best regards,
>>>>>> Oluwafemi
>>>>>>
>>>>>> On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar <
>>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>>
>>>>>>> Hello Akash,
>>>>>>>
>>>>>>> here are my social profiles
>>>>>>>
>>>>>>> Regards,
>>>>>>> Sarthak Deokar
>>>>>>>
>>>>>>> Linkdin
>>>>>>>
>>>>>>> https://www.linkedin.com/in/sarthak-deokar/
>>>>>>>
>>>>>>> Instagram
>>>>>>>
>>>>>>>
>>>>>>> https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <ak...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi James and Sarthak,
>>>>>>>>
>>>>>>>> Thank you for the detailed guidance and warm welcome!
>>>>>>>>
>>>>>>>> James, I’ll start by reviewing existing PRs and validating old Jira
>>>>>>>> tickets to familiarize myself with the project. I’ll also explore areas for
>>>>>>>> documentation and test coverage improvements. Your suggestions are very
>>>>>>>> helpful!
>>>>>>>>
>>>>>>>> Sarthak, let’s connect and collaborate on these tasks together. We
>>>>>>>> can divide work or brainstorm how to approach it. Let me know how you’d
>>>>>>>> like to proceed.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Akash
>>>>>>>>
>>>>>>>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
>>>>>>>> mandalavijaysuryaopensource@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hey James,
>>>>>>>>>
>>>>>>>>> Thank you for sharing these "first-steps" to contribute to this
>>>>>>>>> project. Although I wasn’t directly tagged in this email, I greatly
>>>>>>>>> appreciate the steps you’ve outlined for understanding the codebase
>>>>>>>>> and contributing meaningfully.
>>>>>>>>> Your advice is incredibly helpful for someone like me who is eager
>>>>>>>>> to
>>>>>>>>> contribute effectively.
>>>>>>>>>
>>>>>>>>> -Vijay
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>> >
>>>>>>>>> > Akash and Sarthak - thanks for your interest and welcome.
>>>>>>>>> >
>>>>>>>>> > Because Fineract is a large code base used in production at
>>>>>>>>> regulated financial institutions, it is essential that new contributors
>>>>>>>>> start with understanding the code base rather than trying to add new
>>>>>>>>> features.
>>>>>>>>> > There is a tendency for devs to want to do the "next cool thing"
>>>>>>>>> when really what is needed is more documentation, more test coverage, more
>>>>>>>>> detailed tickets, more reviews of changes.
>>>>>>>>> >
>>>>>>>>> > As a first step, you can review the existing PRs that are coming
>>>>>>>>> in.  Do they make sense to you?   Can you follow the logic?  Are the
>>>>>>>>> details in the Jira ticket sufficient?   You might want to try that for a
>>>>>>>>> week or two or five.
>>>>>>>>> > Following project activity is a very important first step.  You
>>>>>>>>> might even have some clarifying questions that could help the project
>>>>>>>>> become better.  That is also a contribution.
>>>>>>>>> >
>>>>>>>>> > Secondly, look for areas that are not well covered.  On many
>>>>>>>>> open source projects, too many devs are writing too much code with too
>>>>>>>>> little documentation.  That is true here as well.  Once you understand the
>>>>>>>>> features and functions and the structure of the code, can you help with
>>>>>>>>> some small piece of documentation?   ... we need people digging into
>>>>>>>>> specific areas that are in the code and documenting what is there.  That
>>>>>>>>> might also involve more test coverage in Cucumber (Gherkin files).
>>>>>>>>> >
>>>>>>>>> > Third, you might  look at the really old jira tickets, and
>>>>>>>>> validate one by one that the tickets are still needing to be fixed.  We
>>>>>>>>> have hundreds of old tickets that have creation dates before 2022 and I
>>>>>>>>> strongly suspect 90% are no longer valid.  This is tedious work, but is
>>>>>>>>> needed.  Pick a ticket, read it, determine if it seems real, put a comment
>>>>>>>>> that "yes, verified as of github checkpoint xxxx-xxxx" that the issue still
>>>>>>>>> exists" or "no, verified as of ... that the bug ticket is no longer valid".
>>>>>>>>> >
>>>>>>>>> > Generally, contributors should come with very modest aims at
>>>>>>>>> first.  This is a very complex project.
>>>>>>>>> >
>>>>>>>>> > James
>>>>>>>>> >
>>>>>>>>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>>>>>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>>>>> >>
>>>>>>>>> >> Hi,
>>>>>>>>> >>
>>>>>>>>> >> I am also suffering the same issues hope we could connect and
>>>>>>>>> work together
>>>>>>>>> >>
>>>>>>>>> >> Regards,
>>>>>>>>> >> Sarthak Deokar
>>>>>>>>> >>
>>>>>>>>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>> >>>
>>>>>>>>> >>> Hi everyone,
>>>>>>>>> >>>
>>>>>>>>> >>> I’m Akash, a new contributor to Apache Fineract. I have
>>>>>>>>> experience with Java, Spring Boot, and building REST APIs. I’ve
>>>>>>>>> successfully set up the project locally, including database connections,
>>>>>>>>> and have explored the Swagger documentation.
>>>>>>>>> >>>
>>>>>>>>> >>> I couldn’t find any "good first issues" or beginner-friendly
>>>>>>>>> tasks on the GitHub Issues page. Could someone please suggest a task or
>>>>>>>>> guide me on how I can get started with my first contribution? I’m
>>>>>>>>> particularly interested in working on APIs or improving existing features.
>>>>>>>>> >>>
>>>>>>>>> >>> Looking forward to your guidance!
>>>>>>>>> >>>
>>>>>>>>> >>> Thanks and regards,
>>>>>>>>> >>> Akash
>>>>>>>>>
>>>>>>>>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Oluwafemi Oluwatuyi <ol...@gmail.com>.
Hi,

I was able to identify the issue. It's working now.

Thanks!

On Thu, Nov 28, 2024, 9:25 PM Oluwafemi Oluwatuyi <
oluwafemioluwatuyi8@gmail.com> wrote:

> Hi Akash Nadar,
> Thanks! It is working now.
>
> But the issue I am facing now is testing the endpoints. Most of the errors
> I am getting are similar to the attached file below.
>
>
> On Wed, Nov 27, 2024 at 4:23 PM Akash Nadar <ak...@gmail.com>
> wrote:
>
>> Hi Oluwafemi,
>> Follow this below given documentation , this helped me to set up the
>> project locally .
>>
>> https://fineract-academy.com/how-to-build-fineract-with-intellij-idea.html
>>
>> Thanks and Regards,
>> Akash
>>
>> On Wed, Nov 27, 2024 at 6:30 PM Oluwafemi Oluwatuyi <
>> oluwafemioluwatuyi8@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I'm experiencing an issue with my Gradle build, where it gets stuck at
>>> 98% when I run the command `./gradlew bootRun`, the build process gets
>>> stuck at 98%. I've tried:
>>>
>>> -Cleaning and rebuilding the project,
>>> -Checking for any errors or warnings in the build output
>>>
>>> However, none of these solutions have worked. I'd greatly appreciate any
>>> guidance or advice on how to resolve this issue.
>>>
>>> Thanks in advance for your help.
>>>
>>> On Tue, Nov 26, 2024, 4:26 PM James Dailey <jd...@apache.org> wrote:
>>>
>>>> As a reminder, this is a public listserv that goes to many hundreds of
>>>> people globally.
>>>> It is archived and searchable - for example, this thread is found at:
>>>> https://lists.apache.org/thread/q2o2lsghj2rr4plnwk7747gs9smf925k
>>>>
>>>> Please note.
>>>>
>>>> I probably would encourage you to contact each other privately and
>>>> perhaps use discord or slack for side conversations.
>>>>
>>>>
>>>>
>>>> On Tue, Nov 26, 2024 at 7:13 AM Oluwafemi Oluwatuyi <
>>>> oluwafemioluwatuyi8@gmail.com> wrote:
>>>>
>>>>> Hello Akash and Sarthak,
>>>>>
>>>>> I also want to be part of this. I have sent a friend request @sarthak
>>>>> via LinkedIn.
>>>>>
>>>>> Below is my social profile
>>>>>
>>>>> https://www.linkedin.com/in/oluwafemioluwatuyi
>>>>>
>>>>> Best regards,
>>>>> Oluwafemi
>>>>>
>>>>> On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar <
>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>
>>>>>> Hello Akash,
>>>>>>
>>>>>> here are my social profiles
>>>>>>
>>>>>> Regards,
>>>>>> Sarthak Deokar
>>>>>>
>>>>>> Linkdin
>>>>>>
>>>>>> https://www.linkedin.com/in/sarthak-deokar/
>>>>>>
>>>>>> Instagram
>>>>>>
>>>>>>
>>>>>> https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6
>>>>>>
>>>>>>
>>>>>> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <ak...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi James and Sarthak,
>>>>>>>
>>>>>>> Thank you for the detailed guidance and warm welcome!
>>>>>>>
>>>>>>> James, I’ll start by reviewing existing PRs and validating old Jira
>>>>>>> tickets to familiarize myself with the project. I’ll also explore areas for
>>>>>>> documentation and test coverage improvements. Your suggestions are very
>>>>>>> helpful!
>>>>>>>
>>>>>>> Sarthak, let’s connect and collaborate on these tasks together. We
>>>>>>> can divide work or brainstorm how to approach it. Let me know how you’d
>>>>>>> like to proceed.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Akash
>>>>>>>
>>>>>>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
>>>>>>> mandalavijaysuryaopensource@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hey James,
>>>>>>>>
>>>>>>>> Thank you for sharing these "first-steps" to contribute to this
>>>>>>>> project. Although I wasn’t directly tagged in this email, I greatly
>>>>>>>> appreciate the steps you’ve outlined for understanding the codebase
>>>>>>>> and contributing meaningfully.
>>>>>>>> Your advice is incredibly helpful for someone like me who is eager
>>>>>>>> to
>>>>>>>> contribute effectively.
>>>>>>>>
>>>>>>>> -Vijay
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org>
>>>>>>>> wrote:
>>>>>>>> >
>>>>>>>> > Akash and Sarthak - thanks for your interest and welcome.
>>>>>>>> >
>>>>>>>> > Because Fineract is a large code base used in production at
>>>>>>>> regulated financial institutions, it is essential that new contributors
>>>>>>>> start with understanding the code base rather than trying to add new
>>>>>>>> features.
>>>>>>>> > There is a tendency for devs to want to do the "next cool thing"
>>>>>>>> when really what is needed is more documentation, more test coverage, more
>>>>>>>> detailed tickets, more reviews of changes.
>>>>>>>> >
>>>>>>>> > As a first step, you can review the existing PRs that are coming
>>>>>>>> in.  Do they make sense to you?   Can you follow the logic?  Are the
>>>>>>>> details in the Jira ticket sufficient?   You might want to try that for a
>>>>>>>> week or two or five.
>>>>>>>> > Following project activity is a very important first step.  You
>>>>>>>> might even have some clarifying questions that could help the project
>>>>>>>> become better.  That is also a contribution.
>>>>>>>> >
>>>>>>>> > Secondly, look for areas that are not well covered.  On many open
>>>>>>>> source projects, too many devs are writing too much code with too little
>>>>>>>> documentation.  That is true here as well.  Once you understand the
>>>>>>>> features and functions and the structure of the code, can you help with
>>>>>>>> some small piece of documentation?   ... we need people digging into
>>>>>>>> specific areas that are in the code and documenting what is there.  That
>>>>>>>> might also involve more test coverage in Cucumber (Gherkin files).
>>>>>>>> >
>>>>>>>> > Third, you might  look at the really old jira tickets, and
>>>>>>>> validate one by one that the tickets are still needing to be fixed.  We
>>>>>>>> have hundreds of old tickets that have creation dates before 2022 and I
>>>>>>>> strongly suspect 90% are no longer valid.  This is tedious work, but is
>>>>>>>> needed.  Pick a ticket, read it, determine if it seems real, put a comment
>>>>>>>> that "yes, verified as of github checkpoint xxxx-xxxx" that the issue still
>>>>>>>> exists" or "no, verified as of ... that the bug ticket is no longer valid".
>>>>>>>> >
>>>>>>>> > Generally, contributors should come with very modest aims at
>>>>>>>> first.  This is a very complex project.
>>>>>>>> >
>>>>>>>> > James
>>>>>>>> >
>>>>>>>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>>>>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>>>> >>
>>>>>>>> >> Hi,
>>>>>>>> >>
>>>>>>>> >> I am also suffering the same issues hope we could connect and
>>>>>>>> work together
>>>>>>>> >>
>>>>>>>> >> Regards,
>>>>>>>> >> Sarthak Deokar
>>>>>>>> >>
>>>>>>>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com>
>>>>>>>> wrote:
>>>>>>>> >>>
>>>>>>>> >>> Hi everyone,
>>>>>>>> >>>
>>>>>>>> >>> I’m Akash, a new contributor to Apache Fineract. I have
>>>>>>>> experience with Java, Spring Boot, and building REST APIs. I’ve
>>>>>>>> successfully set up the project locally, including database connections,
>>>>>>>> and have explored the Swagger documentation.
>>>>>>>> >>>
>>>>>>>> >>> I couldn’t find any "good first issues" or beginner-friendly
>>>>>>>> tasks on the GitHub Issues page. Could someone please suggest a task or
>>>>>>>> guide me on how I can get started with my first contribution? I’m
>>>>>>>> particularly interested in working on APIs or improving existing features.
>>>>>>>> >>>
>>>>>>>> >>> Looking forward to your guidance!
>>>>>>>> >>>
>>>>>>>> >>> Thanks and regards,
>>>>>>>> >>> Akash
>>>>>>>>
>>>>>>>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Oluwafemi Oluwatuyi <ol...@gmail.com>.
Hi Akash Nadar,
Thanks! It is working now.

But the issue I am facing now is testing the endpoints. Most of the errors
I am getting are similar to the attached file below.


On Wed, Nov 27, 2024 at 4:23 PM Akash Nadar <ak...@gmail.com> wrote:

> Hi Oluwafemi,
> Follow this below given documentation , this helped me to set up the
> project locally .
>
> https://fineract-academy.com/how-to-build-fineract-with-intellij-idea.html
>
> Thanks and Regards,
> Akash
>
> On Wed, Nov 27, 2024 at 6:30 PM Oluwafemi Oluwatuyi <
> oluwafemioluwatuyi8@gmail.com> wrote:
>
>> Hi,
>>
>> I'm experiencing an issue with my Gradle build, where it gets stuck at
>> 98% when I run the command `./gradlew bootRun`, the build process gets
>> stuck at 98%. I've tried:
>>
>> -Cleaning and rebuilding the project,
>> -Checking for any errors or warnings in the build output
>>
>> However, none of these solutions have worked. I'd greatly appreciate any
>> guidance or advice on how to resolve this issue.
>>
>> Thanks in advance for your help.
>>
>> On Tue, Nov 26, 2024, 4:26 PM James Dailey <jd...@apache.org> wrote:
>>
>>> As a reminder, this is a public listserv that goes to many hundreds of
>>> people globally.
>>> It is archived and searchable - for example, this thread is found at:
>>> https://lists.apache.org/thread/q2o2lsghj2rr4plnwk7747gs9smf925k
>>>
>>> Please note.
>>>
>>> I probably would encourage you to contact each other privately and
>>> perhaps use discord or slack for side conversations.
>>>
>>>
>>>
>>> On Tue, Nov 26, 2024 at 7:13 AM Oluwafemi Oluwatuyi <
>>> oluwafemioluwatuyi8@gmail.com> wrote:
>>>
>>>> Hello Akash and Sarthak,
>>>>
>>>> I also want to be part of this. I have sent a friend request @sarthak
>>>> via LinkedIn.
>>>>
>>>> Below is my social profile
>>>>
>>>> https://www.linkedin.com/in/oluwafemioluwatuyi
>>>>
>>>> Best regards,
>>>> Oluwafemi
>>>>
>>>> On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar <de...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Akash,
>>>>>
>>>>> here are my social profiles
>>>>>
>>>>> Regards,
>>>>> Sarthak Deokar
>>>>>
>>>>> Linkdin
>>>>>
>>>>> https://www.linkedin.com/in/sarthak-deokar/
>>>>>
>>>>> Instagram
>>>>>
>>>>>
>>>>> https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6
>>>>>
>>>>>
>>>>> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <ak...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi James and Sarthak,
>>>>>>
>>>>>> Thank you for the detailed guidance and warm welcome!
>>>>>>
>>>>>> James, I’ll start by reviewing existing PRs and validating old Jira
>>>>>> tickets to familiarize myself with the project. I’ll also explore areas for
>>>>>> documentation and test coverage improvements. Your suggestions are very
>>>>>> helpful!
>>>>>>
>>>>>> Sarthak, let’s connect and collaborate on these tasks together. We
>>>>>> can divide work or brainstorm how to approach it. Let me know how you’d
>>>>>> like to proceed.
>>>>>>
>>>>>> Thanks,
>>>>>> Akash
>>>>>>
>>>>>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
>>>>>> mandalavijaysuryaopensource@gmail.com> wrote:
>>>>>>
>>>>>>> Hey James,
>>>>>>>
>>>>>>> Thank you for sharing these "first-steps" to contribute to this
>>>>>>> project. Although I wasn’t directly tagged in this email, I greatly
>>>>>>> appreciate the steps you’ve outlined for understanding the codebase
>>>>>>> and contributing meaningfully.
>>>>>>> Your advice is incredibly helpful for someone like me who is eager to
>>>>>>> contribute effectively.
>>>>>>>
>>>>>>> -Vijay
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org>
>>>>>>> wrote:
>>>>>>> >
>>>>>>> > Akash and Sarthak - thanks for your interest and welcome.
>>>>>>> >
>>>>>>> > Because Fineract is a large code base used in production at
>>>>>>> regulated financial institutions, it is essential that new contributors
>>>>>>> start with understanding the code base rather than trying to add new
>>>>>>> features.
>>>>>>> > There is a tendency for devs to want to do the "next cool thing"
>>>>>>> when really what is needed is more documentation, more test coverage, more
>>>>>>> detailed tickets, more reviews of changes.
>>>>>>> >
>>>>>>> > As a first step, you can review the existing PRs that are coming
>>>>>>> in.  Do they make sense to you?   Can you follow the logic?  Are the
>>>>>>> details in the Jira ticket sufficient?   You might want to try that for a
>>>>>>> week or two or five.
>>>>>>> > Following project activity is a very important first step.  You
>>>>>>> might even have some clarifying questions that could help the project
>>>>>>> become better.  That is also a contribution.
>>>>>>> >
>>>>>>> > Secondly, look for areas that are not well covered.  On many open
>>>>>>> source projects, too many devs are writing too much code with too little
>>>>>>> documentation.  That is true here as well.  Once you understand the
>>>>>>> features and functions and the structure of the code, can you help with
>>>>>>> some small piece of documentation?   ... we need people digging into
>>>>>>> specific areas that are in the code and documenting what is there.  That
>>>>>>> might also involve more test coverage in Cucumber (Gherkin files).
>>>>>>> >
>>>>>>> > Third, you might  look at the really old jira tickets, and
>>>>>>> validate one by one that the tickets are still needing to be fixed.  We
>>>>>>> have hundreds of old tickets that have creation dates before 2022 and I
>>>>>>> strongly suspect 90% are no longer valid.  This is tedious work, but is
>>>>>>> needed.  Pick a ticket, read it, determine if it seems real, put a comment
>>>>>>> that "yes, verified as of github checkpoint xxxx-xxxx" that the issue still
>>>>>>> exists" or "no, verified as of ... that the bug ticket is no longer valid".
>>>>>>> >
>>>>>>> > Generally, contributors should come with very modest aims at
>>>>>>> first.  This is a very complex project.
>>>>>>> >
>>>>>>> > James
>>>>>>> >
>>>>>>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>>>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>>> >>
>>>>>>> >> Hi,
>>>>>>> >>
>>>>>>> >> I am also suffering the same issues hope we could connect and
>>>>>>> work together
>>>>>>> >>
>>>>>>> >> Regards,
>>>>>>> >> Sarthak Deokar
>>>>>>> >>
>>>>>>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>
>>>>>>> >>> Hi everyone,
>>>>>>> >>>
>>>>>>> >>> I’m Akash, a new contributor to Apache Fineract. I have
>>>>>>> experience with Java, Spring Boot, and building REST APIs. I’ve
>>>>>>> successfully set up the project locally, including database connections,
>>>>>>> and have explored the Swagger documentation.
>>>>>>> >>>
>>>>>>> >>> I couldn’t find any "good first issues" or beginner-friendly
>>>>>>> tasks on the GitHub Issues page. Could someone please suggest a task or
>>>>>>> guide me on how I can get started with my first contribution? I’m
>>>>>>> particularly interested in working on APIs or improving existing features.
>>>>>>> >>>
>>>>>>> >>> Looking forward to your guidance!
>>>>>>> >>>
>>>>>>> >>> Thanks and regards,
>>>>>>> >>> Akash
>>>>>>>
>>>>>>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Akash Nadar <ak...@gmail.com>.
Hi Oluwafemi,
Follow this below given documentation , this helped me to set up the
project locally .

https://fineract-academy.com/how-to-build-fineract-with-intellij-idea.html

Thanks and Regards,
Akash

On Wed, Nov 27, 2024 at 6:30 PM Oluwafemi Oluwatuyi <
oluwafemioluwatuyi8@gmail.com> wrote:

> Hi,
>
> I'm experiencing an issue with my Gradle build, where it gets stuck at 98%
> when I run the command `./gradlew bootRun`, the build process gets stuck at
> 98%. I've tried:
>
> -Cleaning and rebuilding the project,
> -Checking for any errors or warnings in the build output
>
> However, none of these solutions have worked. I'd greatly appreciate any
> guidance or advice on how to resolve this issue.
>
> Thanks in advance for your help.
>
> On Tue, Nov 26, 2024, 4:26 PM James Dailey <jd...@apache.org> wrote:
>
>> As a reminder, this is a public listserv that goes to many hundreds of
>> people globally.
>> It is archived and searchable - for example, this thread is found at:
>> https://lists.apache.org/thread/q2o2lsghj2rr4plnwk7747gs9smf925k
>>
>> Please note.
>>
>> I probably would encourage you to contact each other privately and
>> perhaps use discord or slack for side conversations.
>>
>>
>>
>> On Tue, Nov 26, 2024 at 7:13 AM Oluwafemi Oluwatuyi <
>> oluwafemioluwatuyi8@gmail.com> wrote:
>>
>>> Hello Akash and Sarthak,
>>>
>>> I also want to be part of this. I have sent a friend request @sarthak
>>> via LinkedIn.
>>>
>>> Below is my social profile
>>>
>>> https://www.linkedin.com/in/oluwafemioluwatuyi
>>>
>>> Best regards,
>>> Oluwafemi
>>>
>>> On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar <de...@gmail.com>
>>> wrote:
>>>
>>>> Hello Akash,
>>>>
>>>> here are my social profiles
>>>>
>>>> Regards,
>>>> Sarthak Deokar
>>>>
>>>> Linkdin
>>>>
>>>> https://www.linkedin.com/in/sarthak-deokar/
>>>>
>>>> Instagram
>>>>
>>>>
>>>> https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6
>>>>
>>>>
>>>> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <ak...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi James and Sarthak,
>>>>>
>>>>> Thank you for the detailed guidance and warm welcome!
>>>>>
>>>>> James, I’ll start by reviewing existing PRs and validating old Jira
>>>>> tickets to familiarize myself with the project. I’ll also explore areas for
>>>>> documentation and test coverage improvements. Your suggestions are very
>>>>> helpful!
>>>>>
>>>>> Sarthak, let’s connect and collaborate on these tasks together. We can
>>>>> divide work or brainstorm how to approach it. Let me know how you’d like to
>>>>> proceed.
>>>>>
>>>>> Thanks,
>>>>> Akash
>>>>>
>>>>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
>>>>> mandalavijaysuryaopensource@gmail.com> wrote:
>>>>>
>>>>>> Hey James,
>>>>>>
>>>>>> Thank you for sharing these "first-steps" to contribute to this
>>>>>> project. Although I wasn’t directly tagged in this email, I greatly
>>>>>> appreciate the steps you’ve outlined for understanding the codebase
>>>>>> and contributing meaningfully.
>>>>>> Your advice is incredibly helpful for someone like me who is eager to
>>>>>> contribute effectively.
>>>>>>
>>>>>> -Vijay
>>>>>>
>>>>>>
>>>>>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org>
>>>>>> wrote:
>>>>>> >
>>>>>> > Akash and Sarthak - thanks for your interest and welcome.
>>>>>> >
>>>>>> > Because Fineract is a large code base used in production at
>>>>>> regulated financial institutions, it is essential that new contributors
>>>>>> start with understanding the code base rather than trying to add new
>>>>>> features.
>>>>>> > There is a tendency for devs to want to do the "next cool thing"
>>>>>> when really what is needed is more documentation, more test coverage, more
>>>>>> detailed tickets, more reviews of changes.
>>>>>> >
>>>>>> > As a first step, you can review the existing PRs that are coming
>>>>>> in.  Do they make sense to you?   Can you follow the logic?  Are the
>>>>>> details in the Jira ticket sufficient?   You might want to try that for a
>>>>>> week or two or five.
>>>>>> > Following project activity is a very important first step.  You
>>>>>> might even have some clarifying questions that could help the project
>>>>>> become better.  That is also a contribution.
>>>>>> >
>>>>>> > Secondly, look for areas that are not well covered.  On many open
>>>>>> source projects, too many devs are writing too much code with too little
>>>>>> documentation.  That is true here as well.  Once you understand the
>>>>>> features and functions and the structure of the code, can you help with
>>>>>> some small piece of documentation?   ... we need people digging into
>>>>>> specific areas that are in the code and documenting what is there.  That
>>>>>> might also involve more test coverage in Cucumber (Gherkin files).
>>>>>> >
>>>>>> > Third, you might  look at the really old jira tickets, and validate
>>>>>> one by one that the tickets are still needing to be fixed.  We have
>>>>>> hundreds of old tickets that have creation dates before 2022 and I strongly
>>>>>> suspect 90% are no longer valid.  This is tedious work, but is needed.
>>>>>> Pick a ticket, read it, determine if it seems real, put a comment that
>>>>>> "yes, verified as of github checkpoint xxxx-xxxx" that the issue still
>>>>>> exists" or "no, verified as of ... that the bug ticket is no longer valid".
>>>>>> >
>>>>>> > Generally, contributors should come with very modest aims at
>>>>>> first.  This is a very complex project.
>>>>>> >
>>>>>> > James
>>>>>> >
>>>>>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>>>>>> deokarsarthak05@gmail.com> wrote:
>>>>>> >>
>>>>>> >> Hi,
>>>>>> >>
>>>>>> >> I am also suffering the same issues hope we could connect and work
>>>>>> together
>>>>>> >>
>>>>>> >> Regards,
>>>>>> >> Sarthak Deokar
>>>>>> >>
>>>>>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com>
>>>>>> wrote:
>>>>>> >>>
>>>>>> >>> Hi everyone,
>>>>>> >>>
>>>>>> >>> I’m Akash, a new contributor to Apache Fineract. I have
>>>>>> experience with Java, Spring Boot, and building REST APIs. I’ve
>>>>>> successfully set up the project locally, including database connections,
>>>>>> and have explored the Swagger documentation.
>>>>>> >>>
>>>>>> >>> I couldn’t find any "good first issues" or beginner-friendly
>>>>>> tasks on the GitHub Issues page. Could someone please suggest a task or
>>>>>> guide me on how I can get started with my first contribution? I’m
>>>>>> particularly interested in working on APIs or improving existing features.
>>>>>> >>>
>>>>>> >>> Looking forward to your guidance!
>>>>>> >>>
>>>>>> >>> Thanks and regards,
>>>>>> >>> Akash
>>>>>>
>>>>>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Oluwafemi Oluwatuyi <ol...@gmail.com>.
Hi,

I'm experiencing an issue with my Gradle build, where it gets stuck at 98%
when I run the command `./gradlew bootRun`, the build process gets stuck at
98%. I've tried:

-Cleaning and rebuilding the project,
-Checking for any errors or warnings in the build output

However, none of these solutions have worked. I'd greatly appreciate any
guidance or advice on how to resolve this issue.

Thanks in advance for your help.

On Tue, Nov 26, 2024, 4:26 PM James Dailey <jd...@apache.org> wrote:

> As a reminder, this is a public listserv that goes to many hundreds of
> people globally.
> It is archived and searchable - for example, this thread is found at:
> https://lists.apache.org/thread/q2o2lsghj2rr4plnwk7747gs9smf925k
>
> Please note.
>
> I probably would encourage you to contact each other privately and perhaps
> use discord or slack for side conversations.
>
>
>
> On Tue, Nov 26, 2024 at 7:13 AM Oluwafemi Oluwatuyi <
> oluwafemioluwatuyi8@gmail.com> wrote:
>
>> Hello Akash and Sarthak,
>>
>> I also want to be part of this. I have sent a friend request @sarthak via
>> LinkedIn.
>>
>> Below is my social profile
>>
>> https://www.linkedin.com/in/oluwafemioluwatuyi
>>
>> Best regards,
>> Oluwafemi
>>
>> On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar <de...@gmail.com>
>> wrote:
>>
>>> Hello Akash,
>>>
>>> here are my social profiles
>>>
>>> Regards,
>>> Sarthak Deokar
>>>
>>> Linkdin
>>>
>>> https://www.linkedin.com/in/sarthak-deokar/
>>>
>>> Instagram
>>>
>>>
>>> https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6
>>>
>>>
>>> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <ak...@gmail.com>
>>> wrote:
>>>
>>>> Hi James and Sarthak,
>>>>
>>>> Thank you for the detailed guidance and warm welcome!
>>>>
>>>> James, I’ll start by reviewing existing PRs and validating old Jira
>>>> tickets to familiarize myself with the project. I’ll also explore areas for
>>>> documentation and test coverage improvements. Your suggestions are very
>>>> helpful!
>>>>
>>>> Sarthak, let’s connect and collaborate on these tasks together. We can
>>>> divide work or brainstorm how to approach it. Let me know how you’d like to
>>>> proceed.
>>>>
>>>> Thanks,
>>>> Akash
>>>>
>>>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
>>>> mandalavijaysuryaopensource@gmail.com> wrote:
>>>>
>>>>> Hey James,
>>>>>
>>>>> Thank you for sharing these "first-steps" to contribute to this
>>>>> project. Although I wasn’t directly tagged in this email, I greatly
>>>>> appreciate the steps you’ve outlined for understanding the codebase
>>>>> and contributing meaningfully.
>>>>> Your advice is incredibly helpful for someone like me who is eager to
>>>>> contribute effectively.
>>>>>
>>>>> -Vijay
>>>>>
>>>>>
>>>>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org>
>>>>> wrote:
>>>>> >
>>>>> > Akash and Sarthak - thanks for your interest and welcome.
>>>>> >
>>>>> > Because Fineract is a large code base used in production at
>>>>> regulated financial institutions, it is essential that new contributors
>>>>> start with understanding the code base rather than trying to add new
>>>>> features.
>>>>> > There is a tendency for devs to want to do the "next cool thing"
>>>>> when really what is needed is more documentation, more test coverage, more
>>>>> detailed tickets, more reviews of changes.
>>>>> >
>>>>> > As a first step, you can review the existing PRs that are coming
>>>>> in.  Do they make sense to you?   Can you follow the logic?  Are the
>>>>> details in the Jira ticket sufficient?   You might want to try that for a
>>>>> week or two or five.
>>>>> > Following project activity is a very important first step.  You
>>>>> might even have some clarifying questions that could help the project
>>>>> become better.  That is also a contribution.
>>>>> >
>>>>> > Secondly, look for areas that are not well covered.  On many open
>>>>> source projects, too many devs are writing too much code with too little
>>>>> documentation.  That is true here as well.  Once you understand the
>>>>> features and functions and the structure of the code, can you help with
>>>>> some small piece of documentation?   ... we need people digging into
>>>>> specific areas that are in the code and documenting what is there.  That
>>>>> might also involve more test coverage in Cucumber (Gherkin files).
>>>>> >
>>>>> > Third, you might  look at the really old jira tickets, and validate
>>>>> one by one that the tickets are still needing to be fixed.  We have
>>>>> hundreds of old tickets that have creation dates before 2022 and I strongly
>>>>> suspect 90% are no longer valid.  This is tedious work, but is needed.
>>>>> Pick a ticket, read it, determine if it seems real, put a comment that
>>>>> "yes, verified as of github checkpoint xxxx-xxxx" that the issue still
>>>>> exists" or "no, verified as of ... that the bug ticket is no longer valid".
>>>>> >
>>>>> > Generally, contributors should come with very modest aims at first.
>>>>> This is a very complex project.
>>>>> >
>>>>> > James
>>>>> >
>>>>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>>>>> deokarsarthak05@gmail.com> wrote:
>>>>> >>
>>>>> >> Hi,
>>>>> >>
>>>>> >> I am also suffering the same issues hope we could connect and work
>>>>> together
>>>>> >>
>>>>> >> Regards,
>>>>> >> Sarthak Deokar
>>>>> >>
>>>>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com>
>>>>> wrote:
>>>>> >>>
>>>>> >>> Hi everyone,
>>>>> >>>
>>>>> >>> I’m Akash, a new contributor to Apache Fineract. I have experience
>>>>> with Java, Spring Boot, and building REST APIs. I’ve successfully set up
>>>>> the project locally, including database connections, and have explored the
>>>>> Swagger documentation.
>>>>> >>>
>>>>> >>> I couldn’t find any "good first issues" or beginner-friendly tasks
>>>>> on the GitHub Issues page. Could someone please suggest a task or guide me
>>>>> on how I can get started with my first contribution? I’m particularly
>>>>> interested in working on APIs or improving existing features.
>>>>> >>>
>>>>> >>> Looking forward to your guidance!
>>>>> >>>
>>>>> >>> Thanks and regards,
>>>>> >>> Akash
>>>>>
>>>>

Re: Guidance Request for Contribution to Apache Fineract

Posted by James Dailey <jd...@apache.org>.
As a reminder, this is a public listserv that goes to many hundreds of
people globally.
It is archived and searchable - for example, this thread is found at:
https://lists.apache.org/thread/q2o2lsghj2rr4plnwk7747gs9smf925k

Please note.

I probably would encourage you to contact each other privately and perhaps
use discord or slack for side conversations.



On Tue, Nov 26, 2024 at 7:13 AM Oluwafemi Oluwatuyi <
oluwafemioluwatuyi8@gmail.com> wrote:

> Hello Akash and Sarthak,
>
> I also want to be part of this. I have sent a friend request @sarthak via
> LinkedIn.
>
> Below is my social profile
>
> https://www.linkedin.com/in/oluwafemioluwatuyi
>
> Best regards,
> Oluwafemi
>
> On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar <de...@gmail.com>
> wrote:
>
>> Hello Akash,
>>
>> here are my social profiles
>>
>> Regards,
>> Sarthak Deokar
>>
>> Linkdin
>>
>> https://www.linkedin.com/in/sarthak-deokar/
>>
>> Instagram
>>
>>
>> https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6
>>
>>
>> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <ak...@gmail.com>
>> wrote:
>>
>>> Hi James and Sarthak,
>>>
>>> Thank you for the detailed guidance and warm welcome!
>>>
>>> James, I’ll start by reviewing existing PRs and validating old Jira
>>> tickets to familiarize myself with the project. I’ll also explore areas for
>>> documentation and test coverage improvements. Your suggestions are very
>>> helpful!
>>>
>>> Sarthak, let’s connect and collaborate on these tasks together. We can
>>> divide work or brainstorm how to approach it. Let me know how you’d like to
>>> proceed.
>>>
>>> Thanks,
>>> Akash
>>>
>>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
>>> mandalavijaysuryaopensource@gmail.com> wrote:
>>>
>>>> Hey James,
>>>>
>>>> Thank you for sharing these "first-steps" to contribute to this
>>>> project. Although I wasn’t directly tagged in this email, I greatly
>>>> appreciate the steps you’ve outlined for understanding the codebase
>>>> and contributing meaningfully.
>>>> Your advice is incredibly helpful for someone like me who is eager to
>>>> contribute effectively.
>>>>
>>>> -Vijay
>>>>
>>>>
>>>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org>
>>>> wrote:
>>>> >
>>>> > Akash and Sarthak - thanks for your interest and welcome.
>>>> >
>>>> > Because Fineract is a large code base used in production at regulated
>>>> financial institutions, it is essential that new contributors start with
>>>> understanding the code base rather than trying to add new features.
>>>> > There is a tendency for devs to want to do the "next cool thing" when
>>>> really what is needed is more documentation, more test coverage, more
>>>> detailed tickets, more reviews of changes.
>>>> >
>>>> > As a first step, you can review the existing PRs that are coming in.
>>>> Do they make sense to you?   Can you follow the logic?  Are the details in
>>>> the Jira ticket sufficient?   You might want to try that for a week or two
>>>> or five.
>>>> > Following project activity is a very important first step.  You might
>>>> even have some clarifying questions that could help the project become
>>>> better.  That is also a contribution.
>>>> >
>>>> > Secondly, look for areas that are not well covered.  On many open
>>>> source projects, too many devs are writing too much code with too little
>>>> documentation.  That is true here as well.  Once you understand the
>>>> features and functions and the structure of the code, can you help with
>>>> some small piece of documentation?   ... we need people digging into
>>>> specific areas that are in the code and documenting what is there.  That
>>>> might also involve more test coverage in Cucumber (Gherkin files).
>>>> >
>>>> > Third, you might  look at the really old jira tickets, and validate
>>>> one by one that the tickets are still needing to be fixed.  We have
>>>> hundreds of old tickets that have creation dates before 2022 and I strongly
>>>> suspect 90% are no longer valid.  This is tedious work, but is needed.
>>>> Pick a ticket, read it, determine if it seems real, put a comment that
>>>> "yes, verified as of github checkpoint xxxx-xxxx" that the issue still
>>>> exists" or "no, verified as of ... that the bug ticket is no longer valid".
>>>> >
>>>> > Generally, contributors should come with very modest aims at first.
>>>> This is a very complex project.
>>>> >
>>>> > James
>>>> >
>>>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>>>> deokarsarthak05@gmail.com> wrote:
>>>> >>
>>>> >> Hi,
>>>> >>
>>>> >> I am also suffering the same issues hope we could connect and work
>>>> together
>>>> >>
>>>> >> Regards,
>>>> >> Sarthak Deokar
>>>> >>
>>>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com>
>>>> wrote:
>>>> >>>
>>>> >>> Hi everyone,
>>>> >>>
>>>> >>> I’m Akash, a new contributor to Apache Fineract. I have experience
>>>> with Java, Spring Boot, and building REST APIs. I’ve successfully set up
>>>> the project locally, including database connections, and have explored the
>>>> Swagger documentation.
>>>> >>>
>>>> >>> I couldn’t find any "good first issues" or beginner-friendly tasks
>>>> on the GitHub Issues page. Could someone please suggest a task or guide me
>>>> on how I can get started with my first contribution? I’m particularly
>>>> interested in working on APIs or improving existing features.
>>>> >>>
>>>> >>> Looking forward to your guidance!
>>>> >>>
>>>> >>> Thanks and regards,
>>>> >>> Akash
>>>>
>>>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Oluwafemi Oluwatuyi <ol...@gmail.com>.
Hello Akash and Sarthak,

I also want to be part of this. I have sent a friend request @sarthak via
LinkedIn.

Below is my social profile

https://www.linkedin.com/in/oluwafemioluwatuyi

Best regards,
Oluwafemi

On Tue, Nov 26, 2024, 4:03 PM Sarthak Deokar <de...@gmail.com>
wrote:

> Hello Akash,
>
> here are my social profiles
>
> Regards,
> Sarthak Deokar
>
> Linkdin
>
> https://www.linkedin.com/in/sarthak-deokar/
>
> Instagram
>
>
> https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6
>
>
> On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <ak...@gmail.com>
> wrote:
>
>> Hi James and Sarthak,
>>
>> Thank you for the detailed guidance and warm welcome!
>>
>> James, I’ll start by reviewing existing PRs and validating old Jira
>> tickets to familiarize myself with the project. I’ll also explore areas for
>> documentation and test coverage improvements. Your suggestions are very
>> helpful!
>>
>> Sarthak, let’s connect and collaborate on these tasks together. We can
>> divide work or brainstorm how to approach it. Let me know how you’d like to
>> proceed.
>>
>> Thanks,
>> Akash
>>
>> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
>> mandalavijaysuryaopensource@gmail.com> wrote:
>>
>>> Hey James,
>>>
>>> Thank you for sharing these "first-steps" to contribute to this
>>> project. Although I wasn’t directly tagged in this email, I greatly
>>> appreciate the steps you’ve outlined for understanding the codebase
>>> and contributing meaningfully.
>>> Your advice is incredibly helpful for someone like me who is eager to
>>> contribute effectively.
>>>
>>> -Vijay
>>>
>>>
>>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org> wrote:
>>> >
>>> > Akash and Sarthak - thanks for your interest and welcome.
>>> >
>>> > Because Fineract is a large code base used in production at regulated
>>> financial institutions, it is essential that new contributors start with
>>> understanding the code base rather than trying to add new features.
>>> > There is a tendency for devs to want to do the "next cool thing" when
>>> really what is needed is more documentation, more test coverage, more
>>> detailed tickets, more reviews of changes.
>>> >
>>> > As a first step, you can review the existing PRs that are coming in.
>>> Do they make sense to you?   Can you follow the logic?  Are the details in
>>> the Jira ticket sufficient?   You might want to try that for a week or two
>>> or five.
>>> > Following project activity is a very important first step.  You might
>>> even have some clarifying questions that could help the project become
>>> better.  That is also a contribution.
>>> >
>>> > Secondly, look for areas that are not well covered.  On many open
>>> source projects, too many devs are writing too much code with too little
>>> documentation.  That is true here as well.  Once you understand the
>>> features and functions and the structure of the code, can you help with
>>> some small piece of documentation?   ... we need people digging into
>>> specific areas that are in the code and documenting what is there.  That
>>> might also involve more test coverage in Cucumber (Gherkin files).
>>> >
>>> > Third, you might  look at the really old jira tickets, and validate
>>> one by one that the tickets are still needing to be fixed.  We have
>>> hundreds of old tickets that have creation dates before 2022 and I strongly
>>> suspect 90% are no longer valid.  This is tedious work, but is needed.
>>> Pick a ticket, read it, determine if it seems real, put a comment that
>>> "yes, verified as of github checkpoint xxxx-xxxx" that the issue still
>>> exists" or "no, verified as of ... that the bug ticket is no longer valid".
>>> >
>>> > Generally, contributors should come with very modest aims at first.
>>> This is a very complex project.
>>> >
>>> > James
>>> >
>>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>>> deokarsarthak05@gmail.com> wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> I am also suffering the same issues hope we could connect and work
>>> together
>>> >>
>>> >> Regards,
>>> >> Sarthak Deokar
>>> >>
>>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com>
>>> wrote:
>>> >>>
>>> >>> Hi everyone,
>>> >>>
>>> >>> I’m Akash, a new contributor to Apache Fineract. I have experience
>>> with Java, Spring Boot, and building REST APIs. I’ve successfully set up
>>> the project locally, including database connections, and have explored the
>>> Swagger documentation.
>>> >>>
>>> >>> I couldn’t find any "good first issues" or beginner-friendly tasks
>>> on the GitHub Issues page. Could someone please suggest a task or guide me
>>> on how I can get started with my first contribution? I’m particularly
>>> interested in working on APIs or improving existing features.
>>> >>>
>>> >>> Looking forward to your guidance!
>>> >>>
>>> >>> Thanks and regards,
>>> >>> Akash
>>>
>>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Sarthak Deokar <de...@gmail.com>.
Hello Akash,

here are my social profiles

Regards,
Sarthak Deokar

Linkdin

https://www.linkedin.com/in/sarthak-deokar/

Instagram

https://www.instagram.com/_sarthakdeokar_/profilecard/?igsh=eHJ4NTU1b2Npemp6


On Mon, Nov 25, 2024 at 11:23 PM Akash Nadar <ak...@gmail.com> wrote:

> Hi James and Sarthak,
>
> Thank you for the detailed guidance and warm welcome!
>
> James, I’ll start by reviewing existing PRs and validating old Jira
> tickets to familiarize myself with the project. I’ll also explore areas for
> documentation and test coverage improvements. Your suggestions are very
> helpful!
>
> Sarthak, let’s connect and collaborate on these tasks together. We can
> divide work or brainstorm how to approach it. Let me know how you’d like to
> proceed.
>
> Thanks,
> Akash
>
> On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
> mandalavijaysuryaopensource@gmail.com> wrote:
>
>> Hey James,
>>
>> Thank you for sharing these "first-steps" to contribute to this
>> project. Although I wasn’t directly tagged in this email, I greatly
>> appreciate the steps you’ve outlined for understanding the codebase
>> and contributing meaningfully.
>> Your advice is incredibly helpful for someone like me who is eager to
>> contribute effectively.
>>
>> -Vijay
>>
>>
>> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org> wrote:
>> >
>> > Akash and Sarthak - thanks for your interest and welcome.
>> >
>> > Because Fineract is a large code base used in production at regulated
>> financial institutions, it is essential that new contributors start with
>> understanding the code base rather than trying to add new features.
>> > There is a tendency for devs to want to do the "next cool thing" when
>> really what is needed is more documentation, more test coverage, more
>> detailed tickets, more reviews of changes.
>> >
>> > As a first step, you can review the existing PRs that are coming in.
>> Do they make sense to you?   Can you follow the logic?  Are the details in
>> the Jira ticket sufficient?   You might want to try that for a week or two
>> or five.
>> > Following project activity is a very important first step.  You might
>> even have some clarifying questions that could help the project become
>> better.  That is also a contribution.
>> >
>> > Secondly, look for areas that are not well covered.  On many open
>> source projects, too many devs are writing too much code with too little
>> documentation.  That is true here as well.  Once you understand the
>> features and functions and the structure of the code, can you help with
>> some small piece of documentation?   ... we need people digging into
>> specific areas that are in the code and documenting what is there.  That
>> might also involve more test coverage in Cucumber (Gherkin files).
>> >
>> > Third, you might  look at the really old jira tickets, and validate one
>> by one that the tickets are still needing to be fixed.  We have hundreds of
>> old tickets that have creation dates before 2022 and I strongly suspect 90%
>> are no longer valid.  This is tedious work, but is needed.  Pick a ticket,
>> read it, determine if it seems real, put a comment that "yes, verified as
>> of github checkpoint xxxx-xxxx" that the issue still exists" or "no,
>> verified as of ... that the bug ticket is no longer valid".
>> >
>> > Generally, contributors should come with very modest aims at first.
>> This is a very complex project.
>> >
>> > James
>> >
>> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
>> deokarsarthak05@gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> I am also suffering the same issues hope we could connect and work
>> together
>> >>
>> >> Regards,
>> >> Sarthak Deokar
>> >>
>> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com>
>> wrote:
>> >>>
>> >>> Hi everyone,
>> >>>
>> >>> I’m Akash, a new contributor to Apache Fineract. I have experience
>> with Java, Spring Boot, and building REST APIs. I’ve successfully set up
>> the project locally, including database connections, and have explored the
>> Swagger documentation.
>> >>>
>> >>> I couldn’t find any "good first issues" or beginner-friendly tasks on
>> the GitHub Issues page. Could someone please suggest a task or guide me on
>> how I can get started with my first contribution? I’m particularly
>> interested in working on APIs or improving existing features.
>> >>>
>> >>> Looking forward to your guidance!
>> >>>
>> >>> Thanks and regards,
>> >>> Akash
>>
>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Akash Nadar <ak...@gmail.com>.
Hi James and Sarthak,

Thank you for the detailed guidance and warm welcome!

James, I’ll start by reviewing existing PRs and validating old Jira tickets
to familiarize myself with the project. I’ll also explore areas for
documentation and test coverage improvements. Your suggestions are very
helpful!

Sarthak, let’s connect and collaborate on these tasks together. We can
divide work or brainstorm how to approach it. Let me know how you’d like to
proceed.

Thanks,
Akash

On Mon, Nov 25, 2024 at 10:01 PM Vijaysurya Mandala <
mandalavijaysuryaopensource@gmail.com> wrote:

> Hey James,
>
> Thank you for sharing these "first-steps" to contribute to this
> project. Although I wasn’t directly tagged in this email, I greatly
> appreciate the steps you’ve outlined for understanding the codebase
> and contributing meaningfully.
> Your advice is incredibly helpful for someone like me who is eager to
> contribute effectively.
>
> -Vijay
>
>
> On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org> wrote:
> >
> > Akash and Sarthak - thanks for your interest and welcome.
> >
> > Because Fineract is a large code base used in production at regulated
> financial institutions, it is essential that new contributors start with
> understanding the code base rather than trying to add new features.
> > There is a tendency for devs to want to do the "next cool thing" when
> really what is needed is more documentation, more test coverage, more
> detailed tickets, more reviews of changes.
> >
> > As a first step, you can review the existing PRs that are coming in.  Do
> they make sense to you?   Can you follow the logic?  Are the details in the
> Jira ticket sufficient?   You might want to try that for a week or two or
> five.
> > Following project activity is a very important first step.  You might
> even have some clarifying questions that could help the project become
> better.  That is also a contribution.
> >
> > Secondly, look for areas that are not well covered.  On many open source
> projects, too many devs are writing too much code with too little
> documentation.  That is true here as well.  Once you understand the
> features and functions and the structure of the code, can you help with
> some small piece of documentation?   ... we need people digging into
> specific areas that are in the code and documenting what is there.  That
> might also involve more test coverage in Cucumber (Gherkin files).
> >
> > Third, you might  look at the really old jira tickets, and validate one
> by one that the tickets are still needing to be fixed.  We have hundreds of
> old tickets that have creation dates before 2022 and I strongly suspect 90%
> are no longer valid.  This is tedious work, but is needed.  Pick a ticket,
> read it, determine if it seems real, put a comment that "yes, verified as
> of github checkpoint xxxx-xxxx" that the issue still exists" or "no,
> verified as of ... that the bug ticket is no longer valid".
> >
> > Generally, contributors should come with very modest aims at first.
> This is a very complex project.
> >
> > James
> >
> > On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <
> deokarsarthak05@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> I am also suffering the same issues hope we could connect and work
> together
> >>
> >> Regards,
> >> Sarthak Deokar
> >>
> >> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com> wrote:
> >>>
> >>> Hi everyone,
> >>>
> >>> I’m Akash, a new contributor to Apache Fineract. I have experience
> with Java, Spring Boot, and building REST APIs. I’ve successfully set up
> the project locally, including database connections, and have explored the
> Swagger documentation.
> >>>
> >>> I couldn’t find any "good first issues" or beginner-friendly tasks on
> the GitHub Issues page. Could someone please suggest a task or guide me on
> how I can get started with my first contribution? I’m particularly
> interested in working on APIs or improving existing features.
> >>>
> >>> Looking forward to your guidance!
> >>>
> >>> Thanks and regards,
> >>> Akash
>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Vijaysurya Mandala <ma...@gmail.com>.
Hey James,

Thank you for sharing these "first-steps" to contribute to this
project. Although I wasn’t directly tagged in this email, I greatly
appreciate the steps you’ve outlined for understanding the codebase
and contributing meaningfully.
Your advice is incredibly helpful for someone like me who is eager to
contribute effectively.

-Vijay


On Mon, Nov 25, 2024 at 4:20 AM James Dailey <jd...@apache.org> wrote:
>
> Akash and Sarthak - thanks for your interest and welcome.
>
> Because Fineract is a large code base used in production at regulated financial institutions, it is essential that new contributors start with understanding the code base rather than trying to add new features.
> There is a tendency for devs to want to do the "next cool thing" when really what is needed is more documentation, more test coverage, more detailed tickets, more reviews of changes.
>
> As a first step, you can review the existing PRs that are coming in.  Do they make sense to you?   Can you follow the logic?  Are the details in the Jira ticket sufficient?   You might want to try that for a week or two or five.
> Following project activity is a very important first step.  You might even have some clarifying questions that could help the project become better.  That is also a contribution.
>
> Secondly, look for areas that are not well covered.  On many open source projects, too many devs are writing too much code with too little documentation.  That is true here as well.  Once you understand the features and functions and the structure of the code, can you help with some small piece of documentation?   ... we need people digging into specific areas that are in the code and documenting what is there.  That might also involve more test coverage in Cucumber (Gherkin files).
>
> Third, you might  look at the really old jira tickets, and validate one by one that the tickets are still needing to be fixed.  We have hundreds of old tickets that have creation dates before 2022 and I strongly suspect 90% are no longer valid.  This is tedious work, but is needed.  Pick a ticket, read it, determine if it seems real, put a comment that "yes, verified as of github checkpoint xxxx-xxxx" that the issue still exists" or "no, verified as of ... that the bug ticket is no longer valid".
>
> Generally, contributors should come with very modest aims at first.  This is a very complex project.
>
> James
>
> On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <de...@gmail.com> wrote:
>>
>> Hi,
>>
>> I am also suffering the same issues hope we could connect and work together
>>
>> Regards,
>> Sarthak Deokar
>>
>> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com> wrote:
>>>
>>> Hi everyone,
>>>
>>> I’m Akash, a new contributor to Apache Fineract. I have experience with Java, Spring Boot, and building REST APIs. I’ve successfully set up the project locally, including database connections, and have explored the Swagger documentation.
>>>
>>> I couldn’t find any "good first issues" or beginner-friendly tasks on the GitHub Issues page. Could someone please suggest a task or guide me on how I can get started with my first contribution? I’m particularly interested in working on APIs or improving existing features.
>>>
>>> Looking forward to your guidance!
>>>
>>> Thanks and regards,
>>> Akash

Re: Guidance Request for Contribution to Apache Fineract

Posted by James Dailey <jd...@apache.org>.
Akash and Sarthak - thanks for your interest and welcome.

Because Fineract is a large code base used in production at regulated
financial institutions, it is essential that new contributors start with
understanding the code base rather than trying to add new features.
There is a tendency for devs to want to do the "next cool thing" when
really what is needed is more documentation, more test coverage, more
detailed tickets, more reviews of changes.

As a first step, you can review the existing PRs that are coming in.  Do
they make sense to you?   Can you follow the logic?  Are the details in the
Jira ticket sufficient?   You might want to try that for a week or two or
five.
Following project activity is a very important first step.  You might even
have some clarifying questions that could help the project become better.
That is also a contribution.

Secondly, look for areas that are not well covered.  On many open source
projects, too many devs are writing too much code with too little
documentation.  That is true here as well.  Once you understand the
features and functions and the structure of the code, can you help with
some small piece of documentation?   ... we need people digging into
specific areas that are in the code and documenting what is there.  That
might also involve more test coverage in Cucumber (Gherkin files).

Third, you might  look at the really old jira tickets, and validate one by
one that the tickets are still needing to be fixed.  We have hundreds of
old tickets that have creation dates before 2022 and I strongly suspect 90%
are no longer valid.  This is tedious work, but is needed.  Pick a ticket,
read it, determine if it seems real, put a comment that "yes, verified as
of github checkpoint xxxx-xxxx" that the issue still exists" or "no,
verified as of ... that the bug ticket is no longer valid".

Generally, contributors should come with very modest aims at first.  This
is a very complex project.

James

On Sun, Nov 24, 2024 at 3:30 AM Sarthak Deokar <de...@gmail.com>
wrote:

> Hi,
>
> I am also suffering the same issues hope we could connect and work together
>
> Regards,
> Sarthak Deokar
>
> On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com> wrote:
>
>> Hi everyone,
>>
>> I’m Akash, a new contributor to Apache Fineract. I have experience with
>> Java, Spring Boot, and building REST APIs. I’ve successfully set up the
>> project locally, including database connections, and have explored the
>> Swagger documentation.
>>
>> I couldn’t find any "good first issues" or beginner-friendly tasks on the
>> GitHub Issues page. Could someone please suggest a task or guide me on how
>> I can get started with my first contribution? I’m particularly interested
>> in working on APIs or improving existing features.
>>
>> Looking forward to your guidance!
>>
>> Thanks and regards,
>> Akash
>>
>

Re: Guidance Request for Contribution to Apache Fineract

Posted by Sarthak Deokar <de...@gmail.com>.
Hi,

I am also suffering the same issues hope we could connect and work together

Regards,
Sarthak Deokar

On Sun, Nov 24, 2024, 13:08 Akash Nadar <ak...@gmail.com> wrote:

> Hi everyone,
>
> I’m Akash, a new contributor to Apache Fineract. I have experience with
> Java, Spring Boot, and building REST APIs. I’ve successfully set up the
> project locally, including database connections, and have explored the
> Swagger documentation.
>
> I couldn’t find any "good first issues" or beginner-friendly tasks on the
> GitHub Issues page. Could someone please suggest a task or guide me on how
> I can get started with my first contribution? I’m particularly interested
> in working on APIs or improving existing features.
>
> Looking forward to your guidance!
>
> Thanks and regards,
> Akash
>