Alternate wiki-implementations - Revision history

142.177.103.132 at 18:02, 16 August 2004

2004-08-16T18:02:22Z

← Older revision		Revision as of 18:02, 16 August 2004
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
Line 27:		Line 27:
	</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]]		*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

142.177.103.132: fix wiki names

2004-08-16T17:59:18Z

fix wiki names

← Older revision		Revision as of 17:59, 16 August 2004
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.

142.177.103.132: restoring legitimate criticisms of worthless SourceForge non-feedback mechanisms and impossibility of submitting bug reports, compressing the rest,

2004-08-16T17:58:42Z

restoring legitimate criticisms of worthless SourceForge non-feedback mechanisms and impossibility of submitting bug reports, compressing the rest,

← Older revision		Revision as of 17:58, 16 August 2004
Line 19:		Line 19:
	*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 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
Line 28:		Line 28:
	<td>		<td>
	GetWiki is a [[fork]] of MediaWiki		GetWiki is a [[fork]] of MediaWiki
			*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		* Well-formed [[XHTML]], replacing deprecated [[HTML]] 4.0 versions
Line 48:		Line 49:
	</tr>		</tr>
	<td>		<td>
			*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)		*Feature rich (e.g. forums, picture gallery, blog, maps, email newsletter)
	*Comment forum on every page		*Comment forum on every page
	*Granular user group permissions		*Granular [[user group]] permissions - may be drawback, see [[forgiveness not permission]]
	*PHP based		*PHP based
	*Uses different [[wikisyntax]] then Wikipedia		*Uses different [[wikisyntax]] then Wikipedia
	*Meets ''many'' standards ([[CSS]], [[XHTML]], [[RDF]]		*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?
	*chat support intended
	*Visualization of wiki-links		*Visualization of wiki-links
	*Polls built in		*[[Polls]] built in
	*~~Highly~~ active ~~development~~		*Large active developer community with scattered documentation and communition forums
	*Large 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

67.70.36.233: revise tikiwiki -JD

2004-08-16T15:58:29Z

revise tikiwiki -JD

← Older revision		Revision as of 15:58, 16 August 2004
Line 48:		Line 48:
	</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]]~~		*Feature rich (e.g. forums, picture gallery, blog, maps, email newsletter)
			*Comment forum on every page
			*Granular user group permissions
	*PHP based		*PHP based
	*~~meets~~ ''many'' standards ([[CSS]], [[XHTML]], [[RDF]]		*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
Line 57:		Line 60:
	*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~~		*Highly active development
	*~~supports~~ Postgres, Oracle, Sybase and [[SQLite]] (built in PHP 5.0!) databases not just MySQL - strategic to integrate with some [[essential projects]]		*Large 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>

Jukeboksi: formatting

2004-03-04T14:18:04Z

formatting

← Older revision		Revision as of 14:18, 4 March 2004
Line 23:		Line 23:
	*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
	*A higher 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		*already converted into the [http://en.wikipedia.org/wiki/TomeRaider TomeRaider format] for off-line browsing on many [[handheld device]]s
Line 30:		Line 29:
	GetWiki is a [[fork]] of MediaWiki		GetWiki is a [[fork]] of MediaWiki
	* 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
	* Well-formed [[XHTML]], replacing deprecated [[HTML]] 4.0 versions
	* 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

Jukeboksi: added GetWiki

2004-03-04T14:16:24Z

added GetWiki

@@ Line 12: / Line 12: @@
 <table>
 <tr>
-<th>[[MediaWiki]]</th><th>[[TikiWiki]]</th><th>[[MoinMoin]]</th>
+<th>[[MediaWiki]]</th><th>[[GetWiki]]</th>
 </tr>
@@ Line 27: / Line 27: @@
 *already converted into the [http://en.wikipedia.org/wiki/TomeRaider TomeRaider format] for off-line browsing on many [[handheld device]]s
 </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]]

142.177.7.136: moved TomeRaider point here

2004-02-29T00:00:14Z

moved TomeRaider point here

← Older revision		Revision as of 00:00, 29 February 2004
Line 21:		Line 21:
	*Most likely basis for [[wikitext standard]]		*Most likely basis for [[wikitext standard]]
	*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]]		*A higher 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>

Line 50:		Line 51:
	*[[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>

Jukeboksi: pear and smarty are requirements not something implemented in TikiWiki. Link to Python from MoinMoin

2004-02-22T17:58:10Z

pear and smarty are requirements not something implemented in TikiWiki. Link to Python from MoinMoin

← Older revision		Revision as of 17:58, 22 February 2004
Line 14:		Line 14:
	<th>[[MediaWiki]]</th><th>[[TikiWiki]]</th><th>[[MoinMoin]]</th>		<th>[[MediaWiki]]</th><th>[[TikiWiki]]</th><th>[[MoinMoin]]</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
Line 25:		Line 26:
	*supports [[MySQL]] only		*supports [[MySQL]] only
	</td>		</td>

	<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]]		*Not humanly possible for [[end user feedback]] to reach developers at all - form for describing [[wiki feature request]] incomprehensible even to a [[usability guru]]
	*PHP based		*PHP based
	*meets ''many'' standards ([[CSS]], [[XHTML]], [[pear.php.net]], [[smarty.php.net~~]], [[RDF~~]]		*meets ''many'' standards ([[CSS]], [[XHTML]], [[RDF]]
			*Relies on [[pear.php.net]], [[smarty.php.net]]
	*email/forums (and integration) built-in		*email/forums (and integration) built-in
	*Group management built-in		*Group management built-in
Line 38:		Line 41:
	*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 47:		Line 51:
	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)
	</td>		</td>

	</tr>		</tr>
	</table>		</table>

142.177.41.42: excellent reference - but doesn't cover application side issues, only installation/integration

2004-01-29T16:36:15Z

excellent reference - but doesn't cover application side issues, only installation/integration

← Older revision		Revision as of 16:36, 29 January 2004
Line 62:		Line 62:
	*[[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

142.177.99.128: +Drupal

2003-11-13T02:26:26Z

+Drupal

← Older revision		Revision as of 02:26, 13 November 2003
Line 50:		Line 50:
	</table>		</table>

	Dark horses include [[VeryQuickWiki]] (a [[Java wiki]] very easy to set up and run without problems), [[UseMod]] (only advantage is that it dumps [[XML output]], very very very important until there is a real [[wikitext standard]]), and [[Zope]] (also dumps XML, and is in use at other [[essential projects]] like [http://act.greenpeace.org ACT.Greenpeace.org].		Dark horses include [[VeryQuickWiki]] (a [[Java wiki]] very easy to set up and run without problems), [[UseMod]] (only advantage is that it dumps [[XML output]], very very very important until there is a real [[wikitext standard]]), and [[Zope]] (also dumps XML, and is in use at other [[essential projects]] like [http://act.greenpeace.org ACT.Greenpeace.org]. There is finally [[Drupal]] which has many advantages and includes XML output as well.

	Also [[Microsoft wiki]] will likely be out eventually, and some [[peer2peer]] options relying perhaps on [[XForms]] later. [[Microsoft Internet Explorer XML Support]] is an important constraint on which of these features can be used at all. It may be a wise tradeoff to support only MSIE for certain [[user role]]s, if these are ''always'' taken on by well-equipped well-supported people who can be far more easily supported by relying on IE's XML, than any other method. By the same argument, if Opera or Netscape does something uniquely well and only two or three people need that capability, requiring those might also make sense for some roles. For ordinary end users the [[APC Action Apps]] baseline browser capabilities should probably be adopted as Consumerium's own.		Also [[Microsoft wiki]] will likely be out eventually, and some [[peer2peer]] options relying perhaps on [[XForms]] later. [[Microsoft Internet Explorer XML Support]] is an important constraint on which of these features can be used at all. It may be a wise tradeoff to support only MSIE for certain [[user role]]s, if these are ''always'' taken on by well-equipped well-supported people who can be far more easily supported by relying on IE's XML, than any other method. By the same argument, if Opera or Netscape does something uniquely well and only two or three people need that capability, requiring those might also make sense for some roles. For ordinary end users the [[APC Action Apps]] baseline browser capabilities should probably be adopted as Consumerium's own.