<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>I like Emil’s list and think it’s the right step to go. It’s a form
of grandfathering. </DIV>
<DIV> </DIV>
<DIV>Chip.</DIV>
<DIV> </DIV>
<DIV>How many insane laws are made in the world that are designed by “Think of
the children!” in mind. There is a law in AV California that
says that parents need to stay within 20 feet of their children on a public
accessible playground at all times. Sure it sounds good, it’s
responsible and you’re “Thinking of the Children” but seriously do you really
need a law for that? </DIV>
<DIV> </DIV>
<DIV>Too many laws not enough freedoms man, get the analogy?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>I just realized not a single person has ever complained to me about how
something doesn’t work when switching to a different theme. There was one
time when someone asked me for the code to add to their new theme, and in that
case I created documentation for it: <A
title=http://frumph.net/2013/04/19/use-my-custom-default-random-avatars-code-in-any-theme/
href="http://frumph.net/2013/04/19/use-my-custom-default-random-avatars-code-in-any-theme/">http://frumph.net/2013/04/19/use-my-custom-default-random-avatars-code-in-any-theme/</A>
It’s amazing how intelligent the end users are – belittling them – considering
them too stupid to make mods is not in my repertoire, helping and teaching them
is.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"></DIV>
<DIV style="FONT: 10pt tahoma">
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=chip@chipbennett.net
href="mailto:chip@chipbennett.net">Chip Bennett</A> </DIV>
<DIV><B>Sent:</B> Monday, July 15, 2013 5:37 PM</DIV>
<DIV><B>To:</B> <A title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">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
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV dir=ltr>I take a different perspective: the end-user experience shouldn't
just factor into everything we do; it should be the primary focus.
<DIV>
<UL>
<LI>Why are copyright and licensing so important? Because they protect
end-user freedoms.<BR>
<LI>Why is handling of credit link text and removal instructions so important?
So that end users are not unwittingly used as advertisers, and so that they
are not misled.<BR>
<LI>Why are code quality and data security so important? Because it is the end
user who is harmed if the Theme throws errors, causes performance issues, or
leads to a security breach.<BR>
<LI>Why is it important that Themes incorporate features in a manner
consistent with core implementation? Because the end user would be harmed if a
Theme causes interaction problems with core, or with Plugins.<BR>
<LI>In the same vein, why is it important that Themes maintain a clear
distinction between presentation and functionality? Because the end user is
harmed when losing non-presentational functionality (or worse: user-generated
content) when switching Themes.<BR></LI></UL></DIV>
<DIV>Most of these things aren't issues for developers. We generally understand
the implications of the GPL, and know how to de-couple functionality from a
Theme. We know how to find code errors, and how to fix security vulnerabilities.
The vast majority of end users don't. Developers don't need any of the Theme
Review Guidelines for their own purposes. But under free software philosophy, it
is not the developer's purposes but rather the end user's purposes that are
paramount.<BR></DIV>
<DIV> </DIV>
<DIV>Now, obviously, there are limits - feasibility, due diligence, etc. - in
the implementation. But as a matter of principle/philosophy, we *must* consider
the end user.</DIV></DIV>
<DIV class=gmail_extra><BR>*****</DIV>
<DIV class=gmail_extra> </DIV>
<DIV class=gmail_extra> </DIV>
<DIV class=gmail_extra> </DIV>
<DIV class=gmail_extra> </DIV>
<DIV class=gmail_extra><BR> </DIV>
<DIV class=gmail_quote>On Mon, Jul 15, 2013 at 6:38 PM, Emil Uzelac <SPAN
dir=ltr><<A href="mailto:emil@uzelac.me"
target=_blank>emil@uzelac.me</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>From Theme Review to User experience is a long journey
<DIV>and should not be part of TRT, because it will never end.</DIV></DIV>
<DIV class=HOEnZb>
<DIV class=h5>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Mon, Jul 15, 2013 at 5:09 PM, Dane Morgan <SPAN
dir=ltr><<A href="mailto:dane@danemorganmedia.com"
target=_blank>dane@danemorganmedia.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV text="#000000" bgcolor="#FFFFFF">
<DIV>I fully disagree, though I'm not sure what that is worth since i have
yet to start reviewing themes. I follow this more to learn and see things
develop. Though I am considering jumping it to volunteer as well.
<DIV>
<DIV><BR><BR>On 2013-07-15 16:58, Emil Uzelac wrote:<BR></DIV></DIV></DIV>
<DIV>
<DIV>
<BLOCKQUOTE type="cite">
<DIV dir=ltr>Anyone can change it, we just need to agree that this is
acceptable :)</DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Mon, Jul 15, 2013 at 4:57 PM, Harish <SPAN
dir=ltr><<A href="mailto:me@harishchouhan.com"
target=_blank>me@harishchouhan.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV lang=EN-IN vlink="purple" link="blue">
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Hi
Emil,</SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN> </P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Now
that is the perfect list. I hope admins, and whoever are in charge adopt
this list. This will this end this discussion.</SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN> </P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Also
when anything extra such as SEO options, custom post types are used, we
can make it mandatory that the theme developer properly documents it
somewhere so it’s easier to use along with a mandatory warning about
what would happen if theme is changed.</SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN> </P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #404040; FONT-SIZE: 11pt"></SPAN> </P>
<P style="LINE-HEIGHT: 150%" class=MsoNormal><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #404040; FONT-SIZE: 11pt">Regards,</SPAN></P>
<P style="LINE-HEIGHT: 150%" class=MsoNormal><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #404040; FONT-SIZE: 11pt">Harish
Chouhan</SPAN></P>
<P style="LINE-HEIGHT: 150%" class=MsoNormal><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Arial','sans-serif'; COLOR: #404040; FONT-SIZE: 10pt"></SPAN> </P>
<P style="LINE-HEIGHT: 150%" class=MsoNormal><B><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #0d0d0d; FONT-SIZE: 11pt">Visit
me at </SPAN></B><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #0d0d0d; FONT-SIZE: 16pt">-
</SPAN><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><A
href="http://www.harishchouhan.com/" target=_blank><SPAN
style="LINE-HEIGHT: 150%; COLOR: black; FONT-SIZE: 10pt">www.harishchouhan.com</SPAN></A></SPAN><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #0d0d0d; FONT-SIZE: 10pt">
</SPAN><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #0d0d0d; FONT-SIZE: 16pt"><BR><BR></SPAN><B><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #0d0d0d; FONT-SIZE: 10pt"></SPAN></B></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN> </P></DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 11pt"
lang=EN-US>From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 11pt" lang=EN-US>
theme-reviewers [mailto:<A
href="mailto:theme-reviewers-bounces@lists.wordpress.org"
target=_blank>theme-reviewers-bounces@lists.wordpress.org</A>] <B>On
Behalf Of </B>Emil Uzelac<BR><B>Sent:</B> Tue 16 July 13 03:14
AM</SPAN></P>
<DIV>
<DIV><BR><B>To:</B> Discussion list for WordPress theme
reviewers.<BR><B>Subject:</B> Re: [theme-reviewers] Webmaster Tools IDs
- plugin territory?</DIV></DIV>
<DIV>
<DIV>
<P class=MsoNormal> </P>
<DIV>
<P class=MsoNormal><SPAN>I would not base this on another Theme and yes
it does seem unfair</SPAN></P>
<DIV>
<P class=MsoNormal><SPAN>for new Themes. The only items that should be
required are:</SPAN></P></DIV>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P style="LINE-HEIGHT: 13.65pt; MARGIN-LEFT: 13.5pt"
class=MsoNormal><SPAN
style="FONT-FAMILY: symbol; FONT-SIZE: 10pt"><SPAN>·<SPAN>
</SPAN></SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt">Removing
or modifying non-presentational core hooks</SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt"></SPAN></P>
<P style="LINE-HEIGHT: 13.65pt; MARGIN-LEFT: 13.5pt"
class=MsoNormal><SPAN
style="FONT-FAMILY: symbol; FONT-SIZE: 10pt"><SPAN>·<SPAN>
</SPAN></SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt">Disabling
the admin toolbar</SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt"></SPAN></P>
<P style="LINE-HEIGHT: 13.65pt; MARGIN-LEFT: 13.5pt"
class=MsoNormal><SPAN
style="FONT-FAMILY: symbol; FONT-SIZE: 10pt"><SPAN>·<SPAN>
</SPAN></SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt">Resource
compression/caching</SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt"></SPAN></P>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'">robots.txt can be stopped
via uploaded, so that part does not need</SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'">to be in.
</SPAN></P></DIV>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'">And we can recommend the
rest:</SPAN></P></DIV>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P style="LINE-HEIGHT: 13.65pt; MARGIN-LEFT: 13.5pt"
class=MsoNormal><SPAN
style="FONT-FAMILY: symbol; FONT-SIZE: 10pt"><SPAN>·<SPAN>
</SPAN></SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt">Analytics
scripts</SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt"></SPAN></P>
<P style="LINE-HEIGHT: 13.65pt; MARGIN-LEFT: 13.5pt"
class=MsoNormal><SPAN
style="FONT-FAMILY: symbol; FONT-SIZE: 10pt"><SPAN>·<SPAN>
</SPAN></SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt">SEO
options (meta tags, page title, post titles, robots.txt,
etc.)</SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt"></SPAN></P>
<P style="LINE-HEIGHT: 13.65pt; MARGIN-LEFT: 13.5pt"
class=MsoNormal><SPAN
style="FONT-FAMILY: symbol; FONT-SIZE: 10pt"><SPAN>·<SPAN>
</SPAN></SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt">Content
Sharing buttons/links</SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt"></SPAN></P>
<P style="LINE-HEIGHT: 13.65pt; MARGIN-LEFT: 13.5pt"
class=MsoNormal><SPAN
style="FONT-FAMILY: symbol; FONT-SIZE: 10pt"><SPAN>·<SPAN>
</SPAN></SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt">Custom
post-content shortcodes</SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt"></SPAN></P>
<P style="LINE-HEIGHT: 13.65pt; MARGIN-LEFT: 13.5pt"
class=MsoNormal><SPAN
style="FONT-FAMILY: symbol; FONT-SIZE: 10pt"><SPAN>·<SPAN>
</SPAN></SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt">Custom
Post Types</SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt"></SPAN></P>
<P style="LINE-HEIGHT: 13.65pt; MARGIN-LEFT: 13.5pt"
class=MsoNormal><SPAN
style="FONT-FAMILY: symbol; FONT-SIZE: 10pt"><SPAN>·<SPAN>
</SPAN></SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt">Custom
Taxonomies</SPAN><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'; FONT-SIZE: 10pt"></SPAN></P></DIV>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'">Good, not, what do you
think? </SPAN></P></DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal> </P></DIV></DIV>
<DIV>
<P class=MsoNormal> </P></DIV></DIV></DIV></DIV></DIV>
<DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal> </P>
<DIV>
<P class=MsoNormal>On Mon, Jul 15, 2013 at 4:15 PM, Harish <<A
href="mailto:me@harishchouhan.com"
target=_blank>me@harishchouhan.com</A>> wrote:</P>
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: #cccccc 1pt solid; PADDING-BOTTOM: 0cm; PADDING-LEFT: 6pt; PADDING-RIGHT: 0cm; MARGIN-LEFT: 4.8pt; BORDER-TOP: medium none; MARGIN-RIGHT: 0cm; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">This
sounds good for existing themes. However it would then seem unfair for
new themes as old themes would have more features and the new once
would feel of less value. </SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN> </P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Instead,
let us consider based on say popular themes such as Responsive, etc.
and whatever features they have, make them acceptable for all new
themes and lets just end that. </SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN> </P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #404040; FONT-SIZE: 11pt"></SPAN> </P>
<P style="LINE-HEIGHT: 150%" class=MsoNormal><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #404040; FONT-SIZE: 11pt">Regards,</SPAN></P>
<P style="LINE-HEIGHT: 150%" class=MsoNormal><SPAN
style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #404040; FONT-SIZE: 11pt">Harish
</SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN> </P>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 11pt"
lang=EN-US>From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 11pt"
lang=EN-US> theme-reviewers [mailto:<A
href="mailto:theme-reviewers-bounces@lists.wordpress.org"
target=_blank>theme-reviewers-bounces@lists.wordpress.org</A>] <B>On
Behalf Of </B>Emil Uzelac<BR><B>Sent:</B> Tue 16 July 13 02:41
AM</SPAN></P>
<DIV>
<DIV>
<P class=MsoNormal><BR><B>To:</B> Discussion list for WordPress theme
reviewers.<BR><B>Subject:</B> Re: [theme-reviewers] Webmaster Tools
IDs - plugin territory?</P></DIV></DIV>
<DIV>
<DIV>
<P class=MsoNormal> </P>
<DIV>
<P class=MsoNormal>Would it be acceptable if <A
href="http://make.wordpress.org/themes/guidelines/guidelines-plugin-territory/"
target=_blank>this guideline</A> does not apply to the Themes that are
already in repository?</P>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P class=MsoNormal><I>Plugin Territory Guidelines are required for new
Themes, and recommended for existing Themes.</I></P></DIV>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P class=MsoNormal>If there are no security issues, conflict with the
core etc.</P></DIV>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P class=MsoNormal>Am I asking too much, what do you think?</P></DIV>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P class=MsoNormal>P.S. Also only few of us are discussing this, are
the rest not interested, affected, what's up?</P></DIV>
<DIV>
<P class=MsoNormal> </P></DIV>
<DIV>
<P class=MsoNormal>Emil </P></DIV></DIV>
<DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal> </P>
<DIV>
<P class=MsoNormal>On Mon, Jul 15, 2013 at 10:36 AM, Philip M. Hofer
(Frumph) <<A href="mailto:philip@frumph.net"
target=_blank>philip@frumph.net</A>> wrote:</P>
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: #cccccc 1pt solid; PADDING-BOTTOM: 0cm; MARGIN: 5pt 0cm 5pt 4.8pt; PADDING-LEFT: 6pt; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">Excuse me, Mr.
Bennett. As part of the ‘community’; there have been
discussions for and against, yet YOU working OUT of the team made
the determination as a requirement. You completely
ignored the make WordPress themes conversation when it was first
discussed and decided ON YOUR OWN. In an email
with other’s they were still under the impression that it was
‘recommended’ still up until several weeks ago when it came back
into topic of conversation.</SPAN></P></DIV></DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV></DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">While it would be
beneficial for you to believe you are in a team, your actions have
stated otherwise. From the very beginning to
now.</SPAN></P></DIV></DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV></DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<P style="BACKGROUND: whitesmoke" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> <A
title=chip@chipbennett.net href="mailto:chip@chipbennett.net"
target=_blank>Chip Bennett</A> </SPAN></P></DIV>
<DIV>
<P style="BACKGROUND: whitesmoke" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Sent:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Monday,
July 15, 2013 8:27 AM</SPAN></P></DIV>
<DIV>
<DIV>
<DIV>
<P style="BACKGROUND: whitesmoke" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">To:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>Discussion list for WordPress theme reviewers.</A>
</SPAN></P></DIV>
<DIV>
<P style="BACKGROUND: whitesmoke" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Subject:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Re:
[theme-reviewers] Webmaster Tools IDs - plugin
territory?</SPAN></P></DIV></DIV></DIV></DIV></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV></DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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. </SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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).</SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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).
</SPAN></P></DIV></DIV>
<DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">On Mon, Jul 15, 2013 at
11:18 AM, Philip M. Hofer (Frumph) <<A
href="mailto:philip@frumph.net"
target=_blank>philip@frumph.net</A>> wrote:</SPAN></P>
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: #cccccc 1pt solid; PADDING-BOTTOM: 0cm; MARGIN: 5pt 0cm 5pt 4.8pt; PADDING-LEFT: 6pt; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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.</SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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.</SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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</SPAN></STRONG>.</SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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.</SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"></SPAN> </P></DIV>
<DIV>
<DIV>
<P style="BACKGROUND: whitesmoke" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> <A
title=chip@chipbennett.net href="mailto:chip@chipbennett.net"
target=_blank>Chip Bennett</A> </SPAN></P></DIV>
<DIV>
<P style="BACKGROUND: whitesmoke" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Sent:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
Monday, July 15, 2013 5:12 AM</SPAN></P></DIV>
<DIV>
<DIV>
<P style="BACKGROUND: whitesmoke" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">To:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>Discussion list for WordPress theme reviewers.</A>
</SPAN></P></DIV>
<DIV>
<P style="BACKGROUND: whitesmoke" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Subject:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Re:
[theme-reviewers] Webmaster Tools IDs - plugin
territory?</SPAN></P></DIV></DIV></DIV></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV></DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P>
<DIV>
<DIV>
<DIV>
<DIV>
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: #cccccc 1pt solid; PADDING-BOTTOM: 0cm; MARGIN: 5pt 0cm 5pt 4.8pt; PADDING-LEFT: 6pt; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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.</SPAN></P></DIV></DIV></DIV></DIV></BLOCKQUOTE>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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.</SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">The single most
important party in this consideration is not the Theme developer,
or the Theme reviewers, but rather the Theme's end users.
</SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: #cccccc 1pt solid; PADDING-BOTTOM: 0cm; MARGIN: 5pt 0cm 5pt 4.8pt; PADDING-LEFT: 6pt; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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.</SPAN></P></DIV></DIV></DIV></DIV></BLOCKQUOTE>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">The core team has made
it the Theme Review Team's responsibility. </SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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. </SPAN></P></DIV>
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: #cccccc 1pt solid; PADDING-BOTTOM: 0cm; MARGIN: 5pt 0cm 5pt 4.8pt; PADDING-LEFT: 6pt; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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.
</SPAN></P></DIV></DIV></DIV></DIV></BLOCKQUOTE>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">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.</SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">The single most
important party in this consideration is not the Theme developer,
or the Theme reviewers, but rather the Theme's end
users.</SPAN></P></DIV></DIV></DIV></DIV></DIV></DIV>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">
<HR align=center SIZE=2 width="100%">
</SPAN></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">_______________________________________________<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></SPAN></P></DIV></DIV></DIV></DIV></DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><BR>_______________________________________________<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></SPAN></P></BLOCKQUOTE></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P></DIV></DIV>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">
<HR align=center SIZE=2 width="100%">
</SPAN></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'">_______________________________________________<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></SPAN></P></DIV></DIV></DIV></DIV></DIV></DIV>
<P style="MARGIN-BOTTOM: 12pt"
class=MsoNormal><BR>_______________________________________________<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></P></BLOCKQUOTE></DIV>
<P class=MsoNormal> </P></DIV></DIV></DIV></DIV></DIV>
<P style="MARGIN-BOTTOM: 12pt"
class=MsoNormal><BR>_______________________________________________<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></P></BLOCKQUOTE></DIV>
<P
class=MsoNormal> </P></DIV></DIV></DIV></DIV></DIV><BR>_______________________________________________<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><BR></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV><BR>
<FIELDSET></FIELDSET> <BR><PRE>_______________________________________________
theme-reviewers mailing list
<A href="mailto:theme-reviewers@lists.wordpress.org" target=_blank>theme-reviewers@lists.wordpress.org</A>
<A href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A>
</PRE></BLOCKQUOTE><BR></DIV></DIV></DIV><BR>_______________________________________________<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><BR></BLOCKQUOTE></DIV>
<DIV> </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>
<DIV class=gmail_extra> </DIV>
<P>
<HR>
_______________________________________________<BR>theme-reviewers mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></DIV></DIV></DIV></BODY></HTML>