Re: [Opentnl-general] Greetings!

[Jarrod R. <ja...@ve...>]

Mark Frohnmayer wrote:

> The official TNL project at www.opentnl.org will be the same code base 
> as the indie/commercial licensed code.  The only code that isn't a 
> part of that codebase is the console platform code which will be 
> seperately licensable from GG.
>
> As far as GPL issues go - we will only be accepting contributions to 
> the official TNL codebase from people who have submitted a joint 
> copyright assignment form, which we will have available soon.  This 
> will allow us to continue licensing the TNL codebase under indie and 
> commercial licenses while at the same time protecting the rights of 
> the people who submit the code.
>
> - Mark
>
Ok what I get from this is - confusion still . . . :-)

ignoring the console code issue for right now . . .

This is what I get from the  above and Ben's response also . . .

 non-OpenTNL code contributions will require the contributor to assign 
dual license rights to GG, thats fine.

Are you going to require the same dual license for contributions to the 
official OpenTNL code base?

So the assumptions are these

that the OpenTNL code base and the "commercial/indie" licensed code base 
will always be the same ( not counting the console code )
that the commercial and indie license fees will just allow you to NOT 
have to ship your own personal code with your product, since the GPL 
includes
any code that is statically or dynamically linked in, anything that uses 
OpenTNL has to be GPL also.

Just to clarify, I fully intend on buying the indie license ( this is 
really what I wanted when I bought Torque :-) ) . . . but I want to work 
with the OpenTNL stuff until I get a full understanding of how it all 
works. So this is more for clarification than anything, since it is kind 
of a moot point once I buy the license correct?