71
Quote:
Quote:
Absolutelly yes.
Now the situation about this issue is:
1.- if you want support about any module you can:
- post here
- in the developer page
- in Module Dev forge.
It you have a suggestion, want report a bug or request a new feature...it is too much confuse and it is very possible that there is no feedback between users and module developer.
The Module repository is closed, and anyway is outdated.
The Module Development Team is not a Project Team, is out of here onhttp://www.xoopsmoddev.org/ and (ïn the future) in xoopsaddons.org.
There is a discussion about the new forums layout and where will be (here or in xoopsinfo.com).
Now look at drupal.org: in the forum there is no support about the modules; these are in a the home page, in a section, and each module has a section with excelent content: Date,Links, versions, Download, Release notes
Find out more, Bugs and feature requests.
It very easy find any module and all the neccesary information and support.
Wich are the problems here?
Xoops organization is confuse (what about community Teams?) and the people that could work in these and another questions have problems. We have lost very valuable people in the last months.
In the forums there are too much personal issues about the past; there are good ideas too, but in the end, lost.
You had post a very important issue; my opinion (look at drupal) could not be good. Other opinions could be better, any doubt. We can discuss about which is the better on modules repository, support, etc. But, castles in the sands
In my opinion, support should be made a priority for XOOPS and it's modules. Empowering users to effectively and successfully use XOOPS is what will drive the success of XOOPS and any XOOPS modules. If there is a significant portion of XOOPS members who become frustrated to the point of giving up on XOOPS or just putting out poor quality implementations of XOOPS, then that is going to have a very negative impact on both the public perception of XOOPS, and the future community support for XOOPS. With more users successfully utilizing XOOPS and its modules, there will be better public perception of XOOPS and more momentum and enthusiasm from the XOOPS community itself.
The key here is support! Developing an efficient and responsive support system for XOOPS and it's modules will be a major factor in driving the success of XOOPS. XOOPS will only be successful in the future if the people who use it are successful with it!
Quote:
The most successful open source products of the future will be the products that provide the best support. The support of a product is just as important as the programming code behind the product.
Absolutelly yes.
Now the situation about this issue is:
1.- if you want support about any module you can:
- post here
- in the developer page
- in Module Dev forge.
It you have a suggestion, want report a bug or request a new feature...it is too much confuse and it is very possible that there is no feedback between users and module developer.
The Module repository is closed, and anyway is outdated.
The Module Development Team is not a Project Team, is out of here onhttp://www.xoopsmoddev.org/ and (ïn the future) in xoopsaddons.org.
There is a discussion about the new forums layout and where will be (here or in xoopsinfo.com).
Now look at drupal.org: in the forum there is no support about the modules; these are in a the home page, in a section, and each module has a section with excelent content: Date,Links, versions, Download, Release notes
Find out more, Bugs and feature requests.
It very easy find any module and all the neccesary information and support.
Wich are the problems here?
Xoops organization is confuse (what about community Teams?) and the people that could work in these and another questions have problems. We have lost very valuable people in the last months.
In the forums there are too much personal issues about the past; there are good ideas too, but in the end, lost.
You had post a very important issue; my opinion (look at drupal) could not be good. Other opinions could be better, any doubt. We can discuss about which is the better on modules repository, support, etc. But, castles in the sands
