<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Going to reiterate.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>I am not doing theme reviews right now, several
reasons. The core team requesting we allow crap onto the repository
is ridiculous. The amount of time to spend reviewing a theme went
from 15 minutes to an hour to differ between what is acceptable and what is
not. </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>There are deprecated functions being used that were
deprecated since 2.1, if you don't fail the themes for those then why deprecate
those functions to begin with? There has to be a limit. I'm not
going to sit and look and weigh every single one, its either an all or nothing,
they fail or not. Notices that give warnings that the wrong property
object signify that the code is either not receiving the right property or value
which then makes the functionality of the theme just not-work. They
display as 'notices'. If you allow that sort of thing on the
repository then you're opening up a can of worms. It just isnt
productive to the wordpress users to do so. When those themes on the
repository to be looked at, exampled and used for other developers themes the
never-ending cycle of crap function usage will just continue.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>@Nacin chastises every little thing for the core
yet when it comes to tertiary products that attach themself to WordPress he's
all "Let it pass". </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>When is the line going to be drawn to what is
acceptable or not? Everythings all "recommended this" "recommend that"
there has to be a coding standard and it has to be 'up to date' with the current
WordPress revision.</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=philip@frumph.net href="mailto:philip@frumph.net">Philip M. Hofer
(Frumph)</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, September 24, 2010 2:24
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] What is
wrong with you people?YourejectedTarski?</DIV>
<DIV><BR></DIV>
<DIV><FONT size=2 face=Arial>So you wouldn't reject it based on the
comment_form() or the get_search_form() ? alrightey. And this is
why i'm not doing theme reviews anymore. You're letting crap coding
pass. Which then other people will then populate their themes with crap
coding.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=wp@andrewnacin.com href="mailto:wp@andrewnacin.com">Andrew
Nacin</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, September 24, 2010 2:04
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] What is
wrong with you people? YourejectedTarski?</DIV>
<DIV><BR></DIV>On Fri, Sep 24, 2010 at 4:50 AM, Philip M. Hofer (Frumph)
<SPAN dir=ltr><<A href="mailto:philip@frumph.net"
target=_blank>philip@frumph.net</A>></SPAN> wrote:
<DIV class=gmail_quote>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Furthermore let's talk about ionfish how he has
functions calling hooks instead of just embedding the hook in the location
used .. erm.. why? .. yeah I would call that unneeded unnecessary
coding. </BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>We're rejecting quality, extremely well coded themes on narrow
technical grounds. It's not even a new theme. It's a minor update to a
long-time existing one that is terrifically coded and wildly popular; it's a
step in the right direction. This kind of rejection goes against the
primary goals of the theme reviews. I see no reason why this theme
update should not be approved. Not on the basis of it being rejected
initially, not on a cursory review of the codebase, and not on this email,
either.</DIV></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></BLOCKQUOTE>
<P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></BLOCKQUOTE></BODY></HTML>