Quote:

Clarification? What has been clarified exactly? That we need more inaction and debate over things that are already in place? I think my head is going to explode!

Quote:

Agree! there is no need for Xoopsinfo.org or any other individual Websites. Let's stop the fragmentation of XOOPS and let's work on keeping the information in one logical location (doesn't have to be physically the same one).

http://forums.xoops.org is just fine by me.

To come back to the original question, the less forums you have, the best it is.

Xoops is made of 5 things, the core, the module, the themes, some hacks and (no) documentation.

So you have 5 forums.

It has not sense to think about designing a room if there are no plans about the building.

So as far as I understand this (for better or worse):

1. Xoopsinfo has no official site status and isn't going to be the official support site.

2. The forums on xoops.org are going to remain here (so in practical terms, xoops.org will stay the official support site). However, they will be restructured.

3. DJ's response *implies* that this is an official thread and that input will be looked at. Sometimes, I wish you would be a bit more direct, if things were clearer we would spend less time talking in circles!

Or have I got it wrong?

I have put my comment here as this is somewhat related

In Response to Madfish comment here.
Quote:

aye, this is a great idea.

I would like to couple this with SailJapan's idea of a ticket system. and Dave_L idea of suggestion (rather than complaint) forum When a suggested is submitted, the person gets a ID number to reference back to.

The Community Coordinators, can then combine suggestion ID numbers of similar nature and submit them all to the responsible group for action or dismissal.

This takes care of two things I see missing here,
One is feedback, you should know where your suggestion is at, or what action is being taken
Second is giving credit where credit is due. If John submits an idea that helps the community, then we should acknowledge him in someway.

There is a pitfall The Community Coordinators in some cases is a little more than a conduit, While we can pass suggestions on to the council, the foundation, a team, or a person, we can't force them to take action or even read it. Some ideas require also require a bit of research and/or discussion before an answer can be reached.

Quote:

I could not have stated this better(and I am a writer)!

Any more comments?

Quote:

So, to summarize -

@xoops.org
XOOPS Core Support
* XOOPS Troubleshooting
* XOOPS Installation
* XOOPS Upgrade or Migration
* XOOPS General Usage

Site Forums
* XOOPS.org Site Issues and Feedback

@ sourceforge.net
XOOPS Core Development
* XOOPS Bug Reports
* XOOPS Feature Requests

@ forums.xoops.org, community.xoops.org or portal.xoops.og (currently @ xoopsinfo.com)
* everything else

We understand one of the big issues was in the name of our site.... "Why not forum.xoops or community.xoops?" ... well the answer is - why not? We have, in fact, offered to do this before. A simple re-direct from forum.xoops to our site is all it would have taken.

1. Agree with Herve's point about keeping the forum structure as simple as possible:

Quote:

Suggest adding the 'suggestions' forum mentioned previously, and not having a 'complaints' forum (similar thing but think positive!)

2. I suggest NOT including the following from the O.P. because they are already handled through comments on the news stories:
* Module reviews
* Theme reviews

Alternatively, if you want to have these as forums then news stories should have comments *disabled* and include a link to direct the discussion to the relevant forum.

3. I think xoops.org needs to make up its mind whether its going to be a 'core support only' site or not. If it is, then the following forums should also be dropped:
* Module usage
* Module hacks and improvements.

Of course, if xoops.org is going to continue to be core + third party modules then it would be helpful to have a formal decision about it. There is a great deal of confusion about 'community' vs 'project', and these terms are being used in an arbitrary (and frankly, quite unhelpful) manner at the moment.

Realistically, if xoops.org has non-core forums on it then its going to continue to be a community site. I'm not saying that's a bad thing, I'm just saying that the people that are trying to pretend that its 'project only' should stop.

Thanks.