First and foremost, I will _not_ debate this subject, so this will be my definitive statement as to what I am doing with Producer.  Your conclusions can be arrived at by experimentation and not by opinions debated on a mailing list or uninformed assumptions.

Producer will grow over the next couple of years.  I have projects that require added functionality. I also intend to contribute to it a collection of tools that I've used over the past 18 years that I've been developing software for 3D graphics and real-time computing.  Producer will provide me the platform to exercise primary design decisions that I cannot on the OSG project.

Most importantly, I have no intention of dividing the OSG community.  Recent changes to Producer reflect a rearrangement of directory structures to allow for added libraries and improved build systems.  The OSG build has not been affected whatsoever.  The Producer build has changed, very slightly and optionally, to allow Producer to be built _after_ OSG.  Producer's current primary focus is a camera library and this is precedent to a scene graph in dependency order.  In other words, Producer is used to visualize OSG, not the other way around.

The only component of OSG this affects is osgProducer, which Robert has stated as being on the chopping block.  Regardless, the "divisive wedge into the heart of OSG" that deeply saddens Robert is two flags being set in a config file.  (I've in fact, just checked in a change to set the default off on those flags).

For reasons I'd prefer not to discuss on the public mailing list, I've resigned as OSG's maintainer of the server, website, mailing lists, database, and asked Robert to find a new home for OSG by Feb 1, 2007 (that's 12 weeks from the time I informed him). If  you'd like details I'll be happy to discuss this one-on-one off of the public mailing list and with no CCs or BCCs in your email. 

Thanks,

-don



On 11/15/06, Robert Osfield <[EMAIL PROTECTED]> wrote:
Hi All,

Don is currently refactoring Producer distribution, he's not keeping the OSG community well informed, or being mindful of the fallout on the OSG side.  This is a troubling development, not so much the ideas behind the refactoring but the manner that this work is being carried, being deliberately divisive, driving a wedge into the heart of the OSG project, forcing the core OSG to be refactored just to keep things compiling sensibly.

I am deeply troubled and saddened by this development.

With the stance that Don is taking on Producer and ProducerOSG it looks like I'll need either to split osgProducer and all associated example out into their own distribution (to avoid the newly introduced OSG-Producer circular dependency), or for us to branch Producer in version prior to this week changes and just use that in conjunction with the OpenSceneGraph in future.

I am currently overwhelmed with other work so taking on massive refactoring of the OSG distribution is not something I can do right now.  Such refactoring would also require sweeping changes to Visual Studio and XCode projects so we are likely to see the build on the OSG go under significant instability for a couple of days.  I'll not undertake such changes without good prior warning, as I'll need the communities help to get things working again once things are refactored. 

Right now I have to recommend that OSG CVS users refrain from doing CVS updates on Producer, at least until Producer changes have settled down, and we can put into place a strategy for migrating the OSG to this new way of Producer, or simply by branching it.

Robert.



















_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/


_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/

Reply via email to