On Fri, Aug 14, 2009 at 7:39 AM, joe hall <[email protected]> wrote:
> > I agree with Florian, Opening up the floodgates to the core of pyglet, > would hack the system to pieces, leaving nothing to base future > development on. Given that the serious "pygleter" would do everything > to keep the core intact, there are many of us who with all good > intentions, will just mess up the base, due to some small oversight of > misconceptions on the "way we would prefer things to be done". A new > core team is a controlled migration, that is required move the pyglet > gem forwards:) > We love your work Alex, don't just go flush it away now. A reasonable compromise is branched development. If we can make the short term goal to reconcile the trunk with the 1.1-maintenance branch, then anyone who wants to experiment with destructive upgrades can be pushed into their own branch. Either way, someone needs to be designated to guard the trunk - integrate bug fixes, decide when new branches are stable enough to be back-ported to trunk, and decide when to publish new releases. Alex inquired whether I would be interested in the position, but I don't have enough time to dedicate to managing an entire project at the moment. -- Tristam MacDonald http://swiftcoder.wordpress.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
