This would be very easy to automate: grep for license.txt, or "License" and/or "License URI" in the style.css header.<div><br></div><div>I *do* read license.txt, if only to ensure that it references GPL or a compatible license.</div>
<div><br></div><div>Chip<br><div><br></div><div>Once it's in the review queue, I advocate doing a single-pass, complete review. But that's just my opinion.<br><br><div class="gmail_quote">On Wed, Aug 18, 2010 at 9:36 AM, yulian yordanov <span dir="ltr"><<a href="mailto:yul.yordanov@gmail.com">yul.yordanov@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Summarizing my experience in theme testing, I think if a theme is missing license it should not be tested further. In most cases it is just omitted but there exist an hypothesis certain themes to be submitted only for testing and reviewing. Since this is a voluntary activity it's better not speculate with it.<br>
And in this way of thoughts it will be useful if the process of license checking is (somehow) automatized during upload.<br>
<br>
<br>
Yulian <Fingli><br>
<br>
<br>
P.S. Do you read the license.txt attached to themes you test? ;)<br>
<br>
-- <br>
<br>
Þëèÿí Éîðäàíîâ<br>
<br>
Yulian Yordanov<br>
<a href="http://post-scriptum.info/" target="_blank">http://post-scriptum.info/</a><br>
<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>
</blockquote></div><br></div></div>