I guess no War of Independence would happen. I can't remember Mel Gibson reported to anybody in Patriot.
I can trust anyone in PMC. OFBiz itself is a brand like a commercial software. Why do we need a release version? What we really need is a predictable vision if OFBiz is our core platform of our business. For example, we also use OpenCms as our core platform. We developed an OpenCms-LDAP module and we don't want it to be a part of OpenCms as it's not perfect. But it's useful, 在 2008-11-15六的 16:36 -0500，David E Jones写道： > On Nov 15, 2008, at 4:27 PM, David E Jones wrote: > > OFBiz is not commercial software with paid developers. JBoss may be > > available under an open source license, but it is developed under a > > commercial model, not a community-driven model like OFBiz. > > > > In the case of a community-driven software project, what would a > > project manager do? Who would he/she boss around? Who would be > > accountable for delivery and how would that accountability be > > enforced? > I guess no War of Independence would happen. I can't remember Mel Gibson reported to anybody in Patriot. I can trust anyone in PMC. OFBiz itself is a brand like a commercial software and clients should be able to trust. People do trust open source now. (ad, you can skip this) We are offering technical support to T-Systems China on BMW Web Hosting, the website of BMW China and worldwide is built on Linux, OpenCms, Tomcat and Mysql, all are open source, except some functions developed by Interone. Open source is not a problem any more. Is community-driven model a problem? If yes, I would suggest CHANGE. > I hope I'm not getting into revisionist history, but my experience > with community-driven software so far is that if someone does propose > something and try to recruit others to work on it then it usually > fails. Generally the champion of the effort has to work on it > themselves, and keep working on it until others start _using_ it, and > then they will get involved with improving and extending it. It's just > that simple. > > Personally I know I've left a wake of unfinished projects where I > tried to recruit others and identify a goal to work towards, like the > framework improvements and framework-only release (a starting point > for higher level releases, something easier). As soon as I got > involved in increased workload, moving, and organizing and preparing > for ApacheCon and such I stopped working on it... and so did everyone > else! > > With new things I'm trying to push, like adoption of open standards > and building some requirements and designs that we can base future > enhancements and extensions of OFBiz on, my plan is to work on them > personally as much as I can and do so until others join in. > > That's how things get done in community-driven projects: by > leadership. That's how everything in OFBiz has been done. Someone lead > the way, and others joined in... hundreds of times in the last 7.5 > years on hundreds of parts of OFBiz. There is a big difference between > leaders and manager, and what self-organizing communities need is > leadership, not management. That's the meritocracy way. > > -David > Nobody would say OFBiz is not good. And it's not necessary to proof OFBiz is good. On the contrary, I think people (at least myself) need OFBiz promising. If you feel the project is hard to control (I know you don't like control, I believe you may not like out of control, then control it), it's a good idea to do the work as you said, narrow your efforts to framework-only, then the framework would play the role of tomcat project, OFBiz as the Jakarta, applications and specailpurposes as the subprojects (including the ex-subprojects) in Jakarta. In other words, if even you don't know what the next version of OFBiz would be, how could the others know? Versioning means promising, means roadmap, means you know, and then we know, everyone knows where we are going. Then the community can unit around you, and costomers will put resources into the real projects based on OFBiz (this is the key reason why I say too much here:)). Though my tone is not that kind. below are what we will open to the community for 2009 as a promising (all we promised for 2008 come to true): 1. Update OFBiz-jBPM component to jBPM 3.3.2 or later and OFBiz trunk. 2. Update OFBiz-LDAP-CAS to support LDAP membership and alias setting. 3. Develop OFBiz-SAML to support SAML(may not the latest SAML 2.0). 4. Develop OFBiz-OpenID 5. Update OFBiz-OpenOCES 6. Develop OFBiz-Lucene-SearchPipeline 7. Continue the OFBiz Chinese localization Regards, Shi Yusen/Beijing Langhua Ltd.
