Platform Team/Distributed Wiki: Difference between revisions

(5 intermediate revisions by 2 users not shown)

Line 1:

==~~Introduction~~==

== The reason ==

~~: ''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~~:

These are the reasons why having a Distributed Wiki would be useful (sorted from the most to the least important):

* ~~Having an "offline" Wiki~~.

* No connectivity at all,

* Connectivity is sporadic when the most regular workflow is off-line,

* Save bandwidth on slow connectivity,

* Support distributed workflow in general,

* Support off-line workflow in general.

~~People have started thinking about (and using) hgwiki~~, ~~http://code~~.~~google~~.~~com/p/hgwiki/~~.

The first three options are important, e.g., for schools in rural regions.

~~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.~~

== References for review ==

~~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)~~.

* http://strategy.wikimedia.org/wiki/Proposal:Distributed_Wikipedia

* 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]

* [[Features/Semantic Web]]

@@ Line 1: / Line 1: @@
-==Introduction==
+== The reason ==
-: ''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:
+These are the reasons why having a Distributed Wiki would be useful (sorted from the most to the least important):
-* Having an "offline" Wiki.
+* No connectivity at all,
+* Connectivity is sporadic when the most regular workflow is off-line,
+* Save bandwidth on slow connectivity,
+* Support distributed workflow in general,
+* Support off-line workflow in general.
-People have started thinking about (and using) hgwiki, http://code.google.com/p/hgwiki/.
+The first three options are important, e.g., for schools in rural regions.
-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.
+== References for review ==
-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).
+* http://strategy.wikimedia.org/wiki/Proposal:Distributed_Wikipedia
+* 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]
+* [[Features/Semantic Web]]