<div dir="ltr">That's a workflow, not actual Guidelines.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 26, 2013 at 11:00 AM, Philip M. Hofer (Frumph) <span dir="ltr"><<a href="mailto:philip@frumph.net" target="_blank">philip@frumph.net</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 dir="ltr">
<div style="font-size:12pt;font-family:'Calibri'">
<div>It’s written below your reply in the message. </div>
<div> </div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal">
<div style="FONT:10pt tahoma">
<div><font size="3" face="Calibri"></font> </div>
<div style="BACKGROUND:#f5f5f5">
<div><b>From:</b> <a title="chip@chipbennett.net" href="mailto:chip@chipbennett.net" target="_blank">Chip Bennett</a> </div>
<div><b>Sent:</b> Wednesday, June 26, 2013 7:57 AM</div>
<div><b>To:</b> <a title="theme-reviewers@lists.wordpress.org" href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">[theme-reviewers]</a> </div><div class="im">
<div><b>Subject:</b> Re: [theme-reviewers] Formal Request for Change of
Methodology.</div></div></div></div>
<div> </div></div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal"><div><div class="h5">
<div dir="ltr">If you're going to propose a complete overhaul of the Theme Review
philosophy, that will require a complete rewrite of the Theme Review Guidelines.
Please proffer a replacement set of Guidelines - i.e. what exact content you
would have on the Theme Review Codex page. Then we can compare, contrast, and
discuss.
<div> </div>
<div> </div></div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">On Wed, Jun 26, 2013 at 1:10 AM, Philip M. Hofer (Frumph)
<span dir="ltr"><<a href="mailto:philip@frumph.net" target="_blank">philip@frumph.net</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">1) Remove all requirements and recommendations, change it
all to 'best practices', do not remove anything in the codex just
yet.<br><br>2) Theme review process.<br>* Theme reviewers tag a theme for
review. / It already passed the upload checker<br>* Check theme with the other
plugin(s)[1] available for development, check it for notices, warnings, fatals
and deprecation messages, Pass/Fail<br>* Check theme with theme unit
test. Pass/Fail<br>* Review the tags, website links, theme name.
Pass/Fail<br><br>It's done, it's reviewed, it's over, if it passed all of
those, flag it as passing review and live.<br><br>3) Anything else missing on
the above list that is a MUST should be added to the list but only if it's a
MUST, and can't go live no exception.<br><br>[1] Make the plugins work for the
theme review team; add common security problems,
etc.<br><br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<u></u>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br><br>This
is it, this is all that is needed. Everything else is
icing on the cake for best practices.<br><br><br>Themes are the 'meat and
potatoes' of WordPress, the idea that a theme must adhere and be cross
compatible with other themes in features is a nuance that is unnecessary to
worry about. Plugins are made to enhance themes; if a plugin
doesn't work with a theme the community WILL contact the author; they always
do. As long as the theme is up to date with core coding which all
of the tools at our disposal make you aware of - of which even the messages
from core will also state things it is unnecessary to do anything
otherwise.<br><br>// not sure about<br>Not sure what Nacin wrote in entirety
on the Make site, but having the themes that are live and pass the upload
process and immediately go live again would be a boon; that basically makes it
like the theme developer has svn access, without having svn
access.<br><br><br><br><br><br>______________________________<u></u>_________________<br>theme-reviewers
mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</blockquote></div>
<div> </div></div>
</div></div><p>
</p><hr><div class="im">
_______________________________________________<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>
</div><p></p></div></div></div></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>