<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Does this need to bother “upstream” folk?<br><div apple-content-edited="true">
<p style="margin: 0.0px 0.0px 0.0px 0.0px"><br></p><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Comic Sans MS">Could it just be as easy as adding “License: GPL 2” (as a default, being the same as PmWiki’s license) to the Cookbook header template so that new authors are encouraged to add their license information on each Cookbook page?</font></p><div><br></div><div><div>If it’s under custom license, say:</div><div>License: Custom</div></div><div>And link it via anchor deeper into the page content under an optional “License" headline for any custom license info. Then it can be copied from the php to the recipe page.</div><div><br></div><div>If I open a PHP file for a recipe and find a license in it, I’m more than happy to add the license type info into the cookbook document. Anyone else could do that, too — and authors can update their own recipes &/or the <a href="http://pmwiki.org">pmwiki.org</a> Cookbook recipe page themselves. i.e. crowdsource it.</div><div><br></div><div>Bonus: intermediate users can search recipes for their license via PTVs (for “*GPL*”) and they could be shown via a custom pagelist template if desired.</div><div><br></div><div><br></div><div>I’m a little more concerned about the recipes where there’s absolutely no license information to be found. That goes for mine as well, if I forgot to add it to the recipes. My intent was GPL, but technically people aren’t allowed to alter it unless I say that.</div><div><br></div><div>Crisses</div><div><br></div></div><div><div>On Jun 25, 2014, at 1:25 PM, michael paulukonis <<a href="mailto:xraysmalevich@gmail.com">xraysmalevich@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div>This sounds like a good wiki-maintenance project!<br><br></div>However, we might want to agree on some sort of guidelines, first.<br><br></div>could you open a PITS for this?<br></div><div class="gmail_extra">
<br clear="all"><div>-Michael Paulukonis<br><a href="http://www.xradiograph.com/" target="_blank">http://www.xradiograph.com</a><br><a href="http://goog_2112721603/" target="_blank"></a><a href="http://www.xradiograph.com%5cinterference/" target="_blank">Interference Patterns (a blog)</a><br>
<a href="https://twitter.com/XraysMonaLisa" target="_blank">@XraysMonaLisa</a><br><a href="http://michaelpaulukonis.com/" target="_blank">http://michaelpaulukonis.com</a><br><a href="http://www.bestandroidresources.com/" target="_blank"></a><br>
<br>Sent from somewhere in the Cloud<br>(hearthrug, by the fender)<br></div>
<br><br><div class="gmail_quote">On Wed, Jun 25, 2014 at 10:44 AM, Criss Ittermann <span dir="ltr"><<a href="mailto:crisses@kinhost.org" target="_blank">crisses@kinhost.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Yes,<div><br></div><div>And I’m probably guilty of not putting licensing information in my own recipes.</div><div><br></div><div>But it would also be good to put licensing information on the recipe page. It’s actually important, and in this case it would help me select recipes I can and cannot use. I’ll have to chase down every recipe author and ask them to fix their licensing info. (including me)</div>
<div><br><div><div style="margin: 0px;"><font style="font:12.0px Comic Sans MS" face="Comic Sans MS" size="3">Crisses</font></div>
</div><div class="">
<br><div><div>On Jun 25, 2014, at 9:49 AM, Hans Bracker <<a href="mailto:design@softflow.co.uk" target="_blank">design@softflow.co.uk</a>> wrote:</div><br><blockquote type="cite">Hello Criss,<br><br>Wednesday, June 25, 2014, 2:28:01 PM, you wrote:<br>
<br><blockquote type="cite">Does PmWiki have a standing Cookbook licensing policy or is each cookbook<br>developer required to state their own license information for their plug-ins?<br></blockquote><br>you need to check out each individual recipe. Hopefully there is some<br>
information in the main php file. At least that's where I put it,<br>following the lead from pmwiki.php.<br><br>Hans<br><br></blockquote></div><br></div></div></div><br>_______________________________________________<br>
pmwiki-users mailing list<br>
<a href="mailto:pmwiki-users@pmichaud.com">pmwiki-users@pmichaud.com</a><br>
<a href="http://www.pmichaud.com/mailman/listinfo/pmwiki-users" target="_blank">http://www.pmichaud.com/mailman/listinfo/pmwiki-users</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></body></html>