On Tuesday, September 14, 2021, Awasum Yannick <[email protected]> wrote:
> > > Hi Saransh, > > > On Tue, Sep 14, 2021 at 10:45 AM Saransh Sharma <[email protected]> > wrote: > >> Fineract CN as of right now has not been improved and looks like it’s a >> stale project with no commits and work on it. >> >> For a long time no one contributed changes to Fineract CN, but over the > past few months, Avik, Manoj and Victor have been contributing code based > on a project they implemented in Mexico. Thank you all for those > contributions so far. > I remember this email coming from victor but so far have you seen or merging any PR related to the work! > > We probably need more hands on deck to review, understand and document > these new changes as it arrives. > Understood but before that we need to work on the overall change of the architecture that needs to be submitted to the Apache Awasum would you like to help in drafting this report since your are part of the PMC ? > > I tried submitting my talk about Improvement proposal but got rejected >> 🙅‍♀️ >> >> So state of the project is quite dark unless we swiftly act on it and >> improve the overall condition. >> > > Fineract needs contributors to step up and make the code better. > > How do you contribute to Apache Fineract and Fineract CN? > > 1) Discuss with the community on what you like to change. Open, polite and > frank discussions. > 2.) Create JIRA issues and Confluence specs on your change proposals. > 3.) Submit PRs to Apache Fineract 1.x and Fineract CN repos. And wait for > review. > 4.) Document how end users can use your features on Apache Wiki etc or > Apache Github. > I presented a solution , I can submit more documentation , but how do I create an issue of overall architecture change of the product I think before all of this it needs to be discussed with all the stakeholders ! > >> >> On Tuesday, September 14, 2021, James Dailey <[email protected]> >> wrote: >> >>> Devs - I will, shortly, be posting the results of the survey that we >>> took in late August. A bit delayed. >>> >>> I wanted to share that I am going to be giving a "State of the Project" >>> talk at ApacheCON next week and I would like your input into that. >>> ApacheCON is the annual conference that this year is again online. >>> https://www.apachecon.com/acah2021/tracks/. Register today! >>> >>> To help me with my REPORT OUT: Please feel free to share observations, >>> criticisms, concerns, as well as compliments to specific contributors. >>> Please either respond on list, or email me directly. >>> >>> If you or your company is engaged in developing new features and wants >>> to be mentioned, I would like to highlight that. >>> >>> There is much to celebrate and I am very grateful to all of the >>> contributors this past year. >>> >>> Thank you, >>> - James >>> >> >> >> -- >> Saransh Sharma >> Research Partner >> >> Sent from my phone >> This mail is governed by Muellners® IT policy. >> The information contained in this e-mail and any accompanying documents >> may contain information that is confidential or otherwise protected from >> disclosure. If you are not the intended recipient of this message, or if >> this message has been addressed to you in error, please immediately alert >> the sender by reply e-mail and then delete this message, including any >> attachments. Any dissemination, distribution or other use of the contents >> of this message by anyone other than the intended recipient is strictly >> prohibited. All messages sent to and from this e-mail address may be >> monitored as permitted by applicable law and regulations to ensure >> compliance with our internal policies and to protect our business. E-mails >> are not secure and cannot be guaranteed to be error free as they can be >> intercepted, amended, lost or destroyed, or contain viruses. You are deemed >> to have accepted these risks if you communicate with us by e-mail. >> > -- Saransh Sharma Research Partner Sent from my phone This mail is governed by Muellners® IT policy. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
