<div dir="ltr">Thanks Chip. I've filed this: <a href="https://core.trac.wordpress.org/ticket/27104">https://core.trac.wordpress.org/ticket/27104</a>.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 11, 2014 at 1:17 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">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"><div dir="ltr"><div><div><div><div><div><div><div>The key is to *maintain* proper attribution, which requires the original work to *provide* proper attribution (something I've bugged the Automattic and core dev folks about quite a bit *grin*).<br>
<br></div>1) If a Theme is a derivative of another Theme, whether Underscores, or Twenty {X}, or anything else, per the license of that work, retention of the original-work copyright is *required*. That's just basic copyright stuff.<br>
<br></div>2) Bare minimum:<br><br></div>XYZ WordPress Theme, copyright 2014 Mr. Awesome<br></div>XYZ is distributed under the terms of the GNU GPL<br><br></div>XYZ is derived from _S (Underscores) WordPress Theme, copyright 2013, Automattic, Inc.<br>
</div>Underscores is distributed under the terms of the GNU GPL.<br><br></div>3) Yes, it would. "Ported over" is dead-giveaway terminology that code derivation has taken place. Feel free to help me bug the Automattic and core dev folks about proper copyright attribution. :)<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Tue, Feb 11, 2014 at 2:06 PM, Philip Arthur Moore <span dir="ltr"><<a href="mailto:philip@pressbuild.com" target="_blank">philip@pressbuild.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>Chip,<br><br>Can you give me some insight into this?<br><br></div>
Thanks.<br><div class="gmail_extra">
<br><br><div class="gmail_quote"><div>On Sat, Feb 8, 2014 at 3:47 PM, Philip Arthur Moore <span dir="ltr"><<a href="mailto:philip@pressbuild.com" target="_blank">philip@pressbuild.com</a>></span> wrote:<br>
</div><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I've been mulling over a <a href="https://github.com/Automattic/_s/commit/5c3689cd67511c27ce58051805819ec5ce019863#diff-da232d78aa810382f2dcdceae308ff8e" target="_blank">commit</a> I made to _s close to a year ago that included proper copyright and license attribution in style.css.<br>
<br>If I recall correctly—I'm getting old so memory is fading!—a big reason for this change was to <a href="https://github.com/Automattic/_s/issues/10" target="_blank">make it easier</a> for the Theme Review Team to enforce proper copyright/license attribution for derivative works in Extend; I believe it was also done so that _s stayed in line with GNU-recommended copyright/license attribution.<br>
<br>I have some questions, though:<br><ol><li>If a theme is built off of _s and submitted to Extend does the Theme Review Team require a notice to be put on its stylesheet that it's a derivative work of _s? If so, how would this look? (i.e. "Child Theme, Copyright 2014 Company Name, distributed under the terms of the GNU General Public License v2 or later, based on Underscores (Copyright 2012-2014 Automattic, Inc.))</li>
<li>Along the lines of the first question, what are the bare minimum requirements for style.css license declarations for Extend with regard to derivative works and/or child themes?</li><li>I just read <a href="http://konstantin.obenland.it/2013/12/19/twenty-fifteen/" target="_blank">Obenland's post on Twenty Fifteen</a> again (he's awesome) and he wrote that Twenty Ten was ported over from Kirby, Twenty Eleven was ported over from Duster, and Twenty Fourteen was ported over from Further, which was developed using _s and an Automattic premium theme before being released to Core for inclusion. Wouldn't this require that Twenty Fourteen have a notice in it that it's based on _s and mention the Automattic copyright?</li>
</ol>Can one of you fine folks shed some light on this for me?<br><br></div>Thank you.<br></div>
</blockquote></div></div></div><br></div></div>
<br></div></div><div class="">_______________________________________________<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>
<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>