@ BlueStocking -
Thank you for your submission. I have directed it to those you might make use of it. I may want to use it on some of the sites that I currently manage.

KC0MAZ

After working with the XOOPS Core Developers, we now have a process of getting the right information from the user to the developers.

Users/customers may submit any problems they are having to any number of places on the Xoops.org web site. We will have keep watch. The Community will try to help, as they always have. You may also help using all the resources at your disposal, including FAQ's, official documentation, your own experience.

If the issue is still unresolved, or you seem to get a number of “me too” posts, then open a topic or thread in the XOOPS Core Bug Reporting Forum, and move that thread over to the new topic. you as the coordinator has just taken ownership of that issue. Developers and and other moderators, please respect that. The coordinators will then use this area to collect all the information about the issue at a minimum:

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:

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

Some customers/users may need help gathering this information, if it happen in multiple versions gather that information as well. In addition it might be wise to ask a developer to come in and help with some issues, use your best judgment.

Once you have all this information, go to Report Core Bug file a bug report. The report will be given an ID number. Go back to the topic that you created and indicated that report has been filed, and give the ID number.
while you don't have to have an account on sourceforge, it is strongly encouraged. If you choose not to have an account, please give some contact information in the notes.

From Sourceforge, a developer will pick up the report and start working it. They will be posting updates to the Sourceforge bug tracker. check back at regular intervals and post updates to your topic on Xoops.org let our customers know we haven't forgotten about them.

Once the issue has a remedy, deploy it per the instructions of the developer. Once it is deployed, check with the customer and make sure the issue is resolved. If it is, great, submit a summery to the communications team for documentation, Once the issue has been documented, and posted. you can close the topic or thread with the finial post pointing the the documented fix.

Our customers may post bug reports directly to Sourceforge, and in their posting they make leave out a vital piece of information. a developer may start a thread on Xoops.org looking for this information. One of us should take ownership of it and work it like any other issue.

It will not always work this way, however, try to stick to this as close as you can.

The big things to remember here are:
1.give the developer what they need to fix it
2.keep the community informed of the progress
3.If you open it, you close it (threads, topic, etc.)

Ladies and Gentlemen, I believe we have a bingo!

Quote:
Once those areas (Module dev, themes, etc) get their 'Coordination' team up and running We will turn the issue over to them for follow-up and vise versa. I urge some caution with this, we don't want user's issues bounced around like a volleyball between the areas.
In addition if a user submits an core issue directly to the SF and is missing some vital information, it could be referred to the Coordinators for additional information or follow-up.
Quote:

If the need arise for a special set up, we, the coordinators will be recruiting other members of the community with the proper set-up to work with you. Of course, each situation will be different and handled accordingly.

Would the developers like to have the coordinators have accounts set-up on SF.net?

Quote:

From what I gather, the developers would like unresolved Core Bugs and Feature requests submitted to SF.net with a minimum of the following 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:

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

The Community Coordinators would use the XOOPS Bug Reporting forum to open topics and collect this information, then use that same topic to provide updates to the community about that issue, once the issue is resolved, and documented, the topic would be closed by the Coordinators who opened it. Does this sound right to everyone here?

KC0MAZ

Now might at be a good time to explain how I see my role in the great scheme.

As the leader, I am the liaison between the moderators/coordinators and the project manager ,council or the administration.

It is my job to keep you informed of all that is going on.
It becomes my job to inform the administration of problems that you are having, and get what you need to fix those problems

It is also my job to make sure you have all the tools you need to the job at hand. If you need permission to a certain area, it becomes my job to get it for you.

I have requested a number of permissions for us, both here and at Xoopsinfo so that we can do our jobs properly.

You represent the XOOPS Project Anything you do, good and bad, reflects back on the administration, and myself. I am responsible for any action that you take.

If you make a mistake, that is okay, admit it, learn from it, fix it.
If you are in the wrong, I will tell you, privately. and I will explain why.
If you are in the right, I will defend your actions to the hilt, to the community and if need be to the administration.

I ask, if you contact the administration about an issue, (ie banning a user, or closing a forum) please let me know what you are doing. Not so much as to stop you, but so I am not blind sided by some action that you may have taken. (This has happened to me before)

I don't mean to seem heavy handed here. I am here to help you. however we need to keep the communication lines open.

Quote:

We are not an 'official' team yet, thus we do not have the authority to do anything in the forums. However, we can get the organized, so when we are official, we can get the ground running.

We can get our processes, rules, resources in order. That is what we are doing here.

Thank you for the list of resources. It will be a bit help to us once we get going.

Our main priority is to provide the best service possible to our community. To that end, Moderators and Coordinators should endeavor to be pro-active in their dealings with users and stay informed on XOOPS development and procedures.

Moderators and Coordinators represent the XOOPS project, and we will often be the first 'official' contact many will have with the project. We want to portray a professional and business like attitude, even when our customers (users) don't. To that end here are a few guidelines.

• Treat Members and co-members and visitors with tolerance, understanding and upmost respect.

• Moderators and coordinators will not harass or personally assault while moderating the forum or while involved in XOOPS CMS business.

• Moderators even when not on duty must always show respect and pose them selves as ambassadors of XOOPS CMS as you represent our services and your actions have an impact on all Moderators and Coordinators and the community.

• Do not use profanity or slang.

• Always try and answer all questions with the best of your knowledge. If a question does arise that you are not know what the answer is of ask any other XOOPS CMS Project member for assistance. Be sure to follow up.

• Attend all mandatory meetings and read all development messages, this way you will stay up to date.

• XOOPS CMS Moderators and Coordinators are encouraged to chat in the discussion forums with members and enjoy your time.

• If a problem arises with a member and you’re not getting anywhere, yet the community member informs you that they will file a complaint against you, you must provide them with a contact e-mail address for the forum administrator. For this purpose you can have the community member PM me.

• All community members have the right to file a complaint on any XOOPS CMS Project member and all Moderators and Coordinators must provide the information requested for the appropriate department.

• Moderators and Coordinators MUST NOT give any information/usernames/passwords regarding any area of Xoops.com. This includes ftp/websites/sourceforge etc.

• Moderators and Coordinators must protect community members personal information, including e-mail address, and any other information you might be privileged to.

• The purpose of a Coordinator to open a topic is to collect information about a specific bug or issue, then use that same topic to provide the community with updates how the developer(s) are coming with the issue. Once the issues has been resolved, and the information has been documented. Then that topic should be closed by the Coordinator that opened it.

When a community member has a problem with the conduct of another community member, resolve the situation in the following manner:
• Address the issue, always in a professional manner and out of view of other community members.

• If the issue could not be resolved then talk to a senior member of the XOOPS CMS staff and ask for assistance or create a log in the ‘Moderator Complaint Procedures’ board.

• Moderators can warn community members for breach of forum conduct. When doing so please point out why they are receiving the warning and post a link into the forum post pointing to which area of conduct the community member has breached. All breaches of conduct and member warnings must be logged for future reference. Three warnings in a rolling 30 day time will result in being banned from the forums for 7 days. upon their return they will be place in a probationary status for 14 days, the next offense, will result in a 30 ban and a 60 day probation, with the next level being 180 day ban. These decisions will not be by a sole moderator or coordinator, we will make them as a group. With one exception:

•If a user is promoting or planning violent illegal activity (i.e. mass murder) that user is to be banned and the thread closed immediately by any moderator or coordinator. notify a system administrator and me immediately. Care must be taken to preserve the logs for law enforcement. Do not delete anything. After consulting with a administrator or myself the moderator or coordinator may move the thread into a private area to keep it out of view of the public.

•Forums, topics, threads not relating to the XOOPS CMS, and have been inactive for 45 days are subject to being closed. Those topic relating to the XOOPS CMS and have been inactive for 60 days are subject to review, if the issue is no long valid, it will be closed.

• Moderator or Coordinator will NOT lock or remove a topic/post at the wish of a community member. All moderators are requested to politely remind the community member that unless a serious breach of conduct as occurs then you are not permitted to do such unless requested by an administrator.

With a few exceptions, these are only guidelines, there is no way to cover every possible situation. Use your best judgment, and if in doubt ask an administrator or myself.
Remember to stay professional, and keep conflicts out of public view.

We now represent the XOOPS CMS Project.

Such a product would be very useful.

However since it is unavailable to us at this time.

we will have do it the old-fashion way.

What do you need / want
where do you want it
How do you want it

All I am try to do is get the groundwork set up for the Community Coordination team to do their job.

Quote:

Is this product ready for deployment now?

Will this product give you everything you need to resolve most issues?