Difference between revisions of "Platform Team/Distributed Wiki"
m (moved Wiki Team/Distributed wiki to Platform Team/Distributed wiki: more of a platform project) |
|||
| Line 16: | Line 16: | ||
* Following [[wikipedia:Wiki_software#cite_note-13|Wiki software citations 14, 15]] | * Following [[wikipedia:Wiki_software#cite_note-13|Wiki software citations 14, 15]] | ||
** [http://www.globule.org/?page_id=72 Decentralized wikipedia at VU University Amsterdam] | ** [http://www.globule.org/?page_id=72 Decentralized wikipedia at VU University Amsterdam] | ||
| + | * [[Features/Semantic Web]] | ||
Revision as of 14:49, 9 December 2011
Introduction
- from Aleksey
Before starting a discussion on the ML level about a distributed Wiki implementation, I'm seeking your thoughts for that topic.
The requirement from from the field is only one:
- Having an "offline" Wiki.
People have started thinking about (and using) hgwiki, http://code.google.com/p/hgwiki/.
But I'm thinking it should be a good idea to have in this offline/distributed wiki an option to behave as a distributed wiki for centralized MediaWiki servers (not only one, but several, e.g., SL's or even Wikipedia). It is better also for teaching (un-skilled) people at school only one markup language - the wikimedia dialect.
I didn't find better solutions except using mwlib (wikipedia uses it for exporting to pdf) as a renderer, keeping wiki page sources in a regular VCS, and having a client that will call mwlib to render the wiki and be a powerful editor for wiki pages (including necessary stuff like i18n, which might be done in client code, not like it is implemented in mediawiki, which is done in php on the server side and renders in http on client's one).