I love the simplicity of having all additional license declarations being in readme.txt, in one place (REQUIRED), and RECOMMENDing proper docblocks as Chip just outlined.<div><br><div class="gmail_quote">On 15 October 2011 12:57, 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 overall Theme copyright/license is covered by style.css License: and License URI: header tags, but other bundled resources need to be listed eplicitly. I would recommend that license declaration be required to be in at least one of the following files:<div>
<br><div>1) index.php phpDoc header docblock</div><div>2) style.css header docblock</div><div>3) readme.txt</div><div><br></div><div>Best practice would be:</div><div><br></div><div>1) ALL php files have phpDoc header docblocks, that include @copyright and @license. Derivative works should declare the copyright and license of the original work, as well</div>
<div>2) ALL php file header docblocks include @package: theme-slug</div><div>3) All php function declarations should have phpDoc docblocks, and if the function is copy-pasta, it should include @copyright and @license from the original source, as well as an @link TO the original source, wherever possible</div>
<div><br></div><div>I've tried to implement these best-practices in Oenology, so if anyone has any suggestions for improvement, please let me know, so I can update Oenology's inline docs.</div><div><br></div><font color="#888888"><div>
Chip</div></font><div><div></div><div class="h5"><div><br><div class="gmail_quote">On Sat, Oct 15, 2011 at 11:39 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Which goes back to my recommended documentation. Do we want to have the "explicit license declaration" somewhere more obvious, such as the theme description? or inline at the first instance of the "SWF" reference?<br>
<br><br clear="all">Cais.<div><div></div><div><br>
<br><br><div class="gmail_quote">On Sat, Oct 15, 2011 at 12:37 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">
Is a link to the human-editable file format acceptable for repository-hosted Plugins? If so, that should be fine for Themes as well.<div><br></div><div>But explicit license declaration is a must.</div><div><br></div><div>
<font color="#888888">Chip</font><div><div></div><div><br>
<br><div class="gmail_quote">On Sat, Oct 15, 2011 at 11:31 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Considering that the theme author likely just used some other<br>
open-source package, then I'd say that it's fine as long as they<br>
properly link back to the source of the included code, and have links<br>
to any licenses that thereby are required. Said licenses must be<br>
GPL-compatible, obviously.<br>
<br>
Personally, I'm not so strict as to require that they include the FLA<br>
source, especially in a theme where the end-user likely doesn't care<br>
and doesn't need it anyway. However, an HTTP link back to that source,<br>
or to the project it originated from, should be there somewhere.<br>
<font color="#888888"><br>
-Otto<br>
</font><div><div></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" 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></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>