Hi there,

I've been reading this thread with interest.  I would like to help out
on pyglet maintenance, particularly I'd be interested (for now) in
doing the appropriate things to open issues.  So far, I've been
pleased with the scope of pyglet, though I haven't used the font and
text stuff myself(yet).

I think what should be done for the immediate future of pyglet is to
take care of all of the important open issues and get a release out
without a scope change.  While that's going on, we can easily discuss
longer-term choices and attempt to determine the fashion in which
pyglet should continue, whether it be a minimalist core with easy ways
to extend, or whether it should become emacs(not a slam on emacs, I <3
it though that's not where I want pyglet to go, myself).

I enjoy DVCS, but sort of as a corollary to the immediate future, we
don't need to jump head first into a different version control system
in order to get an updated release out.   I personally can use git
locally and just build patches for what is to be published via svn, no
big deal.  Or I can just use svn for now.  One issue that comes up in
either case is that some entity(individual or committee) needs to
authoritatively determine whether things are ready for release.  What
may be a determining factor for version control is whichever system is
going to match this entity's style and composition best.  If that is
the case, before making version control decisions, we need to see how
the next wave of pyglet authority shakes out and we'll have a much
better idea which technologies to apply.

My $0.02,
-b



On Aug 14, 8:08 am, George Oliver <[email protected]> wrote:
> On Aug 14, 6:24 am, Tristam MacDonald <[email protected]> wrote:
>
> > On Fri, Aug 14, 2009 at 8:55 AM, Tartley <[email protected]> wrote:
>
> > > +1. I like pyglet because it doesn't try to be a PyGame - while that
> > > is a worthy endeavour, it's not what I'm looking for here.
>
> > +1 for trimming pyglet down, rather than adding features.
>
> As a pyglet user and not a maintainer/developer, I'd like to add my
> support to the above. I appreciate pyglet for precisely the reasons
> Tartley noted.
--~--~---------~--~----~------------~-------~--~----~
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