My point was that people who contributed in the past have identified issues which when solved will make Fineract CN easy to develop. Here is one: https://issues.apache.org/jira/browse/FINCN-25
We should be focused on removing those blockers and still using the current Language (Java), Framework (Spring) and DBs until we get version one. On Mon, Sep 27, 2021 at 4:57 PM Saransh Sharma <sara...@muellners.org> wrote: > You see that;s what i mean the services consume a lot of memory because > you know and I know why? Right > > Anyway let's work together to pave a path, I am just trying to incentivise > people here who can maybe help. > > On Mon, Sep 27, 2021 at 9:22 PM Awasum Yannick <awa...@apache.org> wrote: > >> >> >> On Mon, Sep 27, 2021 at 4:42 PM Saransh Sharma <sara...@muellners.org> >> wrote: >> >>> Hey Awasum , I am just trying to incentivise the developers and >>> contributors here. I know that committers are not paid. That's a good >>> thing, let's keep it that way. >>> >>> I am not hiring a developer plus we are on a different thread, I think >>> we are just discussing the idea of how we can improve the project in terms >>> of making the libs small and introducing some form of automation so that >>> developers can go ahead and develop and maybe a release is possible. >>> >>> Have you ever tried running the fineract CN ? Go ahead and run and >>> perhaps you will know how hard and cumbersome it is to run the project and >>> even extend also at the same time Some might have done it but they have not >>> contributed back ! >>> >>> >> https://issues.apache.org/jira/browse/FINCN-25 >> >> >>> Now tell me since last 2 years did anyone out of the volunteer tried to >>> improve or upgrade the source code ? We tried at some level and found out >>> some issues coming up so we are here reporting them, have some patience and >>> please listen to them, nothing else >>> >>> You have highlighted valid tasks no doubt but again we are discussing >>> something else right now. >>> >>> Again you cannot decide for the community let community first >>> discuss and come to a resolve then we can say but sending such mails from >>> the likes of you does not go well with the community >>> >>> I request all that we are trying to communicate and discuss improvement >>> in Fineract CN at this thread >>> >>> BTW check Micahel email from last year, he clearly mentioned that it's >>> good to incentivise the developers and contributors after all the work is >>> going back. He also gave a boilerplate in his email on how to do that . >>> >>> Patience my friend ,Again dont jump on conclusion >>> >>> >>> On Mon, Sep 27, 2021 at 8:56 PM Awasum Yannick <awa...@apache.org> >>> wrote: >>> >>>> Hi Saransh, >>>> >>>> The Fineract PMC or Committers do not pay anyone here to do development >>>> on the Fineract codebase. The PMC does not manage a budget for developing >>>> Fineract. We are all volunteers here and contribute as individuals not >>>> companies. >>>> >>>> If you want to hire a Developer to do work on Fineract, then you have >>>> to manage that outside of Fineract. Hire someone at your foundation and >>>> define their role and get them to fix issues if you like. But they have to >>>> fix issues which the community wants and needs. >>>> >>>> If you want to do any of the tasks which I highlighted in my >>>> earlier email then go ahead. If you want to rewrite Fineract CN or Fineract >>>> CN, then fork the project and call it a different name and take the >>>> discussion to another forum and leave the majority of people here who >>>> believe in Fineract CN to stay on. You can even create your own new Apache >>>> Project if that is what you want.. Apache Incubator is there to guide you. >>>> >>>> The community at this time does not want to change the language, >>>> framework or architecture of Fineract CN at this time. We want to test, >>>> improve and release what is already available. >>>> >>>> >>>> >>>> On Mon, Sep 27, 2021 at 4:13 PM Saransh Sharma <sara...@muellners.org> >>>> wrote: >>>> >>>>> I don't know what this email means. I am not asking you to enter in >>>>> any kind of business with me? It's a grant Myrle, I mean it's not a >>>>> typical >>>>> business transaction. Grant from a non profit that could help developers >>>>> and contributors to work together nothing else ,I am not going to >>>>> influence >>>>> anyone in any way. >>>>> >>>>> Actually zero trust protocol aka Blockchain does help in such >>>>> transactions by the way , the idea that we need to trust someone is >>>>> already >>>>> flawed in many ways. >>>>> >>>>> I neve dismissed Sander; he raised an interesting point but I >>>>> highlighted why the point is no longer valid. >>>>> >>>>> Banking the unbanked by also a solution that the unbanked cannot >>>>> manage or use , that is what we are trying to solve. >>>>> >>>>> >>>>> >>>>> On Mon, Sep 27, 2021 at 7:46 PM Myrle Krantz <my...@apache.org> wrote: >>>>> >>>>>> So much wrong here, I'm just gonna skip to the end. >>>>>> >>>>>> On Mon, Sep 27, 2021 at 3:09 PM Saransh Sharma <sara...@muellners.org> >>>>>> wrote: >>>>>> >>>>>>> Ok , understood we can put more fire power once we get this rolling, >>>>>>> but if you look at the work I asked was to develop the Proposal not >>>>>>> actual >>>>>>> development, think that's a lot ? >>>>>>> >>>>>> >>>>>> Saransh, I do not trust you, and won't be entering into a business >>>>>> relationship with you already for that reason. But even if I did, your >>>>>> management approach here is completely wrong: you are trying to replace >>>>>> intrinsic motivation to bank the unbanked, or build a software >>>>>> architecture >>>>>> I can believe in, or (equally valid) build a business that I can own. >>>>>> You >>>>>> are trying to replace that intrinsic motivation with extrinsic motivation >>>>>> of $1500 and <handwave> blockchain. (Which, given the way you dismissed >>>>>> Sander, you clearly don't understand either.) I shouldn't need to tell >>>>>> you >>>>>> that that is... unlikely to lead to your own success. The people here >>>>>> have >>>>>> earned more dignity than that. >>>>>> >>>>>> Best Regards, >>>>>> Myrle >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thanks and regards, >>>>> >>>>> Saransh Sharma >>>>> Research Partner >>>>> >>>>> 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. >>>>> >>>> >>> >>> -- >>> Thanks and regards, >>> >>> Saransh Sharma >>> Research Partner >>> >>> 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. >>> >> > > -- > Thanks and regards, > > Saransh Sharma > Research Partner > > 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. >
