On Sat, Aug 15, 2009 at 11:53 AM, Lucas indited:
> I think that this discussion has moved from the important topic.
> I don't think it is important right now which VCS we keep using (it is just a
> tool),
> the important thing right now, is how pyglet is going to keep alive
> (maintenance, bug fixing, improvements, port to python 3, etc).
I agree that the VCS is a secondary decision but I also agree that
once we've read the charts and decided to set sail, the VCS used will
have an affect on how/if folks participate. I feel we can afford to
cruise on SVN for now since there is resistance to changing it right
now.
> I agree we Tristam, we must start by merging back maintenance branch with
> trunk.
I've just started using pyglet(1) and was lured in to its elegance by
Steve Johnson's "Game Development With Python and Pyglet" talk at
pyohio a few weeks ago.(2)
I don't yet even know what the outstanding bugs are, as I'm still
getting my head around how little it takes to do some awesome
things... Which leads me to the point of this reply. I'm having a bit
of trouble constructing a google search for snippets and bits of
user-shared pyglet code. Then I said: "Wait! Why isn't there a place
on the pyglet site for sharing code (kind of like CPAN or pypi)?"
I don't know that it matters where the code itself is, maybe it's good
enough to have a wiki page or three which are just links to bitbucket
or git hub or whatever.
I'm also wondering about the release testing process. I use a Mac (OS
X Leopard) at home and a <shudder>Dell running Windows XP</shudder> at
work. The former is only one while being used and the latter is behind
a firewall, so I can't offer them as buildbot slaves, but I would be
willing to put release candidates through their paces and report
bugs/issues.
Thanks for listening,
-Doug
(1) - I'm using a lot of the font/text features because I'm using this
for my day-job, not (yet) for personal/game apps. :)
(2) - http://www.pyohio.org/Talks#talk18
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
