On 22/01/15 03:50, Richard Jones wrote:
At the moment, there's zero core active contributors. Adam has taken
the initiative to move the code to bitbucket, and I'd like to hear his
thoughts on the future of the codebase, but frankly as far as I'm
concerned (and I'm sure Alex would agree with me on this) the pyglet
code is everyone's now, and whoever is actively working on it can
pretty much dictate where it goes, and how it goes.
Yes, I pay for and operate the website, but I'd love for someone to
migrate it to rtfd.org <http://rtfd.org> so I all I have to do is pay
the annual domain fee :)
Richard
We definitely need some core contributors, they few times I've tried to
look at some bugs I've often come to a point where I needed more
information or someone to have a look at a patch and it hasn't happened.
I would agree that it could do with some sort of a leader, there seems
to be a lot of unchecked code being pushed into the codebase. I would
like to have a fully-automated set of tests that could be run on some
sort of continuous integration system that checks for correctness and
performance. That would be quite a tricky task that would benefit from a
lot of hardware.
The last time I was working with the code I ran into some problems with
the pulseaudio implementation that I might get around to tackling at
some point.
I think that's all my thoughts for now. I've started updating the xml
for the website to point at bitbucket and will push that asap. The
readme is already up-to-date.
Adam.
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
