Improve CONTRIBUTING

Author: dolfinus

CONTRIBUTING.rst

@@ -6,6 +6,23 @@ reports, improving documentation, submitting feature requests, reviewing
 new submissions, or contributing code that can be incorporated into the
 project.
 
+Review process
+--------------
+
+For any **significant** changes please create a new GitHub issue and
+enhancements that you wish to make. Describe the feature you would like
+to see, why you need it, and how it will work. Discuss your ideas
+transparently and get community feedback before proceeding.
+
+Small changes can directly be crafted and submitted to the GitHub
+Repository as a Pull Request. This requires creating a **repo fork** using
+`instruction <https://docs.github.com/en/get-started/quickstart/fork-a-repo>`_.
+
+Important notes
+---------------
+
+Please take into account that some companies still use old Python versions, like 3.7. So the changes should be compatible.
+
 Initial setup for local development
 -----------------------------------
 
@@ -14,45 +31,31 @@ Install Git
 
 Please follow `instruction <https://docs.github.com/en/get-started/quickstart/set-up-git>`_.
 
-Create a fork
-~~~~~~~~~~~~~
-
-If you are not a member of a development team building Evacuator, you should create a fork before making any changes.
-
-Please follow `instruction <https://docs.github.com/en/get-started/quickstart/fork-a-repo>`_.
-
 Clone the repo
 ~~~~~~~~~~~~~~
 
-Open terminal and run these commands:
+Open terminal and run these commands to clone a **forked** repo:
 
 .. code:: bash
 
     git clone git@github.com:myuser/evacuator.git -b develop
 
     cd evacuator
 
-Setup environment
-~~~~~~~~~~~~~~~~~
+Enable pre-commit hooks
+~~~~~~~~~~~~~~~~~~~~~~~
 
 Create virtualenv and install dependencies:
 
 .. code:: bash
 
-    # create virtual environment
     python -m venv venv
     source venv/bin/activate
     pip install -U wheel
     pip install -U pip setuptools
-
-    # install requirements
     pip install -U \
-        -r requirements-dev.txt \
-        -r requirements-docs.txt \
-        -r requirements-test.txt
-
-Enable pre-commit hooks
-~~~~~~~~~~~~~~~~~~~~~~~
+        -r requirements.txt \
+        -r requirements-dev.txt
 
 Install pre-commit hooks:
 
@@ -69,19 +72,36 @@ Test pre-commit hooks run:
 How to
 ------
 
-
 Run tests
 ~~~~~~~~~
 
+.. note::
+
+    You can skip this if only source code behavior remains the same.
+
+Create virtualenv and install dependencies:
+
 .. code:: bash
 
-    # run tests
-    pytest
+    pip install -U -r requirements-test.txt
+
+.. code:: bash
 
+    pytest
 
 Build documentation
 ~~~~~~~~~~~~~~~~~~~
 
+.. note::
+
+    You can skip this if only source code behavior remains the same.
+
+Create virtualenv and install dependencies:
+
+.. code:: bash
+
+    pip install -U -r requirements-docs.txt
+
 Build documentation using Sphinx:
 
 .. code:: bash
@@ -92,21 +112,6 @@ Build documentation using Sphinx:
 Then open in browser ``docs/_build/index.html``.
 
 
-Review process
---------------
-
-Please create a new GitHub issue for any significant changes and
-enhancements that you wish to make. Provide the feature you would like
-to see, why you need it, and how it will work. Discuss your ideas
-transparently and get community feedback before proceeding.
-
-Significant Changes that you wish to contribute to the project should be
-discussed first in a GitHub issue that clearly outlines the changes and
-benefits of the feature.
-
-Small Changes can directly be crafted and submitted to the GitHub
-Repository as a Pull Request.
-
 Create pull request
 ~~~~~~~~~~~~~~~~~~~
 
@@ -204,7 +209,11 @@ How to skip change notes check?
 Just add ``ci:skip-changelog`` label to pull request.
 
 Release Process
-^^^^^^^^^^^^^^^
+---------------
+
+.. note::
+
+    This is for repo maintainers only
 
 Before making a release from the ``develop`` branch, follow these steps: