I agree with Florian and I think that giving full SVN access to anybody might make things a real mess in a short period of time. We need some sort of roadmap and identify priorities (bug fix, adding feature, doc, ...). I think Alex made a fantastic job with the pyglet abstraction and I would be happy to code for pyglet under his direction. Also, there is already a lot of contribution that could make it into pyglet (gletools, simplui/kytten, ...).
Nicolas On Aug 14, 7:42 am, Florian Bösch <[email protected]> wrote: > On Aug 13, 1:59 pm, Alex Holkner <[email protected]> wrote: > > > If you have some time to contribute to pyglet, I invite you now to do > > so directly. Email me privately with your Google account ID (email > > address) so I can add you to the googlecode project committer list. > > This will give you full access to SVN, the issue tracker and wiki. > > I am looking forward to granting you all commit access! > > 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 -~----------~----~----~----~------~----~------~--~---
