One thing that's not ideal, is that we have some duplicated things between the wiki and the docs. The "contributing" section is basically the same in both places. And, as you know, the home page is currently pointing towards the wiki on Bitbucket.
I agree that it would be useful to have some more specific details about how to contribute, but I don't think we want to put a bunch of Bitbucket specific things in the proper documentation. Perhaps the Bitbucket wiki can contain these specific details where they relate to forking/pull requests on Bitbucket. The documentation, in comparison, can cover more high-level overview of the development process. For example, the fact that we do most development in the default branch, and use specific branches for releases, etc. -Ben On Saturday, August 12, 2017 at 6:45:03 AM UTC+9, Abhik Pal wrote: > > > Mercurial does take a bit of getting used to. Let us know if you > > have questions. Maybe we can update the docs to add a few pointers > > on how to get started. > > I've worked through a tutorial or two, but it would be nice to have > some more pyglet-specific details (+examples?) in the Contribute page > in the wiki. I would be more than happy to take this up after I figure > things out for myself. > > > — > Abhik > -- 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 https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
