7
XOOPS certified modules...
Can we discuss about a QA process for un-official modules as well?
People blame Microsoft for making a very insecure and unstable OS. In reality, OS itself is pretty stable (NT family kernel was designed by same person who designed Digital-UNIX). The operating system is well designed and has great support for muti-threading and other basic stuffs; still it is one of most unstable OS.
The real problem with Microsoft is that they exposed very powerful APIs but had no control (until recently) over how other vendors were using them. Most of the problems were in device-drivers; bringing down the server. Starting from Windows XP, Microsoft finally started driver-certification process which is pretty successful. As a result Windows XP (and family) became much more stable than.
Moral of story is:
Xoops core team should also take responsibility of mentoring and reviewing all XOOPS module development effort. When someone says that his XOOPS site is slow, that is mostly because he is experiencing some in-efficient module. But ironically, this blame mostly goes to Xoops.
In my free time I sometime walk through XOOPS core; and many times I reported any possibilities of improvement via Sourceforge tracker. As a whole my feedback for XOOPS core and official modules is pretty good. Good work team !!!
Many third party modules are also very well written. I appreciate all of their efforts in making this open source project successful. Can we put some effort to improve quality of whole community, not just XOOPS core? 'XOOPS Module Development Forge' is a great effort in this line but what about QA and code-review?
Please discuss it for welfare of whole XOOPS community.
Sudhaker Raj
............
Check on their homepage - 
Check 
