XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


« 1 ... 12 13 14 (15) 16 17 18 »


141
kc0maz
Community Coordination Team

  • 2007/6/28 15:28

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


Welcome to the community Coordination team.

Team Leader:

KC0MAZ

Team Members:

Sailjapan
JAVesey

Current Moderators in good standing are invited to join.

Our tasks will be:
1 responsible for daily administrative jobs
2 help users to contact corresponding teams upon their requests
3 help users to understand and use XOOPS correctly
4 help users to use the XOOPS official sites properly


Rules:
1 a member being inactive (not onlie, no team meeting for more than one month) will be losing his/her XOOPS community coordinator identity
2 every member shall report to Team Coordinator on the First of each month
3 the team shall report to XOOPS Project Council on the First of each month

Anyone is welcome to join please post a note here or PM directly.
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum


142
kc0maz
Re: Xoops Core Discussion and Roadmap

  • 2007/6/28 15:13

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


Quote:

Catzwolf wrote:

Many good questions that would simply would have been answered if we had a good FAQ regarding this and many other important matters.

I'm sure if I searched hard enough I can find different versions of what you need. There lays the problem, what do you need, what do want, and can you do without.
Quote:

A personal fav of mines what to be able submit bug reports from the admin area.

That is our problem. When we get our hands on an issue, and we can not find the answer in the documentation, user forums, or any other resources, then we collect the information you need or want and submit to developers. Issues reguarding unclear documentation, is submitted the documentation team including missing FAQ's
Quote:

The fact is that submitting a bug is only part of process, it doesn't matter how many bugs that get reported if they are not acted on. Bugs should have a critera of importance and severe bugs/security issues should be fixed and made available within 24-48 hours and not as in some cases ignored or debated about for weeks on end.

You are correct, and I am not going to debate that issue with you. In the near future I would like to see a 'fast track' process, where severe bugs and security issues are sent directy to developers,by-passing normal channels and an response given within 30 to 120 minutes.

But we all have dreams
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum


143
kc0maz
Re: Xoops Core Discussion and Roadmap

  • 2007/6/28 14:15

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


The Community Coordination Team is being formed and will be coming on line shortly.

When we submit a bug report or feature request:

How do you want it submitted (SF.net, dev.xoops.org, here, etc.)?
What information do you need included?
What information would you like included?
Do you want it in a specific format?
What do you need from us to make your job easier?

After we submit a report or request how can we get regular updates regarding the issue?

KC0MAZ
Community Coordination team leader (elect)
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum


144
kc0maz
Re: [XoopsTeam] progress - community coordination - June 10th

  • 2007/6/28 12:58

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


Quote:

sailjapan wrote:
I was just a bit unsure what solely for Project meant. Still not all that comfortable with the words governed by Project Council,


Those words can chafe one the wrong way. We will receive our guidance from the project council, based on the direction of of the project. If the council tells us the version 2.2 is dead, then lets not open any more user discussions, rather, we will refer them to version 2.0.16. If the council says that 'coordinator X' was rude, crude, and socially unacceptable, then the council will take some kind of action against 'coordinator X' (if I haven't already done so) The focus of our 'work' will be the end-user.

Quote:
Being basically a tool enabling clear and accurate passing on of requests from various groupings of the XOOPS community at large (devs are community members as much as are end-users), if a team decides to reject a request, that's not our decision, so there's not much that we'd need to be governed over, I'd imagine... except dereliction of duty perhaps.


That's it.
Quote:

Yup, once we're all set up, issue tracking on a wiki would work well, or possibly a ticketing system of some sort.

There are so many tools that could be used for this. I want to keep it simple, both for us and the public. in the meantime I suggest all the the team members become familiar with SF.net Bug tracker as we may be using it to report back to the development teams. We may, as the need arises, set up our own internal tracking system.
Quote:

In the meantime, clutter or not, this is probably the best place to keep our discussions open and on record.

This is what we have, so this is what we will use. I have no problem having the discussions open to the public, I do have a problem having our discussions being the first thing people see when they come to Xoops. Especially first time visitors. Some of the discussions there makes us (the community) look something less that professional. This is an image that we do not want to portray.
Quote:

I'll take on the recording of ideas here and post a weekly synopsis here if people think that would help us not lose track of anything important that gets posted here.
That is a good idea, at least until we rolling. Let people see that we are not just sitting our hands, but as a team we are moving forward.
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum


145
kc0maz
Re: [XoopsTeam] progress - community coordination - June 10th

  • 2007/6/28 11:33

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


Quote:

kc0maz wrote:

1. Select a leader.

Right now there are two people
JAVesey (yet to respond)
KC0MAZ (myself)


JAVesey has responded via PM, and in so many words, declined. Very nicely worded

Quote:

phppp wrote:
you are also a good candidate according to what you have done.


Quote:

BlueStocking wrote:

SIDENOTE: I think I see a leader, leading now, and doing it very well.

BlueStocking


Quote:

sailjapan wrote:
As for leadership, I think you're doing fine, kc0maz. Unless you'd rather not do it, I nominate you

Crip


By default that leaves me.

Unless there are any objections. I will take on the leadership role.

Here is how the team stands now

Team Leader:

KC0MAZ

Team Members:

Sailjapan
JAVesey

Quote:

phppp wrote:
I would suggest the team to be replaced with "community coordinator team"


I have invited all the current moderators to join this team, so far they have been unresponsive or reluctant to join. We will continue without them for now. The door is open for more team members.
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum


146
kc0maz
Re: [XoopsTeam] progress - community coordination - June 10th

  • 2007/6/28 5:02

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


Quote:

BlueStocking wrote:

The thread was started by phppp, with the intention of making it front and center. I think it should be kept that way until resolved.


I am fine with that. However once this is sorted, let's get moved.

Quote:

BlueStocking wrote:
Your team consists of you and
Sailjapan and JVeasly, who has not reported in yet?

Is that correct?


That is correct.

I have invited all the current moderators, they have yet to respond.
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum


147
kc0maz
Re: [XoopsTeam] progress - community coordination - June 10th

  • 2007/6/28 4:32

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


Note taking
keeping track of who is tracking what issue etc.
will be very public.

Before that we need to get together and make a plan and establish some ground rules and of course get some infrastructure in place. I don't mind if this is public or not, it just shouldn't clutter up the XOOPS home page.

I believe there is a report due on 1 July on the status of the team to project council.
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum


148
kc0maz
Re: [XoopsTeam] progress - community coordination - June 10th

  • 2007/6/28 4:02

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


Let's not put the cart in fort of the horse.

1. Select a leader.

Right now there are two people
JAVesey (yet to respond)
KC0MAZ (myself)

2. After we have a leader in place, we need to find a forum, a chat, irc or some other meeting place either on XOOPS sponsored web site or elsewhere, where we can coordinate our efforts. without flooding the XOOPS home page. It would do no good to have two people tracking the same issue.
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum


149
kc0maz
Re: [XoopsTeam] progress - community coordination - June 10th

  • 2007/6/28 2:51

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


It took me a while to digest Jame's announcement and a few PM's between DJ, James and myself. I think I have it down.

To the average Joe User, The Coordinators will be the gatekeepers to the inner sanctum of the developers who gave birth to the code of Xoops, If the user has a problem, they have to get by the coordinators first. The Coordinators are eyes and ears of the developers.

To the developers, the Coordinators are their eyes and ears. They are the data collectors and communicators to the users. Not only do they bring back word of stuff that is broke, They also bring back what is working. However they seem to bring more problems than good news.

my wording is bit overdone. however as I understand the purpose of the Community Coordination team, we the the go-between the core developers, module developers, theme writers, and the users We don't work on a broad scale like the Advisory Council, rather we work one issue at a time.

I foresee many of 'end-user' discussions being held on XoopsInfo. however we have to bring back to Xoops.org what we have learn. We will be coordinating between the two or three sites or forums. I stand by the the synopsis I posted earlier. It may require a bit tweaking, however, the overall idea stands

But we are a long way from that point now.

First we need to select a leader.
Then we need to find a work space where we won't clutter up the home page.

Report time is coming up fast and someone will need to make some kind of report.

PS. I apologize to DJ and James for any harsh words I may have sent via PM.
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum


150
kc0maz
Re: Adsense troubles

  • 2007/6/27 19:37

  • kc0maz

  • Quite a regular

  • Posts: 216

  • Since: 2005/4/18


The two banner ads by Google at the top and bottom appear to be working in IE and Firefox.

The only place where there is a blank block is the welcome block.
Some dream of success, while others wake up and work for it.
--unknown
Topic | Forum



TopTop
« 1 ... 12 13 14 (15) 16 17 18 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

292 user(s) are online (174 user(s) are browsing Support Forums)

Members: 0

Guests: 292

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits