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.

Kc0maz,
You are confirming my suspicions you are a leader.

Now, if phppp will sign on to this I know my issues will be addressed and I will be informed of the outcome in a timely matter.

I say DJ because it is my understanding JMorris has stepped down from xoops.org Project/Community management.


Quote:

Thank you for such a concise statement.

As part of the Community Co-ordination Team, what kc0maz said above also applies to myself and to "Sailjapan".

I will try to help whenever I can, but please remember that I have a day-job, a family and, well, a life

It is good that the three of us are spread around the globe:

kc0maz is in the US
I am in the UK
Sailjapan....... I forget where he is

Anyway, if anything is urgent please remember that if you want a quick(-ish) response then please consider the time-zones

Hi JAVesey,

From outside, looking in
I like what I am seeing develop on this team.

I feel a sense of 'inclusion' of end-users concerns without having to be a team member, I'm free to be just another outside volunteer worker.

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.)

I am going to park this here for the xoopswiki site. This should help to make it multi-language. The code can be copied and pasted on the wiki site.

On this site it wont look right because it is not XOOPS code but it works ...

EDITED CODE FOR XOOPSWIKI.ORG 2007-06-30
=== Change Language ===
[http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Car&hl=en&ie=UTF8 العربية ] * * [http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Cde&hl=en&ie=UTF8 Deutsch] * * [http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Csc&hl=en&ie=UTF8 sc] * * [http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Ces&hl=en&ie=UTF8 Español] * * [http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Cfr&hl=en&ie=UTF8 Français] * * [http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Cit&hl=en&ie=UTF8 Italiano] * * [http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Ces&hl=en&ie=UTF8 Nederlands] * * [http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Ces&hl=en&ie=UTF8 Polski] * * [http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Cpt-br&hl=en&ie=UTF8 Português do Brasil] * * [http://translate.google.com/translate?u=http://www.xoopswiki.org/wiki/index.php?title=Welcome_to_the_XOOPS_wiki&langpair=en%7Czh&hl=en&ie=UTF8 中文 ] * *


BlueStocking
BTW: don't worry about the white blocks or odd characters, that means you do not have the needed character installed set on your pc.

Change the address to reflect the site page you want to put it on.

They may move it, use it, or if not acceptable - just plain lose it... The above code is xoopswiki.org ready and can be used now from here or there.

Quote:

Who?

As for the rest of the above, all I have to say is:

What?

Where do we begin with that?

Can you be a little more succinct?

Sorry, but you have me mighty confused as to your intentions*






* I'm 3/4 the way down a bottle of Cabernet Sauvignon as I type this, so I'm easily confused

@ 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

I am sorry about the name misspelling. I will remember the John V. so I had better stick with that. I had a general idea of the nick but got it wrong. Again I am sorry.

Next...
Onward...
KC0MAZ posted 2007/6/28 10:28
Quote:

The reason for - "go team go"

Quote:

The reason for the language translation code.
They have adapted and applied it (or similar) to their site so I assume at least part of the objective has been met.

Passing the code on so that others might use it - is the objective. Hackbrill has a java script version of it on his site now.

I believe someone needs to find a place for it so it can be shared. The total represents several hours of work.

Of course, it can just be turned down.
I don't have a problem with that.

This forum is great for talk input... but where do we put the results of our labor.
As I read the indentification of your mandates, that is your task.

I am eager to see where it ends up.

The Community Coordination Team is not an active team, yet. Right now we have no authority to open, close, move or edit any topic, thread or posting.

The XOOPS project is quality program, and is worthy of world-class customer support for it users and customers. In the spirit of open source we are having our discussion about policy and procedures in the public, so administrators, users, customers, and visitors will know what to expect from Xoops.org. If you have any questions, comments, concerns, or suggestions regarding any of our policies, please feel free to post them.

Once everything is place, and the team is active, an announcement will be made.

Thank you for your patience while we work though these issues.