<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>We had this conversation before, yearish+ ago.</DIV>
<DIV> </DIV>
<DIV>The end result was that if the coding as you say “locked out” (as someone
cordially put) the ability for other plugins to be used of the same type that it
would be considered plugin territory and ‘recommended’ they remove it as long as
it wasn’t a ‘design’ based situation. Not a requirement.</DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"><FONT
size=3 face=Calibri></FONT></DIV></DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV style="FONT: 10pt tahoma">
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=contact@themezee.com
href="mailto:contact@themezee.com">Thomas from ThemeZee</A> </DIV>
<DIV><B>Sent:</B> Wednesday, June 12, 2013 7:00 AM</DIV>
<DIV><B>To:</B> <A title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV><B>Subject:</B> Re: [theme-reviewers] Questions on my first
review</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>
<DIV>
<DIV>Ah of course shortcodes and CPTs should always be forbidden because they
cause really high lock-in effects, but there are also lock-in effects (although
they're smaller) of Google Analytics and SEO options. <BR><BR></DIV>My email
should not induce that these things should be allowed, I just want a clear
guideline :)<BR><BR></DIV>Best Regards,<BR>Thomas<BR></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>2013/6/12 Thomas from ThemeZee <SPAN dir=ltr><<A
href="mailto:contact@themezee.com"
target=_blank>contact@themezee.com</A>></SPAN><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>Allowing {plugin-territory-stuff} now (even if it's disabled by default)
would have the effect that theme developers are allowed to also include
shortcodes and custom post types in their themes. <BR><BR></DIV>After all in
my opinion shortcodes and CPTs are more presentational than sharing buttons,
google analytics and SEO. I had planned to include a simple image slideshow
based on CPTs a few month ago and was turned down.<BR><BR></DIV>And it was a
good thing. It took me some time but now I truly believe that themes should
not include any plugin territory features. Therefore I would suggest to
continue the {plugin-territory-stuff} is strictly forbidden
policy..<BR><BR></DIV>The only thing that really bugs me is that there is no
guideline and no consistent rules. The result is that their are hundred of
themes which have a lot of plugin stuff in their themes and other themes are
rejected for the exact same features. <BR><BR></DIV>
<DIV>I can live with both {plugin-territory-stuff} is allowed or not, but it
should be stated clearly in the guidelines and applied by all theme
reviewers.<BR></DIV>
<DIV> </DIV>Just my 2 cents<SPAN class=HOEnZb><FONT
color=#888888><BR></FONT></SPAN></DIV><SPAN class=HOEnZb><FONT
color=#888888>Thomas<BR></FONT></SPAN></DIV>
<DIV class=HOEnZb>
<DIV class=h5>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>2013/6/12 Peter Kakoma <SPAN dir=ltr><<A
href="mailto:kakomap@gmail.com"
target=_blank>kakomap@gmail.com</A>></SPAN><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>
<DIV>The issue is that there is no definitive guideline about
{plugin-territory-stuff}. I believe the end-goal of this discussion is to
draft one and share it with the rest of the world (otherwise we'll be
discussing this again two months from now when a first-time reviewer asks
the same question)<BR><BR></DIV>And in as much as my theme is guilty of
adding Analytics, I agree with you-the line should be drawn at
non-presentational stuff (*cough* SEO, *cough*). Removing Analytics now,
updating the theme.<BR></DIV>
<DIV class=gmail_extra>
<DIV>
<DIV><BR><BR>
<DIV class=gmail_quote>On Wed, Jun 12, 2013 at 4:06 PM, Chip Bennett <SPAN
dir=ltr><<A href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.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>I don't agree that the Favicon guidelines are appropriate for
extending to all {plugin territory} functionality.
<DIV>
<DIV> </DIV>
<DIV>Things that are marginally presentational (e.g. sharing links)? Using
the Favicon guidelines as a model is reasonable. But Google Analytics: no
reason to facilitate Themes adding this functionality. It's not in any way
whatsoever presentational. As far as I'm concerned, that's an absolute
line of demarcation. If it's not in any way presentational, it doesn't
belong in a Theme, opt-in/disabled-by-default or
otherwise.</DIV></DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>
<DIV>
<DIV>On Wed, Jun 12, 2013 at 8:37 AM, Edward Caissie <SPAN dir=ltr><<A
href="mailto:edward.caissie@gmail.com"
target=_blank>edward.caissie@gmail.com</A>></SPAN>
wrote:<BR></DIV></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<DIV>
<DIV dir=ltr>
<DIV>
<DIV class=gmail_extra>
<DIV> </DIV>
<DIV class=gmail_quote>On Wed, Jun 12, 2013 at 2:46 AM, Peter Kakoma
<SPAN dir=ltr><<A href="mailto:kakomap@gmail.com"
target=_blank>kakomap@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<LI>Themes are recommended not to implement custom
{plugin-territory-stuff} functionality. <BR>
<LI>If implemented, {plugin-territory-stuff} functionality is required
to be opt-in, and disabled by default. <BR>
<LI>If implemented, {plugin-territory-stuff} functionality is required
to support user-defined {plugin-territory-stuff}
images</LI></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV></DIV>
<DIV class=gmail_extra>Those points are fairly well sorted except for
the third which is really more relevant to the original ideas behind the
use of favicons, but if you use the first two points as your benchmark
then you should be (for the most part but not 100% guaranteed) fine with
going forward.<SPAN><FONT
color=#888888><BR><BR></FONT></SPAN></DIV><SPAN><FONT color=#888888>
<DIV class=gmail_extra>
<DIV> </DIV>
<DIV>Edward Caissie<BR>aka Cais.</DIV></DIV></FONT></SPAN></DIV>
<DIV> </DIV></DIV></DIV>
<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><BR></DIV></BLOCKQUOTE></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><BR
clear=all><BR></DIV></DIV><SPAN><FONT color=#888888>-- <BR><A
href="http://www.urbanlegendkampala.com"
target=_blank>www.urbanlegendkampala.com</A><BR></FONT></SPAN></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></BLOCKQUOTE></DIV>
<DIV> </DIV></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>