Two new projects were started - OpenTaps and Moqui. Speaking personally (and I stress personally - I'm not speaking on behalf of the OFBiz community) that sort of thing is counter-productive. I know the authors of both of those projects and I consider them friends. I'm also very familiar with the projects themselves.
It's easy to just scrap existing code (or an established community) in frustration and start another project. It's hard to find a migration path that continues to embrace new technologies without causing undue hardship on the existing installed base. It would be better if we could find a middle ground - a compromise - that keeps the talent and innovation in a single project, instead of scattering it into competing projects. -Adrian --- On Thu, 1/20/11, Brian Topping <[email protected]> wrote: > On Jan 20, 2011, at 9:02 PM, Adrian Crum wrote: > > > --- On Thu, 1/20/11, David E Jones <[email protected]> > wrote: > >> What the project needs is cutoff points at major > revision > >> releases after which attempts at backward > compatibility are > >> totally abandoned in favor of making something > better. > > > > Why don't we discuss that further? Perhaps in a new > thread? > > Naive question, but has it ever been considered to put the > existing system in legacy mode and start a new > project? One of the attractive aspects of OFBiz is > it's very comprehensive. One of the difficult aspects > is it doesn't take advantage of any recent packaging > technologies like Spring or OSGi or presentation > technologies that would work well with recent browser > capabilities. I can't imagine that the optimal > solution remains one that was architected before any of > these technologies were mature. > > Brian
