Uhm those are quite some claim and restrictions in the GEO code, basically makes it not usable for many OSG users as written
__________________________________________________________ Gordon Tomlinson -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jolley, Thomas P Sent: 04 January 2008 22:19 To: OpenSceneGraph Users Subject: Re: [osg-users] File comment blocks conflict with OSGPL licensing It looks like a few of the libraries (osgFX, osgIntrospection, osgManipulator, osgParticle, maybe osgShadow) were mostly written by someone other than Robert yet Robert has a copyright notice on the top of most of the files in these libraries. Were they assigned to Robert? I beleive the intent on these libraries from the original authors is to use the OSGPL license. The osgPlugins looks like an interesting mishmash of copyright notices, missing notices, very few license terms, and some wild claims. You have to like the geo loader code that claims it is proprietary and has trade secrets. > -----Original Message----- > From: Paul Martz [mailto:[EMAIL PROTECTED] > Sent: Saturday, December 22, 2007 10:46 AM > To: 'OpenSceneGraph Users' > Subject: Re: [osg-users] File comment blocks conflict with OSGPL > licensing > > > The OSG is a collective work, most parts are OSGPL, but > some are GPL > > or other licenses. > > That's interesting. How would I find out what parts of OSG are > governed by which licenses? Especially when a source code comment > block makes no mention of licensing whatsoever, and simply states > that's its copyrighted? > > I understand the Terrex code and OpenFlight import plugin are intended > to be non-restrictive, regardless of the language in their comment > blocks. I fear the issue isn't limited to these two groups of files. > > I have a law firm on retainer. I might have them take a look at the > OSGPL and a couple of source code files just to get an opinion. If the > intent is for the source to be freely available and usable, I'd like > to hear what a lawyer thinks would be the best way to update the > source code to reflect > that: must the more restrictive comment language be stripped out? Or > could we just append a superseding comment block? Or some other > solution? With most businesses shut down for the holidays, I don't > expect any progress on this until early next year. > > Paul Martz > Skew Matrix Software LLC > http://www.skew-matrix.com > 303 859 9466 > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-opensce > negraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
