The new docs library will be run very differently from the old type. One thing we realised is that we cannot rely on a small group of people to provide and maintain all the required documentation. We tried hard to provide the basics, but beyond that we cannot possibly disseminate and document every module, hack, or piece of software requiring user guides.

It appeared to me that the XOOPS tagline "powered by you" and "developed by you" should be continued with the concept "written by you" for documentation.

This follows the true spirit of the XOOPS community ethos. The new docs system will support this fully, by allowing users to submit, ammend and contribute changes to documentation. All this will of course be subject to approval and moderation, so there will be no chance of an uncontrolled free-for-all

All this opens up the work effort to the community, who I believe is very capable and talented enough to supercede all the previous efforts of a small group of documenters. It will also leave an open door invitation for module creators to submit their own documentation, either themselves, or by an appointed writer or co-worker.

Lance, this I think will speak to your comments about a wiki. However the structure will use a non-wiki module utilising templates, which maintain a more uniform and professional presentaion than a wiki can presently offer.

I have been exactly where kalpax is and I understand the frustration. I have a different experience with the support community though; I feel like they have all been extremely helpful. That was before the release of version 2.2 and I have a feeling the community was a little bit more relaxed back then...

with that said, I have made a small observation (which may or may not be correct): I have a feeling there are many many more problems related to modules rather than the core cms itself.

What about a list of modules approved by XOOPS that follow the QA requirements set forth? I know this would require even more work for the moderators and support, but at least then users know what modules are proberly documented and what modules are released without much documentation and so proper support is hard to expect. That would also place an incentive on the module writers to properly document their modules, because if they don't, their module it not listed on the "supported modules list" so to speak.

I consider myself an experienced user of XOOPS by now, and although my schedule doesn't permit me to devote too much time back, I am more than willing to provide whatever help I can (document writing, etc.)

Ken.

Dummy morons must die!!! I can configure, understand and use any and all modules (60+), installed on my Proving Grounds

Overly aggressive flamers must chill out!

Quote:

It's been really nice and productive around here for the last few days without hateful posts. Please don't start mucking up everthing with your hate. If you have something to say, please say it in a respectful way.

Best Regards,

James

Quote:

I think we have our first 'Mentor' here! Thank you for volunteering LazyBadger. It's good to see you have a constructive helpful side as well.

Herko

Quote:
OLD CORRECT FIDO-rule:
"LMD-DML" (for n00bs: "Lamers must die, dummies must learn")

Quote:
No, I can be only "sansay", if you can see difference here

Quote:

Thanks Ken nearer the time, we will be lloking for volunteers to assist in moderation and document housekeeping.

Quote:

That sounds great.
It like a "Beginner's Guide from a Beginner's point of view"

Consider me as a volunteer for this. My studies schedule is tough but i will love to help the community.

Quote:

Something was started in this direction. But now we need some structure on getting it done. The QA check list is done, all that needs doing is putting modules through their paces and reporting the results back.

It would be good to have a public list of modules to check, maybe in a forum,(one thread per module) then have the volunteers fill in the QA checklist and post it back on that forum. Moderate those threads so a moderator needs to approve the post before it shows, this way we'll get rid of the useless chatter in those threads. Put out only maybe 5 modules per week/2week period, so as not to have the whole thing undoable by having 60 modules on the list at once.

Anyway, just some rough ideas.