I also would prefer to have first bug fixed and then take time to  
think on whether some features are necessary and how to integrate them  
within the existing architecture. If there is no principal maintainer  
anymore, I guess we also need some procedure to decide whether or not  
to include this or that feature. In this context, having a minimal  
bulletproof pyglet would certainly help further development.

Nicolas


On 14 Aug, 2009, at 13:47 , Martin O'Leary wrote:

>
> 2009/8/14 Steve Johnson <[email protected]>:
>>
>> I mentioned switching to a DVCS to Alex in another email, and he said
>> it wouldn't be hard for us to use hg-svn for our working copies and
>> treat the svn server as a push target. Is that an acceptable  
>> solution,
>> or are there other factors?
>>
>> I wold also be in favor of switching over to a DVCS completely,
>> preferably hg because Google Code supports it.
>
> I think a lot of this is tied up in the question of where the future
> of Pyglet lies. If we're going to be adding heaps of new
> functionality, which Richard and Alex are both against, and which I at
> least have fairly strong reservations about, then yes, we probably
> need a DVCS system. However, if we're considering Pyglet to be roughly
> feature-complete, and only talking about bug fixes and minor
> enhancements, then the current SVN system seems perfectly acceptable.
>
> At the moment, it seems like people have a new toy, and are rushing to
> play with it. Let's sit back, fix the bugs that we've got, and have a
> discussion about where we'd like things to go, development-wise. Then
> we can decide what the appropriate technical solution should be.
>
> Martin
>
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to