Wikis have their place as information repositories. It sounds like what you are describing is not a FAQ, though, no? I'm all for using Lucene Wiki as we are currently using - scratch pad, whiteboard, community tips, etc. I think the FAQ is a slighly different beast, hence my double-checking with lucene-dev people.
I'm still unsure about the best setup, so I'll wait a little longer to hear some more opinions. Otis --- Erik Hatcher <[EMAIL PROTECTED]> wrote: > On Dec 19, 2004, at 8:37 PM, Otis Gospodnetic wrote: > > OK. > > Is this _really_ what everyone's okay with? I'm asking because > once we > > put the FAQ onto Wiki we: > > > > 1. no longer have authoritative FAQ - anyone can write to the FAQ > > 2. we have to monitor the Wiki FAQ for correctness > > 3. we have no user-friendly GUI/webapp for Q/A formatting, which > makes > > it more of a pain in the ass to contribute > > > > If anyone has any strong opinions, please share them. If I don't > hear > > anything, I'll (try to) get the jGuru FAQ XML dump and give it to > > Daniel for 'wikification'. > > I prefer to leverage the wiki for this type of information for a > number > of reasons. It is self-maintaining, not requiring a committer to > take > time out to commit changes and update the website. We have e-mail > notification of wiki modifications and thus we already have > monitoring. > There are many cases when using Lucene when the answer is "it > depends" > (such as the filtering question that just came up). Having a wiki > "whiteboard" for these scenarios allows for a broader perspective. > > Erik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
