Let’s organize feature requests into 3 categories -
Framework Level
Domain/process Specific
Customer Specific
I propose to having a mechanism to address these separately.
For Framework Level - These include features that are core to the system, like addition of dynamic reporting (including charts ,groupings and BI), Improved customisations and other additions to bench, offline-online and multi-database sync capabilities, etc.
I think frappe team and foundation supported developers would be the best people to implement these. (of-course public beta like system to develop these will be great)
Domain and process specific Apps - One of the things I noticed at the conference and otherwise on forums is that there are a lot of users willing to contribute, only handicapped by their programming skills (myself included). I’ve been wishing for just this little more from the framework.
In my opinion ERPNext has great doctype and workflow capabilities. We are 90% there, but if we just add that 10% - A GUI like odoo/flectra studio or zoho app creator. We will definitely have a lot of contributions back from end users.
In manufacturing domain for instance - I promise to share and send back ISO/quality documentation & Reports, Maintenance module, training and skill matrix, Attendance! and more.
In fact we can get this “app-creator” (apologies for using the A word) online so that every app that is created on it, is published online for the community to comment and contribute to. Something similar to a wiki for module creators. Further enhancement of apps, if required for more complex tasks could then be taken up as public betas. This could then be integrated into the core.
You could think of this as an approach to enable the vast functional resource of the community to contribute back.
Customer Specific - ERPNext does this so well already! So as was said in the “scratch your own itch!”. And hopefully share your code using gist, etc.