<?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: Distributed User Testing of Archive Behavior in Ubuntu</title>
	<atom:link href="http://davidsiegel.org/distributed-user-testing-archives/feed/" rel="self" type="application/rss+xml" />
	<link>http://davidsiegel.org/distributed-user-testing-archives/</link>
	<description>David Siegel</description>
	<lastBuildDate>Wed, 08 Sep 2010 16:29:35 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lightbreeze</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1724</link>
		<dc:creator>Lightbreeze</dc:creator>
		<pubDate>Tue, 04 Aug 2009 03:05:28 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1724</guid>
		<description>He might mean http://www.mono-project.com/Python</description>
		<content:encoded><![CDATA[<p>He might mean <a href="http://www.mono-project.com/Python" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.mono-project.com/Python?referer=');">http://www.mono-project.com/Python</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1712</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sun, 02 Aug 2009 16:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1712</guid>
		<description>Apologies for off topic. David, on twitter you say &quot;MonoDevelop has excellent Python support thanks to a plugin&quot;. Can you please point to the plugin, or how to install it? After lots of googling it&#039;s still unclear. Thanks!</description>
		<content:encoded><![CDATA[<p>Apologies for off topic. David, on twitter you say &#8220;MonoDevelop has excellent Python support thanks to a plugin&#8221;. Can you please point to the plugin, or how to install it? After lots of googling it&#8217;s still unclear. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aldo</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1709</link>
		<dc:creator>Aldo</dc:creator>
		<pubDate>Fri, 31 Jul 2009 23:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1709</guid>
		<description>How about non-english-speaking users? will the test videos still help you guys get relevant data out of them? Will cultural factors play a role to some extent? And how, if I may, will you guys tackle that?

Although I think having a broad, international, multi-cultural testers can help in producing a wider spectrum of result data, I fear we&#039;ll end up with a &quot;good enough&quot; solution that involves some compromises to a certain degree.

Similar to what translators sometimes encounter when trying to come up with a &quot;good enough&quot; term in their language to describe a functionality that was ad-hoc defined in the first place by the english-speaking developer. 

But that was yesterday. Today we enter distributed user testing. Hooray.

I think what you guys are doing here is good. More than good. It&#039;s great. Finally a pragmatic approach to usability. Now that&#039;s real progress. 

It&#039;ll  indeed be a fun discovery. Can&#039;t wait for the results!</description>
		<content:encoded><![CDATA[<p>How about non-english-speaking users? will the test videos still help you guys get relevant data out of them? Will cultural factors play a role to some extent? And how, if I may, will you guys tackle that?</p>
<p>Although I think having a broad, international, multi-cultural testers can help in producing a wider spectrum of result data, I fear we&#8217;ll end up with a &#8220;good enough&#8221; solution that involves some compromises to a certain degree.</p>
<p>Similar to what translators sometimes encounter when trying to come up with a &#8220;good enough&#8221; term in their language to describe a functionality that was ad-hoc defined in the first place by the english-speaking developer. </p>
<p>But that was yesterday. Today we enter distributed user testing. Hooray.</p>
<p>I think what you guys are doing here is good. More than good. It&#8217;s great. Finally a pragmatic approach to usability. Now that&#8217;s real progress. </p>
<p>It&#8217;ll  indeed be a fun discovery. Can&#8217;t wait for the results!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Great to See User Testing In&#160;Ubuntu &#124; listen to...</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1697</link>
		<dc:creator>Great to See User Testing In&#160;Ubuntu &#124; listen to...</dc:creator>
		<pubDate>Wed, 29 Jul 2009 15:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1697</guid>
		<description>[...] Siegel posted today about doing user testing in Ubuntu with a link to the user testing procedures as part of the 100 Paper [...]</description>
		<content:encoded><![CDATA[<p>[...] Siegel posted today about doing user testing in Ubuntu with a link to the user testing procedures as part of the 100 Paper [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1696</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Wed, 29 Jul 2009 11:04:57 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1696</guid>
		<description>Handling archives transparently is how Windows Explorer handles zipped files if you dont have third party tools installed (if i remember correctly).</description>
		<content:encoded><![CDATA[<p>Handling archives transparently is how Windows Explorer handles zipped files if you dont have third party tools installed (if i remember correctly).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peder</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1692</link>
		<dc:creator>peder</dc:creator>
		<pubDate>Wed, 29 Jul 2009 05:01:16 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1692</guid>
		<description>Simon: I don&#039;t think so. You can *still* have a right click menu entry to create an archive when you select folder/s and files.

I don&#039;t think there is much user testing needed here as i have seen it often enough with my parents and other people: They are absolutely puzzled by the concept of an archive.

That said, +1 to the first comment. Handling archives should be completely transparent, which means handling an archive as a folder when i double click it.</description>
		<content:encoded><![CDATA[<p>Simon: I don&#8217;t think so. You can *still* have a right click menu entry to create an archive when you select folder/s and files.</p>
<p>I don&#8217;t think there is much user testing needed here as i have seen it often enough with my parents and other people: They are absolutely puzzled by the concept of an archive.</p>
<p>That said, +1 to the first comment. Handling archives should be completely transparent, which means handling an archive as a folder when i double click it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1690</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Tue, 28 Jul 2009 21:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1690</guid>
		<description>Of course, if you do change it to hide the concept of an archive, all the people who *do* know what an archive is will be struggle to work out how to create one.</description>
		<content:encoded><![CDATA[<p>Of course, if you do change it to hide the concept of an archive, all the people who *do* know what an archive is will be struggle to work out how to create one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jake Tolbert</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1687</link>
		<dc:creator>Jake Tolbert</dc:creator>
		<pubDate>Tue, 28 Jul 2009 18:17:21 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1687</guid>
		<description>Very, very cool. It&#039;s great to see you guys figuring out how to apply open source structures to the hard work of usability.

Thanks for what you&#039;re doing--keep up the good work.</description>
		<content:encoded><![CDATA[<p>Very, very cool. It&#8217;s great to see you guys figuring out how to apply open source structures to the hard work of usability.</p>
<p>Thanks for what you&#8217;re doing&#8211;keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: frustphil</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1685</link>
		<dc:creator>frustphil</dc:creator>
		<pubDate>Tue, 28 Jul 2009 18:05:57 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1685</guid>
		<description>what if the archive that is to be expanded automatically requires a password?</description>
		<content:encoded><![CDATA[<p>what if the archive that is to be expanded automatically requires a password?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://davidsiegel.org/distributed-user-testing-archives/comment-page-1/#comment-1684</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 28 Jul 2009 17:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/?p=487#comment-1684</guid>
		<description>I don’t know what the optimal solution is, exactly, but I do know what it is not: exposing the concept of ‘archive’ to the user in any way. Archives are merely a workaround for technological limitations (too little space, too hard to transfer a whole folder in one shot, etc.). They are part of the underlying implementation. But the user should not have to care about such issues that are clearly not relevant to the task of actually getting to his content. Ideally, if something needs to be expanded or archived, it should all happen automatically, leaving the user in “ignorant” bliss. If I want to mail a folder, it should automatically be archived without me realizing that it’s ‘compressed’. If there’s a file-size restriction somewhere, the file should be compressed as well—but appear completely normally to the user.

This is not a simple issue to fix. It requires rewriting a lot of software. A lot. The more I think about it, the more complicated it seems. But, in an ideal world, the contents of an archive is all one would ever see, and the concept of ‘archive’ would be as hidden as the kernel.

I’d also like to point out that there are quite a number of computing concepts that should have been restricted to the underlying implementation but completely hidden from users: e-mail attachments (the distinction between those and inline content is meaningless to people), folders, and applications (an inhumane concept I blame Apple for widely popularizing as an ideal computing paradigm). If we can slowly chip away at these relics of interfaces that are thin veneers over their underlying implementations, Ubuntu really will be for human beings.</description>
		<content:encoded><![CDATA[<p>I don’t know what the optimal solution is, exactly, but I do know what it is not: exposing the concept of ‘archive’ to the user in any way. Archives are merely a workaround for technological limitations (too little space, too hard to transfer a whole folder in one shot, etc.). They are part of the underlying implementation. But the user should not have to care about such issues that are clearly not relevant to the task of actually getting to his content. Ideally, if something needs to be expanded or archived, it should all happen automatically, leaving the user in “ignorant” bliss. If I want to mail a folder, it should automatically be archived without me realizing that it’s ‘compressed’. If there’s a file-size restriction somewhere, the file should be compressed as well—but appear completely normally to the user.</p>
<p>This is not a simple issue to fix. It requires rewriting a lot of software. A lot. The more I think about it, the more complicated it seems. But, in an ideal world, the contents of an archive is all one would ever see, and the concept of ‘archive’ would be as hidden as the kernel.</p>
<p>I’d also like to point out that there are quite a number of computing concepts that should have been restricted to the underlying implementation but completely hidden from users: e-mail attachments (the distinction between those and inline content is meaningless to people), folders, and applications (an inhumane concept I blame Apple for widely popularizing as an ideal computing paradigm). If we can slowly chip away at these relics of interfaces that are thin veneers over their underlying implementations, Ubuntu really will be for human beings.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
