On Nov 23, 2008, at 5:18 PM, Eric Ongerth wrote:
I would be glad to contribute typo and spelling fixes to the new pylons docs at docs.pylonshq.com. I have been reading through them and I have such volume of small fixes to offer that it would not be most efficient to package them up in email, have someone else read through the correspondence, and so on. So I'm thinking I could help out more directly.
So, a few simple steps, you'll want to check out the project and fork it first:
1) Login to bitbucket.org and setup a new account if you don't have one2) Go to http://www.bitbucket.org/bbangert/pylons/overview/ and click the Fork project button
3) Checkout the your fork of the project 4) Commit your fixes to the docs in your forkThis way I can then see that you forked it, and pull your changes from your repo. This is about the easiest way for me to track external changes to the Pylons project (which is where all the docs are, in the pylons/docs/en/ dir). It's also the easiest for me to pull new changes that you make to the docs.
If you want to build the docs locally on your machine, make sure you have the latest Sphinx installed:
easy_install Sphinx Then cd into the pylons/docs/en/ dir and: make htmlWhich will build the HTML copy in a _build directory that you can take a look at.
Cheers, Ben
smime.p7s
Description: S/MIME cryptographic signature