I recently saw a reddit post on which some people claim pyglet is better than pygame<http://www.reddit.com/r/Python/comments/15lz1m/pygame_pyglet_something_else_entirely/> but don't use pyglet because pyglet "does not have a community".
I don't know if there was any reaction within pyglet community, but I believe this is a criticism that pyglet could address. In this post I will try to identify some of the areas that could be improved in pyglet community support. I will use an example of what I believe has a good community support: Django web framework. 1. Better documentation to new contributors (https://docs.djangoproject.com/en/1.6/internals/contributing/new-contributors/) Main question to be answered: how a wanna-be contributor can start in pyglet? 2. Better documentation to address issues and post issues (https://docs.djangoproject.com/en/1.6/internals/contributing/bugs-and-features/) Main question to be answered: I found a bug, how do I report it? 3. Ticket triaging policy (https://docs.djangoproject.com/en/1.6/internals/contributing/triaging-tickets/) Main question to be answered: new feature was wontfix, why or how should this be made? 4. Guide-lines for writing code (https://docs.djangoproject.com/en/1.6/internals/contributing/writing-code/) Main question to be answered: I cloned the code, any particular guides I should be aware when modifying it to my patch don't be rejected strait away? 4. Guide-lines for writing documentation (https://docs.djangoproject.com/en/1.6/internals/contributing/writing-documentation/) Main question to be answered: Ok, the code is too complex for me, I would like to start in something simpler, documentation. How can I improve it? 5. Adding a comitting policy (https://docs.djangoproject.com/en/1.6/internals/contributing/committing-code/#commit-access) Main question to be answered: How do committers proceed on committing to the master? 6. New features, deprecation policy, versioning, release process and others (https://docs.djangoproject.com/en/1.6/internals/release-process/) (https://docs.djangoproject.com/en/1.6/internals/deprecation/) (https://docs.djangoproject.com/en/1.6/internals/git/) (https://docs.djangoproject.com/en/1.6/internals/howto-release-django/) Main question to be answered: what is the pyglet policy? -------------------------- I don't intent to preach any of this neither say that pyglet should or should not have this documentation. I'm just saying that there is documentation that make an open source project more appealing to participate in. The bottom line is: I found it difficult to contribute to pyglet without having to ask on the mailing list. So, I'm reporting what were the things I tried to find in pyglet docs and I couldn't. I would gladly help on this. Jorge -- 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/groups/opt_out.
