Andrew, ACTION is good mm'kay.
I think we should at least consider a Java based wiki: - JSPWiki at http://www.ecyrd.com/JSPWiki/Wiki.jsp is used by Cocoon (I installed this locally and had it running in about 5 minutes). - Micael mentioned Chiki (http://chiki.emaho.org/) - this looks pretty good too (but I haven't tried installing it yet). Rodney Waldhoff's comment concerning namespaces is very important. For JSPWiki I think we would need to go down the "federation of wikis with intra-wiki links" path (prefixing with project names becomes a PITA fairly quickly IMO). It looks like Chiki's "nodes" provide independent namespaces, but it wasn't obvious how to go about creating a node (it is worth looking into this though as the "federation" model may require more effort to set up new sub-wikis, but perhaps this is not such a bad thing). Twiki is an excellent cgi based wiki (http://www.twiki.org), but I think we are better off adopting a solution that we can more easily contribute to if we so desire (note that both JSPWiki and Chiki are GPL). I am unsure of the legal ramifications that Tim O'Brien raises, but the whole point of wanting a wiki is to allow update access by non-committers. A more subtle point is whether or not to allow anonymous postings - I myself prefer people to register before they can make changes, it only takes a few seconds, and provides at least some form of (albeit easily circumvented) author trail. It is excellent to see that you are so keen - targeting the end of next week sounds great. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com On 21/12/2002 6:25 AM, "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: > +1 > > Sam, do you or someone have the abillity/will to give me sufficient > rights to install a small cgi script on an apache webserver somewhere > with filesystem access? > > If not, what about servlet engine + database access? > > If so. I will select one based on ease of maintenence, setup, > "security" and set it up by the end of next week. > > Thank you, > > -Andy > > Tom Copeland wrote: > >> Love 'em. Let's pick one and set it up... they're very cool.... >> >> tom >> >> >> >>> -----Original Message----- >>> From: Rodney Waldhoff [mailto:[EMAIL PROTECTED]] >>> Sent: Friday, December 20, 2002 12:36 PM >>> To: Jakarta General List >>> Subject: Re: A Jakarta wiki? >>> >>> >>> On Sat, 21 Dec 2002, Scott Eade wrote: >>> >>> >>> >>>> So how about some feedback: >>>> 1. Wiki's - love 'em or hate 'em? >>>> >>>> >>> Love 'em, and think they would provide (a) a good way to write ad hoc >>> documentation, (b) a good way to host certain discussions. >>> At my day job >>> we use an internal wiki for documentation almost exclusively, and >>> sometimes as an effective public brainstorming tool. (And >>> we're fairly >>> centrally located--for distributed, asynchronous discussion a >>> wiki is even >>> more useful.) >>> >>> >>> >>>> 2. JSPWiki - good choice or bad choice? >>>> >>>> >>> Never used it, so no real opinion, although there seem to be >>> a number of >>> wiki's that are much more popular (perhaps not in java >>> though). There's a >>> big list of wiki impls on Ward's Wiki at >>> <http://c2.com/cgi/wiki?WikiEngines>, of course. >>> >>> (Most wiki clones, JSPWiki included, seem to be GPLed, if >>> that matters to >>> anyone.) >>> >>> >>> >>>> 3. Scope of the wiki(s) - ((Turbine) and (Avalon)), Jakarta >>>> >>>> >>> or Apache? >>> >>> I'd like to see a wiki with at least jakarta scope. >>> >>> One option might be to use a wiki that supports "namespaces", or a >>> federation of wikis with intra-wiki links, so that one could create a >>> "sub-wiki" per project but still support "global" cross-linking. >>> >>> For example, a intra-wiki link might look like >>> Turbine:OracleHowTo versus >>> plain ol' OracleHowTo. >>> >>> Alternatively, a simple convention of prefixing the project >>> name might be >>> sufficient for a shared wiki namespace, but might need >>> support from some >>> WikiGnomes. >>> >>> >>> >>>> 4. Hosting - apache.org or external >>>> >>>> >>> Something internal would seem official. >>> >>> >>> >>>> 5. Timing - now, soon, later or never >>>> >>>> >>> Soon. >>> >>> >>> If I can use this wiki (or this makes it easier to set up >>> another wiki) >>> for other jakarta/apache projects, I'd be more than happy to help out >>> however I can. Please keep me posted, either via jakarta-general, by >>> pointing out where this discussion is happening, or via a direct note. >>> >>> - Rod >>> >>> >>> -- >>> To unsubscribe, e-mail: >>> <mailto:general-> [EMAIL PROTECTED]> >>> For >>> additional commands, >>> e-mail: <mailto:[EMAIL PROTECTED]> >>> >>> >>> >>> >>> >> >> >> -- >> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> >> >> >> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
