[Bf-committers] extension clause

[Roger Wickes]

i think the person who made that statement is wrong. Any program 
needs an OS to "work", yet you can license your program differently from
the way the OS is licensed. The API is the dividing line. If you dance on the
outside of the API, your stuff is yours. 

 --Roger


Check out my website at www.rogerwickes.com for a good deal on my book and 
training course, as well as information about my latest activities. Use coupon
Papasmurf for $15 off!



----- Original Message ----
From: Michelangelo Manrique <michelangelomanrique at hotmail.com>
To: bf-blender developers <bf-committers at blender.org>
Sent: Wed, October 6, 2010 3:08:19 AM
Subject: Re: [Bf-committers] extension clause

well, sentences like "If something needs x to work..." is little bit
tricky. After all you require a pc to run scripts independently what
they do. If we see little bit far away we can say you can't publish
anything under GPL because you require an Intel chipset to make it
running or you require Windows or anything else... this is a point of
view issue after all imo.

On Wed, 2010-10-06 at 08:20 +0200, Damir Prebeg wrote:
> That sentence is also unclear to me. If I understand it right, that means
> that Blender can't have for instance, a legal VRay plugin. That doesn't make
> much sense because If any proprietary program can use GPL'd DLL as long as
> they provide license and access to the code of that DLL, why GPL program
> shouldn't be able to use proprietary DLL?
> 
> If Python script and MyDLL doesn't use any GPL code, I don't see a reason
> that they couldn't be published under a different license than GPL. That's
> not supporting of proprietary code.
> 
> Few years a go I've watched a discussion about Python scripts for Blender
> and licensing and someone stated that If some script needs Blender to work,
> then It can not be published under any license but GPL.
> And what If that script is divided in two parts? One that works only in
> Blender and second that uses only generic python? For instance, first one
> takes Blender mesh, gathers vertex coordinates and face data, creates
> generic lists and exports them to second one. That way second one can be
> used by any program that can create lists.
> 
> 
> Damir
> 
> 
> On 6 October 2010 04:43, Roger Wickes <rogerwickes at yahoo.com> wrote:
> 
> > What is not OK about it?
> > I think it is clear that the Blender Foundation cannot support proprietary
> > code.
> >
> > If you have the situation where a company wants to build
> > some DLL and keep it proprietary, then never release it to the public.
> > Guard it
> > as
> > your own intellectual property. Use your code to your competitive
> > advantage.
> > I have a client who did just that. Their scripts that they wrote and paid
> > for
> > are theirs.
> > They license their code and have a great business model. Their complete
> > solution
> > includes Blender, but they do not sub-license Blender or steal code;
> > instead the
> > customer gets Blender from BF, and their solution from them.
> >
> > Or do you have the situation where you want to develop a plugin to Blender
> > that
> > you
> > license out (sell) to customers?
> >
> >  --Roger
> >
> >
> > Check out my website at www.rogerwickes.com for a good deal on my book and
> > training course, as well as information about my latest activities. Use
> > coupon
> > Papasmurf for $15 off!
> >
> >
> >
> > ----- Original Message ----
> > From: john grant <johnkonradgrant at yahoo.com>
> > To: bf-committers at blender.org
> > Sent: Tue, October 5, 2010 10:09:50 PM
> > Subject: [Bf-committers] extension clause
> >
> > Hello,
> > I assume this topic has been brought up before, but I have not yet found
> > evidence of those conversations.  I would like to voice my opinion to find
> > out
> > what is the truth.  If I am not understanding correctly, please let me
> > know.  I
> > presume that the following text,
> > "Not OK is:
> > Author publishes a Blender script, calling a compiled C library with own
> > code,
> > both under own license. "
> >
> > from this source,
> > http://www.blender.org/education-help/faq/gpl-for-artists/
> >
> >
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
> >
> >
> >
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
> 


_______________________________________________
Bf-committers mailing list
Bf-committers at blender.org
http://lists.blender.org/mailman/listinfo/bf-committers