8
Quote:
Peekay wrote:
As a non-commercial organisation I can't imagine why those stats would be needed. Zen Cart has a similar link and also has automated upgrade notifications. I turn it off. I do not want my customers nagging me to upgrade their installation just because a newer version is available. I think XOOPS is great, but as numerous XOOPS upgrades have actually proven to be worse than the previous version, there is no way I would allow core or module upgrades to be determined by anyone except myself (following a thorough test).
This will be controlled, there will be a certification team for this system, that will test modules etc, before they can be certified, once they are certified and hashed then there will be a system where by people can install verified modules that are 'recommended' by XOOPS cert team.
Quote:
If xoops.org webmasters had ever taken any of the countless opportunities in the past to insist that module developers provide basic system requirements to get their module listed in the repository, the 'hit-and-miss' experience that is XOOPS would have been solved by now.
Do you want to hire a beta testing team to check modules completely?
Quote:
The idea of using an intrusive technology to make a suitability determination is unbelievable. You would spend time on that, rather than insisting that a developers puts 'PHP 5 compatible' if their module works with PHP 5?
Well modules will be tested before installed into the certification system, a team at XOOPS France, has developed a certification checklist for modules that people should publish here.. it would be good..
Quote:
The big flaw with that idea is that many (not just some) modules require modification to get them to...
a) Work
b) Validate
This is in the eye of the beholder I guess, I have had no problems with the modules, i have used, mind you that is not many, as the modules will be validated before installed into the checksum archived system XoopsCert which mind you will not disable the system or provide any form of limit wear, it is a system that will be able to eventually identify where changes where made in a module/core so a secondary party editing those modules can quickly digress where changes where made, and either fix or identify problems.
Quote:
You're proposing a service for simpletons that cannot FTP a few folders and press an 'install' button.
I was a simpleton once like you peekay not everyone is leet like you with your FTP client..
Quote:
IMHO, the thing that new XOOPS users lack most is a single official instruction manual (just one - on this website - not a WIKI or 20+ useful articles) and proper system-specs for modules.
Instead of complaining about it why don't you start documenting it, the problem is most people use the XOOPS site for a drop and run generics they don't edit or create a wiki page for there modules nor offer any support.
Quote:
Given that information, I am confident most users will have the ability to set things up by themselves without big brother's help.
Hey big brother was a kewl dream I had last night, I don't know what the government has to do with xoops, this is GNU...
