<div dir="ltr">Authors that offer this as an optional feature via Theme Options<div>should not be allowed to include them with their Themes! Why?</div><div><br></div><div>I really don't see the reason to ban this from Themes. Recommend,</div>
<div>sure, let's do that, but to say no, you cannot, is just wrong :)</div><div><br></div><div>Excluding this from Themes (<i>in case that author does not fork</i></div><div><i>into a plugin</i>) will "break" the Theme and that user experience we</div>
<div>talked about will be a terrible one. Not to mention the author.</div><div><br></div><div>So in this case it's fine to do that because that's the guideline</div><div>but it is not if the same user decides to switch the Theme and</div>
<div>loses their features. Sorry I don't buy that.</div><div><br></div><div><i>Cease and desist :(</i><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Jul 15, 2013 at 11:33 PM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
I've stayed out this discussion because I thought it'd be over with
by now. This particular case seems to be clear-cut plugin
territory. I can't think of a good reason for Analytics codes,
Webmaster IDs, and stuff like that to be in a theme. It doesn't
make sense from a developer or user perspective.<br>
<br>
Would I reject a theme for one of these things? Probably not if
that was the only issue, but I'd ask for it to be removed in the
next version.<br>
<br>
There are other borderline plugin/theme things that would've made
for a better discussion.<div><div class="h5"><br>
<br>
On 7/15/2013 4:10 PM, Emil Uzelac wrote:<br>
<blockquote type="cite">
<div dir="ltr">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?
<div><br>
</div>
<div>
<i>Plugin Territory Guidelines are required for new Themes,
and recommended for existing Themes.</i><br>
</div>
<div><br>
</div>
<div>If there are no security issues, conflict with the core
etc.</div>
<div><br>
</div>
<div>Am I asking too much, what do you think?</div>
<div><br>
</div>
<div>P.S. Also only few of us are discussing this, are the rest
not interested, affected, what's up?</div>
<div><br>
</div>
<div>Emil </div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Jul 15, 2013 at 10:36 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>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal">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.</div>
</div>
<div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal"> </div>
</div>
<div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal">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.</div>
</div>
<div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal"> </div>
</div>
<div>
<div style="FONT:10pt tahoma">
<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 8:27 AM</div>
<div>
<div>
<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>
<div>
<div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal">
<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> </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> </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 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>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-STYLE:normal;DISPLAY:inline;FONT-FAMILY:'Calibri';FONT-SIZE:small;FONT-WEIGHT:normal;TEXT-DECORATION:none">
<div style="FONT:10pt tahoma">
<div> </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>
<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-STYLE:normal;DISPLAY:inline;FONT-FAMILY:'Calibri';FONT-SIZE:small;FONT-WEIGHT:normal;TEXT-DECORATION:none">
<div dir="ltr"><span style="FONT-FAMILY:calibri;FONT-SIZE:12pt"></span><br>
<div>
<div>
<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>
<hr>
<div>_______________________________________________<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>
</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>
<p>
</p>
<hr>
_______________________________________________<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>
</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">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>