Interesting timing. As a new Castor user, I can relate to this discussion.

> New users are HIGHLY unlikely to "go to CVS" to check the docs.  Even if
> they do manage to get a copy of the recent codebase (which is basically
> impossible to even find given the current site), there isn't even a simple
> README to tell them how to build the docs!!  New users are therefore
forced
> to rely on the public website.  The public site MUST be updated more
> frequently in order to decrease the redundant questions on the mailing
list.

I wouldn't even think to look in the CVS repository for new docs.

> The solution I propose is for the Castor team to install a public Wiki
site
> to house documentation.  As has been proven by many other such
> installations, Wiki is by far the best way to enable rapid creation and
> dissemination of information.  It's extremely easy for even the newest
users
> to search, correct, and even contribute content to a Wiki site.

Excellent idea! This works extremely well for the WebMacro project (another
component I'm actively using). I'd love to see something like this
implemented for Castor.

Michael

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to