Hi everyone,

I am not sure where to post this comment. but here it goes.

I think there should be a Modules Teem created to handle things such as:
- module security auditing,
- integration of scripts as modules,
- take over abandoned modules
- officially introduce modules as safe to use by the community which will bring more credibility to the XOOPS script as well.
- Take over the management of the modules repository.
- Work with developers to encourage them to make use of existing frameworks and make use of other existing modules incorporating as much re-usage of code instead of everyone re-inventing the wheel. I see drupal cms does this a lot.

as it is now, I can't see us getting anywhere with most of the modules, for my part I have identified modules for my site but feel uncomfortable opening my site to the public since nowhere can I see a list of security validated modules, I want my site to be a reputable one, and of course their is nothing secure in this world.

But at least there should be a Team to audit modules and to work along with developers to help make their modules security compliant. I can see this needs a couple of people for this team, the CMS core development team I don't think can handle all this on their own.

What do you all think?

my 2cents here.

BTESEC

We are currently working on creating a "Module Team" as discussed in the Proposal:

https://xoops.org/modules/mediawiki/index.php/Draft_Proposal_Team

some of the tasks defined were:

* Maintain a module development forge as a collaborative work facility for community module developers.
* Maintain a high-quality repository of completed modules, addons and themes for distribution to the XOOPS community in cooperation with other work groups.
* Create and maintain module packs for different applications of XOOPS including a standard pack to be made available for download with the core XOOPS distribution.
* Publish and maintain documents outlining module design specifications, best practices and security/quality assurance standards.
* Assist in the training and development of emerging module developers for the XOOPS Project
* Assist in preparation of documentation concerning module development, in partnership with the Documentation group.
* Establish dialog to identify the most desired modules sought by the community.

Your ideas would be a nice addition to team objectives/goals!

Now, we'll need a lot of members who would like to help us with that. Those who would be interested to help, please PM me.

Quote:

We are pretty much finalized organization of the Module Catalog. Over the next couple of weeks we'll be adding the modules to the repository.

Now we need help from XOOPS members to start testing the modules and providing us with feedback. Please let us know who would be interested in joining the Modules Team.

I would be more then happy to help.

Fantastic!

Burning is working now on creating catalog of Modules that work with 2.3.x:

http://www.babylonbyxoops.net/

so this would be one option.

Which area would you like to help?

I can help with any documentation you may need, I'm intermediate in PHP and MySQL, or can work on testing. So whatever needs the most attention I can start on.