<?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: AMO Review Queue Burndown a Huge Success</title>
	<atom:link href="http://blog.mozilla.com/addons/2009/06/29/amo-review-queue-burndown-a-huge-success/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/addons/2009/06/29/amo-review-queue-burndown-a-huge-success/</link>
	<description>Official Blog of Mozilla Add-ons</description>
	<lastBuildDate>Sun, 22 Nov 2009 00:59:06 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rey Bango</title>
		<link>http://blog.mozilla.com/addons/2009/06/29/amo-review-queue-burndown-a-huge-success/comment-page-1/#comment-6308</link>
		<dc:creator>Rey Bango</dc:creator>
		<pubDate>Tue, 21 Jul 2009 16:28:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=715#comment-6308</guid>
		<description>@AnAddOnDeveloper: Unfortunately we can&#039;t do that. While it certainly would seem easy to do, an update needs to be reviewed to ensure that it doesn&#039;t introduce code or features that would adversely affect Mozilla users. We work with add-on developers daily who have submitted updates that cause problems&amp; it&#039;s important that we troubleshoot as many of these situations as possible before it goes out to a Mozilla user.

We&#039;re considering new techniques as is being discussed in this thread:

http://groups.google.com/group/mozilla.dev.amo/browse_thread/thread/d8c2bf3f9a0c1997/bfe9e6cc00b9e051</description>
		<content:encoded><![CDATA[<p>@AnAddOnDeveloper: Unfortunately we can&#8217;t do that. While it certainly would seem easy to do, an update needs to be reviewed to ensure that it doesn&#8217;t introduce code or features that would adversely affect Mozilla users. We work with add-on developers daily who have submitted updates that cause problems&amp; it&#8217;s important that we troubleshoot as many of these situations as possible before it goes out to a Mozilla user.</p>
<p>We&#8217;re considering new techniques as is being discussed in this thread:</p>
<p><a href="http://groups.google.com/group/mozilla.dev.amo/browse_thread/thread/d8c2bf3f9a0c1997/bfe9e6cc00b9e051" rel="nofollow">http://groups.google.com/group/mozilla.dev.amo/browse_thread/thread/d8c2bf3f9a0c1997/bfe9e6cc00b9e051</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AnAddOnDeveloper</title>
		<link>http://blog.mozilla.com/addons/2009/06/29/amo-review-queue-burndown-a-huge-success/comment-page-1/#comment-6307</link>
		<dc:creator>AnAddOnDeveloper</dc:creator>
		<pubDate>Tue, 21 Jul 2009 15:51:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=715#comment-6307</guid>
		<description>While this is great work and appreciated by add on developers, I think you&#039;re making more work for yourself by having to review new versions of existing addons. I put in a new version of my add on on July 4 and it still has not been reviewed. It contains a number of bug fixes that users would benefit from. But they can&#039;t receive it until somebody reviews it. This process prevents timely updates from appearing. What if the update was critical and needed to be distributed to users quickly? I would still have to wait months until a reviewer gets to my new version. Why not allow developers to upload a new version without a review and let the reviewers concentrate on new addons?</description>
		<content:encoded><![CDATA[<p>While this is great work and appreciated by add on developers, I think you&#8217;re making more work for yourself by having to review new versions of existing addons. I put in a new version of my add on on July 4 and it still has not been reviewed. It contains a number of bug fixes that users would benefit from. But they can&#8217;t receive it until somebody reviews it. This process prevents timely updates from appearing. What if the update was critical and needed to be distributed to users quickly? I would still have to wait months until a reviewer gets to my new version. Why not allow developers to upload a new version without a review and let the reviewers concentrate on new addons?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Meattle</title>
		<link>http://blog.mozilla.com/addons/2009/06/29/amo-review-queue-burndown-a-huge-success/comment-page-1/#comment-5154</link>
		<dc:creator>Jay Meattle</dc:creator>
		<pubDate>Tue, 30 Jun 2009 19:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=715#comment-5154</guid>
		<description>Yay!</description>
		<content:encoded><![CDATA[<p>Yay!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Hagerty</title>
		<link>http://blog.mozilla.com/addons/2009/06/29/amo-review-queue-burndown-a-huge-success/comment-page-1/#comment-5149</link>
		<dc:creator>Michael Hagerty</dc:creator>
		<pubDate>Tue, 30 Jun 2009 16:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=715#comment-5149</guid>
		<description>Fantastic work.  I truly appreciate the dedication and hard work.  I am hoping the 3.x revision of CBext made it through as it is a life-saver for those of us colorblind websurfers.  Too many webmasters are ignorant of the confusion their choice of colors create for us and this add-on really helps.</description>
		<content:encoded><![CDATA[<p>Fantastic work.  I truly appreciate the dedication and hard work.  I am hoping the 3.x revision of CBext made it through as it is a life-saver for those of us colorblind websurfers.  Too many webmasters are ignorant of the confusion their choice of colors create for us and this add-on really helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sven Schwarz</title>
		<link>http://blog.mozilla.com/addons/2009/06/29/amo-review-queue-burndown-a-huge-success/comment-page-1/#comment-5134</link>
		<dc:creator>Sven Schwarz</dc:creator>
		<pubDate>Tue, 30 Jun 2009 08:48:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=715#comment-5134</guid>
		<description>Yes, these guys did a great job, indeed! Sacrificing a weekend for the mozilla world. Thanks a lot, guys!!!

However, I am not sure if the whole idea of _moderating_ add-ons really scales---at least not in the way it&#039;s done today. Maybe you should think about either making more layers (1st level moderation &quot;usefull/not usefull and new/not new&quot; and 2nd level moderation &quot;look at the code&quot; or something alike)---or: (maybe even better) think about more automatic or &quot;anarchic&quot; ways.

I would go for the latter alternative. I recommend to think about an &quot;unmoderated&quot; or at least think about a &quot;late/post-poned moderation&quot; strategy or something alike. Attention: This is just an idea and not a thouroughly thought-over approach! One idea could be to &quot;substitute&quot; the moderation somehow, for example, by using usage statistics and free votes (easy clickable votes for everyone!) _alone_ to generate _quantitative_(!) arguments for an end-user. The question is: How can we really know that a user is actually _using_ the add-on rather than letting it run without him/her knowing it?? Well, I don&#039;t know... But, maybe it would be a good idea to let moderators vote as well---like normal users---but then counting their votes with a factor of 1000 or even greater!?

My idea might not be the perfect already, but I have the impression that the moderation of a continously increasing number of add-ons will get harder and harder every day and, thus, the moderation process as it is now just can not scale!
A _conceptional_ improvement has to be done here---tuning is not sufficient.

Anyway, thanks to all you moderators doing a great job already. I am sure, that you sacrifice a big part of you life for the good, for others! This is a noble thing! Thank you guys!

Have a nice day!
Sven</description>
		<content:encoded><![CDATA[<p>Yes, these guys did a great job, indeed! Sacrificing a weekend for the mozilla world. Thanks a lot, guys!!!</p>
<p>However, I am not sure if the whole idea of _moderating_ add-ons really scales&#8212;at least not in the way it&#8217;s done today. Maybe you should think about either making more layers (1st level moderation &#8220;usefull/not usefull and new/not new&#8221; and 2nd level moderation &#8220;look at the code&#8221; or something alike)&#8212;or: (maybe even better) think about more automatic or &#8220;anarchic&#8221; ways.</p>
<p>I would go for the latter alternative. I recommend to think about an &#8220;unmoderated&#8221; or at least think about a &#8220;late/post-poned moderation&#8221; strategy or something alike. Attention: This is just an idea and not a thouroughly thought-over approach! One idea could be to &#8220;substitute&#8221; the moderation somehow, for example, by using usage statistics and free votes (easy clickable votes for everyone!) _alone_ to generate _quantitative_(!) arguments for an end-user. The question is: How can we really know that a user is actually _using_ the add-on rather than letting it run without him/her knowing it?? Well, I don&#8217;t know&#8230; But, maybe it would be a good idea to let moderators vote as well&#8212;like normal users&#8212;but then counting their votes with a factor of 1000 or even greater!?</p>
<p>My idea might not be the perfect already, but I have the impression that the moderation of a continously increasing number of add-ons will get harder and harder every day and, thus, the moderation process as it is now just can not scale!<br />
A _conceptional_ improvement has to be done here&#8212;tuning is not sufficient.</p>
<p>Anyway, thanks to all you moderators doing a great job already. I am sure, that you sacrifice a big part of you life for the good, for others! This is a noble thing! Thank you guys!</p>
<p>Have a nice day!<br />
Sven</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kurt (supernova_00)</title>
		<link>http://blog.mozilla.com/addons/2009/06/29/amo-review-queue-burndown-a-huge-success/comment-page-1/#comment-5107</link>
		<dc:creator>Kurt (supernova_00)</dc:creator>
		<pubDate>Mon, 29 Jun 2009 17:34:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=715#comment-5107</guid>
		<description>Thank you all very much!  The whole community will appreciate this!</description>
		<content:encoded><![CDATA[<p>Thank you all very much!  The whole community will appreciate this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: clouserw</title>
		<link>http://blog.mozilla.com/addons/2009/06/29/amo-review-queue-burndown-a-huge-success/comment-page-1/#comment-5103</link>
		<dc:creator>clouserw</dc:creator>
		<pubDate>Mon, 29 Jun 2009 15:02:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=715#comment-5103</guid>
		<description>Nice work, everyone.</description>
		<content:encoded><![CDATA[<p>Nice work, everyone.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
