[Bf-docboard] Wiki is not to hold commercial or restriced content, imho

[Roger Wickes]

The issue, I think, is that the Blender Wiki was not intended, and I personally do not want it, to hold our house or distribute commercially licensed software. It goes against the grain of Open Source and exposes us to liability. So, yes, we have to restrict scripts that are posted or linked to or reference to AVOID commercially licensed scripts and software, and only contain content that is open for others to freely download and use. I also want to AVOID the qualified licenses that some people put in, like "free for non-commercial use" - realistically, this is a worthless distraction, because you would have to prove that the script was embedded in some commercial product, then determine if there was any damage, and then sue the vendor...all a bunch of negative crap and not worth the effort, and again, going against the Open Content philosophy. If you can use Blender or a Script to make money, do it!

 

-----Inline Attachment Follows-----

Erm. . .not sure if this is technically correct, like I said before the copyright page in the wiki *does* have open content in it.  And by default it should apply to every page in the wiki, unless someone added an exception for scripts.

Joe


On Wed, Jun 4, 2008 at 8:28 AM, Juho Vepsäläinen <bebraw at gmail.com> wrote:

Hi,

Thank you Roger. I clarified the licensing terms at

http://wiki.blender.org/index.php/Resources/PyNode_Cookbook .
Hopefully it is fine now. Feel free to tweak it as you see necessary.
:)

Sincerely,
Juho "BeBraw" Vepsäläinen

2008/6/4 Roger Wickes <rogerwickes at yahoo.com>:

> Scripts that are posted and given to the public domain in an unrestricted
> fashion, should NOT bear any copyright or other license/ownership title,
> like the color ones. They just start off with import Blender. That is
> easiest. anyone can use that fragment/code any way they want.


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20080606/621edee3/attachment.htm