<div class="gmail_quote">On Wed, Aug 25, 2010 at 4:21 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I don't necessarily want to bring that discussion over here, but maybe<br>
it should be here.<br></blockquote><div><br></div><div>I would suggest that this is the *best* place to have the discussion. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Acting as a wall between theme developers and their users is not good<br>
for either side, and it is definitely not good for the community as a<br>
whole.<br>
<br>
We don't need high quality code or high quality themes. </blockquote><div><br></div><div>Disagree, 100%. The Theme repository is linked directly into the back-end of WordPress, and represents and reflects WordPress. </div>
<div><br></div><div>Also, poor code quality and failure to keep Themes from becoming obsolete through function deprecation and failure to include new/improved core functions and features is *bad* for end users.</div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">We<br>
*desperately* need high quality people who can help out these theme<br>
authors, and point out the problems and explain *why* things should be<br>
done a certain way. But if you keep summarily rejecting themes for<br>
frankly trivial reasons, then you just drive out theme developers and<br>
you never have a chance to help them improve anything.<br></blockquote><div><br></div><div>Review a Theme or two, by the standards, and then let us know how the experience was for you. The vast, vast majority of Themes are not failing for "trivial reasons". Most are failing for the basics: errors output by WP_DEBUG, invalid HTML/CSS, no wp_head() or wp_footer(), etc.</div>
<div><br></div><div>There are some Theme developers that are complaining that they have to accommodate wp_nav_menu() for their navigation menus, but that is not a valid complaint, IMHO. It is an opportunity to help the Theme developer understand why supporting the built-in Nav Menu functionality is appropriate, and good for their Theme users.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
We're actively driving away people with this process. </blockquote><div><br></div><div>No, we're not. </div><div><br></div><div>Maybe the timeliness of reviews is a concern. That's fair - but then, we only have 3-4 active reviewers at any given time.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Seriously, it<br>
*must* change. Approving only 1 in 8 themes is simply a travesty.<br></blockquote><div><br></div><div>Go audit the 545 Themes that were rejected. You tell us what percentage of those should have been approved, in your opinion, and why.</div>
<div><br></div><div>The only travesty here is the dearth of code quality being submitted for inclusion in the Theme repository. </div><div><br></div></div>Chip