So you got your answer @max_morais_dmm
As far as @rmehta is concerned the way to get the community built is to provide fixes:
As you can see there is NO representation for your concept of:
This developer team does not have any non-coders and does not know how to respond to them. So, the only contributions that are considered are those that provide the code to fix an issue and all of the supporting documentation and testing to validate. That is it. That is all.
This sentiment has been expressed many times in the forum.
I am sorry max, but unless the make-up of the core team were to change, (or their ideals were to change) I do not see a way to have the non-coder community represented. This pretty much makes the ERPNext community a community of ONLY developers. I just think that distorts the the business viewpoint the project is supposed to enhance and support.
This is how open source projects become abandonware. If the target user is not involved in the design or upgrade aspects of the project, it tends to wander off on tangents that does not ultimately help the user base, but merely caters to the developer whims. This is likely how we end up with tons of new features and really no in-depth work to fully develop any features beyond their initial introductions.
Once a developer has checked the new feature off their bucket list, they look for the next feature challenge to build out their portfolio of developer accomplishments. Nobody goes back to actually build any real-world use cases into the skeleton of a feature left behind after it is first introduced.
I contend this is the EXACT same thing that @rmehta describes here:
The difference is that it is the very developers that claim to be burned that are in fact burning their users in much the same way. They develop only the beginnings of a feature and get it into the core, then never revisit it. IT is left there to give false hope to a user community that it will ever become a full feature.
How is that any different form the complaint that developers are unable to support fixes that the PR submitter have no “log term commitment to” ??
In my estimation it is exactly the same thing. It just depends on which side of the ever widening abyss you happen to be standing on.
This is why @max_morais_dmm I question the viability of enhancing the user community. It will always be met with the retort of “Provide PR fixes that are ready to merge in order to contribute.”
That has always been the answer, and that has always set the parameters for the growing abyss.
Non-coders need not apply.