Apr 22, 2024 at 4:56 AM Abhinav Sinha
> wrote:
>
>> I’ll provide an update by the end of the week.
>>
>> Thanks,
>> Abhinav
>>
>> From: James Dailey
>> Date: Sunday, April 21, 2024 at 7:32 PM
>> To: Abhinav Sinha , dev@fineract.apache.org <
>
Apologies, for the delay. I’ll look into it this weekend and send an update
here by Monday.
Abhinav
From: James Dailey
Date: Friday, May 31, 2024 at 12:07 PM
To: Abhinav Sinha , dev@fineract.apache.org
Subject: Re: New contributors guide (need your suggestions)
Abhinav - Can this be
> Date: Sunday, April 21, 2024 at 7:32 PM
> To: Abhinav Sinha , dev@fineract.apache.org <
> dev@fineract.apache.org>
> Subject: Re: New contributors guide (need your suggestions)
>
> This was an excellent start. What’s the status?
>
> We really need better onboarding
I’ll provide an update by the end of the week.
Thanks,
Abhinav
From: James Dailey
Date: Sunday, April 21, 2024 at 7:32 PM
To: Abhinav Sinha , dev@fineract.apache.org
Subject: Re: New contributors guide (need your suggestions)
This was an excellent start. What’s the status?
We really need
;
>> Abhinav
>>
>> From: James Dailey
>> Date: Sunday, March 3, 2024 at 8:08 PM
>> To: dev@fineract.apache.org
>> Subject: Re: New contributors guide (need your suggestions)
>>
>> Could you highlight the outdated information in some way in
>> t
n fix the remaining
> issues incrementally. But, I would defer to you.
>
> Abhinav
>
> From: James Dailey
> Date: Sunday, March 3, 2024 at 8:08 PM
> To: dev@fineract.apache.org
> Subject: Re: New contributors guide (need your suggestions)
>
> Could you highlight the ou
@fineract.apache.org
Subject: Re: New contributors guide (need your suggestions)
Could you highlight the outdated information in some way in the documentation?
Or put in a jira ticket?
I think we want to move forward incrementally.
Are you suggesting we do this PR first and then continue to work on it
Date: Tuesday, February 27, 2024 at 11:03 AM
> To: dev@fineract.apache.org
> Subject: Re: New contributors guide (need your suggestions)
>
> Thanks Abhinav
>
> On Tue, Feb 27, 2024 at 9:38 AM Abhinav Sinha
> wrote:
>
>> I agree with your point- removing redundant doc
@fineract.apache.org
Subject: Re: New contributors guide (need your suggestions)
Thanks Abhinav
On Tue, Feb 27, 2024 at 9:38 AM Abhinav Sinha
mailto:abhinav7.si...@gmail.com>> wrote:
I agree with your point- removing redundant documentation is going to help a
lot. So I’ll extract most of the informat
hread with my changes over the weekend. Thanks for the
> suggestions!
>
>
>
> Abhinav
>
>
>
> *From: *Aleksandar Vidakovic
> *Date: *Monday, February 26, 2024 at 8:09 PM
> *To: *dev@fineract.apache.org
> *Subject: *Re: New contributors guide (need your suggesti
Vidakovic
Date: Monday, February 26, 2024 at 8:09 PM
To: dev@fineract.apache.org
Subject: Re: New contributors guide (need your suggestions)
... I would keep the README as short and generic as possible and refer to one
source of truth to avoid frequent updates. The README contains in its current
form a
f duplicate information.
>
>
>
> Abhinav
>
>
>
> *From: *James Dailey
> *Date: *Monday, February 26, 2024 at 3:03 PM
> *To: *dev@fineract.apache.org
> *Subject: *Re: New contributors guide (need your suggestions)
>
> A lot of people expect the readme. If
I can update the current README to point to the asciidoc. Also, clean it up a
bit – so that it doesn’t have a lot of duplicate information.
Abhinav
From: James Dailey
Date: Monday, February 26, 2024 at 3:03 PM
To: dev@fineract.apache.org
Subject: Re: New contributors guide (need your
ciidoc module now.
>
>
>
> Thanks,
> Abhinav
>
>
>
> *From: *Aleksandar Vidakovic
> *Date: *Monday, February 26, 2024 at 10:58 AM
> *To: *dev@fineract.apache.org
> *Subject: *Re: New contributors guide (need your suggestions)
>
> ... @Abhinav why not add i
That makes sense Aleks! Thanks for pointing that out. Moving it to the Asciidoc
module now.
Thanks,
Abhinav
From: Aleksandar Vidakovic
Date: Monday, February 26, 2024 at 10:58 AM
To: dev@fineract.apache.org
Subject: Re: New contributors guide (need your suggestions)
... @Abhinav why not add
e development environment setup instructions.
>
>
>
> Thanks,
>
> Abhinav
>
>
>
> *From: *James Dailey
> *Date: *Saturday, February 24, 2024 at 8:59 PM
> *To: *dev@fineract.apache.org
> *Subject: *Re: New contributors guide (need your suggestions)
>
> Ab
include
the development environment setup instructions.
Thanks,
Abhinav
From: James Dailey
Date: Saturday, February 24, 2024 at 8:59 PM
To: dev@fineract.apache.org
Subject: Re: New contributors guide (need your suggestions)
Abhinav - Great initiative and much needed.
The Apache Software Foundation
Abhinav - Great initiative and much needed.
The Apache Software Foundation (ASF) adage is: "If it didn't happen on the
list, then it didn't happen."
if you're going to point to a slack channel, remember to point to the
Apache Fineract channel ==> https://the-asf.slack.com/archives/C4QPZURQQ
an
Hi,
I am working on a new contributors guide for the Fineract project.
The idea is pretty straightforward – it’s going to be the first link any new
contributor to Apache Fineract can visit, and it will have everything they need
to get started.
We have a lot of good documentation scattered acro
19 matches
Mail list logo
