<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>Yes, get rid of the rule that makes it a requirement to push them to
plugins and move said rule back to recommendation.</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=greg@siteorigin.com
href="mailto:greg@siteorigin.com">Greg Priday</A> </DIV>
<DIV><B>Sent:</B> Tuesday, June 25, 2013 12:32 PM</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] Grandfather Themes?</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>From a user's perspective, what do you all feel would be the best
way to update a theme that has "plugin domain" functionality?
<DIV> </DIV>
<DIV>The best strategy I've thought of is to just include a nag to install the
"advanced features" plugin. It just feels risky pushing an update that you know
will break 10s of thousands of sites - even if a site will only be broken until
a user installs the plugin.</DIV>
<DIV> </DIV>
<DIV>Has anyone thought of a better strategy?</DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Tue, Jun 25, 2013 at 8:55 PM, Edward Caissie <SPAN
dir=ltr><<A href="mailto:edward.caissie@gmail.com"
target=_blank>edward.caissie@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>
<DIV dir=ltr>
<DIV class=im>
<DIV class=gmail_extra>
<DIV> </DIV>
<DIV class=gmail_quote>On Tue, Jun 25, 2013 at 2:15 PM, 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>We all agreed that it would be case by case at that point, hence
grandfathering.</DIV>
<DIV> </DIV></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV></DIV>
<DIV class=gmail_extra>I would say, although I no longer recall our
conversation, that "grandfathering" would be for the case-by-case exceptions
(at best).<BR></DIV>
<DIV class=gmail_extra>As far as the rest of the arguments (and I did re-read
that entire linked archive) I would still lean towards *not* grandfathering
any themes for much of the same reasons Chip brought forward in his
response.<BR><BR></DIV>
<DIV class=gmail_extra>If an older theme absolutely requires code that will
not meet current guidelines the theme author is more than welcome to present
their case for an exception. If an exception is granted and subsequently
over-looked by a reviewer we will make every effort to address the issue ...
and let us remember "to err is human".<SPAN class=HOEnZb><FONT
color=#888888><BR></FONT></SPAN></DIV><SPAN class=HOEnZb><FONT color=#888888>
<DIV class=gmail_extra><BR><BR></DIV>
<DIV class=gmail_extra>
<DIV> </DIV>
<DIV>Edward Caissie<BR>aka
Cais.</DIV></DIV></FONT></SPAN></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><BR
clear=all>
<DIV> </DIV>-- <BR>I make free WordPress themes<BR><A
href="http://siteorigin.com" target=_blank>http://siteorigin.com</A> </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>