Thanks Chris. Unless other have opinions I am also favoring confluence based on the assertions I infer from - https://cwiki.apache.org/CWIKI/ and summary of a long discussion thread from solr - http://s.apache.org/Yqx. Here are some random texts I copied from these sources:
"The Confluence wiki has more finely grained permissions. Some groups are using it to create official project documentation by restricting access to committers and contributors who have filed a CLA. Other spaces that do not represent the official documentation are open to all Confluence users. The Confluence wiki is autoexported to static HTML whenever edits occur, so that high-volume serving can be done. The look-and-feel of the autoexport can be changed, and some projects are working toward making the autoexport site look just like their main website. Confluence also supports commenting on pages, which can be an interesting way to help build up a community. Even if a site is restricted to CLA-equipped authors, other people can still leave comments." "FWIW, at Krugle we started off using MoinMoin and switched to Confluence. In general it's been a good change for us, especially as the scale and scope of our wiki activity increased. And the integration with Jira can be very handy." Some pros as I see: * Create a wiki in close resemblance to the website and minimize the static content on website and move all documentation and tutorials to wiki * Have a PMC area where we bundle release documentation pack * Have a contributors area for tutorials so others in community can contribute (they just need to file a CLA and need not be committers) * Have a public wide open editable area for unofficial content like, this is how I am using airavata, or here is my wish list or random experiences, here is my blog link on how I finally made airavata to build successfully with test cases... * Have the word import export features so we can better encourage user and developer guides * Integrate a section of story/epic for use cases and associate them to jira creating sub tasks Some Cons: * Confluence has more learning curve than moinmoin * Moinmoin editing is much simpler compared to confluence * Confluence has more knobs to tweak which will distract and tempt people like me instead of spending time on content It may be that what all we want can be done with both the wiki's, but we just need to pick one. I will vote +1 on confluence, if any one else has opinion against cwiki or favor strongly on moinmoin, I am ok with that too. --Suresh On Apr 21, 2012, at 1:21 AM, Mattmann, Chris A (388J) wrote: > I find Confluence a heck of a lot easier to PMC-admin, and I like it's markup > better. > > That's just my 2c. :) > > Cheers, > Chris > > On Apr 19, 2012, at 8:11 PM, Suresh Marru wrote: > >> Looks like we are ready for a wiki then. Now the last question before we >> request into setting one up. >> >> Do we have any opinions on CWiki Vs MoinMoin? I am + 0 for both and will go >> with majority. >> >> Suresh > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >
