Posted on: 2005/4/27 18:56
Re: What's going on with XOOPS
I have a fairly strong organizational background and will assist in this however I can be best utilized.
I would also like to add:
1) Make the Local Support criteria simple enough to not deter potential contributors.
2) It seems to me that the forums/site should be enabled for multi-lang even though a good bit of the content posts may (permanantly) reside in native languages... This would make it easier for Local Support team members to create a structure where multiple people can commit information and only a single entity would be necessary to perform translations on vital posts and act as the lead for that geography.
If this would create issues for the existing infrastructure of xoops.org or dev.xoops.org I suggest creating a new multi-lang site 'team.xoops.org' or something similar. As to the nuiances (user reg. etc) this could all be ironed out one way or another.
3) Maintaining user access will be necessary regardless of how this is implemented. I would suggest a bit more discussion of how to 'maximize the benifit' prior to actually adding additional resources that may or may not provide the desired functionality in a long term scenario.
This would be simplified by the structure created by suggestion 2 (above) as the moderators of the newsletter could pull directly from the posts which have been translated by the 'in geography' lead (on the new site/forums) due to importance. EG: there could be a single forum (WOX) for posts which Local Support site Leads wish to see appear in the WOX.
If we were to make a forum specific to the newsletter, it would take the responsibility for posting timely, important entries AND translation out of the moderators hands, and place the responsibility on the local administrators. This way the accountability chain seems to be better defined and at a local level.
If we are to better inform and unite XOOPS contributors and local support site users, we should make every effort to meet today's and tomorrow's needs the first time.
We should attempt to make the system as self actualizing as possible from both an accountability and procedural vantagepoint. Creating the tools is one thing, but management is another... the closer we can tie the two together the less legwork any one person need do.
Personally I think the language barriers are the root of most of the communications voids. If this is the case, it is imperative that the structure of this project be geared toward dealing with, or breaking down, the language barriers if not by technology then by administration. Otherwise we will find ourselves expending effort and not resolving the issues we hope to address.
While reading the posts on this topic I noticed that many people are under the assumption that Q&A forums would exist in this environment and may detract from the existing forums. I see no reason for this project to have that type of functionality, and would imagine that this endeavor would serve as a method of keeping the entire XOOPS community abreast of future plans, changes, announcements and development news.
But that's just my 2cents...