Mithrandir wrote:
2. Not following you entirely. You mean a list of contacts for e.g. the French support site in the event of the webmaster not being available? Isn't that a task for the support site to make their contact points available? On the other hand, I do see the point of having e.g. a "2nd in command" who is not listed as the webmaster of the site, but who the xoops.org staff or other local support site representatives could contact... I don't know, really. I expected some 2-3 people from each support site being involved in this - plus a handful of people to coordinate, write WOX newsletters, picking up information here and there etc.
In Taiwan, there are two or more local community support site. Because webmasters try to limit the posts more and more or they make the site be personal style which full of the information about personal business. So it's sad that there are two community sites for XOOPS in Taiwan. I think the situation may happened in other countries. The contact point I mean just like the guy who could transfer information between local community site and here. Maybe the guy who don't like to stay at the official local community site but would like to let the world know what happened in local area, like me.
Is this project an open source project?? Yes, you don't have to open everything here. But you'll make more and more gaps between us if you try to make more private areas here. Something happened similarly in egroupware. Some developers hated to communicate in private areas and then the fighting happened. There's a result :
http://www.egroupware.org/ConstitutionB
Some developers were sad and left. They now only limit the post privilege but open all information for the whole community. I hope there will be no the same fighting here.
You could try to send the latest news to all webmasters who in charge of the local community site. Using mailing list in sf.net or dev.xoops.org is great. The process could even be automatic sent when the news are submited.