<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>Excuse me, meant that as “That is quite not right and should be relooked
at.”</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 style="FONT: 10pt tahoma">
<DIV> </DIV>
<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> Wednesday, June 12, 2013 8:50 AM</DIV>
<DIV><B>To:</B> <A title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">[theme-reviewers]</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>What is meant by "custom post-content shortcodes" is hashed out in
the linked post on Make/Themes, and IIRC, a separate Make/Themes
post/discussion. The term refers to Theme-defined shortcodes that are intended
to be used in the Post Content.</DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Wed, Jun 12, 2013 at 11:20 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>Define “<FONT face="Times New Roman">custom post-content
shortcodes” sure, it does not mean ‘all shortcodes”</FONT></DIV>
<DIV><FONT face="Times New Roman"></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT face="Times New Roman"></FONT> </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><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> Wednesday, June 12, 2013 8:02 AM</DIV>
<DIV><B>To:</B> <A title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>[theme-reviewers]</A> </DIV>
<DIV>
<DIV class=h5>
<DIV><B>Subject:</B> Re: [theme-reviewers] Questions on my first
review</DIV></DIV></DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV>
<DIV class=h5>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV dir=ltr><A style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px"
href="http://make.wordpress.org/themes/2012/11/26/wordpress-3-5-guidelines-revisions/"
target=_blank>http://make.wordpress.org/themes/2012/11/26/wordpress-3-5-guidelines-revisions/</A><BR></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Wed, Jun 12, 2013 at 10:56 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>@Thomas where are you getting the information that shortcodes are not
allowed?</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=contact@themezee.com
href="mailto:contact@themezee.com" target=_blank>Thomas from ThemeZee</A>
</DIV>
<DIV><B>Sent:</B> Wednesday, June 12, 2013 7:39 AM</DIV>
<DIV><B>To:</B> <A title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A> </DIV>
<DIV>
<DIV><B>Subject:</B> Re: [theme-reviewers] Questions on my first
review</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>
<DIV>
<DIV dir=ltr>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>Sorry Chip, I don't saw your last email until now. Stupid Gmail
Import..<BR><BR></DIV>I know the Presentation vs Functionality Guideline,
but this guideline is really unclear worded for me. I only understand it
know because I have followed the mailing list here for some time. Since then
I know most things I can include in my themes and what not. I'm no native
speaker so maybe it's just that ;)<BR><BR></DIV>I agree that the guideline
can not list every possible issue, but a few examples below the guidelines
would be nice. <BR><BR></DIV>
<DIV></DIV>
<DIV>Post Content Shortcodes are not allowed. <BR></DIV>Custom Post Types
not allowed (except for special use cases?)<BR></DIV>Functionality which is
not presentational like Tracking Codes, SEO Options ...<BR><BR></DIV>As you
have said every human interprets the guidelines differently. Therefore they
should be as clear as possible to make the theme reviews as consistent as
possible. <BR><BR></DIV>That is just my opinion, I don't want to offend
anyone ;)<BR></DIV></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>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>
<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><FONT
color=#888888><BR></FONT></SPAN></DIV><SPAN><FONT
color=#888888>Thomas<BR></FONT></SPAN></DIV>
<DIV>
<DIV>
<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></DIV></DIV></BLOCKQUOTE></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>
<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">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>
<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>