I haven't used JSPWiki, but I have used the Python-based MoinMoin and really, really like it.
I just took a quick look at JSPWiki and I wouldn't be surprised if it's feature set is based on MoinMoin (or vice-versa, it's always hard to tell). It helps with discussions, and provides a temporary home for documentation and such. Part of the Tapestry/Jakarta proposal is a request for a Wiki. Tapestry has gotten great mileage out of its Wiki, even those its the completely lame PHPWiki (which can be hosted directly on SourceForge, the only reason to use it). ----- Original Message ----- From: "Scott Eade" <[EMAIL PROTECTED]> To: "Jakarta General List" <[EMAIL PROTECTED]> Sent: Friday, December 20, 2002 8:39 AM Subject: A Jakarta wiki? > About a month ago a discussion occurred over on turbine-user/dev about the > possibility of setting up a wiki to use for creating ad hoc documentation as > well as a place to develop more formal documentation that might perhaps > later be converted to xdoc for direct inclusion in the actual project site. > > We discussed setting something up on a non-apache server, but thought we > would first seek an opinion as to whether or not an apache hosted solution > might be a possibility. > > To this end, I posted a query to [EMAIL PROTECTED] (quoted below). > The brief discussion that ensued between Brian Behlendorf, Pier Fumagalli > and myself concluded that I was to liaise with Pier to set up a JSPWiki > instance on nagoya. I provided Pier with some information and asked him > what the next steps might be, but unfortunately Pier has become overloaded > with work and has been unable to get back to me (I'm not complaining Pier - > all things take time and time is a limited resource). > > Anyway, I have two motivations for mailing the general list: > 1. To raise the profile of this request in hope of sparking some action. > 2. To gain some feedback as to the desirability of widening the scope of the > wiki beyond turbine. As mentioned below, Cocoon already have an external > (non-apache hosted) wiki. Leo Simons has also indicated that a similar > discussion has recently taken place over on the Avalon lists with the > conclusion being that they too would like to set up a wiki. > > So how about some feedback: > 1. Wiki's - love 'em or hate 'em? > > 2. JSPWiki - good choice or bad choice? > > 3. Scope of the wiki(s) - ((Turbine) and (Avalon)), Jakarta or Apache? > > 4. Hosting - apache.org or external > > 5. Timing - now, soon, later or never > > > Cheers, > > Scott > -- > Scott Eade > Backstage Technologies Pty. Ltd. > http://www.backstagetech.com.au > .Mac Chat/AIM: seade at mac dot com > > > On Fri, 15 Nov 2002, Scott Eade wrote: > > On turbine-user & turbine-dev (jakarta) we have been discussing the > > possibility of setting up a wiki to use for creating ad hoc documentation as > > well as a place to develop more formal documentation (perhaps we will > > convert it to xdoc and make it part of the "real" docs once we are happy > > with it). > > > > To this end, we are wondering if it would be possible to establish a wiki > > somewhere on an apache server. > > > > At this stage our desire is for a wiki that provides information about > > turbine and its related projects (torque, fulcrum, etc.), but perhaps the > > entire jakarta or even apache community could benefit from the free flow of > > information that is facilitated by a wiki. > > > > We are open minded about the wiki implementation to be used. There is a > > maven plugin that provides quite a nice customisation of the UseMod wiki. I > > myself have used twiki and am fairly happy with it. Cocoon uses an > > externally hosted JSPWiki which looks pretty good (being a Java person I > > would probably have used this in preference to twiki had I found it > > earlier). > > > > Anyway, what are the chances of getting something set up on an apache > > server? > > > > What would I need to do to get something happening? > > > > Thanks, > > > > Scott > > > > > -- > 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]>
