[i'm not on [EMAIL PROTECTED], so the moderator there will have to push this thru]
David Blevins <[EMAIL PROTECTED]> writes: > Replying primarily for the people on [EMAIL PROTECTED] Further > replies should probably just go to [EMAIL PROTECTED] Someone correct me if > I'm > wrong. > > On Feb 3, 2006, at 7:08 AM, Noel J. Bergman wrote: >> To quote Atlassian: "Confluence will likely die if slashdotted, so shouldn't >> be used as a *primary* project website if slashdotting is likely." Read >> "slashdotting" as heavy load, and we experience sufficient load on the Wiki >> to make caching mandatory. > > IMHO, this quote comes out opposite as it was meant. > > On Feb 2, 2006, at 4:29 PM, Jeff Turner wrote: >> On Thu, Feb 02, 2006 at 11:56:44AM -0500, Noel J. Bergman wrote: >>> Even Atlassian has recommended against Confluence as a Wiki in our >>> enviroment at this time. >> >> Not quite; Confluence will likely die if slashdotted, so shouldn't be >> used as a *primary* project website if slashdotting is likely. > > The distinction made is: > > - Confluence as a wiki, Good > - Confluence as a live website, Bad IIRC the technical requirements come from experience with the existing moin-moin wiki, so that's probably the context best suited for Noel's remarks. > > There are ways to use the *content* create via Confluence in a website. A > number of people have working solutions already. Most fall into one of or a > mix of this: > > 1. Serving static pages that are generated whenever from content in > Confluence > 2. Smart front-end generating and caching pages from Confluence My concern is that people will be far less creative in how they manage their content if there's an asf-endorsed wiki they can just point users at. IOW, are people doing similarly creative things with the moin-moin wiki, or do they normally just refer folks directly to the content on the "apache wiki"? > I think we are in good shape sans the fact that we should have our own > confluence install. We'd be in better shape if we could just get confluence to perform as well as moin-moin, so policing people's usage would be less of a concern. When it comes to options, the issue of failure recovery is important. What happens if the box dies; does the content die with it? What will happen to the projects dependent on an asf confluence if the technical support for it (which is a perpetual committment) diminishes over time? -- Joe Schaefer
