Alternate wiki-implementations: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 1: Line 1:
Currently 3 out of 20 of our registered users are registered [[MediaWiki]] developers, which makes our percentage of developers among users '''15%''', which is likely the highest figure any public MediaWiki installation can boost so that is an good incentive to try to adapt MediaWiki for our use over other wikis
Currently 3 out of 20 of our registered users are registered [[MediaWiki]] developers, which makes our percentage of developers among users '''15%''', which is likely the highest figure any public MediaWiki installation can boost so that is an good incentive to try to adapt MediaWiki for our use over other wikis.  However they might just be here ''because'' we are using MediaWiki, so, it is important to make clear that one of the things the [[R&D Wiki]] is doing is ''choosing'' what technology best fits our [[hardware requirements]] later.
 
There are three leading candidates, and a few dark horses listed afterwards.
 
----
----
<table>
<table>
<tr>
<tr>
<th>MediaWiki</th><th>TikiWiki</th><th>MoinMoin</th>
<th>[[MediaWiki]]</th><th>[[TikiWiki]]</th><th>[[MoinMoin]]</th>
</tr>
</tr>
<td>
<td>
*PHP based
*Proven to perform well under heavy load - but with hard limits
*Proven to perform well under heavy load - but with hard limits
*Most likely basis for [[wikitext standard]]
*Most likely basis for [[wikitext standard]]
Line 15: Line 19:
</td>
</td>
<td>
<td>
*PHP based
*meets ''many'' standards ([[CSS]], [[XHTML]], [[pear.php.net]], [[smarty.php.net]], [[RDF]]
*email/forums (and integration) built-in
*Group management built-in
*Group management built-in
*chat support intended
*Visualization of wiki-links
*Visualization of wiki-links
*Polls built in
*Polls built in
*Many developers doing lots of detail work on CM and CMS
*Many developers doing lots of detail work on CM and CMS
*supports ALL databases not just MySQL
*supports ALL databases not just MySQL
*developers [[eat their own dog food]] = run current beta as their live site for all development, so any problem is immediately obvious to every developer
</td>
</td>
<td>
<td>
*Good parser
*Python language
*Python language
*excellent architecture making extensibility very simple
*excellent architecture making extensibility very simple
*easy to write parsers to meet [[wikitext standard]] or read [[MediaWiki]] or [[TikiWiki]] formats
*[[troll]] in the logo
*[[troll]] in the logo
*no need for SQL
*no need for SQL
Anonymous user