Now that an outline of how the proposed Community Coordination Team would operate has been posted and we know that The Community Coordination team is considered to be a 'project' team, and our internal' team work forum will stay at Xoops.org.

Shall we try this again, please.
Quote:

I would like to invite following people to join the Community Coordination Team as Moderators at Large:

JMorris
irmtfan
akitson
vaughan ( M0nty)

They are all current moderators in good standing.

The moderators tasks will not change, in fact some may be added. The moderators will continue to work as they have, with little interference from the rest of the team.

If it ain't broke, don't fix it

I have invited SailJapan as a coordinator, and he has accepted.

If there are any others who would like to join, please PM me or post a note here. otherwise we will assume there are no others who want to be included as a part of the Community Coordinators.

the first item on the 'to do list' is to select a leader.

I have recommended JAVesey because of his experience with the XOOPS Community.
Quote:

Are there any other candidates?

As I suspected. We would work together toward a common goal.

While we are helping users connect with proper documentation, we can let you know if something is unclear, or needs revising. we would also ask for help when new software needs documentation.


I was not shouting, I was emphasizing with italics the fact the Community Coordination Team is only a proposed team, not an official team, as there was some fuss about its status last week.

I did not propose this team, nor am I the team leader. I am just laying the groundwork so the team can be established, and a leader selected. Our respective teams functions are very different, and joining the community coordination with the communication team would not be keeping with the goals of the community coordination team. Thus, I respectfully decline your offer to join the communications team at this time.


-KC0MAZ

It has been brought to my attention that there may be a conflict with what the communications team will be doing and with what the proposed Community Coordination Team is proposed to be doing here.

I really do not foresee a major problem. Rather representatives from both teams would together to produce a usable product with some documentation that really means something.

Quote:

I want to be extremely careful here, as my goal is not to offend.

Before volunteering for any position, either here, or elsewhere, including your church, local Red Cross or Red Crescent, or any other organization, you must know your limits!

To often I have seen people volunteering for positions they can not preform. They become more of a liability than an asset.

I have also seen volunteers take on way too much, and do more harm than good. For this reason several organizations that I work with that depend on volunteers limit people to one job, at a time. They might be multi-talented, but those talents are used at different times.

I have seen organizations that have one to two people do all the work. The result is total misery, for them and those they are trying to serve.

From experience, I have found that one person to do a job at one time, is good policy.

Quote:

Thank you, D.J. for your confidence of my leadership skills.

Maybe now is a good time for me to share how I envision proposed Community Coordination team and how it would operate.

@D.J. please correct me I make a mistake somewhere.

The current moderators would continue to moderate the forums, for the purpose of this team we can call them moderators at large, meaning they moderate most of the forums. While during their trolling they come across a re-occurring, or unresolved issue, a number of people requesting a feature or module. or anything else that requires follow-up. the Moderators @ Large would come to the Coordinators, and say this is going on in this forum/topic.

A Coordinator would then take ownership of the issue, and start a topic with the coordinator as the moderator of that topic only. The coordinator would then use what ever tools they deem necessary to determine what the issue is, what feature(s) is being requested or what a module is suppose to do. Once the Coordinator has the information, they would contact the appropriate development team. From that time forward, that coordinator will be the point of contact between the end-users, via that issues topic, and the development team. All they way through development to the finial release including documentation. Once the issue is resolved, the module released, or upgrade. the coordinator could close/lock the topic. maybe write up a summery to be posted in the FAQ's

For example a there are 20 requests for a APRS/ECHOlink module. The moderators @ large would hopefully notice, and bring it to the attention of the coordinators. I being a coordinator would open a APRS/ECHOlink topic in the Module Request Forum, with me being the moderator. Other moderators would be welcome to troll through, removing spam, indecent posts, etc, however the topic/threads should not be locked or closed, except by the coordinator. Threads relating to this topic should be moved over.

The coordinator would then hold discussion to find out what is APRS and EchoLink and what the module would do. maybe use polls, check legal status, basic research. the coordinator may even call on some of the posters to help.

Once the coordinator understands what the propose module is suppose to do, and what features are requested. the coordinator would contact the module development team either here or on SF and simply layout the request. Hopefully someone would pick it up. The coordinator would then request and post a regular update to the project. once a week or so.

Once the module is ready for beta testing the coordinator would lead the test. reporting back the developer the outcome. During this time the coordinator would be communicating with the documentation team.

When the module is released and documented, the coordinator would then close the topic, write a summery and pass it to the communication team as a news item.

Next issue please..

Of, course I might be way off base here.

The Moderators @ Large are still doing what they have always done, only they are keeping an extra eye out those issues that may need some extra follow up. The coordinators are doing just that coordinating the various teams to resolve issues and get new useful modules out. It is the end users who drive it the entire process.

It has been several days since the current moderators were invited to join the proposed Community Coordinator Team.

From the lack of any responses, I will assume everyone is content with the following proposed Community Coordinator Team:

JAVesey
KC0MAZ

Unless someone else steps forward, I suggest that JAVesey be named team leader.

Quote:

Forgive me I can be a bit slow from time to time.

You read news, weeks ago, That is different from the news you are reading today?

Can you provide a link for the news you read weeks ago?

I have seen several of these applications. I am in the process of evaluating several of them for a small office.
It is not really a CMS, more of network/web suite of desktop applications.

This one is really cool. I will have to add it to my list.

chas2 said:
Quote:

Posted here:

vaughan said:
Quote:

Would you like to see the forums & threads streamlined?

After reading and filtering discussions here and on sourceforge. I sense a real disconnect between the developers and the users. The users feel they are talking, but no one is listening. The developers are trying to get something going, but get bogged down in administrative tasks. The moderators are trying to do their job, however, they have administrators / developers putting up road blocks. So far what I have read, it is US vs. Them vs. Them

IMHO, there are too few people on too many teams trying to do too many functions and too many people complaining, The users are frustrated with the continuous in fighting and fewer answers.

I recommend the following guidelines across the board.

1.One person can be on no more than one team, with the exception of representing their team on a council.

2.Each team respects the other teams' autonomy.

While I at first supported an End-users group or team, I am beginning to question the motivation behind such a move. Maybe a pool of end-users who are willing to work a short-term project might be a better move. Until the core management is made official, we should hold off on this idea.

That is some mighty hard reading. I think I had to enlarge the font, so I would lose my place. (old age?)

I have read this passage before. I find it quite interesting that you should post it, here, and at this time.