Convert other md files to rst

Author: Janneke van der Zwaan

{{cookiecutter.project_slug}}/CHANGELOG.md

@@ -0,0 +1,14 @@
+###########
+Change Log
+###########
+
+All notable changes to this project will be documented in this file.
+This project adheres to `Semantic Versioning <http://semver.org/>`_.
+
+[Unreleased]
+************
+
+Added
+-----
+
+* Empty Python project directory structure

{{cookiecutter.project_slug}}/CHANGELOG.rst

@@ -1,6 +1,9 @@
-# Contributor Covenant Code of Conduct
+###############################################################################
+Contributor Covenant Code of Conduct
+###############################################################################
 
-## Our Pledge
+Our Pledge
+**********
 
 In the interest of fostering an open and welcoming environment, we as
 contributors and maintainers pledge to making participation in our project and
@@ -9,7 +12,8 @@ size, disability, ethnicity, gender identity and expression, level of experience
 education, socio-economic status, nationality, personal appearance, race,
 religion, or sexual identity and orientation.
 
-## Our Standards
+Our Standards
+*************
 
 Examples of behavior that contributes to creating a positive environment
 include:
@@ -31,7 +35,8 @@ Examples of unacceptable behavior by participants include:
 * Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
-## Our Responsibilities
+Our Responsibilities
+********************
 
 Project maintainers are responsible for clarifying the standards of acceptable
 behavior and are expected to take appropriate and fair corrective action in
@@ -43,7 +48,8 @@ that are not aligned to this Code of Conduct, or to ban temporarily or
 permanently any contributor for other behaviors that they deem inappropriate,
 threatening, offensive, or harmful.
 
-## Scope
+Scope
+*****
 
 This Code of Conduct applies both within project spaces and in public spaces
 when an individual is representing the project or its community. Examples of
@@ -52,7 +58,8 @@ address, posting via an official social media account, or acting as an appointed
 representative at an online or offline event. Representation of a project may be
 further defined and clarified by project maintainers.
 
-## Enforcement
+Enforcement
+***********
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported by contacting the project team at {{ cookiecutter.code_of_conduct_email }}. All
@@ -65,9 +72,8 @@ Project maintainers who do not follow or enforce the Code of Conduct in good
 faith may face temporary or permanent repercussions as determined by other
 members of the project's leadership.
 
-## Attribution
+Attribution
+***********
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+This Code of Conduct is adapted from the `Contributor Covenant <https://www.contributor-covenant.org>`_, version 1.4,
 available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org

…cutter.project_slug}}/CODE_OF_CONDUCT.md …utter.project_slug}}/CODE_OF_CONDUCT.rst{{cookiecutter.project_slug}}/CODE_OF_CONDUCT.md renamed to {{cookiecutter.project_slug}}/CODE_OF_CONDUCT.rst {{cookiecutter.project_slug}}/CODE_OF_CONDUCT.md renamed to {{cookiecutter.project_slug}}/CODE_OF_CONDUCT.rst

@@ -1,6 +1,8 @@
-# Contributing guidelines
+############################
+Contributing guidelines
+############################
 
-We welcome any kind of contribution to our software, from simple comment or question to a full fledged [pull request](https://help.github.com/articles/about-pull-requests/). Please read and follow our [Code of Conduct](CODE_OF_CONDUCT.md).
+We welcome any kind of contribution to our software, from simple comment or question to a full fledged `pull request <https://help.github.com/articles/about-pull-requests/>`_. Please read and follow our `Code of Conduct <CODE_OF_CONDUCT.rst>`_.
 
 A contribution can be one of the following cases:
 
@@ -10,30 +12,33 @@ A contribution can be one of the following cases:
 
 The sections below outline the steps in each case.
 
-## You have a question
+You have a question
+*******************
 
-1. use the search functionality [here](https://github.com/{{ cookiecutter.github_organization }}/{{ cookiecutter.project_slug }}/issues) to see if someone already filed the same issue;
+1. use the search functionality `here <https://github.com/{{ cookiecutter.github_organization }}/{{ cookiecutter.project_slug }}/issues>`_ to see if someone already filed the same issue;
 1. if your issue search did not yield any relevant results, make a new issue;
 1. apply the "Question" label; apply other labels when relevant.
 
-## You think you may have found a bug
+You think you may have found a bug
+**********************************
 
-1. use the search functionality [here](https://github.com/{{ cookiecutter.github_organization }}/{{ cookiecutter.project_slug }}/issues) to see if someone already filed the same issue;
+1. use the search functionality `here <https://github.com/{{ cookiecutter.github_organization }}/{{ cookiecutter.project_slug }}/issues>`_ to see if someone already filed the same issue;
 1. if your issue search did not yield any relevant results, make a new issue, making sure to provide enough information to the rest of the community to understand the cause and context of the problem. Depending on the issue, you may want to include:
-    - the [SHA hashcode](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) of the commit that is causing your problem;
+    - the `SHA hashcode <https://help.github.com/articles/autolinked-references-and-urls/#commit-shas>`_ of the commit that is causing your problem;
     - some identifying information (name and version number) for dependencies you're using;
     - information about the operating system;
 1. apply relevant labels to the newly created issue.
 
-## You want to make some kind of change to the code base
+You want to make some kind of change to the code base
+*****************************************************
 
-1. (**important**) announce your plan to the rest of the community _before you start working_. This announcement should be in the form of a (new) issue;
+1. (**important**) announce your plan to the rest of the community *before you start working*. This announcement should be in the form of a (new) issue;
 1. (**important**) wait until some kind of consensus is reached about your idea being a good idea;
-1. if needed, fork the repository to your own Github profile and create your own feature branch off of the latest master commit. While working on your feature branch, make sure to stay up to date with the master branch by pulling in changes, possibly from the 'upstream' repository (follow the instructions [here](https://help.github.com/articles/configuring-a-remote-for-a-fork/) and [here](https://help.github.com/articles/syncing-a-fork/));
+1. if needed, fork the repository to your own Github profile and create your own feature branch off of the latest master commit. While working on your feature branch, make sure to stay up to date with the master branch by pulling in changes, possibly from the 'upstream' repository (follow the instructions `here <https://help.github.com/articles/configuring-a-remote-for-a-fork/>`_ and `here <https://help.github.com/articles/syncing-a-fork/>`_);
 1. make sure the existing tests still work by running ``python setup.py test``;
 1. add your own tests (if necessary);
 1. update or expand the documentation;
-1. [push](http://rogerdudler.github.io/git-guide/) your feature branch to (your fork of) the {{ cookiecutter.project_name }} repository on GitHub;
-1. create the pull request, e.g. following the instructions [here](https://help.github.com/articles/creating-a-pull-request/).
+1. `push <http://rogerdudler.github.io/git-guide/>`_ your feature branch to (your fork of) the {{ cookiecutter.project_name }} repository on GitHub;
+1. create the pull request, e.g. following the instructions `here <https://help.github.com/articles/creating-a-pull-request/>`_.
 
 In case you feel like you've made a valuable contribution, but you don't know how to write or run tests for it, or how to generate the documentation: don't let this discourage you from making the pull request; we can help you! Just go ahead and submit the pull request, but keep in mind that you might be asked to append additional commits to your pull request.