Indeed, doing cleanups in the data model is a major feat requiring awareness, focus and coordination. But not putting these improvement issues on the docket (roadmap) will ensure that the suggestions (discussion items) done in this thread will be overwhelmed by other threads and keep recurring as discussion topics not addressed. But also the perception of (potential) organisations, that investing in (the implementation of) OFBiz is a valid option, will wither and die.
After incorporating these improvement issues in the roadmap, associated JIRA issues can be created to discuss impact in detail, increase awareness of impact and dependencies, and integration can be planned. In stead of muddling along on the path where we are now. If the community would embark on the endeavour regarding the cleanup the data model, services and ui aspects, it would warrant a new branch of trunk leading to new version of OFBiz. I believe that this could also recharge the community to interact more and even grow. Otherwise this project will not live long enough to celebrate a second decade. Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Sat, Jan 18, 2014 at 11:04 AM, David E. Jones <[email protected]> wrote: > > Doing significant data model cleanups and changes is a LOT of work with a > large code base and user community. All code that uses the data structure > needs to be changes, and accommodations are needed for deprecating the old > entity or fields and migrating data to the new ones. So yes, to the point > Jacques made, it's not likely short-term and without significant investment > and coordination with others in the community it is not really likely > long-term either. > > For years I built up a list of changes that would be nice to do in OFBiz > itself, but so many are not really feasible. There may still be some of > them worth doing, so for some ideas to consider here are my change notes > for the Mantle data model: > > https://github.com/jonesde/mantle/blob/master/mantle-udm/Planning.txt > > At this point there are lots of generic services and end-to-end automated > tests that use many of these changes to the data structures so they are > pretty well vetted and validated and not just theoretical like when this > thread started a couple years ago. One of the benefits to many of these > changes is that not only is the data model smaller and cleaner, but it > makes it possible to simplify or eliminate large amounts of logic layer > code. > > For OFBiz, along the lines of the reasons mentioned above, that would > involve quite a few code changes but maybe the best way to look at it is > that this is the main reason to do the data model changes (ie simplifying > and eliminating code) as opposed to just changing the data model for the > sake of the data model itself. > > -David > > > > On Jan 17, 2014, at 4:57 AM, Jacques Le Roux <[email protected]> > wrote: > > > I think it's still alive, but I bet it will not be short-term... > > > > Jacques > > > > On Friday, January 17, 2014 12:34 PM, [email protected] wrote > >> Is this subject still valid? And wouldn't it be great to have one (or > some) > >> of the subjects on the (short-term) roadmap? > >> > >> Regards, > >> > >> Pierre Smits > >> > >> *ORRTIZ.COM <http://www.orrtiz.com>* > >> Services & Solutions for Cloud- > >> Based Manufacturing, Professional > >> Services and Retail & Trade > >> http://www.orrtiz.com > >
