Thread: [Opentnl-general] Greetings!
Brought to you by:
mark_frohnmayer,
s_alanet
From: David W. <op...@gn...> - 2004-04-20 21:04:18
|
Greetings! Wow, imagine my surprise when I found out about the OpenTNL project! = Congrats GarageGames on your commercial and Open Source TNL release. And I suppose introductions are in order. I'm David Wyand writing from = Toronto, Ontario, Canada, Earth. I'm an avid Torque Engine user bent on = making tools for the indie game developer. Oh, and I'm interested in = networking too. :o) - Dave http://www.gnometech.com |
From: Mark F. <ma...@ga...> - 2004-04-20 23:16:44
|
Welcome to the TNL community Dave! You win first post prize for Opentnl-general too. We're still trying to track down some bugs in the Zap code and then we're going to do a binary release of the Zap demo.... - Mark David Wyand wrote: > Greetings! > > Wow, imagine my surprise when I found out about the OpenTNL project! > Congrats GarageGames on your commercial and Open Source TNL release. > > And I suppose introductions are in order. I'm David Wyand writing > from Toronto, Ontario, Canada, Earth. I'm an avid Torque Engine user > bent on making tools for the indie game developer. Oh, and I'm > interested in networking too. :o) > > - Dave > http://www.gnometech.com > |
From: David W. <op...@gn...> - 2004-04-21 15:27:45
|
From: "Mark Frohnmayer" <ma...@ga...> > Welcome to the TNL community Dave! > > You win first post prize for Opentnl-general too. > > We're still trying to track down some bugs in the Zap code and then > we're going to do a binary release of the Zap demo.... > > - Mark Wow! I've never won anything before. With my new found responsibility I will spread the message of world peace. *weeps* Mark, I have a question regarding the code base. Will the OpenTNL code base be kept in step with the indie/commercial TNL code base? If I were to initially work with the OpenTNL and then decide to go for a closed source license, would there be any code differences? Thanks. - Dave http://www.gnometech.com |
From: Thomas H. L. <th...@tr...> - 2004-04-21 15:34:59
|
First congratulations to GG for releasing TNL. Oh, and while we are at it - will the indie/commercial license feature features that are not in the GPL one? Or will future enhancement in that end also be GPL'ed? /Thomas David Wyand wrote: >From: "Mark Frohnmayer" <ma...@ga...> > > >>Welcome to the TNL community Dave! >> >>You win first post prize for Opentnl-general too. >> >>We're still trying to track down some bugs in the Zap code and then >>we're going to do a binary release of the Zap demo.... >> >>- Mark >> >> > >Wow! I've never won anything before. With my new found responsibility I >will spread the message of world peace. *weeps* > >Mark, I have a question regarding the code base. Will the OpenTNL code base >be kept in step with the indie/commercial TNL code base? If I were to >initially work with the OpenTNL and then decide to go for a closed source >license, would there be any code differences? > >Thanks. > >- Dave >http://www.gnometech.com > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >Opentnl-general mailing list >Ope...@li... >https://lists.sourceforge.net/lists/listinfo/opentnl-general > > |
From: Jarrod R. <ja...@ve...> - 2004-04-21 16:04:09
|
Thomas Hentschel Lund wrote: > First congratulations to GG for releasing TNL. > > Oh, and while we are at it - will the indie/commercial license feature > features that are not in the GPL one? Or will future enhancement in > that end also be GPL'ed? > > /Thomas I would expect the codebases to diverge pretty quickly depending on popularity as anything added by the "community" will be GPL and would not be able to be put back into the non-GPL code base. Like wise any non-GPL code can't be added to the GPL version. Interbase/Firebird is a good example of this divergence. This divergency has happened with lots of dual licensed source code bases. |
From: Ben G. <be...@ga...> - 2004-04-21 17:09:46
|
Howdy, All contributors to the code base will be required to assign copyright of their contributions to us. Divergant code bases are a lot more hasstle than we want to work with. The indie/commercial versions will, code wise, have the same features as the GPL version. Hope that clears things up, Ben Jarrod Roberson wrote: > Thomas Hentschel Lund wrote: > >> First congratulations to GG for releasing TNL. >> >> Oh, and while we are at it - will the indie/commercial license >> feature features that are not in the GPL one? Or will future >> enhancement in that end also be GPL'ed? >> >> /Thomas > > > I would expect the codebases to diverge pretty quickly depending on > popularity as anything added by the "community" will be GPL and would > not be able to be put back into the non-GPL code base. Like wise any > non-GPL code can't be added to the GPL version. Interbase/Firebird is > a good example of this divergence. > > This divergency has happened with lots of dual licensed source code > bases. > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Opentnl-general mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opentnl-general > > |
From: Mark F. <ma...@ga...> - 2004-04-21 17:24:37
|
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 Jarrod Roberson wrote: > Thomas Hentschel Lund wrote: > >> First congratulations to GG for releasing TNL. >> >> Oh, and while we are at it - will the indie/commercial license >> feature features that are not in the GPL one? Or will future >> enhancement in that end also be GPL'ed? >> >> /Thomas > > > I would expect the codebases to diverge pretty quickly depending on > popularity as anything added by the "community" will be GPL and would > not be able to be put back into the non-GPL code base. Like wise any > non-GPL code can't be added to the GPL version. Interbase/Firebird is > a good example of this divergence. > > This divergency has happened with lots of dual licensed source code > bases. > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Opentnl-general mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opentnl-general |
From: Jarrod R. <ja...@ve...> - 2004-04-21 17:59:35
|
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? |
From: Ben G. <be...@ga...> - 2004-04-21 18:12:16
|
Jarrod Roberson wrote: > > 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? Yes. That's the whole point of the joint copy right stuff - is to keep the source code legally "ours", so that people can use it for things. Open source projects all have similar issues, which is why things like the Apache Software Foundation exist - as an entity to which to assign copyright for Apache source, as much as anything else. > > 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 ) Yes. Console code will probably live in its own space (assuming that the licenses are such we can't put the console-specific parts up for public download) but all will be kept in synch. > 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. Yes. > > 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? Yes. Ben |
From: Ben G. <be...@ga...> - 2004-06-08 18:34:38
|
Hi, We're occasionally asked by the press for projects using TNL (right now we're talking to NewsForge), and we'd like to include anyone who has a project that they'd be interested in having mentioned. Of course, that means we have to know about your project. :) If you're interested in having your project mentioned, we'll need a brief project overview and contact person for following up. You can contact me off-list with information. Thanks, Ben Garney |