<div dir="ltr"><div>I see having Commercial Theme houses being required to have at least one "free" theme hosted on the dot-org repository as either a good thing or having no affect on most everyone involved.<br>
<br></div>It's good for the commercial theme houses as it adds an avenue for them to "advertise" their existence as well as their skills. This would provide the community (high) quality themes and possible insights into how a "paid" theme may be supported by these same authors aside from what end-users may be able to read from reviews, word-of-mouth, etc. ... and the WPTRT would, or at least should, see some quality code to review.<br>
<br>No matter the case, a commercial theme house submission may require a bit more time to validate against the "up-sell" guidelines but in the end it is simply another theme that needs to be reviewed and processed like any other theme submission; and should be treated in exactly the same fashion. Although the question that this brings to mind, since there is a time element to this possible guideline, is what happens to the Commercial Theme house's listing if the free theme (especially in cases where there is only one free theme in the repository from the author) is subsequently resolved to "not-approved"?<br>
</div><div class="gmail_extra"><br clear="all"><div>Edward Caissie<br>aka Cais.</div>
<br><br><div class="gmail_quote">On Sat, May 11, 2013 at 10:21 PM, Josh Pollock <span dir="ltr"><<a href="mailto:jpollock412@gmail.com" target="_blank">jpollock412@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Scott-<div><br></div><div>Thank you for asking for the team's advice.</div><div><br></div><div><div>I know this is a difficult request to make, but having been asked to customize some terribly coded "premium themes" I wish there was a coding standard included in the requirement. Given that being listed ont hat page could be seen as being "approved by WordPress" don't you think there should be some defense for consumers against bad practices?</div>
</div><div><br></div><div>Also, I think requiring these theme shops to have a free theme in the repository is a good idea, it actually partially address my first point, since that theme would have to meet the theme review standards. My concern is that this will add more themes to the review backlog, which is 4-6 weeks, and make it even harder for developers like me, who do not offer premium themes to get our themes listed in a timely manner.</div>
<div class="gmail_extra"><br><div class="gmail_quote"><div class="im">On Sat, May 11, 2013 at 9:52 PM, Bryan Hadaway <span dir="ltr"><<a href="mailto:bhadaway@gmail.com" target="_blank">bhadaway@gmail.com</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><div dir="ltr"><div><div>"<i>A requirement to use the <a href="http://wordpress.org" target="_blank">wordpress.org</a> forum would be a little bit counter-productive. On the other hand, users might expect that.</i>"<br>
<br></div></div>Not sure there's any plans to make that happen, but I agree. Would definitely not want to see it become mandatory to use .org forums under any circumstance. Should always remain optional.<br></div>
<br></div><div class="im">_______________________________________________<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><br></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><br></div>