draj,
I went to the link:
Quote:
According the each of the Project teams' discussion, it is time for the teams to be finalized.
Can each of the project teams, 1)core dev, 2)design, 3)documentation and 4)coordinator, please send your documents to the Project council for pre-review and discussion with:
team mission and tasks
rules
member list
team leader and coordinator
team roadmap (if available)
extra materials
We hope the materials to be sent to xoops-council AT googlegroups.com (please use phppp @ users.sourceforge.net if the googlegroup mail does not work) by this Saturday.
The Project aim or stated goal is getting or producing opensource code, and presenting it to the community for their use, with documentation.
The community then takes this code to build their modules, themes, with the added expectation they document their efforts also.
Everything I see he has done so far is ready the field to make progress on presenting this code as bug free as possible under the circumstances. And re-creating the xoops.org websites structure to present the core product along with the necessary documentation, and help structure.
People have been appointed to POINT end-uses and prospective new-users to the proper areas of XOOPS expertise. Taking the #oops# I'm lost out of xoops.
The community of XOOPS is just that, a community; we are spread far and wide and have many XOOPS prefixed outlets from which to choose our add-ons. Also outlets that don't even have XOOPS in its tradename.
Bringing all the community's under one roof called xoops.org is not practical from the standpoint of server accommodations or language considerations.
I believe ANYONE who has the ability or desire to build a community around XOOPS is free to do so, without any interferenced from phppp. As a matter of fact I think he will support any of the communities that spring up.
Meanwhile give him space to do his job, and put your efforts to building a community of XOOPS module/theme/add-on builders or end-users etc., and let the appropriate team appointees know where to find you when a client has a question you are most qualified to answer and help with.
Xoops may be powered by us, but it is not our ball in play... never has been.
The project belongs to the foundation, the results of its code building is a free gift to the people.
phppp (in his statement omissions) gave the community members the gift of freedom to do and to use without his "interference" I say pick up the ball and go with it , and don't expect phppp to do it for you, he has a plate full.
Just my BlueStocking opinion.