On 9/6/07, Janne Jalkanen <[EMAIL PROTECTED]> wrote: > > > What do you mean? Apache does not have needed lower level projects to > > run JSPWiki? > > How about Tomcat+Harmony? > > Well, let me put it this way: it would be kinda dumb to run our > public wiki site on another wiki engine. ;-)
Dumb? So we must already be dumb, then, to be running other things like JVMs that don't come from the ASF, rather than our own. Is there a roadmap for when JSPWiki will have all of the features and functionality of both Confluence and MoinMoin, including the Confluence macros we use, and the migration tools so that we can move all the existing data from these existing wikis to JSPWiki? Without that, I don't see us replacing our existing wikis with JSPWiki, and I'm absolutely not in favour of adding a third wiki flavour to our infrastructure. Is this the real reason JSPWiki wants to come to the ASF? To be the wiki that the ASF runs on? We also have separate documentation and sandbox wikis. > > http://www.jspwiki.org/wiki/ApacheJSPWikiProposal#section- > ApacheJSPWikiProposal-RequiredResources It's not at all clear from that list that those are wikis and not just regular web sites. Does JSPWiki have an auto-export capability, like Confluence does, so that pages can be offloaded to static resources, instead of hitting the wiki all the time? A tomcat instance is fine (preferably non-shared; JSPWiki cannot be > deployed simply from a war file right now), and I can offer to run > some of the wiki sites (e.g. the sandbox, which is wiped out > regularly) myself. You'll need a dedicated team of people, not just one person, that is committed to doing this on an ongoing basis. -- Martin Cooper /Janne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
