<div class="gmail_extra">I think a guideline like this is far too subjective. How do you possibly determine how many is too many? A theme uses jQuery UI and some jQuery plugins to do some interesting stuff. That could had several additional requests. How do you really say to a developer that their functionality is no good because it has one file request to many?</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">At best I could see us asking for heavy http requests to be documented as some server set-ups might not be able to handle some heavier themes. While others have no issue. But setting a rule that says how many seems a little off.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">James<br><br><div class="gmail_quote">On Tue, Apr 24, 2012 at 9:41 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra">Setting aside (for the moment) the proposition to add guidelines regarding max HTTP requests/page speed, I want to address quickly your last two points:</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">
URLs are not permanent. The Theme URI was verified to exist and to be appropriate at the time of Theme approval. We can neither control, nor effectively police, URLs post-approval. (In this case, Justin Tadlock simply moved his own Themes back to his own domain, <a href="http://justintadlock.com" target="_blank">justintadlock.com</a>, when we divested himself from DevPress. Nothing underhanded going on there.)</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Also, repository-hosted Themes are not required to be offered with support, through the WPORG support forums, the developer's site, or anywhere else. Offering commercial support for a free, 100% GPL Theme does not violate WPORG policy or Theme review guidelines. (In fact, a developer having a vested interest in providing support for a repository-hosted Theme will generally provide a *better* support experience for end users.)</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Having addressed those two points, I'm curious what others think about your proposed guidelines...</div><div class="gmail_extra"><br></div><div class="gmail_extra">
Chip<br><br><div class="gmail_quote"><div><div class="h5">On Tue, Apr 24, 2012 at 6:36 AM, Robb Shecter <span dir="ltr"><<a href="mailto:robb@weblaws.org" target="_blank">robb@weblaws.org</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div>I propose a guideline for maximum number of http requests generated per single-post and index views. The plugin can test this via a custom YSlow or Page Speed suite. We can have minimum scores for inclusion in the directory as well as the "featured" list in the Admin theme installer.
</div><div><br></div><div>The reason: I had a disastrous experience with one of the featured themes, News. I installed it on a brand new blog. Each page visit caused 47 http requests to the server. A moderately popular link from Reddit crashed my entire server. (Details are in my blog post: <a href="http://www.g33klaw.com/2012/04/the-hidden-dangers-of-beautiful-themes/" target="_blank">http://www.g33klaw.com/2012/04/the-hidden-dangers-of-beautiful-themes/</a> ) </div>
<div><br></div><div>Furthermore, the "theme homepage" link on the <a href="http://wordpress.org" target="_blank">wordpress.org</a> site is broken, and support seems to only be offered via a for-pay forum. These should also be grounds for exclusion from the directory and featured lists.</div>
<span><font color="#888888"><div><br></div><div>Robb</div><div><br></div>
</font></span><br></div></div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>