@northern.

(always copy before hitting the submit button I feel your pain)

mate, we're 24/7 here (slight exaggeration for humor's sake, but not so far from the truth).

Personally speaking, and bearing in mind that we don't have our official workspace yet, when I find something that I think might need our attention I post a comment here on the forums where I know other team members will see it. I mention what I've seen and what I've done about it or propose to do.

See here for an example.

I think that this is the best way to see if anyone else has any input on the matter, and if the team leader thinks our action is or is not required, he can say there for all to see.

We're open here

Like I said a little above, we don't have any workspace other than here at the moment. So what needs saying all gets said here. I kind of hope our official workspace (when it arrives) will be somewhat similar to this, but with the added tools of a ticketing system so that we can track projects more clearly. Still open, of course.

Crip

Hi Northern.
Sounds like you're the type of person who would suit Community Coordination pretty well, actually.
I'm not a code expert either, but I think I'm good at tracking down and introducing people who are.

In this job (it feels like a job, and my RL boss might start complaining soon) the first two of the four points you quoted are maybe explained reasonably well here.
The third and fourth point I too am a little blurry on, but through our work in the first two tasks, we should be able to enable the improvement in the overall efficiency of the official site from an end user's point of view too.

Meaning: if it becomes apparent that a significant number of users don't know where to find 'X', it should come to our attention and we would consider it as good as a request. Maybe Team 'Y' could change something that would make 'X' more visible or accessible.

Similarly, if customers find themselves posting stuff in the wrong places too often, maybe the problem is that the forum is inelegantly described, or that the procedure is unclear. Again, a job for the Community Coordination team.

Basically, it's up to us to learn the way that the whole XOOPS community (devs, customers, sites etc.) works, and make sure that as many other people can understand it too.

As far as I see it, that is

Crip

Heads Up

There's a good point been brought up in the forums over on xoopsinfo.com

Quote:

I'll be approaching skenow shortly to see if he's taking it on or would like us to.

Quote:

Actually David, there's more of a need for fixers and coordinators than moderators here in the Community Coordination Team (I believe the Mods have their own team... somewhere... can't find it right now). I don't mean to say that moderators are not needed nor that they are unwelcome if they have the time and inclination to help. What I mean is, that our role here is to pursue issues until they reach a conclusion rather than maintain decorum and relevancy in the forums.
While we do have some moderator type rights, they are mainly for editorial purposes (moving posts etc.) rather than policing purposes.
If you'd like to get away from the policing and politics of XOOPS (as far as anyone involved with 47,000 other people can) and into the business of customer satisfaction and problem solving, the Community Coordination team may well suit you down to a T.

Just a thought.

Crip

Quote:

Yes, I can see how that would come about.

Quote:

Me? Noooo. Seems like a perfectly good solution if applied with due afore thought.

Quote:

I don't think it's a matter of lowering our expectations. Simply a matter of persuading folk to title their posts more accurately. No harm in phrasing the guideline as a friendly piece of advice rather than as a 'Do as you're told!' type of thing, is there? Everyone would gain...

But maybe that's just me.

Crip

How about re-phrasing the 'Subject = Help!' guideline:

Subjects - Please try to use meaningful subjects when opening a new topic in the forums. Including some key words (such as 'Theme' or 'Module' or 'Installation') which give some hint about your problem will help attract people knowledgeable about your issue. Though we do our best to keep a track of all new issues that arrive, subjects like "Help! I'm lost" can be overlooked, and may take longer to find a resolution to than is usually the case. Help us to help you

Crip

Hello irmtfan.

Some more members would be good indeed.

Our 'etiquette' or Team Guidlines can be found here

Currently we are contacting the other teams here at XOOPS to work out guidelines and formats for the handling of questions and requests.

You can see an example of this here where our guidelines for questions/requests to the Core Dev team have been laid out. Admittedly, this post was for the coordination team, a more end-user friendly version will be compiled shortly.

Similar sets of guidelines will be made available once discussions with the other teams have been completed.

As always, we're happy to hear from anyone who feels they have some input on how we go about simplifying the submission of requests.

Crip

Hi communications.

You've probably seen this, but incase you haven't, here's a link to The XOOPS Challenge

Thought it could do with some publicity. A news article or announcement perhaps?

Crip

Hello Darcy

Right then, straight to the point as usual. Bearing in mind that this team has actually only been around for... what time is it? Umm, a little under 24hrs, let me see which of your questions I can answer.

Quote:

Presuming you're not on death's door, yes.
You are of course right, the will be was quoted directly, but of course should have been altered to are.

Quote:
Today, we can reply to your post as Community Coordinators.
Tomorrow we can discuss the definition of our tasks.

Quote:
I would definitely hope so, though seeing as how we just started today, we may not be able achieve them all tomorrow.

Quote:

I don't think that's the kind of administration that we're being asked to perform. As you say, that'd be a moderators job. Before you ask, we have yet to discover exactly what admin jobs are expected of us, nor have we had a moment to discuss what admin related work we should propose to take on.

Quote:
By all means, go ahead. As the names of all the team members are not listed concisely anywhere and as, in fact, the teams are still in a state of flux, it might take us a day or two to put together the list ourselves. If you're proposing that the list be put in a sidebar somewhere, there was a similar call from alitan in the comments of this news article today.

Quote:
Indeed it does. And we will be trying to help bring people with questions together with people with answers too.

Quote:
I think that depends on how you put it to this theoretical themer. If a theme has a serious flaw (and assuming that it has managed to slip through the peer review that I think the theme dev team and design team will be providing), then I'd have thought said themer would appreciate being advised concisely, and in a non confrontational manner, how this flaw was turning people off of his/her theme.

Quote:
I don't think so, Darcy. Under this proposal, we should:
*Co-ordinate with the documentation and/or site's team to have a clear set of 'Proper Use Guidelines' for the official sites drawn up.
*Have made sure that the folk who run the site get a copy if they didn't write it themselves.
*Suggest that they put a prominent link to it in a place where people people likely to need guidance can see it.

I think that the mods of each particular site would be policing their sites for abuse, and if said guidelines were available, pointing abusers to it.

Quote:
That's exactly what we're about to discuss and find out. Feel free to join in the discussion.

Quote:
Not if I have anything to do with it, no.

We have three, 1 day old, team members at present. It's going to take us a wee bit of time to work out where we stand and where we're going. You can rest assured that all of this will be in public, and that our ears will most definitely be open to suggestions.

Thank you very much for kick-starting the proposed discussion on our list of tasks. You have given us food for thought, and helped me to express some of what I was going to write tomorrow. Oh, it is tomorrow. Off to bed now. Work in... 3 hours.

Crip

Reporting in.

Shall we start by expanding on the list of tasks?

Quote:

Crip