Platform Team/Distributed Wiki - Revision history

FGrose at 21:53, 9 December 2011

2011-12-09T21:53:11Z

← Older revision		Revision as of 17:53, 9 December 2011
Line 1:		Line 1:
	== The reason ==		== The reason ==

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

	* No connectivity at all,		* No connectivity at all,

Alsroot: moved Platform Team/Distributed wiki to Platform Team/Distributed Wiki

2011-12-09T21:16:52Z

moved Platform Team/Distributed wiki to Platform Team/Distributed Wiki

← Older revision	Revision as of 17:16, 9 December 2011
(No difference)

Alsroot at 21:14, 9 December 2011

2011-12-09T21:14:26Z

← Older revision		Revision as of 17:14, 9 December 2011
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~~:		The reasons why having Distributed Wiki is 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).
	~~==References for review==~~
	* http://strategy.wikimedia.org/wiki/Proposal:Distributed_Wikipedia		* http://strategy.wikimedia.org/wiki/Proposal:Distributed_Wikipedia
	* 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]]		* [[Features/Semantic Web]]

FGrose at 19:49, 9 December 2011

2011-12-09T19:49:16Z

← Older revision		Revision as of 15:49, 9 December 2011
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]]

FGrose: moved Wiki Team/Distributed wiki to Platform Team/Distributed wiki: more of a platform project

2011-12-09T19:38:36Z

moved Wiki Team/Distributed wiki to Platform Team/Distributed wiki: more of a platform project

← Older revision	Revision as of 15:38, 9 December 2011
(No difference)

FGrose at 19:25, 9 December 2011

2011-12-09T19:25:18Z

← Older revision		Revision as of 15:25, 9 December 2011
Line 12:		Line 12:

	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).
			==References for review==
			* 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]

FGrose: Created page with "==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 requireme..."

2011-12-09T18:44:58Z

Created page with "==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 requireme..."

New page

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