On Jan 22, 2007, at 5:28 PM, Jonathon -- Improov wrote:
Right off bat, you'll see some functionalities fully fleshed out (half-baked in mainstream OFBiz). You'll also spot (or not spot) many bugsfixes.For now, I'm just moving my boss' OFBiz along his requirements. But if you, like Ian, has a vision for fleshing out all "best practices" (commonly needed, "duh, why isn't it there" functionalities), then you are free (like Ian is) to submit issues (via Mantis) to me. Together, we'll:1. Round off all half-implemented concepts so newcomers don't have so many redherrings to deal with.2. Document all fully-implemented concepts so newcomers know that undocumentedconcepts are either not there or not fully there.The above is something David has clearly said he will not address (not OOTB-oriented).
That is simply not true. I never said I would not address it, and of course since the fact is that I am not OFBiz I should also make it clear that this is not the OFBiz policy. I never said we would not do something that works great OOTB, I just said that is not currently the focus of OFBiz given that we have to set priorities so that limited resources are best used, and that we have a sustainable model for growing and perpetuating the project.
Besides, for the 2 issues you mentioned above, what do they have to do with OOTB use orientation? Those 2 things sound a lot like exactly what we're doing in OFBiz right now...
So, it's open season for us. :) We'll be swimming in another pond, so David shouldn't mind.
This is true though. It is always open season for you. There are means for contribution and the more you contribute and get involved in the project the more we'll want to give you permissions so it is easier for us to work together.
I do stress that this isn't a fork of OFBiz.
Hmmmm.... if you're encouraging people to send you fixes and enhancements that are core to OFBiz instead of sending them to the main project, that sounds an awful lot like a fork to me...
If that's not a fork, what is?
I don't support dilution of open source resources (yes yes, in many cases it's simply necessary, and yes I do have my own fork of hibernated project phpMVC, even relatively active Mantis, and many others).(* military band starting to drum a march *)Some of us may be currently breaking off to handle smaller skirmishes (smaller clients who cannot afford non-OOTB, big customization projects); some will stay in fatherland factory to continue plodding along, serving the bigger (easier?) clients. I believe David will give his blessing to those of us who will venture out, who stick our necks out to take the horizons.
I don't see how any of this is necessary. To have a better OOTB experience we need feedback from users including bug reports, bug fixes, and enhancements as well. It sounds like this is mostly what you are proposing.
It sounds like what I wrote about applications well suited for real world OOTB use didn't make it through. The point I was trying to make is that generic user interfaces will never be well suited to all possible tasks. In order to create a true fully feature system to use OOTB you have to define a target audience, like a specific type of company to create a complete system for.
Lastly a quick question: why do you keep saying my name? What in blazes does ANY OF THIS have to do with me? I don't own OFBiz. I don't control OFBiz. I don't even implement most of what goes into OFBiz any more. I'm just a moderator trying to keep things flowing smoothly for the project and clarify to the best of what I can see what is and isn't a good idea. I can't force anyone to do anything, nor can I even manage and moderate every bit that makes it into the project. That just isn't realistic. This is why there is an organization and why we need more people involved with the project.
So, yes, you can create your own project and try to recruit people to it. I just hope you have a long term sustainable plan, direction, and scope for it.
-David
smime.p7s
Description: S/MIME cryptographic signature
