wiki-better-than-email - Revision history

Tantek: web archive of wikinomics site, Wikipedia page

2024-09-18T01:07:50Z

web archive of wikinomics site, Wikipedia page

← Older revision		Revision as of 01:07, 18 September 2024
Line 21:		Line 21:

	== additional documentation ==		== additional documentation ==
	* See the book http://www.wikinomics.com/ for more details and explanations on how wikis are more efficient than email for a variety of workflows.		* See the book [https://web.archive.org/web/20100611000023/http://www.wikinomics.com/ www.wikinomics.com] (Internet Archive, or [https://en.wikipedia.org/wiki/Wikinomics its Wikipedia page]) for more details and explanations on how wikis are more efficient than email for a variety of workflows.
	* This picture helps illustrate one of many scenarios - and though we are not sending word documents, the point is, that iterating content through email is far less efficient than iterating content on a wiki: <br /> [http://www.wikinomics.com/blog/index.php/2008/03/26/wiki-collaboration-leads-to-happiness/ http://www.wikinomics.com/blog/uploads/wiki_collaboration2.jpg]		* This picture helps illustrate one of many scenarios - and though we are not sending word documents, the point is, that iterating content through email is far less efficient than iterating content on a wiki: <br /> [http://www.wikinomics.com/blog/index.php/2008/03/26/wiki-collaboration-leads-to-happiness/ http://www.wikinomics.com/blog/uploads/wiki_collaboration2.jpg]

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:35:08Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:35, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Wiki is better than email~~</entry-title>~~		{{DISPLAYTITLE:Wiki is better than email}}

	The wiki works better than email for content (examples, issues, brainstorms etc.) for numerous reasons.		The wiki works better than email for content (examples, issues, brainstorms etc.) for numerous reasons.

Uranther: Fix dead link to 7 Deadly Sins That Block Team Collaboration

2016-06-08T15:41:36Z

Fix dead link to 7 Deadly Sins That Block Team Collaboration

← Older revision		Revision as of 15:41, 8 June 2016
Line 199:		Line 199:
	* [[put-it-on-the-wiki]]		* [[put-it-on-the-wiki]]
	== see also ==		== see also ==
	* [http://pbworks.com/team-collaboration 7 Deadly Sins That Block Team Collaboration (And How To Overcome Them)]		* [http://www.pbworks.com/7-deadly-sins-block-team-collaboration/ 7 Deadly Sins That Block Team Collaboration (And How To Overcome Them)]

TomMorris: /* what if someone starts an edit war on an issue */ adding a discussion about Wikipedia's BRD

2014-07-23T17:43:58Z

what if someone starts an edit war on an issue: adding a discussion about Wikipedia's BRD

← Older revision		Revision as of 17:43, 23 July 2014
Line 150:		Line 150:
	If the individual persists in an edit war, especially after one of the admins have stepped in, the admins will warn and then ban the individual for progressively longer ban times as necessary.		If the individual persists in an edit war, especially after one of the admins have stepped in, the admins will warn and then ban the individual for progressively longer ban times as necessary.

			<div class="discussion">
			* On Wikipedia, there is a principle called the [https://en.wikipedia.org/wiki/Wikipedia:BOLD,_revert,_discuss_cycle BOLD, revert, discuss cycle] (or "BRD" for short). The idea is that you initially make a ''bold'' change to a page without having to have a lot of discussion up-front, and thus avoiding the feeling that one must seek permission from the "owner" of the page. If others disagree with the change, they then revert the change, and then a discussion is conducted to seek consensus. The point of the BRD cycle is to encourage people to engage in reasoned and evidence-based discussion about their disagreements rather than rather than starting an edit war. —[[User:TomMorris\|Tom Morris]] 17:43, 23 July 2014 (UTC)
			</div>

	=== how is the wiki better for controversial issues ===		=== how is the wiki better for controversial issues ===

Tantek: how do wikis reduce duplication of discussions, some re-ordering for better flow

2012-05-22T20:13:06Z

how do wikis reduce duplication of discussions, some re-ordering for better flow

@@ Line 57: / Line 57: @@
 * If a simple search of the wiki fails to quickly reveal an answer to an issue, then ask in the [[IRC]] channel or on an email list as noted in the previous FAQ.
 * Responses to such queries should include URLs to answers on the wiki, hopefully with improved discoverability to increase findability of similar issues in the future.
@@ Line 64: / Line 104: @@
 # People can easily choose to be on IRC or not when it is convenient for them to participate in discussions or not and that aspect of easy in/out control is very important.  Email on the other hand, is much more cumbersome to subscribe/unsubscribe when you have time to handle discussions or don't.
 # In IRC, if a participant has a misconception, others in the channel can quickly correct that participant, rather than the participant waste a lot of time with writing something up that is based on that misconception. In email OTOH, a mistaken assumption in the start of an email can lead to the author wasting time writing paragraphs upon paragraphs dependent on that bad assumption.
@@ Line 136: / Line 170: @@
 As [http://www.paulgraham.com/trolls.html Paul Graham wrote]:
 <blockquote><p>There's a sort of Gresham's Law of trolls: trolls are willing to use a forum with a lot of thoughtful people in it, but thoughtful people aren't willing to use a forum with a lot of trolls in it. Which means that once trolling takes hold, it tends to become the dominant culture.</p></blockquote>

Tantek: /* FAQ */ why do IRC and email lists repeat conversations

2012-05-22T20:01:26Z

FAQ: why do IRC and email lists repeat conversations

← Older revision		Revision as of 20:01, 22 May 2012
Line 64:		Line 64:
	# People can easily choose to be on IRC or not when it is convenient for them to participate in discussions or not and that aspect of easy in/out control is very important. Email on the other hand, is much more cumbersome to subscribe/unsubscribe when you have time to handle discussions or don't.		# People can easily choose to be on IRC or not when it is convenient for them to participate in discussions or not and that aspect of easy in/out control is very important. Email on the other hand, is much more cumbersome to subscribe/unsubscribe when you have time to handle discussions or don't.
	# In IRC, if a participant has a misconception, others in the channel can quickly correct that participant, rather than the participant waste a lot of time with writing something up that is based on that misconception. In email OTOH, a mistaken assumption in the start of an email can lead to the author wasting time writing paragraphs upon paragraphs dependent on that bad assumption.		# In IRC, if a participant has a misconception, others in the channel can quickly correct that participant, rather than the participant waste a lot of time with writing something up that is based on that misconception. In email OTOH, a mistaken assumption in the start of an email can lead to the author wasting time writing paragraphs upon paragraphs dependent on that bad assumption.


			=== why do IRC and email lists repeat conversations ===
			''Why do IRC channels and email lists repeat conversations, e.g. conversations about wikis and emails?''

			The very mediums of IRC and email tend to cause forgetting the past (preferring brief summary statements to actual search/citation) and thus inevitably repeating conversations, including repeating errant statements (see: every email list), unless briefly (and repeatedly) corrected with URLs to answers (like this one).


Line 168:		Line 174:
	** On the side of friendliness, we should reach out to and contact new editors over IRC and email as necessary to help familiarize them with [[how-to-play]] and the [[mailing-list]] guidelines. [[User:Tantek\|Tantek]] 21:23, 15 June 2009 (UTC)		** On the side of friendliness, we should reach out to and contact new editors over IRC and email as necessary to help familiarize them with [[how-to-play]] and the [[mailing-list]] guidelines. [[User:Tantek\|Tantek]] 21:23, 15 June 2009 (UTC)
	</div>		</div>


	== historical note ==		== historical note ==

Tantek: add Will anyone see stuff, When is it better, move historical note to separate section, move capture consensus discussion to its own q

2012-05-22T19:56:33Z

add Will anyone see stuff, When is it better, move historical note to separate section, move capture consensus discussion to its own q

Show changes

Tantek: fix shorturl

2012-05-15T18:59:21Z

fix shorturl

← Older revision		Revision as of 18:59, 15 May 2012
Line 4:		Line 4:

	;short URL		;short URL
	:http://tr.im/wikibetter		:http://ufs.cc/w/wikibetter

	== wikis in plain english ==		== wikis in plain english ==

Jsalsman: /* reasons */ not everyone knows s/n

2010-04-03T18:58:02Z

reasons: not everyone knows s/n

← Older revision		Revision as of 18:58, 3 April 2010
Line 14:		Line 14:
	Here are some reasons why wikis work better than email for microformats in particular, and in fact, for any kind of open standards development.		Here are some reasons why wikis work better than email for microformats in particular, and in fact, for any kind of open standards development.

	* <span id="scaling">'''~~s/n~~ scaling.'''</span> Not everyone is interested in every issue on every format.		* <span id="scaling">'''signal-to-noise scaling.'''</span> Not everyone is interested in every issue on every format.
	* <span id="efficiency">'''efficiency: reading current state vs deltas.'''</span> You can read one wiki page to get the status/thread of an issue whereas with emails you often have to read thru numerous emails (and threads) and apply them like deltas/diffs in your head to understand where an issue etc. ended up.		* <span id="efficiency">'''efficiency: reading current state vs deltas.'''</span> You can read one wiki page to get the status/thread of an issue whereas with emails you often have to read thru numerous emails (and threads) and apply them like deltas/diffs in your head to understand where an issue etc. ended up.
	* <span id="search">'''search/discoverability.'''</span> search for the web/wikis works much better in practice than searching mailing lists (web search of email archives has no thread-smarts for example).		* <span id="search">'''search/discoverability.'''</span> search for the web/wikis works much better in practice than searching mailing lists (web search of email archives has no thread-smarts for example).

Tantek: /* related */ see also pbwiki collab article

2010-04-01T06:46:20Z

related: see also pbwiki collab article

← Older revision		Revision as of 06:46, 1 April 2010
Line 143:		Line 143:
	* [[how-to-play]]		* [[how-to-play]]
	* [[put-it-on-the-wiki]]		* [[put-it-on-the-wiki]]
			== see also ==
			* [http://pbworks.com/team-collaboration 7 Deadly Sins That Block Team Collaboration (And How To Overcome Them)]