I got some feedback from a lawyer on this. If a source file states that its usage is governed by a specific license, then there's no problem. So, all of the core OSG stuff, plus the OpenFlight importer with Brede's recent changes, are no problem: They explicitly state that their usage is governed by the OSGPL.
The Terrex files don't refer to any license governing their usage, but there is a license file in the Terrex directory. One can assume it governs the use of the files. If one wanted to really be legally secure, one would have to contact the source code authors and/or Terrex and inquire as to what license governs the source files' usage. I infer from this that if a file simply claimed "copyright such-and-such", but was distributed with OSG, then it'd be safe to assume that the OSGPL governed its usage (unless there was some other license file present, as in the case with Terrex). It might be helpful to go through all the OSG source files and enhance each one's copyright to refer to its governing license. But I'll wait until someone is willing to fund this project, as it could get quite tedious. Moving forward, perhaps we should all adopt the practice of making sure the comment blocks of any new files specify a governing license, be it OSGPL or whatever. 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-openscenegraph.org
