<?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: SUMO Localization Dashboard</title>
	<atom:link href="http://blog.mozilla.com/sumo/2009/02/19/sumo-localization-dashboard/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/sumo/2009/02/19/sumo-localization-dashboard/</link>
	<description>The support.mozilla.org (SUMO) project</description>
	<lastBuildDate>Tue, 07 Feb 2012 08:20:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: David Tenser</title>
		<link>http://blog.mozilla.com/sumo/2009/02/19/sumo-localization-dashboard/comment-page-1/#comment-17189</link>
		<dc:creator>David Tenser</dc:creator>
		<pubDate>Fri, 20 Feb 2009 12:14:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/sumo/?p=489#comment-17189</guid>
		<description>Hey Tomer, thanks for the feedback. The problem with the number of articles is that it depends on which articles you translate. We could say how many articles are usually required to reach 50% (which the text below the status bar also does in the mockup), but if you translate other articles that are less frequently visited, you may need to translate more articles than that.

Of course, the best for everyone (in our support communities, and our users) is to translate the most visited pages, as that means the more users are helped by it.

Maybe we could say something like &quot;xx% complete (yy articles translated)&quot; ?

About the other request, that&#039;s definitely something we need: an overview of articles that have been changed and needs approval. That&#039;s something that we should be showing on the contributor home page. It&#039;s not restricted to l10n, but is something we should have on the en-US page as well.</description>
		<content:encoded><![CDATA[<p>Hey Tomer, thanks for the feedback. The problem with the number of articles is that it depends on which articles you translate. We could say how many articles are usually required to reach 50% (which the text below the status bar also does in the mockup), but if you translate other articles that are less frequently visited, you may need to translate more articles than that.</p>
<p>Of course, the best for everyone (in our support communities, and our users) is to translate the most visited pages, as that means the more users are helped by it.</p>
<p>Maybe we could say something like &#8220;xx% complete (yy articles translated)&#8221; ?</p>
<p>About the other request, that&#8217;s definitely something we need: an overview of articles that have been changed and needs approval. That&#8217;s something that we should be showing on the contributor home page. It&#8217;s not restricted to l10n, but is something we should have on the en-US page as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomer</title>
		<link>http://blog.mozilla.com/sumo/2009/02/19/sumo-localization-dashboard/comment-page-1/#comment-17167</link>
		<dc:creator>Tomer</dc:creator>
		<pubDate>Thu, 19 Feb 2009 23:20:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/sumo/?p=489#comment-17167</guid>
		<description>Looks awesome. Please add to the first mock-up some information about how many articles are translated, and not just percents. Also, we need better control about articles which changed in the original language. I am not going to look on every page just to see what changed and if it require some actions from us.</description>
		<content:encoded><![CDATA[<p>Looks awesome. Please add to the first mock-up some information about how many articles are translated, and not just percents. Also, we need better control about articles which changed in the original language. I am not going to look on every page just to see what changed and if it require some actions from us.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

