It is VERY simple…
Business Use Case Advice
Features are started with noble goals, but they are never brought to the full force of their perceived intent. Business users make up the apparent intended target user base, but unless they are also coders, they cannot begin to continue to expand a weak feature into a robust option.
Take for instance the Manufacturing module. For years it has been just a simple and scaled down implementation of what is really needed. There is no ability to manage lengthy work order and build processes, there is still no functional scarp management function that does not require an accountant level permission to get involved to right the books, there are other numerous missing pieces to this module that other less friendly (and open source) projects have been able to do better or at least more.
There are other modules that began as feature additions that never get finished. With only the skeletons of features ever existing, businesses get frustrated with the lack of power and useful functions.
It is those voices that need to be heard in order to have the developers take notice and finish what they started with some of these “features” that never really amount to anything useful in a business setting.
It is the culture of the project that is forcing the frustration of the business community and turning them toward other business management solutions.
ERPNext should and could be the proper business management solution if only it could finish some of the feature projects it started years ago. The need for scrap management in manufacturing has been on the github radar for over 3 years. it never got any attention, but tons of other new features get plenty of attention (even if they too are never finished).
This COULD be a revolutionary project if it changed it focus away from developer tinkering and into better solving business problems. Sadly the people that are best equipped to help the project in that direction (business users) are not coders, so nothing ever happens to improve the business use cases.
This is about as “specific” as anyone can get about the kinds of contributions you actually need to improve this project.
- The barrier is we are not coders!
- we cannot read and understand the code to make documentation
- we cannot understand the framework for making the system do what we need it to do becasue we are not developers
There are the barriers! You only need to start asking the same question that started this whole thread. “What would you like to see?”
NOT “What can users code to make it do what they want?”
The barrier is the coding and the importance the project managers put on that as being a valid voice in the improvement of the overall project.
If you only talk to coders, then you only get code challenges and code portfolios that get used to promote the coders themselves in other projects rather that actually help THIS project gain business use. How many developers have cycled through he ranks of the frappe/erpnext team, doe their pet project contribution, and moved on? It is the coder only culture of the project that creates this phenomenon. They do a skeleton of a feature, get it merged, then go away to take what they learned to some other project where they will turn the skills into something fuller and more useful.
If you start to actually have developers ask what the business community needs and them code to those needs, you will have a far better and more prestigious project. You will also finally get the attention of the greater business community to become users.
If you want to greatly expand the paying user base to your own hosted services, then you must attract them with something they want. They do not want boastful features that turn out to be very incomplete. You get there by focusing on the business owners needs and not your coding desires.
Just my opinion. Some say that opinions are like rear ends. Everybody has them and the all stink. But since you ask for specifics, I presented them here.