Bah ... I think I need another coffee ... some very good points and questions, Chip. Which again asks the question why would "Automattic" think this is necessary for the Theme?<br><br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Sat, Oct 15, 2011 at 12:10 PM, 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;">
Plugins that bundle binary blobs are required to include the human-editable version of the file as well. I don't see why Themes would be any different.<div><br></div><div>The lack of a license is not merely a red-flag, but a show-stopper. Just as we require explicit license declaration for font files, so would we also require explicit license declaration for other binaries, such as SWF files. (Personally, I think we're a bit lax on this point WRT bundled image/icon files, too.)</div>
<div><br></div><div>Note that the Guidelines *do* discuss licensing, at length - but, I can certainly clarify on this point if necessary.</div><div><br></div><div>But, all that said, my underlying question is: why does a Theme need to bundle a flash audio player to begin with? Would a flash audio player be rightly considered as Plugin Territory?</div>
<div><br></div><div><font color="#888888">Chip</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Sat, Oct 15, 2011 at 10:58 AM, Michael Fields <span dir="ltr"><<a href="mailto:michael@mfields.org" target="_blank">michael@mfields.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Kirk,<br>
<div><br>
> Just a SWF, no FLA.<br>
<br>
</div>This sounds like a red flag to me.<br>
<br>
It cannot be open source without the source file :)<br>
<br>
IMHO the presence of the FLA should be required in a GPL compatible theme.<br>
<div><br>
> There is no reference to any restrictions, nor a license.<br>
<br>
<br>
</div>This sounds red flag-ish as well. But maybe not ...<br>
<br>
If no explicit license is present, I believe that the component (SWF) should inherit the license of the package as declared in style.css or license.txt in the theme folder.<br>
<br>
I have only limited experience with flash but, from what I remember seeing, license information in flash components is sometimes included directly in the source (FLA) file.<br>
<br>
Without being able to see the source, it is impossible to know whether the component's licensing conflicts with the GPLv2.<br>
<br>
These are just my opinions on the matter. I'm no expert when it comes to licensing, but I do my best to approach situations with common sense. logic and a love for open source. This is a very good topic for discussion and maybe something that should be added to the theme guidelines once a consensus is reached.<br>
<div><div></div><div><br>
Best,<br>
- Mike<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>
</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>