I have recently got attracted to ERPNext, so keeping a low profile. Initially I thought this is just a wishlist of items for v9, which will help in creating the official v9 roadmap. However that doesn’t seem to be the case looking at another thread where community developers have already started working on the python migration(First Foundation supported Developer! - #10 by vrms). I can’t question the priority of python 3.0 migration, so merely trying to stress the importance of improving the process and communication. Sometimes we need to slow down in order to move faster later, especially while there are so many voices vouching for quality before features. Discussions take a lot of time, often feels counterproductive for many people. However that is essential when we are trying to scale-out the development with community help. Perhaps v9 roadmap is being discussed officially in community meetings, in which case it would really help to get a glance of meeting minutes.
I was in the recent code-sprint held at Kozhikode, so had the privilege to discuss the reasons behind merging healthcare to erpnext. While I understood the reasons to some extent, it also raised many more questions, like scale-out issues with same approach for other apps, unnecessary increase in upgrade times, stability, additional effort by the app team for merging, upgrades etc. Traditionally, in our design meetings, we used to have a table of advantages and disadvantages with priority for each item when it comes to deciding these things. By opening these discussions to wider community, we are likely to get more inputs which would help in taking decisions based on data.
1 Like