<div dir="ltr"><div><div><div><div><div><div><div>In all fairness, the system isn't going to sustain itself forever relying on a volunteer-basis anyways, period.<br><br></div>Let's not forget that WordPress is a business, the success of its monetization relies on a lot of things including everything we all do, whether reviewing, contributing themes and plugins or both.<br>
<br></div>Recently, Responsive, a theme that needs no introduction was taken from the free .org repo and made available on .com. While they don't sell Responsive directly this is a huge deal that leads to more .com signups that without a doubt leads to more upsells to premium .com features. While the explanation of the move is a littler more superficial, it's still an undeniable perk.<br>
<br></div>I'm not complaining or pointing fingers or anything of the sort mind you, this is great for everyone, we all benefit. These are all good things.<br><br></div>I don't think all volunteers should be paid by any means, but there's no doubt in my mind that all the admins should be hired and paid to dedicate time to the project like a full time job.<br>
<br></div>I can't speak for all the admins, especially what work goes on behind the scenes, but I can without a doubt say Chip should be hired on. I'm not speaking for Chip, I'm sure he'll graciously continue to volunteer purely out of his interest in the project, but he's not expendable.<br>
<br></div>You can't argue, well it's his choice to volunteer, because that was all transcended a long time ago. Admins like Chip are a backbone to the day-to-day operational of this beast and if the admins dropped out it would crumble. They aren't just helpful, they are necessary.<br>
<br></div>To keep up with the demand, WordPress needs to step up and hire the admins and get them to dedicate to the project full time. That is a realistic solution of substance that is a no-brainer. Any other ideas of trying to "make this work better" are all half-measures.<br>
</div><div class="gmail_extra"><br clear="all"><div><br><br>Bryan Phillip Hadaway<br>
<div><span style="font-size:13.3px;font-family:Verdana,Arial,Helvetica,sans-serif"><div style="margin:0pt 0pt 8px"><p style="margin:0pt"><span style="color:rgb(46,45,46)"> <br> Web & Graphic Designer<br>
<a href="http://calmestghost.com/" target="_blank">calmestghost.com</a><br> <a href="mailto:bhadaway@gmail.com" target="_blank">bhadaway@gmail.com</a></span></p><p style="margin:0pt"><span style="color:rgb(46,45,46)"><br>
<b>Socialize:</b></span> <span style="font-size:13.3px;font-family:Verdana,Arial,Helvetica,sans-serif"><a href="http://www.facebook.com/calmestghost" target="_blank">Facebook</a> |</span><span style="font-size:13.3px;font-family:Verdana,Arial,Helvetica,sans-serif"> <a href="http://twitter.com/calmestghost" target="_blank">Twitter</a> </span><span style="font-size:13.3px;font-family:Verdana,Arial,Helvetica,sans-serif">| </span><a href="http://www.linkedin.com/in/calmestghost" target="_blank">LinkedIn</a> | <a href="https://plus.google.com/104582075016689917593" target="_blank">Google+</a></p>
</div></span></div>
</div>
<br><br><div class="gmail_quote">On Wed, Apr 10, 2013 at 5:29 AM, Greg Priday <span dir="ltr"><<a href="mailto:greg@siteorigin.com" target="_blank">greg@siteorigin.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm not sure that this would promote favoritism, especially if the<br>
ordering is completely automated. It also wouldn't change anything<br>
about the review process, only the order in which the themes are<br>
reviewed. If I found an issue in one of @automattic's themes, I'd<br>
gladly let them know ;)<br>
<br>
I agree that first come, first serve is ideal. The problem is that we<br>
can't view our pool of reviewers as a black box that gobbles up<br>
tickets and spits out feedback. There are very few active reviewers<br>
working against a constantly growing queue. My solutions might not be<br>
the best ones, but we do need to come up with a solution to the<br>
problem.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
On Wed, Apr 10, 2013 at 1:12 PM, Bryan Hadaway <<a href="mailto:bhadaway@gmail.com">bhadaway@gmail.com</a>> wrote:<br>
> This would promote favoritism, whether intended or not.<br>
><br>
> Review order and queue should remain relevant to the theme itself on a<br>
> "first come, first serve" basis.<br>
><br>
> And the review of a theme should only be based on the merit of that specific<br>
> theme and have nothing to do with the developer, whether they're new,<br>
> seasoned, have zero themes in the repo or a hundred.<br>
><br>
><br>
><br>
> Bryan Phillip Hadaway<br>
><br>
><br>
> Web & Graphic Designer<br>
> <a href="http://calmestghost.com" target="_blank">calmestghost.com</a><br>
> <a href="mailto:bhadaway@gmail.com">bhadaway@gmail.com</a><br>
><br>
><br>
> Socialize: Facebook | Twitter | LinkedIn | Google+<br>
><br>
><br>
><br>
> On Wed, Apr 10, 2013 at 5:04 AM, Greg Priday <<a href="mailto:greg@siteorigin.com">greg@siteorigin.com</a>> wrote:<br>
>><br>
>> If you look at the new themes (#4) queue, Around 75% of the tickets<br>
>> (at the time of my research) are from new theme developers, without<br>
>> any approved themes on .org. These themes are waiting in the same<br>
>> queue as established developers with lots of approved themes like<br>
>> @automattic (23 themes), @d5creation (9 themes), etc.<br>
>><br>
>> In my experience, established developers have a much higher chance of<br>
>> having a high quality issue-free theme. I'm sure someone could analyze<br>
>> all the tickets on track find the exact relationship of number of<br>
>> themes to approval rate.<br>
>><br>
>> I'm not hating on new developers. We all had to start somewhere, and<br>
>> there definitely are diamonds in the rough.<br>
>><br>
>> I burned out a little on reviewing themes because searching through<br>
>> poorly written code for the same handful of issues is mind numbing.<br>
>> The highlight of my day was finding someone who actually checked the<br>
>> theme review guidelines instead of just tweaking their theme until<br>
>> they made it past the theme check. I'm sure that's the case for a lot<br>
>> of us.<br>
>><br>
>> We simply don't have the reviewer resources to make this a priority.<br>
>><br>
>> Solutions:<br>
>><br>
>> * Order the theme review queues first by number of approved themes<br>
>> from a given developer, then date. This will allow us to focus on<br>
>> established developers first, then get around to finding the<br>
>> diamond-in-the-rough new developers (I'm not sure this is possible in<br>
>> trac though).<br>
>><br>
>> * Screen new developers with a quiz that ensures they understand the<br>
>> guidelines. Even 20 multiple choice questions covering the most common<br>
>> issues would go a long way.<br>
>><br>
>> Side Notes:<br>
>><br>
>> Interestingly, if you look at the #3 queue (previously reviewed), only<br>
>> 50% of the tickets are from new developers. Much less than the 75% in<br>
>> #4. This is some indication of the drop out rate of new devs vs<br>
>> established devs.<br>
>><br>
>> --<br>
>> I make free WordPress themes<br>
>> <a href="http://siteorigin.com" target="_blank">http://siteorigin.com</a><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>
><br>
><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>
<br>
<br>
<br>
--<br>
I make free WordPress themes<br>
<a href="http://siteorigin.com" target="_blank">http://siteorigin.com</a><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>
</div></div></blockquote></div><br></div>