Alternate wiki-implementations: Difference between revisions
no edit summary
(added GetWiki) |
No edit summary |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
'''Wiki code''' enables the [[ | '''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 16: | Line 16: | ||
<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 | ||
* | *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 developers heavily involved in content problems, although they are in general [[Wikipedia]] content problems | *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 | ||
*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 | *already converted into the [http://en.wikipedia.org/wiki/TomeRaider TomeRaider format] for off-line browsing on many [[handheld device]]s | ||
</td> | </td> | ||
<td> | <td> | ||
GetWiki is a [[fork]] of MediaWiki | 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 | * 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) | * Improved use of [[Cascading Style Sheets|CSS]] styles (colours, positioning) | ||
* Cleaner output to the browser, [[PHP programming language|PHP]] code underneath | * 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 integrated and effective use of [[Cascading Style Sheets|CSS2]], beyond font colours | ||
* More intuitive User Preferences page | * More intuitive User Preferences page | ||
| Line 49: | Line 49: | ||
</tr> | </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 | ||
* | *Uses different [[wikisyntax]] then Wikipedia | ||
*Meets ''many'' standards ([[CSS]], [[XHTML]], [[RDF]] | |||
*Relies on [[pear.php.net]], [[smarty.php.net]] | *Relies on [[pear.php.net]], [[smarty.php.net]] | ||
*email/forums (and integration) built-in | *email/forums (and integration) built-in but rarely used | ||
*Group management built-in | *[[Group management]] built-in - would this help with [[faction]]s? | ||
*Visualization of wiki-links | *Visualization of wiki-links | ||
*Polls built in | *[[Polls]] built in | ||
* | *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]] | ||
*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> | ||