@ sailjapan

So its not much more then what I already do?
just adding the reports, and suggesting a change for item X to team Y.

Quote:

because we just found out that we're official today and this seems to be working just fine for now.

Crip

Now dont get me wrong, but dont we have modules in the modules section that deal with this type of thing?
sorta like this one?

or would it be more on the line of a new cat in the forum?

monthly meetings has not been decided yet. Mainly due to the time difference. We may have to fall back on using a forum for the meetings. I was going to work on that after the 4th.

I am partial to the Xi ticket system. However I want to have a closer look at it.
@Sailjapan - since you already are working the documentation team on that want to have a gander at their system and see if it will work for us.

thanks,
KC0MAZ

kc0maz;
RE: Re: Progress Report [proposed] Community Coordination Team 1 July 2007 #24
Quote:

I wanted to say I voted FOR you as "Community Coordinator and Team Leader" and I have not regretted it for a second. You are an EXCELLENT Team Leader and I am glad to be a part of your selection.

@JAVesey - From what I have gather in the threads here, the module teams are splitting up into core modules and what ever is on Xoopsinfo. We need to find out what modules are going to be supported by who, where.

If they are not cooperating let us know by weeks' end get back to us and we will come up with our own plan for dealing with module issues.

I am going to answer several questions here, because here is where they belong.

I am going to preface this a bit. I did not ask for this position. D.J. sent out a request for help, I answered, via e-mail and in the thread. The community coordinators thread sat dormant for some time, while other teams were getting their act together, we sat around waiting for something to happen, while other possible leaders were stepping down or taking other roles. I took upon myself to get what few people we did have together and start moving. D.J. Himself recommended me as the leader. I was dully elected by my peers. Now the job is mine, and I am going to do it to the very best of my ability. If that means stepping on some toes or treading on sacred ground, then so be it.

Alitan wrote:
Quote:

You are correct, this is an Open Source project. If we were a business, we would have been out of business a long time ago. Maybe it is time we started to get a business-like attitude. Other groups use it and are very successful. This doesn't mean we start charging for Xoops, it means we get an efficient organization together, and select the best people who are willing to serve in the those positions.

so far I have no complaints with D.J's leadership or those select to serve on the project council. I have been given the tools I need to complete my tasks. I need not ask for more.

Terms of Service and XOOPSiquette

I recently opened a thread asking for a review of the current Terms of use and XOOPSiquette. I reviewed each and every response.

From the community coordinators finial report:
Quote:
This report will be made public once it is finalized.

Catzwolf wrote:
Quote:

That burden is mine, and mine alone.

I have a tremendous amount of respect for the moderators, both current and those coming up. They have to endure a lot of 'stuff' to get the job done. They know what is expected from them, and they will be held to a higher level. They also understand, when they represent the XOOPS CMS, here at Xoops.org, another web site, and even off-line how to present themselves.

I want the XOOPS community to know I take allegations of moderator abuse or neglect very seriously. Anything they do, good or bad, is a direct reflection on me, professionally and personally. All reports of moderator abuse or neglect will be investigated. Once I make my decision, that's it. If you don't like it you may appeal to the project council if you like, however, have your ducks in row, because I will. The community should also know, in similar situations, rarely have I decided solely in favor of one side. In most cases I have found the situation is caused by a combination of bad choices on both sides. There are a variety of tools at my disposal for discipline. everything from private censure to recommending a lifetime ban from Xoops.org website(s). Of course, my actions will be reviewed by the project council and they have the same options. I consider the discipline of the moderators to be a private matter. The complainant will be informed of the decision and any discipline imposed. Otherwise no one has a need to know. Only the moderator in question will have the option of making the event public.

There are going to be some very trying and painful times coming. the moderators and the coordinators will be there to help understand what is going on and help the rest of the community transition through it.

I made a statement and Catz, rightfully, jumped me about it:

Quote:

@ catz I wanted your opinion about the topic at hand, not your opinion weather or not the leadership is capable, or if the review of the Terms of Use and XOOPSiquette was a knee-jerk reaction to the change in leadership or anything else not directly related to the current Terms of use or XOOPSiquette.

I can assure you it was not a knee-jerk reaction. Before the 'new' moderators can move in and start enforcing the rules, they have to know the rules they are going to enforce. After checking many of the forums, I have found that some rules are enforced vigorously, some are not enforced at all, some rules are only partly enforced, and no one calling foul. It make sense that before the 'new' moderators took over, to go to the community and ask “What are the rules that you want?”, then make a recommendation to the project council to change the rules. It also make sense for the moderators to understand the spirit behind the rules. This type of review would have happened no matter who was the leader or on the project council.

My goal is to get the moderators the tools they need to get the job done, yet keep them in check, The last thing we need is a bunch of renegade moderators running around carrying out their own agendas. If you thought we have chaos now, can you image the the trouble we'd be in if we just them go without any direction. I really don't think my little 200 GB hard drive can handle all the hate-mail I would get.

@phppp the Community Coordination Team final report will be sent by 17:00 CDT today and posted to this thread soon afterward.

Community Coordination team-

Our tasks will be:
1.responsible for daily administrative jobs
a)removing spam
b)removing profanity
c)removing /deferring personal attack (flames)
d)closing / removing inactive threads & topics
2.Provide customer service to all XOOPS user and perspective users
a) help users to understand and use XOOPS correctly
b) help users to use the XOOPS official sites properly
c) assist with troubleshooting Xoops.
d) Submit for documentation any fixes
e) Submit any unknown issue to the proper area for evaluation and repair. (fixing bugs)


Team leader:

KCØMAZ

Team members:

Sailjapan
JAVesey
Bluestockings
Northern
---Pending are:
vaughan


Future community coordinators will be added by invitation only.
any community coordinator can make a recommendation to the team, the team will vote weather or not to have the member join the team. The project council can veto the nomination.

Team leader will be selected by the team, by means of a popular vote, then confirmed by the project council.
Overview-
The community coordinators represent the XOOPS project and the XOOPS CMS. The XOOPS CMS project being all the developmental and support teams needed to make XOOPS CMS happen. The community coordinators will be the first contact most webmasters, web designers or or perspective customers will have with the XOOPS CMS project. The image they portray will affect how that customer views the project, therefore it is imperative that the community coordinators express themselves in a professional manner at all times, and treat all they come in contact with, either at Xoops.org or other venues with respect.

The Community Coordinators preform two similar tasks for Xoops.org, The moderators maintain the forum areas and provide a suitable environment for the users, the coordinators provide customer service.

General Team rules:
1.a member being inactive will be losing his/her XOOPS community coordinator identity
a)not being on-line, missing team meeting or report deadlines for 30 days.
2.every member shall report to Team Coordinator before the First of each month
a)That they are indeed active.
b)any unresolved issues they are work on with the core developers
c)All fixes referred to the communications/documentation team.
d)Any topic or threads open or closed or removed.
There will be a running moderator / coordinator log or forum to document these events.
3.The team shall report to XOOPS Project Council on the First of each month
a)Active or inactive team members
any complainants and the result of those complaints.
b)Open projects
c)anything that may be of interest to the council, Some items may be for informational use only, others require action

for the purpose of moderating, request create accounts with username of "Lead moderator, forum moderator1, forum moderator2, etc." with newbb administration permissions; The account will be held by all coordinators will only be used for topic/posts management, like closing, removing, recovering threads and posts. Once a moderators leaves the team, the password on the account will be changed by the team leader / system administrator and readied for a new team member.

Moderating
The moderators are charged with daily maintenance and generally keeping the proper usage of the forums. This includes but not limited to:
1.Removing spam
2.Removing profanity
3.Moving personal attacks off the public forums
4.Closing and/or remove inactive and unneeded topics or threads.
5.Assisting the coordinators as needed
6.other duties as assigned.

The rules for moderating:

• All moderation actions should be done with the user account of "forum moderatorX". The coordinators should not respond individually to any complaints about moderation actions.

• Treat Members and co-members and visitors with tolerance, understanding and up-most 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 on all questions.

• 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. or e-mail me at kc0maz@gmail.com

• All community members have the right to file a complaint on any Moderatorsand Coordinator. See the complaint process.

• 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. Use PM or E-mail. Always ensure all communication is documented.

• If the issue could not be resolved then talk to a senior member of the XOOPS CMS staff and ask for assistance and 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.

•Only the project council can impose a lifetime ban on a member. The Community Coordinator team leader will present a proposal to the council along with any evidence supporting the ban. The member will be informed that s/he is bing considered for a lifetime ban and all the evidence supporting the ban, and will be given an opportunity to defend their position before the project council.
-any bans currently in effect, shall stay in effect.
-Only the project council as a whole may lift a ban.

•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 or project council.

Moderation compliant process

All members have the right to file a complaint against a community coordinators.

A special forum area will be established for complaints. One thread = one complainant, The only moderator allowed to make any changes is the lead moderator/team leader.

The team leader is responsible for investigating, reporting, and deciding all complaints. in the decision the team leader must give any reasons for the decisions, as well as any action taken against a community coordinator or user. The team leader will mark the thread as solved. As a general rule usernames will be removed from the complainant.

Either the complainant or the moderator can appeal the decision of the team leader to project council. The project council may take action against the complainant, the moderator or the team leader or any combination there of. The decision of the project council is finial.

Coordinating
It coordinators main function is customer service. It is the coordinators' job to make sure the customer is completely satisfied with Xoops, and that the XOOPS CMS and XOOPS Project exceeds their expectations. When a customer shows up with an issue that is not documented, or not being fixed, it falls to the coordinators to take ownership of that issue, and get it to the right people who can resolve it. Not only does the coordinator get the issue the attention of the proper developer, they follow through to ensure the issue has been resolved. To help the next customer who might have the same problem, the coordinator will have the issue and resolution documented by the communication/documentation team.

Ideally the the troubleshooting process would work in this way.

The customer has problem with a XOOPS program.
1.The Customer searches the documentation to see if there is similar issue, and how to fix it.
a)if there is, and the customer resolves the issue, there is no need for any other action
b)If there is not and or the issue is not resolved...
2.The user submits the issue to the community. The community provides possible solutions to the the customer. The coordinator will take note of the issue and observe the responses.
a)If the issue is resolved, the coordinators will ask a developer if the resolution is indeed a resolution or just a work around.
If the resolution is a resolution, The thread will be closed by the coordinator and submitted for documentation
If the resolution is a work around, it will be left opened for 30 days, If after 30 days there is not activity, The thread will be closed by the coordinator and submitted for documentation as a work around.
b)if the issue is not resolved after reasonable attempts or a reasonable amount of time, or there are several reponses like “me too” it moves to ....
2.The coordinator taking ownership of the issue. At this point, the coordinator will collect what ever information is missing then refer to the correct area, i.e. themes, modules, etc. If the issue is in the core of Xoops. the coordinator will:
a)move the thread to the core troubleshooting forum.
b)submit the issue to the developers via SF.net bug tracker
c)Change the title of the thread title to reflect the SF.net bug tracker reference number.
d)This thread is to be moderated by that coordinator.
e)The developer assigned will provide regular updates via SF.net
f)the coordinator will relay those updates to the thread.
g)Once a resolution has been developed, the coordinator will deploy the resolution per the developer's instructions, and confirm the issue has been resolved.
h)Once the issue is resolved. The thread status will changed to [fixed] by the community coordinator and submitted for documentation.
Currently the only method of submitting items for documentation is through the XOOPSinfo.com web site, helpdesk ticket system. In addition to a summery, a link back to the thread will be provided.
3.Only threads that have been documented may be removed.

Not every issue will work in this manner. The community coordinator are granted the flexibility needed to meet the needs of the customer, and still get required information the developers need to fix the issue.

Coordinator may provide web site reviews, suggest modules, etc.

As a general rule, coordinator will refrain from troubleshooting servers, or other issues not directly controlled by the XOOPS project. The coordinator can suggest where the problem may lie then refer the user to the proper agency.

The coordinator will assist the moderators as needed
and other duties as assigned.

Any other rules or modification to the current rules will submitted to the project council by the team leader for approval.

Terms of Use and XOOPSiquette

From a community review of the current Terms of Use and XOOPSiquette, no changes need to be made. The community is just asking for better and even enforcement of the current rules.

There where a couple of posts indicating that the project side of XOOPS should adopt the code of conduct from Xoopsinfo.com However after comparing the two side by side, other than a few minor tweaks, there is no difference.

The Community Coordination Team recommends not changing the Terms of Use nor XOOPSiquette. rather charging the Community Coordination Team with enforcement of the Terms of Use and XOOPSiquette as they stand.

The item about reporting criminal activities, will be referred to the individual moderators, meaning they will need to comply with the laws in their area. making logs and records available to law enforcement will be done through due process, i.e. warrants and other legal instruments.

//edited by author to reflect recent changes//

Thank you, kc0maz
That is how I understand our mandate.

And of course, I agree to its terms.

Lets make sure this is copyed or moved and sticked once we have a location to put it.

sence this will help alot in the near future. untill we get use to this.