<div dir="ltr"><div>I think it’s worth saying something because there are those of us that review who see it as absolutely a worthwhile thing to do. I know it’s made me a better themer and that alone is a good reason to be a theme reviewer. That said, this is only one reason. It’s something a themer can do and give back as a contribution.</div>
<div><br></div><div>Michael, if for whatever reason you feel that theme reviewing isn’t a good fit for you, that’s fine. It is important though and I also think everyone in this community is grateful to any reviewer. Everyone’s time is valuable, theme reviewing is a valuable thing you can do. But, again if it’s not right for you then that is fine. Nobody should be made to be a reviewer. Encouragement and support rock - enforced reviewing is never fun.</div>
<div><br></div><div>We have to respect each other and realise we all have that thing called life. Life and work mean we may not have time to review. That’s fine, this is a community contribution and we should be sure to keep this a supportive, happy, friendly theme review community. People may come, people may go - that’s ok, that’s open source. The theme review team admins have a lot on their plate and a lot of 'balls up in air'. As reviewers I think we should all make sure we remember that and support them as a community.</div>
<div><br></div><div>As someone that has lead and participated in a theme review groups for contributions days, I think I have to just say how important these are. Whether contributors continue or not, that’s not the point. I myself in no way see it as a recruitment drive. What I do see it as is a potential. A potential to set a themer on a path where they know about theme checks. A potential to show them what theme reviews are. If the review bug gets them - great. If not, well they know more about what should be done with themes and that will make them a better themer. That I think is pretty cool.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Thanks</div><div class="gmail_extra">Tammie Lister<br><br><div class="gmail_quote">On Thu, Jul 31, 2014 at 5:22 PM, 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 style="font-family:arial,helvetica,sans-serif"><div>Just had a nice chat with Jen on Skype and here are some suggestions:</div>
<div><br>
</div><div>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><br></div><div>
Once we got this information in we could then incorporate into Theme Check (or similar) and <i>automate</i>. </div><div><br></div><div>We will be looking into smaller and basic errors, nothing to complex, or issues that require special handling. </div>
<div><br></div><div>Second:</div>
<div><br></div><div>#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><br></div>
<div>For #3 and #4 priorities to be reviewed within 48hrs?</div><div><br></div><div>This will clear-out the backlog and the process will be much faster. </div>
<div><br></div><div>Admins would still carry out their duties and reviewers as well.</div><div><br></div><div>Thanks,</div><div>
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>