<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>I'm in agreement as well, as you guys know if its
written with the tag in front like the examples the future versions of wordpress
& wordpress.org can find those licenses for automation a bit
easier</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>- Phil</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=m@seoserpent.com href="mailto:m@seoserpent.com">Marty Martin</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, October 12, 2010 7:34
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] Theme
License Declaration</DIV>
<DIV><BR></DIV>For what it's worth, I agree. I think some soft of
license statement in the theme, even if it's just in style.css needs to be
there.
<DIV><BR></DIV>
<DIV>Marty<BR><BR>
<DIV class=gmail_quote>On Tue, Oct 12, 2010 at 10:32 AM, Chip Bennett <SPAN
dir=ltr><<A
href="mailto:chip@chipbennett.net">chip@chipbennett.net</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Perfect example, actually.
<DIV><BR></DIV>
<DIV>I would put something nearly identical in the Codex, when we bump up
the criticality to *required* for the header tags.</DIV>
<DIV><BR></DIV>
<DIV><FONT color=#888888>Chip</FONT>
<DIV>
<DIV></DIV>
<DIV class=h5><BR><BR>
<DIV class=gmail_quote>On Tue, Oct 12, 2010 at 9:27 AM, Edward Caissie <SPAN
dir=ltr><<A href="mailto:edward.caissie@gmail.com"
target=_blank>edward.caissie@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>This is what I am using (from the latest version of
Shades):<BR><BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>...<BR>License: GNU General Public License
v2<BR>License URI: <A
href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html"
target=_blank>http://www.gnu.org/licenses/old-licenses/gpl-2.0.html</A><BR>*/<BR><BR>/*
Revision date: Sept 9, 2010, v1.6 */<BR><BR>/* Copyright
2009-2010 Edward Caissie (email : <A
href="mailto:edward.caissie@gmail.com"
target=_blank>edward.caissie@gmail.com</A>)<BR><BR>
This program is free software; you can redistribute it and/or
modify<BR> it under the terms of the GNU General
Public License version 2,<BR> as published by the Free
Software Foundation.<BR><BR> You may NOT assume that
you can use any other version of the GPL.<BR><BR> This
program is distributed in the hope that it will be
useful,<BR> but WITHOUT ANY WARRANTY; without even the
implied warranty of<BR> MERCHANTABILITY or FITNESS FOR
A PARTICULAR PURPOSE. See the<BR> GNU General
Public License for more details.<BR><BR> You should
have received a copy of the GNU General Public
License<BR> along with this program; if not, write to
the Free Software<BR> Foundation, Inc., 51 Franklin
St, Fifth Floor, Boston, MA 02110-1301
USA<BR><BR> The license for this software can also
likely be found here:<BR> <A
href="http://www.gnu.org/licenses/gpl-2.0.html"
target=_blank>http://www.gnu.org/licenses/gpl-2.0.html</A><BR>*/<BR></BLOCKQUOTE>
<DIV><BR>Which was borrowed heavily from Otto's (suggested?) text for use
with plugins discussed in a completely unrelated place and topic.<BR><BR>I
am not putting this forward as *the* way to document a theme's licensing,
this is just an example of what I believe could be a potential starting
point of "boilerplate" example text that may be suitable to
use.<BR><BR><BR>Cais.<BR></DIV>
<DIV>
<DIV></DIV>
<DIV><BR>
<DIV class=gmail_quote>On Tue, Oct 12, 2010 at 10:19 AM, Chip Bennett
<SPAN dir=ltr><<A href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Right now, we require *either* a full-text license.txt
file, *or* the header tags, which does ensure that the Theme is
GPL-compat.
<DIV><BR></DIV>
<DIV>The reason that I bring it up is that I'm seeing a few Themes that
have license.txt only. The issue with *only* a license.txt file is
that a bundled file really isn't an explicit license declaration. So,
for developers for whom the differences between GPL versions (primarily,
GPLv2 vs GPLv3), it is important that the Theme explicitly state the
license.</DIV>
<DIV><BR></DIV>
<DIV>(Technically, IIRC, GPL-licensed code should have both a copyright
statement AND a license statement. And derivative works should retain
the original copyright statement along with the copyright statement for
the original content. But, that's delving far too deeply into licensing
issues than we need to deal with, IMHO.)</DIV>
<DIV><BR></DIV>
<DIV>At the moment, I'm listing as a "strongly suggested" comment to add
the header tags. I like the idea of making header tags *required*
as part of the 3.1 version-specific changes.</DIV>
<DIV><BR></DIV>
<DIV><FONT color=#888888>Chip</FONT>
<DIV>
<DIV></DIV>
<DIV><BR><BR>
<DIV class=gmail_quote>On Tue, Oct 12, 2010 at 9:13 AM, Edward Caissie
<SPAN dir=ltr><<A href="mailto:edward.caissie@gmail.com"
target=_blank>edward.caissie@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>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>
<DIV>
<DIV></DIV>
<DIV>On Tue, Oct 12, 2010 at 10:01 AM, Chip Bennett <SPAN
dir=ltr><<A href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.net</A>></SPAN>
wrote:<BR></DIV></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<DIV></DIV>
<DIV>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></DIV></DIV>_______________________________________________<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></BLOCKQUOTE></DIV><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><BR></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV><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><BR></BLOCKQUOTE></DIV><BR></DIV></DIV><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><BR></BLOCKQUOTE></DIV><BR></DIV></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>
<P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></BLOCKQUOTE></BODY></HTML>