As a council member I made this request within the Council forums.

Please can the com's team leaders have access to the spotlight block admin, there is currently news on XOOPS security and a new patch release that isn't spotlighted, this should be spotlighted for the benefit of all the community, but there is nothing I can personally do about this.

For those reading this that haven't seen the latest SECURITY news:

Quote:

Quote:

I second this request - the current features news categories a great, but there are several categories that are not featured and those articles never get front page mention, at all. Perhaps even a rethink about the categories and blocks for news is called for.

Quote:

I couldn't agree more Skenow.

i spotlighted the article for you, but i agree spotlight should come under the responsibility of the comms team

1 I don't think it necessary to spot-lighten the news although it should be displayed on front page in some way.

2 the communication team has not been announced yet. Its access will be assigned once the team is officially established.

3 there is no Council member since the Council is not built yet although I invited tom and JMorris as temporary members for the procedure of team establishment.

A permanent spotlight link to security articles on the homepage would be good for XOOPS IMHO. If new users can see that no security patches and advisories have been required for several months, this reinforces the stability of Xoops.

It would also counteract some of the 'I've been hacked' forum comments. These must be off-putting to newcomers, but in many instances they turn out to be down to failings of the web host, not the XOOPS CMS.

Quote:

Well that's what you call a public dressing down, you made the right decision there despite it possibly being an unpopular one.

Congratulations on that.

I've addressed these issues with you in person over the private council forums and via msn, with little effect back so I'll now comment on a point by point basis:

1. Ok lets not spotlight security news as you say, however personally though I feel this is very important to the community in that they can see security updates in a bold manor on the front page to enable them to update, if they miss this and get their servers hacked, surely that we would be at some partial fault for not better advising our community.

2. OK shall we scrap all the current work done, which was being prepared to be published?

I'm not sure here, as my impression was that we had the go ahead, especially after our chats on the private council forum and via MSN

3. ahh now I understand, perhaps better communication in the future would prevent me overstepping the line again, so whats the council for if it's not established yet it has members?

Just calling for clarification here.

Perhaps you wish to carry the world on your shoulders and I should step down from 'unofficial' positions for you, I can't handle one thing being said and agreed, then something different being done.

Your welcome to keep the work I did with the com's team, should I step from this 'unofficial' position.

Also I've been in contact with a nuke developer whom is considering supporting his module as an XOOPS version too, he's just testing the system and so, who should I pass him onto as part of XOOPS promotion and communications?