Hi Chris, a similar discussion was already started by me longer time ago. Check this thread: http://forum.openscenegraph.org/viewtopic.php?p=5006&highlight=#5006
So the thing is, that in order to move from the way how its currently managed, it requires a lot of power and time. And it seems that there are not so much will would to take the opportunity and to remanage/rearchitecture the whole OSG library. I would like to see some changes too, so that for example libraries could be hosted in more official way in the osg repository. Currently every project maintainer can put his webpage on the wiki. Yeah, even with the forum I tried to create a place where support for the projects can be given (think on sub-categories on the forum). The only one thing is, that all projects are managed outside and are not included into main repository. I would claim that every project maintainer has to take care of being compatible to the current official releases of osg. Cheers, art Chris 'Xenon' Hanson wrote: > One thing I've noticed recently is that there is no central organization of > OSG-related > code that is not part of the actual core OSG SVN. > > I'm referring to both complete projects (things like osgAL, osgVRPN, etc) and > just > snippets like "here's a visitor that squooshes models into mashed potatoes". > > There's alot of stuff in various FAQs, in forum threads and other random > places. > > I'm thinking it might take two forms. one would be a section of the Wiki for > code > snippets, organized by some sort of categorization. This is pretty easy. > > The second part is more complex. As an analogy, if we consider the Linux > kernel versus a > Linux distribution (like Debian for example). OSG is currently like the > kernel -- it needs > to be complete and internally consistently tested. A new kernel should have > no bugs in the > portions of code considered the "kernel", but doesn't especially care about > failures > relating to things outside the kernel but considered part of the > "distribution". As an > example, Linus doesn't especially worry about whether a kernel change breaks a > distribution application like, for example, KOffice. > > What i'm trying to get it is I think it would be good to draw together some > of the more > significant OSG-related projects (like osgAL, etc, project maintainers > willing) and > perhaps host them on the main OSG SVN and wiki, but NOT have them be > considered an > official part of the OSG "kernel". What I'm trying to achieve is offering new > (and > existing!) developers a more complete picture of what's available for OSG, > WITHOUT > incurring any new testing and maintenance load for Robert. > > These new parts might not be able to be fully maintained (we just don't have > the people > to do this), but we could perhaps note when they were last verified to be > functional with > the current OSG, and what OSG version that was. > > -- > Chris 'Xenon' Hanson, omo sanza lettere Xenon AlphaPixel.com > PixelSense Landsat processing now available! http://www.alphapixel.com/demos/ > "There is no Truth. There is only Perception. To Perceive is to Exist." - Xen > _______________________________________________ > osg-users mailing list > > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > ------------------ > Post generated by Mail2Forum ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=18673#18673 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
