<?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"
	>
<channel>
	<title>Comments on: AMO Site Updated, Rolled Back</title>
	<atom:link href="http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/</link>
	<description>Mozilla Web Development Blog</description>
	<pubDate>Wed, 03 Dec 2008 21:39:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Anders</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2152</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Sat, 24 Mar 2007 13:21:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2152</guid>
		<description>It seems strange to me that localization would have any performance impact. Since the site is mostly a static site, I would expect most of the pages to be baked as static html-files (and pre-compressed) in the file system, leaving only the search (if not outsourced) and the review submission as dynamic. Have you instead chosen to generate all pages dynamically and, if so, why?</description>
		<content:encoded><![CDATA[<p>It seems strange to me that localization would have any performance impact. Since the site is mostly a static site, I would expect most of the pages to be baked as static html-files (and pre-compressed) in the file system, leaving only the search (if not outsourced) and the review submission as dynamic. Have you instead chosen to generate all pages dynamically and, if so, why?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MASA</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2127</link>
		<dc:creator>MASA</dc:creator>
		<pubDate>Sat, 24 Mar 2007 01:15:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2127</guid>
		<description>@max1million

Agreed.

@Mozilla

I bet you 5 bucks you won't make the next deadline if it's in March of 2007.</description>
		<content:encoded><![CDATA[<p>@max1million</p>
<p>Agreed.</p>
<p>@Mozilla</p>
<p>I bet you 5 bucks you won&#8217;t make the next deadline if it&#8217;s in March of 2007.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kiroset</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2126</link>
		<dc:creator>Kiroset</dc:creator>
		<pubDate>Sat, 24 Mar 2007 00:10:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2126</guid>
		<description>Thanks for the update, good luck</description>
		<content:encoded><![CDATA[<p>Thanks for the update, good luck</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bogdan</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2124</link>
		<dc:creator>Bogdan</dc:creator>
		<pubDate>Fri, 23 Mar 2007 23:10:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2124</guid>
		<description>Oh, the sweetness of bitching!

I'm an extension developer caught pants down by this site update (just so you know where I'm coming from: I haven't followed the site update process, and released a new version of my extension early during the site freeze -- therefore I'm most affected by all subsequent delays). And yes, there /are/ things I'm not happy with in the new incarnation as well.

But *come* *on*! There really is waaay too much whining in here -- guys, get a grip! Do you really, truly, honestly think you would've managed this significantly better with the same resources? Or do you think the developers here are squarely ill-willed? Or at least mildly not interested in AMO? Come now.

Instead of whining, let's give the AMO team a nice, good round of applause for their efforts, let's hope for the best, and most importantly, let's allow them the peace of mind to fix all current issues: unless you're wildly pessimistic, you'd agree they're all doing their best to make it thorough a tough site update -- and upgrade.</description>
		<content:encoded><![CDATA[<p>Oh, the sweetness of bitching!</p>
<p>I&#8217;m an extension developer caught pants down by this site update (just so you know where I&#8217;m coming from: I haven&#8217;t followed the site update process, and released a new version of my extension early during the site freeze &#8212; therefore I&#8217;m most affected by all subsequent delays). And yes, there /are/ things I&#8217;m not happy with in the new incarnation as well.</p>
<p>But *come* *on*! There really is waaay too much whining in here &#8212; guys, get a grip! Do you really, truly, honestly think you would&#8217;ve managed this significantly better with the same resources? Or do you think the developers here are squarely ill-willed? Or at least mildly not interested in AMO? Come now.</p>
<p>Instead of whining, let&#8217;s give the AMO team a nice, good round of applause for their efforts, let&#8217;s hope for the best, and most importantly, let&#8217;s allow them the peace of mind to fix all current issues: unless you&#8217;re wildly pessimistic, you&#8217;d agree they&#8217;re all doing their best to make it thorough a tough site update &#8212; and upgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geva</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2122</link>
		<dc:creator>Geva</dc:creator>
		<pubDate>Fri, 23 Mar 2007 22:54:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2122</guid>
		<description>At least let us use the old CPanel in the meantime... You shouldn't locked it up while you fix things up... first fix it and then do the migration stuff.

And also, please don't sandbox all the extensions while you review them one by one -- you should first review them, and only then make the results of the reviews into effect.</description>
		<content:encoded><![CDATA[<p>At least let us use the old CPanel in the meantime&#8230; You shouldn&#8217;t locked it up while you fix things up&#8230; first fix it and then do the migration stuff.</p>
<p>And also, please don&#8217;t sandbox all the extensions while you review them one by one &#8212; you should first review them, and only then make the results of the reviews into effect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meatball</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2121</link>
		<dc:creator>Meatball</dc:creator>
		<pubDate>Fri, 23 Mar 2007 22:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2121</guid>
		<description>It would also be nice if Mike Shaver could blog about the process by which extensions are "chosen" for recommendation. Assuming of course there is a process.</description>
		<content:encoded><![CDATA[<p>It would also be nice if Mike Shaver could blog about the process by which extensions are &#8220;chosen&#8221; for recommendation. Assuming of course there is a process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: max1million</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2120</link>
		<dc:creator>max1million</dc:creator>
		<pubDate>Fri, 23 Mar 2007 22:24:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2120</guid>
		<description>Sandboxed extensions not likely to go public.

Now instead of having perfectly good or new extensions (even already released) at the end of the most popular list cause of fewer downloads and fewer updates to cause automatic downloads, they are hidden away in an if you find this section don’t bother cause they haven’t been tested or just aren’t any good section. 

If you rely on average users to be able to even find them, not to mention take time to, test, rate and nominate for public, before actually reviewing and adding to regular public section, you might as well forget them.

 That will only reinforce the existing and most popular extensions, not serve to promote others. I thought promote other less popular extensions was one of the goals.</description>
		<content:encoded><![CDATA[<p>Sandboxed extensions not likely to go public.</p>
<p>Now instead of having perfectly good or new extensions (even already released) at the end of the most popular list cause of fewer downloads and fewer updates to cause automatic downloads, they are hidden away in an if you find this section don’t bother cause they haven’t been tested or just aren’t any good section. </p>
<p>If you rely on average users to be able to even find them, not to mention take time to, test, rate and nominate for public, before actually reviewing and adding to regular public section, you might as well forget them.</p>
<p> That will only reinforce the existing and most popular extensions, not serve to promote others. I thought promote other less popular extensions was one of the goals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: docwhat</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2119</link>
		<dc:creator>docwhat</dc:creator>
		<pubDate>Fri, 23 Mar 2007 21:36:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2119</guid>
		<description>I'm waiting with bells on....</description>
		<content:encoded><![CDATA[<p>I&#8217;m waiting with bells on&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: morgamic</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2116</link>
		<dc:creator>morgamic</dc:creator>
		<pubDate>Fri, 23 Mar 2007 21:15:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2116</guid>
		<description>Mike Shaver will be posting a separate blog about the sandbox to help clear things up.  We didn't want to mix the two posts up.</description>
		<content:encoded><![CDATA[<p>Mike Shaver will be posting a separate blog about the sandbox to help clear things up.  We didn&#8217;t want to mix the two posts up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: docwhat</title>
		<link>http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2115</link>
		<dc:creator>docwhat</dc:creator>
		<pubDate>Fri, 23 Mar 2007 21:13:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/2007/03/23/amo-site-updated-rolled-back/#comment-2115</guid>
		<description>And the evilness that is the sandbox?  Will that be fixed as well?</description>
		<content:encoded><![CDATA[<p>And the evilness that is the sandbox?  Will that be fixed as well?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
