Currently the requirement we look for is GPL-compatible as far as themes go; and, the basis of this topic, as I read it is how do we recommend a theme be clearly documented as GPL-compatible for inclusion into the Extend Themes repository?<br>
<br>I like the idea of using "header tags" in the style.css title block as it would be a minimal load to add a couple of lines to that particular mandatory file. While a full copy of the relevant license text is nice to include, appropriate link(s) and verbiage would suffice as I see it.<br>
<br>Personally I have taken to adding "header tags" to all of my themes as a proactive/preemptive measure, if this is an acceptable method of indicating a theme's GPL compliance then I would suggest this as a possible requirement to fall in line with the release of WordPress version 3.1<br>
<br><br>Cais.<br><br><div class="gmail_quote">On Tue, Oct 12, 2010 at 10:01 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Greetings, all,<div><br></div><div>I've been thinking: in light of Hakre's recent escalation of the, erm, license discrepancies with WordPress core*, I'm wondering if we shouldn't look at making the License/LicenseURI header tags *required* for Themes at some point in the near future? As we've seen with WordPress, merely bundling a full-text license really isn't sufficient, and can lead to assumptions/misunderstandings/problems later.</div>
<div><br></div><div>What do you think?**</div><div><br></div><div>Chip</div><div><br></div><div>* Is WordPress "GPL", "GPLv2", "GPLv2 (or later)", "GPLv2 (may NOT assume any later versions)"? As it turns out, based on the actual copyright notice (and that of its predecessor, B2), WordPress is merely "GPL".</div>
<div><br></div><div>** Personally, I just like the standardization of using header tags. But merely liking the standardization, IMHO, isn't sufficient reason to require header-tag use. The license confusion issue, though, might be.</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>