okfn/ckan — pull request #173 by seanh (2012-11-17 12:47:59+00:00)
Title: [#3020] Coding standards updates and tidy up

If this gets merged I'd like to add a link in the README on the GitHub front page to the For CKAN Developers section to make it a little more prominent.

Still lots of stuff could be added to the CKAN Code Architecture page, and the Release Cycle page could maybe get the contents from the Release Process wiki page.

- Break the very long coding standards page up into several pages

- Collect all the docs about how to contribute to CKAN (fork, feature branch, commits, pull request..) into their own page and add some missing details to them

- Add how to contribute to docs docs

- Add a couple of tips to the CKAN Code Architecture section

- Update some outdated stuff e.g. outdated links to Python code checkers

- Remove some unnecessary stuff trying to keep these docs shorter e.g. don't repeat things from PEP8 etc.

- Remove some outdated and/or incomplete docs pages about CKAN's domain model. buildbot, etc.