Hi James, This is great work. The survey reveals ways we can improve Apache Fineract.
On Thu, Sep 23, 2021 at 4:20 PM James Dailey <[email protected]> wrote: > [Reminder - please stay on thread] > > RESULTS: On Tuesday this week I gave a talk at ApacheCON about a few key > themes. One of those was a discussion of the recent Survey that I > advertised here on dev. > > > https://cwiki.apache.org/confluence/display/FINERACT/Survey+Results+-+2021+August > <https://cwiki.apache.org/confluence/display/FINERACT/Survey+Results+-+2021+August> > > A few key things jump out at me: (commentary). > > 1) We have a growing number of people who are here (nearly 30%) because > of their workplace. They have been introduced to the project due to where > they work. > I believe this is a sign of a maturing project. > Caveat: Since we did not ask this question before in exactly this way, we > will need to ask it again in a year or two to find out if this is a real > phenomena. > This has been true for a long time I think. I got introduced to Apache Fineract while at my day job in 2015. This means we should engage more with companies building on top of Fineract as we have always done to encourage more contributions. > > 2) n = 41, which is exactly the number of Committers on the project. > Coincidence?!? > or a sign that we're getting a good sample of engaged people? > Next time I will ask if respondents are Committers or members of PMC. > > Yes, we should ask people if they are PMC members or committers. I think more non committers or non PMC members have contributed to this survey. > 3) Despite not having a formal release out, fineractCN is being used in > production, and (for obvious reasons) clearly forked by a fairly high > percentage of respondents. While fineract1.x is still dominant, the use of > FineractCN by 22% of respondents is super interesting. > > Fineract CN is a good proposition for companies with the finances to hire good developers and sophisticated DevOps teams at the moment. The next goal is to try to optimize and adjust Fineract CN and make it easy to deploy and easy to make changes. This requires very good Engineers and time. I think we will get there. > 4) Related, and a sign of a healthy community, about 50% of the > respondents said that they would be interested in helping with fineractCN > despite a lower percentage actually using it and knowing what changes it > entails. That seems like a vote for Community! It also suggests a > strategy: let's find out what those forks are doing, what domains, what > features? [new thread to be started, related to Architecture working group > ] > > 5) We asked where "your customers are located".... meaning if you are an > integrator or working for one, where are your implementations. Africa > region #1, Americas #2. See the results. > > Please feel free to comment here. Please stay on thread... i.e. it should > be about what the survey is telling us, not some other thread. > I am interested to see more details on the blocker which community members face when contributing code or docs to Apache Fineract 1.x as well as Fineract CN. Do you have larger and clearer images of the survey result analysis? like the one below: [image: image.png] > Thanks > @[email protected] <[email protected]> >
