Hi Drew, > Alexandro does bring up a good point though, about information > pollution. I suppose one way to look at it might be to use the main site > for a location where information is vetted. > ... > MySQL is a good example of this. They have the documentation and then at > the end they have comments by end users, sometimes these have the most > pertinent information when looking for an answer. > ... > I really think something like this would be great > approach.
I'd suppose there are different types of information. "How to connect to MySQL" is not really something I'd like to moderate, that's kind of "low level" information which I think fits perfectly into a Wiki. On the other hand, something like a Developer's Guide /might/ be a different story. Though, I'm not completely sure about this. One reason why I'm looking forward to the Wikified DevGuide is that I (or others) will be able to quickly correct the small errors which are in our chapters. The current process is too cumbersome, and too much overhead for a one-line change, so I simply don't care ATM. In the Wiki, this will change, but only if we do not, again, install big hurdles for contribution. Perhaps MySQL's appraoch is in fact the best compromise. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
