Hi Todd,
Excellent comments... "Todd V. Jonker" wrote: > > On 12/10/01 9:00 PM, [EMAIL PROTECTED] wrote: > > > Gerard Mason wrote: > >> > >> Excellent idea. The same questions are coming up time and again, especially > >> with regard to JDO. > > > > I fail to see how a new list (castor-user) will prevent that. > > I agree. The *volume* here isn't the problem. Here's the problems I see: > It's been FAR too long since a release, and thus (due to a policy decision > by the Castor team) FAR too long since the easily-accessible online docs > have been updated. I totally agree...I'm trying to get some of those things changed, but the policies are not necessarily created by the "Castor team" but they are more Exolab policies. We're definately working to make it better. I am the project manager, but I don't really have total control over what happens, especially since I have no access to the Exolab servers. I will use all the "clout" that I do have to try to correct these issues. > > 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!! I suppose we assume to much sometimes. I never thought anyone would have a problem building the docs. I don't recall anyone even asking that question, though they may have. > 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 agree... > > Furthermore, there is no easy way to contribute documentation in a way that > others can even read them easily, much less improve them. What do you mean? Have you tried to contribute documentation and others couldn't read it easily or improve them? > > 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. Yikes...I don't know if I like that...I wouldn't want just anyone updating the documentation. Sure we'd get some good comments or updates...but I wouldn't want someone updating the docs with incorrect or misleading information. I agree we need more frequent updates of documentation, but I don't want to a new user to be able to change the documentation because he or she didn't like the way it was written. > > For an excellent example of Wiki technology put to good use, see > > http://twiki.org/ > > We use TWiki as our core Intranet site server, and it is an excellent piece > of (Open Source, of course) software. The TWiki site also demonstrates how > it can be used to track bugs, brainstorm solutions, and document the product > all at the same time. I'll look into it. I don't have access to the Exolab servers so anything like this needs to be approved by Exolab...no just me. Believe me, I wish it was easier to get things like this...but I don't make most of the policies...I just follow them. You've definately "hit the nail on the head" for a number of these issues, and we'll do our best to improve them. Thanks for your comments. --Keith ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
