Given Otto's two comments I am seriously thinking we should be, starting with 3.3, RECOMMENDING all Theme assets (CSS, images, code, etc.) be included with the Theme package/archive; then moving to REQUIRED with 3.4 ... although the only real go-forward issue I see at the moment is the inclusion of Google-fonts (low-risk but still contravening this idea) this can be addressed as well (per Otto).<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Tue, Nov 15, 2011 at 6:16 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><div class="gmail_quote">On Tue, Nov 15, 2011 at 4:44 PM, Daniel Fenn <span dir="ltr"><<a href="mailto:danielx386@gmail.com" target="_blank">danielx386@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
While we are on this subject, what about themes like mine where it<br>
make reference to style.Php on someone's phpbb forum? That<br>
configuration is controlled in wp-admin.<br>
<div><div></div></div></blockquote></div><br><div><br></div></div><div>If it's optional or something the user has to specifically configure, then it's clearly okay. The user should be presumed to know what they are doing and the ramifications thereof. This may not be the case, but any other assumption leads to Cthulu-level madness.</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div>-Otto</div><div><br></div>
</font></span><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>