It is not the first time that this happen. The Comms Team worked too but now...The Doc Team started the jobs (in xoopswiki and xoopsinfo) but now the Council want take the control about documentation; results, no docs.

But the worse thing of everything is than valuable people finish tired which their work is not taken advantage of or are obstructed and they leave xoops. (the last Madfish).

Some people would like to work on their own sites of which they have full control instead of on the xoops.org If you have interest to help the Project, either on a specific area, or to improve the management, please contact the Project Council at xoops-council@googlegroups.com or contact me at phppp@users.sourceforge.net

a request to be allocated a private discussion forum at xoops.org has been denied. This forum is to be used as a team thinking room to thrash out things before seeking public feedback. It will of course mean that such discussions become a matter of record accessible to XOOPS Council. The team has commenced this discussions using email.

Some people would like to work on their own sites of which they have full control instead of on the xoops.org

seth_sd wrote:

I dont't question anyone's technical ability nor do I question their dedication but I do wonder what the direction is and how it can continue like this.

Seth

No one is arguing having a closed repository is a bad thing, we only are wondering about the change in protocol and lack of direction that brought about this change.

Welcome to the Official XOOPS Module Repository!
The Module Repository is the place where you can find many of the finest extension modules for your XOOPS powered website, conveniently categorised and available for download.

The XOOPS Module Repository is, like all parts of XOOPS.org, a community effort. The purpose is simple: to make as many (stable) XOOPS modules available to the XOOPS user community as possible. To that end, we only accept stable, non-beta modules and add a copy of the module release file to the SourceForge.net File Release System and ensure the primary download link points there, thus ensuring its availability to all.

There are three ways in which you can help us maintain the Repository:
· Write a review or vote on the modules you use.
· Add the latest version of your own module to the Repository;
· Make sure the existing entries are up-to-date.

Please Note:
The module repository is currently closed for new module releases as a new system is coming soon. In the mean time please select modules from here carefully. We recomend you use the search function to find the latest release of a module, as they can all be found in the news section.

Up to now, XOOPS has been distributed including a set of “official” or “core” modules. Soon there will be no “officialy” modules, that is, XOOPS will be offered as a framework or operating core, and XOOPS webmasters will decide what modules to install. There will be, on the other hand, a ReviewingProcess that will serve to identify modules built by xoopsers and that operate correctly under XOOPS framework. These modules will be marked with an “approved” seal and as such will have the XOOPS core team endorsement as secure to use in a XOOPS Web site.