26
This is ridiculous conversation.
As a community we should be MUCH more angry at folks who take XOOPS and build proprietary code around it then NEVER give back to the community. Those are the folks that piss me off.
AMS uses a GREAT model. Why? Because it speeds up the development cycle AND code gets released back to the community for forking and/or development.
Why is this necessary? Why can't we just wait around for "free modules"? Because development cycles for opensource software (with the exception of OpenOffice, Linux, and Mozilla) suck. XOOPS has a great track record for the core - but module and theme development only go in spurts. Why have I been waiting a year for WF-Sections? Why do we NOT YET have an effect shopping cart, or a good newsletter system? The list goes on...
No offense...I love Xoops, but that's the reality. AMS solves that problem buy allowing interest parties to "buy into" the cycle and hence expedite it.
I have developed some simple modules but I'm not a real coder. To get stuff done that I need done ... NOW ... I have to hire the talent. Is it so bad to ask, "Hey anybody want in with me to get this done fast?" Not in my opinion - especially if the code is released back.
As a business running XOOPS I just want to know how I can speed things up.
The IT-HQ guys are doing the same thing. Saying look - I'm willing to pay for this and release it back, if you want to support development and get the release a bit early then you win. If you don't and want to wait - that's cool too - it'll be out in a couple months.
Regardless - I'm pushing for a XOOPS incubator to codify this process for business critical needs.
https://xoops.org/modules/newbb/viewtopic.php?topic_id=31535&forum=11&post_id=137700#forumpost137700
Really folks - XOOPS is an AWESOME CMS. Let's support great development, not discourage it.
Play on,
Dan