Add docs for contributors.

[barrachri]

This PR try to address #1185.

Adding also github issue and PR templates.

It's WIP because I'd like to improve/clarify:

• testing process
• how to get a dev env ready
• how to collect new contributors

[AmplabJenkins]

Can one of the admins verify this patch?

[robertnishihara]

ok to test

[AmplabJenkins]

Merged build finished. Test FAILed.

[AmplabJenkins]

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/2288/
Test FAILed.

[robertnishihara]

Thanks for getting this started, this'll be really helpful!

I haven't seen any other projects use a pull request template. Do you know of any?

The CONTRIBUTING.rst file could be modeled after https://github.com/apache/arrow/blob/master/.github/CONTRIBUTING.md as well as https://github.com/tensorflow/tensorflow/blob/master/CONTRIBUTING.md. It may make sense to put instructions for getting set up for development somewhere else in the documentation. I don't feel strongly about this though.

[robertnishihara]

This section isn't relevant, is it?

[barrachri]

If you send a PR about improving the docs I think it's a great idea to check the docs (so open the local link and...).

About Changelog, how do you collect the changes so far?
This is really useful if you want to collect info between releases and publish also the changelog, together with the new release.

[robertnishihara]

We currently don't maintain a changelog. We could certainly add one, though we can always construct it after the fact just by looking through the commit history.

[barrachri]

Ok, so I will remove this changelog part.

[barrachri]

About the pull request template just to cite a few:

https://github.com/pandas-dev/pandas/blob/master/.github/PULL_REQUEST_TEMPLATE.md
https://github.com/dask/dask/blob/master/.github/PULL_REQUEST_TEMPLATE.md
https://github.com/apache/spark/blob/master/.github/PULL_REQUEST_TEMPLATE

Also Keras has also something similar but inside the CONTRIBUTING.md

I think it's nice to have because you can see what is needed directly inside the PR.
In this way as a admin you don't need to always remember that something is missing.

[robertnishihara]

Thanks for the links, those look reasonable.

[AmplabJenkins]

Merged build finished. Test FAILed.

[AmplabJenkins]

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/2308/
Test FAILed.

[robertnishihara]

@barrachri Mind if I take a pass over these docs (e.g., and push to your branch)? I'd prefer to start with more minimal versions of these files and then add to them as appropriate.

[barrachri]

@robertnishihara you are more than welcome in doing so.

[robertnishihara]

@barrachri I removed a lot of stuff, want to take a look? I'd suggest that we get this merged and then augment it as needed in follow up PRs.

[AmplabJenkins]

Merged build finished. Test FAILed.

[AmplabJenkins]

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/2335/
Test FAILed.

[robertnishihara]

I took some of the issue template from TensorFlow and the contributing doc from Arrow.

[barrachri]

Green light, I think you can merge!

[robertnishihara]

Thanks @barrachri!