Completing the Developer Guide#144
Conversation
Getting started: sign up for Github, make a fork, etc Setting up: install things, env variables Building: compiling C ext and Cython Testing: unit and doctests Code style: PEP8 and the auto checker Documentation: Building and serving the docs All have links to reference material (most are software carpentry)
|
Hi @leouieda, I found your text very clear and concise. |
That is a very good suggestion. We've been needing a nice and clear mission statement. Something like this for the khmer project. I'll try to come up with a draft for that but I'll leave it for another PR (and another section of the docs). It might be better placed in the front page. I've opened #145 for this so we can move this particular discussion there. |
They some really nice tutorials.
Added some more tips for getting started: look at issues, tell what you're working on, low-hanging fruit.
Reorder some things in the PR section as well.
|
@hbueno any other suggestions for this? Just as a reminder, there is a compiled version on read the docs: http://fatiando.readthedocs.org/en/devel-guide/develop.html |
|
No, it's ok for me. |
|
Merging this then. If anything else comes up we can always open a new one. |
Completing the Developer Guide
Writing some more sections for the Developer Guide.
I tried to include some links to reference material for those new to software development. Most are links to Software Carpentry.
There is a version of the docs of this PR on ReadTheDocs: http://fatiando.readthedocs.org/en/devel-guide/develop.html
It will be updated automatically with the PR.
Fixes #25 (probably all of it)
Checklist: