8,288
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − + + + + + + + − +
Talk:Platform Team/Distributed Wiki (view source)
Revision as of 17:44, 9 December 2011
, 17:44, 9 December 2011formatting
== Initial email ==
== Initial email ==
Before starting a discussion on the ML level about a distributed Wiki implementation, I'm seeking your thoughts for that topic.
Before starting a discussion on the ML level about a distributed Wiki implementation, I'm seeking your thoughts for that topic.
The most clear requirement from from the field is about vaving an "offline" Wiki for connectivity-less cases.
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/.
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.
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).
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).
--[[User:Alsroot|alsroot]] 15:42, 9 December 2011 (EST)
: --[[User:Alsroot|alsroot]] 15:42, 9 December 2011 (EST)