I would like to give a grant worth 2000 US Dollars if someone from the community is willing to develop a generator using NodeJS or Jhipster to make a microservice and its boilerplate.
The desired results for the payout 1. A generator that issues a command line and uses the existing project codebase from Jhipster or something like that. 2. This generator should be able to generate microservices that can be connected with existing Fineract CN and its structure should be like the template. 3. One should be able to follow commands like create new app , upgrade app. 4. Lets keep the existing command lines that are supported by Jhipster, that will be useful. I can make this payout by the help of PMC who will review the code and its implications are as follows. That any developers/PMC can upgrade the existing codebase then it's a success. Let me know your thoughts. On Sun, Sep 26, 2021 at 3:03 PM Awasum Yannick <[email protected]> wrote: > > Please continue the discussion here. > > On Sun, Sep 26, 2021 at 9:15 AM Saransh Sharma <[email protected]> > wrote: > >> Hey, >> >> Myrle thanks for sharing his profile and his work. I am not denying and >> closing my eyes from your work and his work. The idea is pretty wild that >> we are proposing, I think it needs a different setting and perhaps context. >> >> I think, so tell me, If i have to contribute to the project in terms of >> changing something from the ground up, how should we do that? How do we >> find out that there are some technical limitations to the existing project >> That does not mean you did not do a great job. I would like to point this >> out, this is an effect of time things improve. >> >> Alexander, refer to last year discussion that we had at the Apache Con >> about Improvement Proposal, our story was based on an individual, not any >> group, it was about solving problems related to development. >> >> For an eg: We have done some work on the generators that automatically >> generates boilerplate for Fineract CN templates saving time for developers, >> but the problem is where do we make this PR since there is no repo that >> matches the idea. (I mean give us the repo / or should we just make a PR on >> the template?) >> >> Does this sound disrespectful to you? A generator that generates code >> templates and services to run a functional piece of code. It can create a >> new application, insert another small sub-logic service or update the >> application. >> >> Another instance is of a set of libs that come with Fineract CN, they >> need to be maintained alongside and is a burden for especially developers >> and the community, why don't we make the project lightweight, leaving some >> choices to the developers (there are many libs that do the same work and >> maybe battle-tested already, why re-invent the wheel) >> >> > Here is a Fineract CN Template Defined at the beginning of the project: > https://github.com/apache/fineract-cn-template > > It has the structure to guide developers when creating new microservices. > Is that what you want? > > >> As Giorgio pointed out above that we need people or PMC who have >> developed Financial products, that may understand the value behind using a >> mix of toolkits. I think maybe our communication was vague according to you >> some say so, but there are some who do not see it that way. we have a >> division. >> >> So, I request that we close this thread and move on and work on further >> points that, I have highlighted. >> >> and Alex I think we have backwards compatibility and it actually has been >> tested out, that's why we are proposing changes on the top of the Fineract >> CN, these changes are add on and if someone wishes to use them in the true >> sense of microservices. To add real innovation, we should move towards a >> distributed architecture that allows smart contract deployment then we will >> truly have marketplace of business logic and value that could flow from >> Fineract CN. >> >> PS >> We are here to give grants related to the Fineract CN work ,reach out we >> could get you started on the above points. >> >> >> On Sun, Sep 26, 2021 at 12:37 PM Myrle Krantz <[email protected]> wrote: >> >>> Saransh, >>> >>> Wikipedia would have helped you on this one. Greg Stein is one of the >>> earliest members of the Apache Software Foundation. He was a long time >>> board member, including a board chair for five years. He is currently >>> working as Infrastructure Administrator for The ASF where he has contact >>> with all 200 project communities. I'm not certain, but he may not have >>> missed a single ASF board call for the last 20 years. Beyond that Greg was >>> VP of Subversion for several years, and he has made significant >>> contributions to the Python programming language. He is also one of the >>> incubation mentors for Apache Fineract. We elected him into that role in >>> part to guide us on implementing the Apache way, and we were *honored* that >>> he chose to serve our community in that role. >>> >>> Basically: you just told someone who played a significant role >>> in defining the Apache Way as part of his life's work, that he doesn't >>> understand it. Hence his reaction. >>> >>> Best Regards, >>> Myrle Krantz >>> >>> https://en.wikipedia.org/wiki/Greg_Stein >>> >>> >>> On Sun, Sep 26, 2021 at 2:23 AM Greg Stein <[email protected]> wrote: >>> >>>> On Sat, Sep 25, 2021 at 08:13:54PM +0530, Saransh Sharma wrote: >>>> >... >>>> > Greg, seems like your understanding is limited, community over code >>>> is the >>>> > Apache way. >>>> >>>> Hahahaaa.... This is one of the funniest things I've read all week. >>>> >>>> Thank you for the laugh, >>>> -g >>>> >>> >> >> -- >> 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.
