On 07/11/13 12:21, Jorge Cardoso Leitão wrote: > [...] > > I would gladly help on this.
I totally agree with you and I'd love your help :) This is the best we have at the moment: http://pyglet.org/contribute.html There's no structured contribution process. I agree we need one because Google Code is not as clear in that regard as other hosting environments are (I don't think we should move to GitHub or Bitbucket, not now at least). There are three places where we can include information about contributing, although maintaining three docs could be a pain: - Adding CONTRIBUTE file in pyglet's main directory - Adding a section in doc/internal/contribute.txt - Improving website/contribute.xml We can start with the third point and add a reference in README so anyone downloading the source can find where is the doc. Can you open a ticket and attach a diff of your changes to contribute.xml? You can also clone the hg repo and commit the changes there and link it to the ticket. Just make a version of what do you think that would be a good "contribute" document and I'll give it a second pass. Regards, Juan -- jjm's home: http://www.usebox.net/jjm/ blackshell: http://blackshell.usebox.net/ -- 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.
