Alternate wiki-implementations: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| 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. | '''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. | ||
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. | ||
There are three leading candidates, and a few dark horses listed afterwards. It seems likely that we'd ask those who want to be [[Consumerium developers]] to work on [[wikitext standard]]s and on soliciting and forwarding [[end user feedback]] better, starting with our own [[MediaWiki modifications]] requests. Consumerium users should not have to do anything but list these here. Similar pages for [[TikiWiki modifications]] and [[MoinMoin extensions]] can be created, and which one meets our needs can be more of a competition. In most cases, the features that must be ''added'' are different for each package, since they start with different feature sets. | Also, a good [[software development process]] ''requires'' shifting to a ''new'' development base when moving from [[R&D]] to [[production code]] - most studies show that it is very very bad to use the same platform and the same libraries, for instance, as one used in the R&D phase, in real production. | ||
So, there is ample reason to believe that we might move off [[MediaWiki]] later, or reserve it only for R&D use. There are three leading candidates, and a few dark horses listed afterwards. It seems likely that we'd ask those who want to be [[Consumerium developers]] to work on [[wikitext standard]]s and on soliciting and forwarding [[end user feedback]] better, starting with our own [[MediaWiki modifications]] requests. Consumerium users should not have to do anything but list these here. Similar pages for [[TikiWiki modifications]] and [[MoinMoin extensions]] can be created, and which one meets our needs can be more of a competition. In most cases, the features that must be ''added'' are different for each package, since they start with different feature sets. | |||
Also [[APC Action Apps]] might become important to integrate, since they have broad use among [[nonprofit]]s. One might for instance be written to support some common [[barcode]] readers, in cooperation with [[Adbusters]] or another of the [[essential projects]] which recognizes barcodes as being as critical as we think they are. Maximum cooperation and out-sourcing should be encouraged. | Also [[APC Action Apps]] might become important to integrate, since they have broad use among [[nonprofit]]s. One might for instance be written to support some common [[barcode]] readers, in cooperation with [[Adbusters]] or another of the [[essential projects]] which recognizes barcodes as being as critical as we think they are. Maximum cooperation and out-sourcing should be encouraged. | ||