<?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: Improving the WordPress Theme Review Experiment</title>
	<atom:link href="http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/feed/" rel="self" type="application/rss+xml" />
	<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/</link>
	<description>The Home of Suffusion</description>
	<lastBuildDate>Wed, 16 May 2012 13:46:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: The WordPress Theme Review Experiment &#8211; Take II &#187; Aquoid Themes</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-2587</link>
		<dc:creator>The WordPress Theme Review Experiment &#8211; Take II &#187; Aquoid Themes</dc:creator>
		<pubDate>Mon, 25 Jul 2011 04:14:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-2587</guid>
		<description>[...] a year back I wrote an article on the Theme Review process that WordPress had instituted. In only its second month at that time I [...]</description>
		<content:encoded><![CDATA[<p>[...] a year back I wrote an article on the Theme Review process that WordPress had instituted. In only its second month at that time I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Towfiq I.</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-1106</link>
		<dc:creator>Towfiq I.</dc:creator>
		<pubDate>Wed, 09 Mar 2011 18:32:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-1106</guid>
		<description>How about putting up a donation box in wordpress home page to support the theme/plugin repository. So, the theme reviewers won&#039;t work as a volunteer. 

By the way,  I found this website. Is it a official blog of wordpress?
http://wordpressfoundation.org/

Just my two cents
Towfiq I.</description>
		<content:encoded><![CDATA[<p>How about putting up a donation box in wordpress home page to support the theme/plugin repository. So, the theme reviewers won&#8217;t work as a volunteer. </p>
<p>By the way,  I found this website. Is it a official blog of wordpress?<br />
<a href="http://wordpressfoundation.org/" rel="nofollow">http://wordpressfoundation.org/</a></p>
<p>Just my two cents<br />
Towfiq I.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chip Bennett</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-1105</link>
		<dc:creator>Chip Bennett</dc:creator>
		<pubDate>Mon, 10 Jan 2011 21:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-1105</guid>
		<description>Indeed, there is a backlog. But you might consider that we have just gone through the holiday season. All of the reviewers, who contribute entirely on a volunteer basis, have families and full time jobs that don&#039;t involve WordPress or Themes. A backlog - especially around Thanksgiving, Christmas, and New Year&#039;s - is to be expected.

You&#039;re welcome to join us, and help take care of that backlog!</description>
		<content:encoded><![CDATA[<p>Indeed, there is a backlog. But you might consider that we have just gone through the holiday season. All of the reviewers, who contribute entirely on a volunteer basis, have families and full time jobs that don&#8217;t involve WordPress or Themes. A backlog &#8211; especially around Thanksgiving, Christmas, and New Year&#8217;s &#8211; is to be expected.</p>
<p>You&#8217;re welcome to join us, and help take care of that backlog!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-1104</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 04 Jan 2011 12:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-1104</guid>
		<description>Well here we are at the start of 2011 and if you look at the backlog, there are themes waiting to be reviewed that were submitted 5 weeks ago. So instead of speeding up, it looks like things are slowing down.

Anyone know what the criteria are to judge the &#039;WordPress theme review Experiment&#039;  are?</description>
		<content:encoded><![CDATA[<p>Well here we are at the start of 2011 and if you look at the backlog, there are themes waiting to be reviewed that were submitted 5 weeks ago. So instead of speeding up, it looks like things are slowing down.</p>
<p>Anyone know what the criteria are to judge the &#8216;WordPress theme review Experiment&#8217;  are?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chip Bennett</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-1103</link>
		<dc:creator>Chip Bennett</dc:creator>
		<pubDate>Tue, 28 Sep 2010 19:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-1103</guid>
		<description>Thanks for the mention in the 3.6.5 release notes! I&#039;m glad an important bugfix was able to get out to your users as quickly as possible.

Long-term, what the Theme Review team really needs is more volunteers. In addition to the sheer volume of Themes submitted, we also have to deal with the complexity of some Themes. Speaking for myself personally, I&#039;m not particularly expert in JavaScript/jQuery/etc - so it takes me longer to perform a proper review of a heavily scripted Theme. Also, we get a fair number of BuddyPress themes - and we only have one person on the Theme Review team who has much expertise with BuddyPress.

Hopefully, the addition of more automated checks during the upload process, and general education about the guidelines, as well as the overall ironing-out of the review process, will make things easier for everyone, moving forward.

As for Simon&#039;s &lt;a href=&quot;http://pross.org.uk/theme-check/&quot; rel=&quot;nofollow&quot;&gt;Theme-Check&lt;/a&gt; tool, it&#039;s available for anyone to use. We&#039;re in the process of incorporating most/all of its checks into the Theme Repository uploader tool. Hopefully that should all be ironed out within a week or so!</description>
		<content:encoded><![CDATA[<p>Thanks for the mention in the 3.6.5 release notes! I&#8217;m glad an important bugfix was able to get out to your users as quickly as possible.</p>
<p>Long-term, what the Theme Review team really needs is more volunteers. In addition to the sheer volume of Themes submitted, we also have to deal with the complexity of some Themes. Speaking for myself personally, I&#8217;m not particularly expert in JavaScript/jQuery/etc &#8211; so it takes me longer to perform a proper review of a heavily scripted Theme. Also, we get a fair number of BuddyPress themes &#8211; and we only have one person on the Theme Review team who has much expertise with BuddyPress.</p>
<p>Hopefully, the addition of more automated checks during the upload process, and general education about the guidelines, as well as the overall ironing-out of the review process, will make things easier for everyone, moving forward.</p>
<p>As for Simon&#8217;s <a href="http://pross.org.uk/theme-check/" rel="nofollow">Theme-Check</a> tool, it&#8217;s available for anyone to use. We&#8217;re in the process of incorporating most/all of its checks into the Theme Repository uploader tool. Hopefully that should all be ironed out within a week or so!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sayontan</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-1102</link>
		<dc:creator>Sayontan</dc:creator>
		<pubDate>Tue, 28 Sep 2010 14:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-1102</guid>
		<description>Chip,
Thanks for the extremely detailed response, and I am glad that this caught the attention of someone on the theme reviewers&#039; team.
I did notice that the last couple of releases that I made got approved extremely quickly, within a day or two and I made a point of mentioning this on &lt;a href=&quot;http://www.aquoid.com/news/2010/08/suffusion-version-3-6-5/&quot; rel=&quot;nofollow&quot;&gt;some of my release announcements&lt;/a&gt;:
&lt;blockquote&gt;Version 3.6.5 of Suffusion went live today. Actually first 3.6.4 went live, then some users pointed out a rather serious flaw, then I immediately patched it. &lt;strong&gt;The theme approvers, who have really improved their approval process a few notches up approved it rather quickly too.&lt;/strong&gt;&lt;/blockquote&gt;
So obviously themes previously approved are getting the &quot;frequent flier&quot; privileges, which saves a lot of time.

I guess overall once the speed issues are ironed out this will be a really great process. I know for sure that Suffusion is much more adherent to good design guidelines as per WP recommendations and if all themes follow the same rigorous approval method, the overall quality of themes on WP will go up significantly.

BTW, Simon&#039;s tool sounds pretty interesting. Is that a variant of the current upload checker (or is this already in action)?

Thanks for taking the time to respond here.
Sayontan.</description>
		<content:encoded><![CDATA[<p>Chip,<br />
Thanks for the extremely detailed response, and I am glad that this caught the attention of someone on the theme reviewers&#8217; team.<br />
I did notice that the last couple of releases that I made got approved extremely quickly, within a day or two and I made a point of mentioning this on <a href="http://www.aquoid.com/news/2010/08/suffusion-version-3-6-5/" rel="nofollow">some of my release announcements</a>:</p>
<blockquote><p>Version 3.6.5 of Suffusion went live today. Actually first 3.6.4 went live, then some users pointed out a rather serious flaw, then I immediately patched it. <strong>The theme approvers, who have really improved their approval process a few notches up approved it rather quickly too.</strong></p></blockquote>
<p>So obviously themes previously approved are getting the &#8220;frequent flier&#8221; privileges, which saves a lot of time.</p>
<p>I guess overall once the speed issues are ironed out this will be a really great process. I know for sure that Suffusion is much more adherent to good design guidelines as per WP recommendations and if all themes follow the same rigorous approval method, the overall quality of themes on WP will go up significantly.</p>
<p>BTW, Simon&#8217;s tool sounds pretty interesting. Is that a variant of the current upload checker (or is this already in action)?</p>
<p>Thanks for taking the time to respond here.<br />
Sayontan.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chip Bennett</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-1101</link>
		<dc:creator>Chip Bennett</dc:creator>
		<pubDate>Mon, 27 Sep 2010 22:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-1101</guid>
		<description>Hi Sayontan,

Great feedback on the Theme Review process (even if I&#039;m a few months late to this post - I just discovered it today). I just wanted to post a bit of a response, and a follow-up.

First, in defense of the Theme Review team: it took us a couple months really to get up and going. First, we had no good, objective list of review criteria by which to ensure that all of us would be conducting fair, objective, and consistent reviews. It took us at least a month to develop such guidelines. 

After that, the Theme Unit Test data needed to be updated (the previous XML file was from 2008). 

Even then, each of us had to conduct several reviews - making several missteps in the process - before we really felt like we had our feet underneath us. Joseph Scott had done yeoman&#039;s work in handling all this by himself before forming the team! We found that we had a considerable learning curve before we were really performing good, consistent reviews.

Your point about cycle time for Theme review and approval is an ongoing problem. The sad reality is, the Theme Review team only has 3-5 people who come anywhere near approaching an average of 1 Theme review per day, while Themes continue to be submitted at a rate of around 10 per day. It is a constant struggle, and we&#039;re continuing to find ways to expedite the process. To that end:

1) We have implemented a couple of the things you suggest here:

First: tickets for already reviewed Themes are prioritized ahead of tickets for newly submitted Themes, and rather than a full-blown review, are given a review based on the diff between the approved version and the new revision. This way, bugfixes and other improvements to already approved Themes should happen much more quickly. 

Second, for all tickets, if a newer version is submitted before the existing ticket is reviewed, the new ticket takes the original ticket&#039;s place in the review queue. This way, bugfixes and other improvements do not cost the Theme its place in the queue.

2) The Theme Review continues to add tools and helps for Theme developers:

First is Simon Prosser&#039;s Theme-Check tool, that will check Theme .zip files for issues that would cause the Theme to fail the review.

Second, the Codex pages are continually improved, and the Guidelines continually revised, based on Theme-developer feedback.

3) We&#039;ve attempted to improve the submission and review process, by making better use of the tools available to us. We continue to improve our use of Trac, adding version-diffs for previously approved Themes, adding the Theme developer to the ticket by default, to ensure email notifications work, and have created the review prioritization reports. We are right now in the process of improving the Theme uploader script, to ensure that it checks for more criteria, and outputs all results in one pass, rather than requiring multiple passes.

If there is anything else that anyone can think of to help improve the Theme Review process or guidelines, we&#039;re always open to feedback. We&#039;re trying to do our best, but please let us know where we can do better!

Thanks,

Chip</description>
		<content:encoded><![CDATA[<p>Hi Sayontan,</p>
<p>Great feedback on the Theme Review process (even if I&#8217;m a few months late to this post &#8211; I just discovered it today). I just wanted to post a bit of a response, and a follow-up.</p>
<p>First, in defense of the Theme Review team: it took us a couple months really to get up and going. First, we had no good, objective list of review criteria by which to ensure that all of us would be conducting fair, objective, and consistent reviews. It took us at least a month to develop such guidelines. </p>
<p>After that, the Theme Unit Test data needed to be updated (the previous XML file was from 2008). </p>
<p>Even then, each of us had to conduct several reviews &#8211; making several missteps in the process &#8211; before we really felt like we had our feet underneath us. Joseph Scott had done yeoman&#8217;s work in handling all this by himself before forming the team! We found that we had a considerable learning curve before we were really performing good, consistent reviews.</p>
<p>Your point about cycle time for Theme review and approval is an ongoing problem. The sad reality is, the Theme Review team only has 3-5 people who come anywhere near approaching an average of 1 Theme review per day, while Themes continue to be submitted at a rate of around 10 per day. It is a constant struggle, and we&#8217;re continuing to find ways to expedite the process. To that end:</p>
<p>1) We have implemented a couple of the things you suggest here:</p>
<p>First: tickets for already reviewed Themes are prioritized ahead of tickets for newly submitted Themes, and rather than a full-blown review, are given a review based on the diff between the approved version and the new revision. This way, bugfixes and other improvements to already approved Themes should happen much more quickly. </p>
<p>Second, for all tickets, if a newer version is submitted before the existing ticket is reviewed, the new ticket takes the original ticket&#8217;s place in the review queue. This way, bugfixes and other improvements do not cost the Theme its place in the queue.</p>
<p>2) The Theme Review continues to add tools and helps for Theme developers:</p>
<p>First is Simon Prosser&#8217;s Theme-Check tool, that will check Theme .zip files for issues that would cause the Theme to fail the review.</p>
<p>Second, the Codex pages are continually improved, and the Guidelines continually revised, based on Theme-developer feedback.</p>
<p>3) We&#8217;ve attempted to improve the submission and review process, by making better use of the tools available to us. We continue to improve our use of Trac, adding version-diffs for previously approved Themes, adding the Theme developer to the ticket by default, to ensure email notifications work, and have created the review prioritization reports. We are right now in the process of improving the Theme uploader script, to ensure that it checks for more criteria, and outputs all results in one pass, rather than requiring multiple passes.</p>
<p>If there is anything else that anyone can think of to help improve the Theme Review process or guidelines, we&#8217;re always open to feedback. We&#8217;re trying to do our best, but please let us know where we can do better!</p>
<p>Thanks,</p>
<p>Chip</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sayontan</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-1100</link>
		<dc:creator>Sayontan</dc:creator>
		<pubDate>Mon, 02 Aug 2010 18:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-1100</guid>
		<description>Chris,
Thanks for the feedback. FYI, there is a full-blown support forum (see the top of the page) that you can use for queries - I tend to ignore queries posted through comments or email.

Regarding the speed of the back-end I am aware of it. The issue there is that the humongous number of options are all loaded into JavaScript variables, slowing things down a bit. I have already submitted version 3.5.9 of the theme with significant improvements in the admin panel speed, so hopefully the theme reviewers will approve it soon; it has already spent quite some time on the review queue.

Sayontan.</description>
		<content:encoded><![CDATA[<p>Chris,<br />
Thanks for the feedback. FYI, there is a full-blown support forum (see the top of the page) that you can use for queries &#8211; I tend to ignore queries posted through comments or email.</p>
<p>Regarding the speed of the back-end I am aware of it. The issue there is that the humongous number of options are all loaded into JavaScript variables, slowing things down a bit. I have already submitted version 3.5.9 of the theme with significant improvements in the admin panel speed, so hopefully the theme reviewers will approve it soon; it has already spent quite some time on the review queue.</p>
<p>Sayontan.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-1099</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Mon, 02 Aug 2010 13:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-1099</guid>
		<description>Hi again Sayontan, your Buddypress Pack solved the problem. The generic BP template pack we were using did not. So problem resolved and again many thanks for whatwe are hoping could become the standard out there!

ps the only think we could add really is the need for a little more speed in the admin area but it sure is not a show stopper. 

Rgds Chris</description>
		<content:encoded><![CDATA[<p>Hi again Sayontan, your Buddypress Pack solved the problem. The generic BP template pack we were using did not. So problem resolved and again many thanks for whatwe are hoping could become the standard out there!</p>
<p>ps the only think we could add really is the need for a little more speed in the admin area but it sure is not a show stopper. </p>
<p>Rgds Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/comment-page-1/#comment-1098</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Mon, 02 Aug 2010 11:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.aquoid.com/news/2010/07/improving-the-wordpress-theme-review-experiment/#comment-1098</guid>
		<description>Hi Sayontan, out team is new to your theme but we are already using it for a couple of clients. You will be pleased to know the site developers here are all business consultants with no prgramming skills! 

We have a question for you. When the Suffusion theme is used in conjunction with Buddypress the sidebars get pushed underneath the Buddypress content but only on Buddypress Pages. However the sidebar reverts to its correct position when navigating back to non-Buddypress pages. Do you have a nice and easy solution to that problem please? Thanks and wow what a fantastic job Suffusion is. Think you will soon pass the other contenders with your ratings.</description>
		<content:encoded><![CDATA[<p>Hi Sayontan, out team is new to your theme but we are already using it for a couple of clients. You will be pleased to know the site developers here are all business consultants with no prgramming skills! </p>
<p>We have a question for you. When the Suffusion theme is used in conjunction with Buddypress the sidebars get pushed underneath the Buddypress content but only on Buddypress Pages. However the sidebar reverts to its correct position when navigating back to non-Buddypress pages. Do you have a nice and easy solution to that problem please? Thanks and wow what a fantastic job Suffusion is. Think you will soon pass the other contenders with your ratings.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

