JAVesey wrote:
Quote:

JMorris wrote:

Sourceforge.net
XOOPSinfo.com
XOOPSforge.com
Any one of the local support sites
Any one of the several XOOPS related sites. (XOOPS-magazine, XOOPSFactory, XOOPS-Tips, independent module developers, etc.)

Good suggestions, but a big job to post to all of them.

Is any one of the above list the most "logical" choice were there to be a single nominated posting point?

Or is just one posting-point a little idealistic?

JMorris wrote:

Viral distribution.

If an official statement is posted on say, SF.net, Xi, and XOOPSforge.com, then you reach enough of an audience to kick in the viral effect and the message would spread rapidly.

A single point would be idealistic as not everybody visits a single site.

Your destructive posts about the people who are trying to rebuld the XOOPS project result in a lack of motivation among people who might otherwise want to help.

Good suggestions, but a big job to post to all of them.

Is any one of the above list the most "logical" choice were there to be a single nominated posting point?

Or is just one posting-point a little idealistic?

Dave, I don't think your comments were entirely fair. The perpetual flame wars are a symptom of a problem, not the cause. Get the teams set up, give them access to the tools and authority they need to do their job, let people who want to participate do so, and provide some kind of mechanism to interface the community with the management. And then let it run. Trying to run the project from the top down is a mistake. It hasn't worked before, its not going to work now. No offense intended to anybody, its just what I think.

MadFish wrote:
Quote:

Good suggestions, but a big job to post to all of them.

Is any one of the above list the most "logical" choice were there to be a single nominated posting point?

Or is just one posting-point a little idealistic?

Why not set up a XOOPS security email list that people can subscribe to? Not only could it be used to provide timely security patch announcements, it could also be used to advise users of xoops.org downtime and similar issues. Ideally should not be on the same server, of course.

It should be trivial to set up, inexpensive to run and provides the single launch point for the admins. If its opt-in there'd probably only be a few thousand users max, so bandwidth would not be onerous. People that care can subscribe to it, and people that don't won't have many grounds to complain about being uninformed.

Dave, I don't think your comments were entirely fair. The perpetual flame wars are a symptom of a problem, not the cause. Get the teams set up, give them access to the tools and authority they need to do their job, let people who want to participate do so, and provide some kind of mechanism to interface the community with the management. And then let it run.

Trying to run the project from the top down is a mistake. It hasn't worked before, its not going to work now. No offense intended to anybody, its just what I think.