Hmm ... how far are we going to get into this image copyright issue?<br><br>If an author uses several images in, for example, a collage will they be required to provide the "source" (as in the individual images) or the license for each image, or simply state it is their creation ... which as far as I see it (and understand it) would not be necessary as the theme license would cover this "new" image.<br>
<br>Which then pushes us to revisit the header License tag, as stating only one license there may not be entirely correct either, especially if there are multiple licenses being used for various items in the theme.<br><br>
Ideally all theme authors would be above board and provide the "necessary" attribution for any works they are including with their theme but are we really qualified to decide what is and what is not acceptable in how the licensing is being stated? Where it is to be stated? and what language should be used? Are we going to continue down the rabbit hole and also state where the legal jurisdiction of any related legal matters is, as well? (Extremism, I know, but let's start looking down the road before we get to far along it and find ourselves with no where to turn.)<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Fri, Feb 10, 2012 at 9:26 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The binary *is* the editable source, isn't it?<span class="HOEnZb"><font color="#888888"><div><br></div></font></span><div><span class="HOEnZb"><font color="#888888">Chip</font></span><div><div class="h5"><br><br><div class="gmail_quote">
On Fri, Feb 10, 2012 at 8:17 AM, Doug Stewart <span dir="ltr"><<a href="mailto:zamoose@gmail.com" target="_blank">zamoose@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Here's my question:<br>
How does a developer provide the "source" in order to comply with GPL<br>
licensing constraints?<br>
<div><div><br>
On Fri, Feb 10, 2012 at 9:15 AM, Kirk Wight <<a href="mailto:kwight@kwight.ca" target="_blank">kwight@kwight.ca</a>> wrote:<br>
> How do we feel about adding the following to the Guidelines, as another<br>
> bullet under Licensing :<br>
><br>
> "If the theme includes any binary files (such as images, fonts, or icons),<br>
> themes are required to explicitly declare all GPL-compatible licenses for<br>
> these files (this can be done in readme.txt)."<br>
><br>
><br>
><br>
> On 9 February 2012 19:44, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
>><br>
>> The main question is: who holds the *copyright* on the binaries in<br>
>> question, and is the *copyright holder's license* explicit?<br>
>><br>
>> if the Theme dev has created all of the binaries (images, etc.) in the<br>
>> Theme, then the style.css license declaration is sufficient. If, on the<br>
>> other hand, the Theme is bundling binaries for which the developer *isn't*<br>
>> the copyright holder, then the original copyright and license need to be<br>
>> included explicitly.<br>
>><br>
>> Chip<br>
>><br>
>><br>
>> On Thu, Feb 9, 2012 at 6:35 PM, Emil Uzelac <<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>> wrote:<br>
>>><br>
>>> If the media in general is GPL I don't think that they need to<br>
>>> be separated from the i.e. license.txt. Everything can be combined into one<br>
>>> license, either license.txt or link to browser-based license. If the licence<br>
>>> is GPL-Compatible, small note in readme.txt should be more than enough.<br>
>>><br>
>>> Emil<br>
>>><br>
>>> On Thu, Feb 9, 2012 at 6:20 PM, Kirk Wight <<a href="mailto:kwight@kwight.ca" target="_blank">kwight@kwight.ca</a>> wrote:<br>
>>>><br>
>>>> Speaking of: <a href="http://codex.wordpress.org/Theme_Review#Licensing" target="_blank">http://codex.wordpress.org/Theme_Review#Licensing</a><br>
>>>> and <a href="http://lists.wordpress.org/pipermail/theme-reviewers/2011-October/007141.html" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/2011-October/007141.html</a><br>
>>>><br>
>>>> How do you all handle licensing for binaries, such as images, fonts,<br>
>>>> etc? I've been quite a hard-ass with it lately in my reviews because of the<br>
>>>> above two references, but I'm noticing that it's difficult to even point<br>
>>>> people to an approved theme in the repo where it's done well. And if it's<br>
>>>> only a few images/graphics, are people being more lenient?<br>
>>>><br>
>>>> One could argue that if the explicit license isn't there for binaries,<br>
>>>> then it falls under the general statement in style.css - but that makes me<br>
>>>> feel funny.<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>
>>><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>
>><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>
><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>
<br>
<br>
<br>
</div></div><span><font color="#888888">--<br>
-Doug<br>
</font></span><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>
</div></div></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>