Many good points in many directions have been made here. What I'd like to suggest is that someone (kcomaz, maybe, or original poster) put together a compendium of what has come out of this discussion, open a new topic with that compendium so we move towards closure on these things, post a link to the new topic and close this topic so no more posts can be made here.

I'd also like to propose that as something we do on topics like this. Especially because topics like this become divergent and need to be started anew somewhere else, and it becomes hard to keep track of the changes, and very old topics get dredged up where agreement (or apathy) eventually came. Things we agree upon will naturally die out. The newer topics arise better in the searches, too.

Anyhoos, just a thought. Once agreement is made, it probably belongs in documentation somewhere.

I thought this is hammered out.

The Community Coordinators will be going through the forums looking for issues that are not being fixed by the community. The Coordinators will then take ownership of that issue, and move the thread to XOOPS Bug Report or similar forum, The coordinators will then work with the customer to collect all the required information:

XOOPS Version:
Module Name/Version:
PHP Version:
MySQL Version:
Web Server Software (Apache/IIS/Other):
Operating System:
Theme you are using:
Custom template: (Yes/No)
Debug info. When posting any debug messages please 'wrap' the message like this:

Debug message here


A full description of the issue, please indicate how the issue can be reproduced:

Once all this information has been collected, it will be posted to the bug tracker on SF.net

The developer working on the bug should post weekly if not daily updates to SF.net The Coordinator will repost the updates on the thread with the issue.

Once the issue has been resolved, The developer will post it to SF.net. The coordinator will take resolution and deploy it per the developer's instructions and confirm the issue has been resolved. Once the issue has been resolved. the thread will be locked by the coordinator that opened it.
The issue and the resolution will be submitted to Xi tracker form for documentation. Once the issue/resolution has been documented, the thread will be deleted.

This was the process agree upon, thus, it is the one that is gong to be documented.

KC0MAZ