To reflect the reorganization I moved debugging.rst to tips.rst. Does this mean links will be broken, and should we worry about that?...

I think the circle stuff is already in the doc somewhere.

You should probably add the outdated diff gist while you are at it ;-). https://gist.github.com/lesteve/b4ef29bccd42b354a834

please mention the PR pull thing from the wiki, and maybe the codecov browser plugin

@lesteve I couldn't find the circle stuff with git grep, if you can find it could you post a link?

good point about the other additions, I'm simply not familiar enough with them yet, will do

@lesteve I couldn't find the circle stuff with git grep

http://scikit-learn.org/dev/developers/contributing.html#documentation

You may also be asked to show your changes when it’s built. When you create a pull request or make changes in an existing one modifying the docs, CircleCI automatically builds them. Thus, you can easily view your changes in the built artifacts using the following formula:
http://scikit-learn.org/circle?{BUILD_NUMBER}
We attempt to assemble a more precise set of changed files in the documentation at:
http://scikit-learn.org/circle?{BUILD_NUMBER}/_changed.html

Made the suggested additions and corrections.

rendered here

thanks for this @vene ! As a new contributor I'm just a bit confused about testing: in the contributing section it is mentioned to use nose and nosetests but you recommend pytests to run unit tests.

Long story short, we used nosetests historically and will be moving to pytest once 0.19 is released.

lgtm

Thanks @vene