Jump to content

Alternate wiki-implementations: Difference between revisions

no edit summary
(+Drupal)
No edit summary
 
(8 intermediate revisions by 5 users not shown)
Line 1: Line 1:
'''Wiki code''' enables the [[Content Wiki]] and [[Opinion Wiki]].  Choices we make about it will guide the [[Consumerium Software License]] and likely also the [[software development process]] - probably in ways we can't easily change or undo later.  With so many '''alternate wiki implementations''' out there, it is important to sort through the advantages and disadvantages of each.
'''Wiki code''' enables the [[Research Wiki]] and [[Publish Wiki]].  Choices we make about it will guide the [[Consumerium Software License]] and likely also the [[software development process]] - probably in ways we can't easily change or undo later.  With so many '''alternate wiki implementations''' out there, it is important to sort through the advantages and disadvantages of each.


This starts by considering the [[wikitext standard]] that our present text is in:  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.
This starts by considering the [[wikitext standard]] that our present text is in:  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.
Line 12: Line 12:
<table>
<table>
<tr>
<tr>
<th>[[MediaWiki]]</th><th>[[TikiWiki]]</th><th>[[MoinMoin]]</th>
<th>[[MediaWiki]]</th><th>[[GetWiki]]</th>
</tr>
</tr>
<td>
<td>
*Not humanly possible for [[end user feedback]] to reach developers reliably
*Not humanly possible for [[end user feedback]] to reach developers reliably, though [[Meta-Wikipedia]] has some channels experienced [[trolls]] can exploit
*PHP based
*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]]
*Only rational basis for [[wikitext standard]] given over one million articles in fifty languages
*Working now for R&D purposes
*Working now for R&D purposes
*Dedicated developer community which also mostly develops content
*Dedicated developers heavily involved in content problems, although they are in general [[Wikipedia]] content problems
*Readable documentation, thanks to the above
*Readable documentation, thanks to the above
*A very high ratio of developers (15% of registered users) registered in [[consumerium]]
*supports [[MySQL]] only
*supports [[MySQL]] only
*already converted into the [http://en.wikipedia.org/wiki/TomeRaider TomeRaider format] for off-line browsing on many [[handheld device]]s
</td>
<td>
GetWiki is a [[fork]] of MediaWiki under [[CC-nc-sa]]
*same de facto [[wikitext standard]]
* Auto-import of Wikipedia articles via [[XML]] using [[PHP programming language|PHP]]'s [[Expat]] Library
* Well-formed [[XHTML]], replacing deprecated [[HTML]] 4.0 versions
* Improved use of [[Cascading Style Sheets|CSS]] styles (colours, positioning)
* Cleaner output to the browser, [[PHP programming language|PHP]] code underneath
* More integrated and effective use of [[Cascading Style Sheets|CSS2]], beyond font colours
* More intuitive User Preferences page
* Clearer labeling and checkbox placements
* Fixed user login retention and other fixes
* Better use of [[license|licensing]] notices on pages
* Image [[Wikinfo:Image use policy|thumbnail]] display
* Better organization of [[function]]s and classes, filenames and [[variable]]s
* More comprehensive [[sysop|administrator]] tools
</td>
</td>
</tr>
<tr>
<th>[[TikiWiki]]</th><th>[[MoinMoin]]</th>
</tr>
<td>
<td>
*Not humanly possible for [[end user feedback]] to reach developers at all - form for describing [[wiki feature request]] incomprehensible even to a [[usability guru]]
*incomprehensible, worthless, [[SourceForge]] bug reporting;  Not humanly possible for [[end user feedback]] to reach developers at all - form for describing [[wiki feature request]] incomprehensible even to a [[usability guru]]
*Feature rich (e.g. forums, picture gallery, blog, maps, email newsletter)
*Comment forum on every page
*Granular [[user group]] permissions - may be drawback, see [[forgiveness not permission]]
*PHP based
*PHP based
*meets ''many'' standards ([[CSS]], [[XHTML]], [[pear.php.net]], [[smarty.php.net]], [[RDF]]
*Uses different [[wikisyntax]] then Wikipedia
*email/forums (and integration) built-in
*Meets ''many'' standards ([[CSS]], [[XHTML]], [[RDF]]
*Group management built-in
*Relies on [[pear.php.net]], [[smarty.php.net]]
*chat support intended
*email/forums (and integration) built-in but rarely used
*[[Group management]] built-in - would this help with [[faction]]s?
*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
*Large active developer community with scattered documentation and communition forums
*supports Postgres, Oracle, Sybase and [[SQLite]] (built in PHP 5.0!) databases not just MySQL - strategic to integrate with some [[essential projects]]
*Supports Postgres, Oracle, Sybase and [[SQLite]] (built in PHP 5.0!) databases not just MySQL - strategic to integrate with some [[essential projects]]
*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
*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>
*[[End user feedback]] directly solicited in a public wiki
*[[End user feedback]] directly solicited in a public wiki
*Python language
*[[Python]] language, useful for possible future development of advanced [[UI]] and [[Consumer Agent]]-program(s) on mobile platforms
*excellent architecture making extensibility very simple - [[Market Model]] separating [[ActionMarket]], [[ProcessorMarket]], [[SkinMarket]] and [[ParserMarket]] - each of which runs in strict [[Request and Offer form]].
*excellent architecture making extensibility very simple - [[Market Model]] separating [[ActionMarket]], [[ProcessorMarket]], [[SkinMarket]] and [[ParserMarket]] - each of which runs in strict [[Request and Offer form]].
*thanks to [[ParserMarket]], it's easy to write parsers to meet [[wikitext standard]] or read [[MediaWiki]] or [[TikiWiki]] formats
*thanks to [[ParserMarket]], it's easy to write parsers to meet [[wikitext standard]] or read [[MediaWiki]] or [[TikiWiki]] formats
Line 46: Line 74:
*[[troll]] in the logo
*[[troll]] in the logo
*no need for *any* SQL - relies on [[Unix file system]] only - fewer glitches, fewer reports (most of which are turned off in the heavy-load wikis anyway)
*no need for *any* SQL - relies on [[Unix file system]] only - fewer glitches, fewer reports (most of which are turned off in the heavy-load wikis anyway)
*thanks to Python, easy [[mobile device code]] integration (11 lines of Python does what 1000 lines of C++ does, according to some [[mobile device vendor]]s)
</td>
</td>
</tr>
</tr>
</table>
</table>
Line 62: Line 92:
*[[Opinion Wiki]]
*[[Opinion Wiki]]
*[[The Consumerium Exchange]]
*[[The Consumerium Exchange]]
*[http://www.semioticpixels.com/cms/techmatrix.php detailed comparison of integration requirements of various LAMP CMS] including tikiwiki
Anonymous user
We use only those cookies necessary for the functioning of the website.