Hrm. You could try contacting some admins. We went with OCL because the manual is OCL, and it seemed to make sense (as back then the wiki was primarily for user documentation/developer documents).<br><br>Joe<br><br><div class="gmail_quote">
On Thu, Jun 5, 2008 at 10:07 PM, Juho Vepsäläinen <<a href="mailto:bebraw@gmail.com">bebraw@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Okay. If the license cannot be changed, the wiki cookbook has to be<br>
restricted only to scripts licensed with OCL.<br>
<br>
Of course one alternative would be to set up an external site that<br>
does not have such an unfortunate restriction.<br>
<br>
Sincerely,<br>
Juho "BeBraw" Vepsäläinen<br>
<br>
2008/6/6 joe <<a href="mailto:joeedh@gmail.com">joeedh@gmail.com</a>>:<br>
> Erm not sure. I'm the one who got OCL as the wiki license in the first<br>
<div><div></div><div class="Wj3C7c">> place, I just poked some wiki admins until a consensus was reached.<br>
><br>
> Joe<br>
><br>
> On Thu, Jun 5, 2008 at 11:41 AM, Juho Vepsäläinen <<a href="mailto:bebraw@gmail.com">bebraw@gmail.com</a>> wrote:<br>
>><br>
>> Who has the authority to add such an exception? It would be a shame if<br>
>> the wiki could contain only scripts licensed under OCL.<br>
>><br>
>> Sincerely,<br>
>> Juho "BeBraw" Vepsäläinen<br>
>><br>
>> 2008/6/5 joe <<a href="mailto:joeedh@gmail.com">joeedh@gmail.com</a>>:<br>
>> > Erm. . .not sure if this is technically correct, like I said before the<br>
>> > copyright page in the wiki *does* have open content in it. And by<br>
>> > default<br>
>> > it should apply to every page in the wiki, unless someone added an<br>
>> > exception<br>
>> > for scripts.<br>
>> ><br>
>> > Joe<br>
>> ><br>
>> > On Wed, Jun 4, 2008 at 8:28 AM, Juho Vepsäläinen <<a href="mailto:bebraw@gmail.com">bebraw@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> Hi,<br>
>> >><br>
>> >> Thank you Roger. I clarified the licensing terms at<br>
>> >> <a href="http://wiki.blender.org/index.php/Resources/PyNode_Cookbook" target="_blank">http://wiki.blender.org/index.php/Resources/PyNode_Cookbook</a> .<br>
>> >> Hopefully it is fine now. Feel free to tweak it as you see necessary.<br>
>> >> :)<br>
>> >><br>
>> >> Sincerely,<br>
>> >> Juho "BeBraw" Vepsäläinen<br>
>> >><br>
>> >> 2008/6/4 Roger Wickes <<a href="mailto:rogerwickes@yahoo.com">rogerwickes@yahoo.com</a>>:<br>
>> >> > Scripts that are posted and given to the public domain in an<br>
>> >> > unrestricted<br>
>> >> > fashion, should NOT bear any copyright or other license/ownership<br>
>> >> > title,<br>
>> >> > like the color ones. They just start off with import Blender. That is<br>
>> >> > easiest. anyone can use that fragment/code any way they want.<br>
>> >> ><br>
>> >> > If the author wants credit or wants to give credit to people who<br>
>> >> > helped<br>
>> >> > them, they can say "thanks go out to Roger (PapaSmurf) and Campbell<br>
>> >> > (IdeasMan42) for this awesome script." in a comment in the header or<br>
>> >> > wherever in the code the help was given.<br>
>> >> ><br>
>> >> > If the author wishes some control over the future use of the script,<br>
>> >> > that is<br>
>> >> > when they want to say<br>
>> >> ><br>
>> >> > Copyright (c) 2008 Roger D. Wickes, PO Box 680310, Marietta, GA<br>
>> >> > 30068.<br>
>> >> > All<br>
>> >> > rights reserved worldwide. Use or modification of this script is<br>
>> >> > subject<br>
>> >> > to<br>
>> >> > its license. This script is licensed under the Creative Commons with<br>
>> >> > Attribution license, a copy of which can be found <here>. By<br>
>> >> > downloading<br>
>> >> > or<br>
>> >> > using this script, the user agrees to the full terms of the license<br>
>> >> > without<br>
>> >> > modification.<br>
>> >> ><br>
>> >> > The author must decide which license to use, and should NOT attempt<br>
>> >> > to<br>
>> >> > write<br>
>> >> > their own - it would be worthless in a court of law. Use any of the<br>
>> >> > GNU<br>
>> >> > or<br>
>> >> > CC licenses. If you own something, you may be liable for it as well,<br>
>> >> > so<br>
>> >> > be<br>
>> >> > careful when copyrighting software, and be sure to use an airtight<br>
>> >> > license.<br>
>> >> ><br>
>> >> > ----------------<br>
>> >> > Sent by Roger Wickes for intended recipient. If you are not the<br>
>> >> > intended<br>
>> >> > recipient, please delete this message and contact Mr. Wickes<br>
>> >> > immediately.<br>
>> >> ><br>
>> >> > Atlantica Investments, Inc.<br>
>> >> > PO Box 680310, Marietta, GA 30068 USA<br>
>> >> ><br>
>> >> > ----- Original Message ----<br>
>> >> > From: "<a href="mailto:bf-docboard-request@blender.org">bf-docboard-request@blender.org</a>"<br>
>> >> > <<a href="mailto:bf-docboard-request@blender.org">bf-docboard-request@blender.org</a>><br>
>> >> > To: <a href="mailto:bf-docboard@blender.org">bf-docboard@blender.org</a><br>
>> >> > Sent: Wednesday, June 4, 2008 6:00:02 AM<br>
>> >> > Subject: Bf-docboard Digest, Vol 41, Issue 1<br>
>> >> ><br>
>> >> > Send Bf-docboard mailing list submissions to<br>
>> >> > <a href="mailto:bf-docboard@blender.org">bf-docboard@blender.org</a><br>
>> >> ><br>
>> >> > To subscribe or unsubscribe via the World Wide Web, visit<br>
>> >> > <a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
>> >> > or, via email, send a message with subject or body 'help' to<br>
>> >> > <a href="mailto:bf-docboard-request@blender.org">bf-docboard-request@blender.org</a><br>
>> >> ><br>
>> >> > You can reach the person managing the list at<br>
>> >> > <a href="mailto:bf-docboard-owner@blender.org">bf-docboard-owner@blender.org</a><br>
>> >> ><br>
>> >> > When replying, please edit your Subject line so it is more specific<br>
>> >> > than "Re: Contents of Bf-docboard digest..."<br>
>> >> > Today's Topics:<br>
>> >> ><br>
>> >> > 1. Blenderwiki - script licensing problem ( Juho Veps?l?inen )<br>
>> >> > _______________________________________________<br>
>> >> > Bf-docboard mailing list<br>
>> >> > <a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
>> >> > <a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
>> >> > Hi,<br>
>> >> ><br>
>> >> > I added a simple script cookbook to the wiki. See<br>
>> >> > <a href="http://wiki.blender.org/index.php/Resources/PyNode_Cookbook" target="_blank">http://wiki.blender.org/index.php/Resources/PyNode_Cookbook</a> . Does<br>
>> >> > anyone know if the scripts added directly to the wiki are<br>
>> >> > automatically bound to Open Content License? I mean is it possible to<br>
>> >> > use any other license for a script should it be provided directly at<br>
>> >> > the wiki? It might be nice if the script authors could choose the<br>
>> >> > license (GPL., BAL, OCL) (see<br>
>> >> > <a href="http://wiki.blender.org/index.php/Meta/Licenses" target="_blank">http://wiki.blender.org/index.php/Meta/Licenses</a> for more information)<br>
>> >> > they like.<br>
>> >> ><br>
>> >> > In my opinion it would be great if the script author could include<br>
>> >> > something like "(C) *Year* *script author name* - released under My<br>
>> >> > Awesome License - <a href="http://www.linktomylicense.org" target="_blank">www.linktomylicense.org</a>" at the beginning of the<br>
>> >> > script instead of providing whole license as it takes a lot of space.<br>
>> >> ><br>
>> >> > I am not a licensing expert so that's why I am asking you. If anyone<br>
>> >> > has any sort idea regarding the issue, please let me know. This will<br>
>> >> > help the cookbook to evolve further and hopefully to gain some<br>
>> >> > popularity amongst the users. So far PyNodes have been pretty minor<br>
>> >> > feature but it would be great to see that changed.<br>
>> >> ><br>
>> >> > Sincerely<br>
>> >> > Juho "BeBraw" Vepsäläinen<br>
>> >> ><br>
>> >> ><br>
>> >> ><br>
>> >> > _______________________________________________<br>
>> >> > Bf-docboard mailing list<br>
>> >> > <a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
>> >> > <a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
>> >> ><br>
>> >> ><br>
>> >> _______________________________________________<br>
>> >> Bf-docboard mailing list<br>
>> >> <a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
>> >> <a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Bf-docboard mailing list<br>
>> > <a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
>> > <a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
>> ><br>
>> ><br>
>> _______________________________________________<br>
>> Bf-docboard mailing list<br>
>> <a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
>> <a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
><br>
><br>
> _______________________________________________<br>
> Bf-docboard mailing list<br>
> <a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
><br>
><br>
_______________________________________________<br>
Bf-docboard mailing list<br>
<a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
</div></div></blockquote></div><br>