At some degree Chip is right about the fact that the volunteerism in the theme review process takes a lot of time and adding 2 or 3 revisions to the long cycle takes sometimes months for a theme to get to /extend . However this is somehow annoying when 2 or 3 reviewer remarks mark a theme as non-approved and require a new submission and few weeks of review next.<div>
<br></div><div>Changing few lines in a ready theme might cause side effects to other portions of the site. Building a theme is a small ecosystem and a small changes in a file could break the entire flow in some cases .</div>
<div><br>All I'm saying here is that I see people publishing their own themes on 3rd party markets instead of adapting them to WPORG as it seems long and hard. Correct me if I'm wrong but the second major purpose of /extend themes repo is helping people submitting and receiving back and speeding up the process is a priority task. Step 1 is keeping the repo error free and standardized - and that's a cross point decentralized what we have, in my opinion. </div>
<div><br></div><div>The 'easier' is taking the approach "approved but fix in next update" when we don't have crucial things instead of "non-approved, fix, resubmit and wait 2 more weeks". Some tickets are closed due to 2 or 3 non-critical errors at least to my understanding:</div>
<div><br></div><div><a href="http://themes.trac.wordpress.org/ticket/5907">http://themes.trac.wordpress.org/ticket/5907</a></div><div><a href="http://themes.trac.wordpress.org/ticket/6345#comment:11">http://themes.trac.wordpress.org/ticket/6345#comment:11</a> </div>
<div><br></div><div>Sometimes I see reviews too harsh and cold although helpful and pushing people back. It causes the psychological phenomenon 'fear of rejection' at the end. </div><div><br></div><div>I don't mind reviewing according to the Guidelines. I don't mind building themes from scratch with the Theme Review list in mind. All I see are free themes that work being secure enough and used online without being able to get inside of the repo. <br clear="all">
<br>Mario Peshev<br>Training and Consulting Services @ DevriX<br><a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br><a href="http://devrix.com" target="_blank">http://devrix.com</a><br>
<a href="http://peshev.net/blog" target="_blank">http://peshev.net/blog</a><br><br>
<br><br><div class="gmail_quote">On Mon, Mar 19, 2012 at 7:02 PM, Merci Javier <span dir="ltr"><<a href="mailto:mercijavier@gmail.com">mercijavier@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>I'm not sure what you mean by "easier rules for
working Themes" either. BuddyPress themes submitted to the WP Repo go
through the same thorough reviews - Theme Unit Tests. Debogger, etc. Some BP themes which had been approved
some time ago have even been removed from WP Themes Extend page because
they have not been updated to the latest BP version.<div class="im"><br><br><div style="margin-left:40px"><i>>></i> <i>have to spend tens (if not more) hours to keep all the rules in place,
such as defining classes for byauthor and sticky and many many more
irrelevant for themes being used as web site templates.</i><br></div><br></div>Less than an hour to add minimum theme requirements of index.php, comments.php and screenshot plus style.css - <a href="http://codex.wordpress.org/Theme_Review#Theme_Template_Files" target="_blank">http://codex.wordpress.org/Theme_Review#Theme_Template_Files</a><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></blockquote></div><br></div>