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.
On 8/14/09, Florian Bösch <[email protected]> wrote: > I don't think that'd work particularly well. I would suggest switching > to a dvcs and following the Linux model, where Alex becomes Linus, > Richard and whoever else becomes core developers and everybody else > who wants his favorite patch in becomes a contributor that has to go > trough the gates of the core teams pull/push. Alex and Richard would > still have some work in the short term, but it'd allow to build a core- > team that could eventually replace them and ensure a continuing > quality of changes. > > Cheers, > Florian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
