<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I was thinking something much the same. Why not put more of the onus on the Theme Developers before they can submit theme? Whether it's making them complete two or three reviews before they can submit themes themselves, thus learning the full extent of theme requirements. Or maybe, developing an exam style process where only qualified developers can submit themes.</div><div><br></div><div>This will hopefully lead to better quality themes being developed; making themes quicker & easier to review and improving the quality available for the end user to choose from.</div><div><br></div><div>I learnt a lot about developing themes from doing reviews first and am pleased to have got my first theme live just today. I learnt a lot what I thought I knew to be right was in fact wrong before I even got round to developing my theme.</div><div><br></div><div>I know it'll upset some people and they may say that the submission process is just for experienced developers and we'd be alienating beginner developers, but at the end of the day, as a developer or reviewer we are all here with the common goal of making WordPress better.</div><div><br>Sent from my iPhone</div><div><br>On 31 Jul 2014, at 22:34, Srikanth Koneru <<a href="mailto:tskk79@gmail.com">tskk79@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div><div><div><div>Why not make the theme authors do a pre-review themself?<br></div>Before uploading, they have to confirm for ex:<br><br></div>License of all images/third party resources has be mentioned and source/license link provided (yes/no)<br>
</div>No js/css other than style.css has been hardcoded in header.php (yes/no)<br></div>wp_head() is placed right before </head> (yes/no)<br></div>etc<br><br></div>We can have a big list and make the theme authors check and upload?<br>
<div><div><div><div><br></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 1, 2014 at 2:52 AM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><div class="gmail_default">​Just had a nice chat with Jen on Skype and here are some suggestions:</div>
<div class="gmail_default"><br>
</div><div class="gmail_default">With the help of few volunteers, we need to go back and look at reviews from the past year to identify the errors that we catch most often. </div><div class="gmail_default"><br></div><div class="gmail_default">
Once we got this information in we could then incorporate into Theme Check (or similar) and <i>automate</i>. </div><div class="gmail_default"><br></div><div class="gmail_default">We will be looking into smaller and basic errors, nothing to complex, or issues that require special handling. </div>
<div class="gmail_default"><br></div><div class="gmail_default">Second:</div>
<div class="gmail_default"><br></div><div class="gmail_default">#1 priority themes should be reviewed in right away, not tomorrow or day after, how about if we do the same for #2?</div><div class="gmail_default"><br></div>
<div class="gmail_default">For #3 and #4 priorities to be reviewed within 48hrs?</div><div class="gmail_default"><br></div><div class="gmail_default">This will clear-out the backlog and the process will be much faster. </div>
<div class="gmail_default"><br></div><div class="gmail_default">Admins would still carry out their duties and reviewers as well.</div><div class="gmail_default"><br></div><div class="gmail_default">Thanks,</div><div class="gmail_default">
Emil </div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Thu, Jul 31, 2014 at 4:06 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</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 dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><div>On Thu, Jul 31, 2014 at 4:00 PM, Thomas from ThemeZee <span dir="ltr"><<a href="mailto:contact@themezee.com" target="_blank">contact@themezee.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Relating to the admin bottle-neck: What about appointing trusted / experienced theme reviewers? They can perform second reviews of the "approved themes but not marked live" list. Since they are experienced they will find issues quickly. They should not be allowed to mark themes as live, but are able to reopen tickets. <br>
</div></div></blockquote><div><br></div></div>For what it's worth, anybody can do that right now. You don't have to be "assigned" a ticket to leave comments on it. You don't need to reopen it to tell an author there are problems you've found.<div>
<br></div><div>I honestly never liked the assigning of tickets in the first place. It's too rigid, IMO. I realize that we need order and fairness, but the assignment system seems to imply that there is only one reviewer per theme, and that's absolutely not the case. If you want to go pick a waiting theme at random, find problems in it, and post them in that ticket, then by all means, do so. A problem discovered but not posted helps nobody. </div>
<div><br></div><div>There's nothing preventing anybody from reviewing any theme they want at any time, just by leaving comments on a ticket to tell a theme author about the issues. If a theme is fully good by the time admins get to it, then it's quicker all around, no? Okay, it's more disorderly. But we're all adults; we can deal with a little disorder.<span><font color="#888888"><br>
<div class="gmail_extra"><br clear="all"><div>-Otto</div></div></font></span></div><div><br></div></div></div></div></div>
<br></div></div><div class="">_______________________________________________<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></div></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>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>theme-reviewers mailing list</span><br><span><a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a></span><br><span><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a></span><br></div></blockquote></body></html>