Greetings pygleters! It has probably become quite apparent over the last few months that pyglet is not being maintained or developed. Both Richard and I have become quite occupied with other, er, occupations this year, and without the necessary free time to devote to pyglet.
Richard and I started working on pyglet in August 2006, initially as an experimental OpenGL front-end for Python, and then as an alternative to PyGame/SDL. Looking at the early design documents [1], it's satisfying to note that all of the main goals were achieved, and most of the "pie in sky" ideas have been implemented as modules specifically for pyglet by other developers. In June 2007 the pyglet 1.0alpha1 was published, and after months of fairly intensive testing, feedback and fixing from hundreds of developers, pyglet 1.0 was released in early 2008. pyglet-1.1, released in August 2008, has been downloaded some 13,000 times. While there have been no subsequent releases or feature enhancements since then, the pyglet community continues to grow. There are currently 670 members in the pyglet-users mailing list, with a new member joining every one or two days. The issue tracker is currently filled not just with bug reports, but also many patches for those bugs which have yet to make it into the code base. Many bugs that have been fixed in trunk have not been back-ported to the maintenance branch. At this stage it appears that mine and Richard's non-involvement with pyglet is harming the project. 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 not restricting access to people with specific patches to commit or ideas to implement. For example, there is substantial work available just in verifying issues in the tracker, applying patches and closing duplicates. The trunk is a mostly-complete refactor of the codebase with several new features that possibly just needs documentation and fixes to complete. I'm hoping that some sort of semi-organised anarchy will form to continue pyglet maintenance and development. I am looking forward to granting you all commit access! Regards Alex [1] http://code.google.com/p/pyglet/source/browse/trunk/DESIGN?spec=svn19&r=19 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
