<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><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><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><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>
<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><br></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><br><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 class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<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 class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<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 class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-IN">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi
Emil,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040"> </span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#404040">Regards,</span></p>
<p class="MsoNormal" style="line-height:150%">
<span style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#404040">Harish
Chouhan</span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:10.0pt;line-height:150%;font-family:"Arial","sans-serif";color:#404040"> </span></p>
<p class="MsoNormal" style="line-height:150%"><b><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#0d0d0d">Visit
me at </span></b><span style="font-size:16.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#0d0d0d">-
</span><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1f497d"><a href="http://www.harishchouhan.com/" target="_blank"><span style="font-size:10.0pt;line-height:150%;color:black">www.harishchouhan.com</span></a></span><span style="font-size:10.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#0d0d0d">
</span><span style="font-size:16.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#0d0d0d"><br>
<br>
</span><b><span style="font-size:10.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#0d0d0d"></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
</div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" 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 class="MsoNormal" style="margin-left:13.5pt;line-height:13.65pt">
<span style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">Removing
or modifying non-presentational core hooks</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif""></span></p>
<p class="MsoNormal" style="margin-left:13.5pt;line-height:13.65pt"><span style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">Disabling
the admin toolbar</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif""></span></p>
<p class="MsoNormal" style="margin-left:13.5pt;line-height:13.65pt"><span style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">Resource
compression/caching</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif""></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 class="MsoNormal" style="margin-left:13.5pt;line-height:13.65pt">
<span style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">Analytics
scripts</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif""></span></p>
<p class="MsoNormal" style="margin-left:13.5pt;line-height:13.65pt"><span style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">SEO
options (meta tags, page title, post
titles, robots.txt, etc.)</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif""></span></p>
<p class="MsoNormal" style="margin-left:13.5pt;line-height:13.65pt"><span style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">Content
Sharing buttons/links</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif""></span></p>
<p class="MsoNormal" style="margin-left:13.5pt;line-height:13.65pt"><span style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">Custom
post-content shortcodes</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif""></span></p>
<p class="MsoNormal" style="margin-left:13.5pt;line-height:13.65pt"><span style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">Custom
Post Types</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif""></span></p>
<p class="MsoNormal" style="margin-left:13.5pt;line-height:13.65pt"><span style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">Custom
Taxonomies</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif""></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 class="MsoNormal" style="margin-bottom:12.0pt"> </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:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040"> </span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#404040">Regards,</span></p>
<p class="MsoNormal" style="line-height:150%">
<span style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#404040">Harish
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" 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 class="MsoNormal" style="margin-bottom:12.0pt"> </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:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<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 class="MsoNormal" style="background:whitesmoke">
<b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:chip@chipbennett.net" title="chip@chipbennett.net" target="_blank">Chip
Bennett</a> </span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Sent:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
Monday, July
15, 2013 8:27
AM</span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">To:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:theme-reviewers@lists.wordpress.org" title="theme-reviewers@lists.wordpress.org" target="_blank">Discussion list for WordPress theme reviewers.</a> </span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Subject:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
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 class="MsoNormal" style="margin-bottom:12.0pt"><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:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<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-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:chip@chipbennett.net" title="chip@chipbennett.net" target="_blank">Chip
Bennett</a> </span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Sent:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
Monday, July
15, 2013 5:12
AM</span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">To:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:theme-reviewers@lists.wordpress.org" title="theme-reviewers@lists.wordpress.org" target="_blank">Discussion list for WordPress theme reviewers.</a> </span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Subject:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
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:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<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:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<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:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<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 class="MsoNormal" style="text-align:center" 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 class="MsoNormal" style="margin-bottom:12.0pt">
<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 class="MsoNormal" style="text-align:center" 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 class="MsoNormal" style="margin-bottom:12.0pt"><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 class="MsoNormal" style="margin-bottom:12.0pt"><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>
<br>
</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><br></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>