<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Wiki While You Work</title>
	<atom:link href="http://pundit.ca/2007/08/07/wiki-while-you-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://pundit.ca/2007/08/07/wiki-while-you-work/</link>
	<description>Ideas and the Internet, Josh Chalifour Minding the Current</description>
	<lastBuildDate>Mon, 04 Jul 2011 20:39:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dario</title>
		<link>http://pundit.ca/2007/08/07/wiki-while-you-work/comment-page-1/#comment-8810</link>
		<dc:creator>Dario</dc:creator>
		<pubDate>Sun, 30 Sep 2007 14:31:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.pundit.ca/article/wiki-while-you-work/#comment-8810</guid>
		<description>Hi Josh,

thanks for the nice words on Wikka. I agree that the popular security concern (&quot;in a wiki everyone can edit and read anything&quot;) is truly unjustified. Several 2nd generation wiki engines (including Wikka, but surprisingly not MediaWiki) offer fine-grained ACL allowing admins to determine who has privileges do access specific kinds of content (e.g. who can read/write/delete a page, read/write/delete a comment, upload/download a file etc).
We&#039;d love to hear more about your experience using Wikka: if you want to share some ideas or requests, feel free to start a userpage on our website or pop by on our #wikka IRC channel at freenode.net</description>
		<content:encoded><![CDATA[<p>Hi Josh,</p>
<p>thanks for the nice words on Wikka. I agree that the popular security concern (&#8220;in a wiki everyone can edit and read anything&#8221;) is truly unjustified. Several 2nd generation wiki engines (including Wikka, but surprisingly not MediaWiki) offer fine-grained ACL allowing admins to determine who has privileges do access specific kinds of content (e.g. who can read/write/delete a page, read/write/delete a comment, upload/download a file etc).<br />
We&#8217;d love to hear more about your experience using Wikka: if you want to share some ideas or requests, feel free to start a userpage on our website or pop by on our #wikka IRC channel at freenode.net</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Chalifour</title>
		<link>http://pundit.ca/2007/08/07/wiki-while-you-work/comment-page-1/#comment-8809</link>
		<dc:creator>Josh Chalifour</dc:creator>
		<pubDate>Sun, 12 Aug 2007 23:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.pundit.ca/article/wiki-while-you-work/#comment-8809</guid>
		<description>Lee--very interesting example. The electronic storage nightmare that is discovery, is something I&#039;ve become well-acquainted with in recent times. I call it a nightmare, not because I think there&#039;s anything inherently bad about it, but because it&#039;s a huge amount of work. 

When I read your comment, at first I thought &quot;who would want to add to that?&quot; but considering it more, I agree with your comment about the &quot;relatively controlled&quot; environment enabled by a wiki. (actually I think, perhaps it would have been smart to implement one a long time ago, but that&#039;s another story). I&#039;m wondering whether a wiki coudl actually make some aspects of discovery easier and more clear for all the parties involved. If nothing else, it could centralize and give order to a lot of chaos in a way that e-mail archives or instant messaging or a file server can&#039;t. But I think it might be able to do more too.

Our electronic communication methods now record and disseminate all kinds of communication in ways that nobody used to think about or intend. I believe you essentially said that this can lead to errors, and I would guess, often errors that take place this way can come about even through good-intentioned efforts. It&#039;s a massive amount of work to find and understand what these electronic artefacts are and mean. 

With e-mail, it&#039;s sometimes hard to understand the path of the message. Has it been forwarded outside of a work account? Who has been copied on which messages, did they see the entire string of messages or only part? At which points? Did the person forwarding a message change any part of it before forwarding it? Was the content of an attachment accurately represented or received? There are more issues, but e-mail is wild. It gets passed around very easily, and often though innocently, with little understanding of what the actual content (including things like tone of voice, intentions, etc.) of the e-mail message may mean or refer to. Unlike e-mail, wiki pages are not so easily sent to outside mail accounts, nor can they (if set up this way) be changed from person to person without the open and visible tracking of those changes. 

In an e-mail, people might be prone to summarize or leave out important points because these points might not be necessary to their particular message (though perhaps very important in some other way) or they don&#039;t take the care to recopy all the information needed or are just careless. Maybe they don&#039;t have the most up-to-date information to refer to in their messages. Again the easy linkability of wiki pages encourages people to link to the same, already existing pages (rather than reinvent the wheel). If they need to, they can correct and update those pages (of course, the history is typically tracked by the wiki with the person&#039;s name, a timestamp, and before/after views), which are then also available to other people that need them. In other words, instead of having many copies of some information that could be inaccurate, there could be a page that many eyes refer to and visibly maintain its accuracy.

A wiki might also decrease the confusion that results when someone innacurately responds to a forwarded or group e-mail, because s/he didn&#039;t read the entire string of messages or certain key recipients were left off and didn&#039;t have full knowledge of what was being written about. I suppose there is no guarantee that anyone will read an entire wiki page either, but at least there is just one version of the wiki page rather than any number of copies of different e-mail accounts. 

The wiki, though it feels at first glance like a lot of chaos, actually imposes a transparent control on its content which e-mail, instant messaging, shared file servers, etc. lack. If people were to use a wiki more frequently and e-mail less frequently maybe it would ultimately save a company a lot of work during a legal discovery process.</description>
		<content:encoded><![CDATA[<p>Lee&#8211;very interesting example. The electronic storage nightmare that is discovery, is something I&#8217;ve become well-acquainted with in recent times. I call it a nightmare, not because I think there&#8217;s anything inherently bad about it, but because it&#8217;s a huge amount of work. </p>
<p>When I read your comment, at first I thought &#8220;who would want to add to that?&#8221; but considering it more, I agree with your comment about the &#8220;relatively controlled&#8221; environment enabled by a wiki. (actually I think, perhaps it would have been smart to implement one a long time ago, but that&#8217;s another story). I&#8217;m wondering whether a wiki coudl actually make some aspects of discovery easier and more clear for all the parties involved. If nothing else, it could centralize and give order to a lot of chaos in a way that e-mail archives or instant messaging or a file server can&#8217;t. But I think it might be able to do more too.</p>
<p>Our electronic communication methods now record and disseminate all kinds of communication in ways that nobody used to think about or intend. I believe you essentially said that this can lead to errors, and I would guess, often errors that take place this way can come about even through good-intentioned efforts. It&#8217;s a massive amount of work to find and understand what these electronic artefacts are and mean. </p>
<p>With e-mail, it&#8217;s sometimes hard to understand the path of the message. Has it been forwarded outside of a work account? Who has been copied on which messages, did they see the entire string of messages or only part? At which points? Did the person forwarding a message change any part of it before forwarding it? Was the content of an attachment accurately represented or received? There are more issues, but e-mail is wild. It gets passed around very easily, and often though innocently, with little understanding of what the actual content (including things like tone of voice, intentions, etc.) of the e-mail message may mean or refer to. Unlike e-mail, wiki pages are not so easily sent to outside mail accounts, nor can they (if set up this way) be changed from person to person without the open and visible tracking of those changes. </p>
<p>In an e-mail, people might be prone to summarize or leave out important points because these points might not be necessary to their particular message (though perhaps very important in some other way) or they don&#8217;t take the care to recopy all the information needed or are just careless. Maybe they don&#8217;t have the most up-to-date information to refer to in their messages. Again the easy linkability of wiki pages encourages people to link to the same, already existing pages (rather than reinvent the wheel). If they need to, they can correct and update those pages (of course, the history is typically tracked by the wiki with the person&#8217;s name, a timestamp, and before/after views), which are then also available to other people that need them. In other words, instead of having many copies of some information that could be inaccurate, there could be a page that many eyes refer to and visibly maintain its accuracy.</p>
<p>A wiki might also decrease the confusion that results when someone innacurately responds to a forwarded or group e-mail, because s/he didn&#8217;t read the entire string of messages or certain key recipients were left off and didn&#8217;t have full knowledge of what was being written about. I suppose there is no guarantee that anyone will read an entire wiki page either, but at least there is just one version of the wiki page rather than any number of copies of different e-mail accounts. </p>
<p>The wiki, though it feels at first glance like a lot of chaos, actually imposes a transparent control on its content which e-mail, instant messaging, shared file servers, etc. lack. If people were to use a wiki more frequently and e-mail less frequently maybe it would ultimately save a company a lot of work during a legal discovery process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Ward</title>
		<link>http://pundit.ca/2007/08/07/wiki-while-you-work/comment-page-1/#comment-8808</link>
		<dc:creator>Lee Ward</dc:creator>
		<pubDate>Sun, 12 Aug 2007 03:10:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.pundit.ca/article/wiki-while-you-work/#comment-8808</guid>
		<description>Hi Josh
Really excellent post. I am a senior manager at a very large regulated company (pharmaceuticals). There is, in my opinion, inordinate concern within the firm about the legal exposure of permitting wikis within the firewall. The argument is apparently that we are increasing the volume of potentially inaccurate information that might be discoverable in any legal proceeding. For example, in a scientific wiki, it is possible that the safety profile of a medicine under development could be incorrectly or prematurely stated. 

My opinion is that such posts in relatively &quot;controlled&quot; environments such as wikis pale in comparison to the rubbish that can be broadcast via email, instant messaging and the like--all of which is also discoverable in such situations. 

Any thoughts on this, or any information that might be useful on this topic? 
Best regards,
Lee</description>
		<content:encoded><![CDATA[<p>Hi Josh<br />
Really excellent post. I am a senior manager at a very large regulated company (pharmaceuticals). There is, in my opinion, inordinate concern within the firm about the legal exposure of permitting wikis within the firewall. The argument is apparently that we are increasing the volume of potentially inaccurate information that might be discoverable in any legal proceeding. For example, in a scientific wiki, it is possible that the safety profile of a medicine under development could be incorrectly or prematurely stated. </p>
<p>My opinion is that such posts in relatively &#8220;controlled&#8221; environments such as wikis pale in comparison to the rubbish that can be broadcast via email, instant messaging and the like&#8211;all of which is also discoverable in such situations. </p>
<p>Any thoughts on this, or any information that might be useful on this topic?<br />
Best regards,<br />
Lee</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Wiseman</title>
		<link>http://pundit.ca/2007/08/07/wiki-while-you-work/comment-page-1/#comment-8807</link>
		<dc:creator>Mark Wiseman</dc:creator>
		<pubDate>Thu, 09 Aug 2007 07:29:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.pundit.ca/article/wiki-while-you-work/#comment-8807</guid>
		<description>Josh
Great to see a real life example from someone, who has set up a workplace wiki. I think each workplace will make its choices based on its own needs and the ideas of the wiki champions who introduce the idea. There is not a lot of shared experience out there yet, so it was good to see your story.
Mark</description>
		<content:encoded><![CDATA[<p>Josh<br />
Great to see a real life example from someone, who has set up a workplace wiki. I think each workplace will make its choices based on its own needs and the ideas of the wiki champions who introduce the idea. There is not a lot of shared experience out there yet, so it was good to see your story.<br />
Mark</p>
]]></content:encoded>
	</item>
</channel>
</rss>

