While we are on the required topic here, can I make a point where there may be a case where the theme author didn't include say "wp_enqueue_script( 'comment-reply' )" because of the fact that the theme author has included something that is much better: a quote comment button.<br>
<br>(Just for those who are not sure what I mean, a quote button is a button where it get the content of that post/comment and puts it in the comment box at the ned of the page and you can type under it, like what happens on forums)<br>
<br>I don't want to start a fight over this because there are some required features that I understand (such as rss and widgets) But there are others that not always required.<br> <br><div><div><br></div></div>
<br><br><div class="gmail_quote">On Tue, Jan 8, 2013 at 10:33 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">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">On Mon, Jan 7, 2013 at 1:08 PM, Merci Javier <<a href="mailto:mercijavier@gmail.com">mercijavier@gmail.com</a>> wrote:<br>
</div><div class="im">> I see where you're coming from. The same thing happened to me. I gave a 3-4<br>
> days grace period to theme author to replace a bundled non-GPL font. I would<br>
> like to add that the next theme reviewer should post a note in previous trac<br>
> ticket to inform the previous theme reviewer what's going on with the theme.<br>
><br>
> I was also thinking that I was wrong in keeping the trac ticket open then. I<br>
> should have closed the ticket as not-approved right away and reported the<br>
> theme for removal from theme extend live until the theme was resubmitted<br>
> with GPL-font. The Plugins Review Team are quite strict with the GPL<br>
> requirement where they take down any plugin with non-GPL bundled elements<br>
> within minutes/hours/a-day. What's the theme review team's stand on this?<br>
<br>
</div>On that, it's zero tolerance as far as hosting goes, just the same as<br>
with plugins.<br>
<br>
- A currently available theme using non-GPL-compatible anything will<br>
be suspended when we are alerted to it, and the theme author will be<br>
notified of the problem. They can submit a new version of the theme<br>
without the problematic component.<br>
<br>
- A theme that is not yet available via /extend/themes and is only up<br>
for review, well, you can adopt whatever policy you like there. Keep<br>
it open, work with the theme author, don't, whatever you like. Most<br>
license issues are accidental, the author either didn't know of the<br>
license requirements or just didn't think to check the license on a<br>
third-party component. No reason to be harsh about it, just inform of<br>
the issue, perhaps suggest replacements.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Otto<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br>