<div dir="ltr">For the record: the Theme Review Admins work as a team. There is no "leader". It has always been that way, and will continue to be that way, unless and until we are told otherwise.<div><br></div><div>
The community rep is just that: a liaison to communicate with the rest of the WordPress community. The community rep doesn't have to be one of the Admins (and I think it would be great if a non-admin would want to take up that role sometime).</div>
<div><br></div><div>What we are engaging in at the moment is a *discussion*. As part of that discussion, Emil and I are expressing our opinions. It is not required that all Admins hold to the same opinion (nor would such be a benefit). </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 15, 2013 at 11:18 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>End users have lived with it so far, there haven’t been any major
complaints or suggestions on the forums to say the contrary. I
believe you are over emphasizing the severity.</div>
<div> </div>
<div>There are people including myself that do not agree with this and you
personally are not listening to the community. Which makes things
difficult because you apparently have no one to answer to. Last I
checked Emil was lead at the moment and you are not. When the
community itself or members thereof do not like the results that are happening
there needs to be someone that can be talked with that can mediate the situation
and make a determination.</div>
<div> </div>
<div>It would behoove you to not be as adamant as you are. Consider
a compromise then, most of our ‘concerns’ with the myself and others who have
had themes on the repo for a predominate amount of time would not like to see
our end users have the headache that it will cause to add an additional
plugin. Hostings like 1and1 and some others are very limited with
their memory usage; <strong>so consider making it so that all NEW themes as a
requirement to not include said plugin territory options and things in priority
1 should be a bit more lenient in reviewing updates</strong>.</div>
<div> </div>
<div>I am already maxed out in tech support as it is where I do not have time
nor the inclination to sit here and worry about 20,000+ people who are going to
be emailing me or adding post after post on the forums concerning a new update
which destroys their site. Currently I already point them to
the github instead of the repo. I am positive that the repo was
there for theme’s to be able to be stored and able to be a helpful tool for the
end user and not a hindrance.</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 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> Monday, July 15, 2013 5:12 AM</div><div class="im">
<div><b>To:</b> <a title="theme-reviewers@lists.wordpress.org" href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">Discussion list for WordPress
theme reviewers.</a> </div>
<div><b>Subject:</b> Re: [theme-reviewers] Webmaster Tools IDs - plugin
territory?</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 dir="ltr"><span style="FONT-FAMILY:calibri;FONT-SIZE:12pt"></span><br><div><div class="h5">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div dir="ltr">
<div dir="ltr">
<div style="FONT-FAMILY:'Calibri';FONT-SIZE:12pt">
<div>Those when switching to one theme or another will have some things no
longer work – and that is fine. There are plenty of ways, avenues and
programming that you can take to include those features into the theme you
switch to.</div></div></div></div></blockquote>
<div> </div>
<div>I disagree with "and that is fine." Most end users aren't developers, and
won't have the skills or desire to take advantage of the "plenty of ways,
avenues and programming" to add missing functionality to their new Theme.</div>
<div> </div>
<div>The single most important party in this consideration is not the Theme
developer, or the Theme reviewers, but rather the Theme's end users. </div>
<div> </div>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div dir="ltr">
<div dir="ltr">
<div style="FONT-FAMILY:'Calibri';FONT-SIZE:12pt">
<div> </div>
<div>The BIGGEST idea about that the don’t-worry-about-it group’s main
objective is to make the theme review process easier and faster to get
through. The biggest thing that people get hung up on returning
day after day to review themes is how time consuming they are to go
through. We also believe that it’s not the theme review team’s
responsibility to control that aspect of allowing a theme to have a feature or
not, that is up to the core dev’s to make that
determination.</div></div></div></div></blockquote>
<div> </div>
<div>The core team has made it the Theme Review Team's responsibility. </div>
<div> </div>
<div>And I disagree that what you're suggesting would make Theme reviews easier.
Why would a Theme review be easier if the Theme can include any manner of
arbitrary functionality? Allowing functionality that goes beyond presentation of
user content just means that much more code that a reviewer has to review,
understand, and test. </div>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div dir="ltr">
<div dir="ltr">
<div style="FONT-FAMILY:'Calibri';FONT-SIZE:12pt">
<div> </div>
<div>Use all of the plugins, theme unit test and requirements for the
backlinks and other things. Do the cursory views of everything
that’s important and move em through the review process.
</div></div></div></div></blockquote>
<div> </div>
<div>That's not sufficient for the end user. Code needs to be secure. Included
functionality needs to work properly.I contend that those considerations *are*
important to end users. Thus, everything that a Theme indicates that it does
needs to be tested during the review process.</div>
<div> </div>
<div>The single most important party in this consideration is not the Theme
developer, or the Theme reviewers, but rather the Theme's end
users.</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>