Repository: modin-project/modin
Pull request: DOCS-#3097: Add section regarding installation from conda-forge
Signed-off-by: izamyati <igor.zamyatin@intel.com>

<!--
Thank you for your contribution!
Please review the contributing docs: https://modin.readthedocs.io/en/latest/CONTRIBUTING.html
if you have questions about contributing.
-->

## What do these changes do?

<!-- Please give a short brief about these changes. -->

- [x] commit message follows format outlined [here](https://modin.readthedocs.io/en/latest/contributing.html)
- [x] passes `flake8 modin`
- [x] passes `black --check modin`
- [x] signed commit with `git commit -s` <!-- you can amend your commit with a signature via `git commit -amend -s` -->
- [x] Resolves #3097
- [ ] tests added and passing
- [ ] module layout described at `docs/developer/architecture.rst` is up-to-date <!-- if you have added, renamed or removed files or directories please update the documentation accordingly -->


Problem statement:
Specify Differentiation Between Different Modin Installs
On Modin documentation, for all different installs (conda, pip, conda modin[ray], conda-forge, etc.(r, ensure user knows what backends/dependencies are supporting. i.e. For AI Kit Modin, ensure user knows OmniSci backend and Ray are uincluded, but not Dask. This way, users are aware of what underlying technical stakc is in their specific installation of Modin, and how that may differ to other install method. Best in a spreadsheet chart form.....

@aregm

Hints from issue discussion:

Commit message: DOCS-#3097: Fix review comments

Signed-off-by: izamyati <igor.zamyatin@intel.com>

Patch to review:
diff --git a/docs/installation.rst b/docs/installation.rst
index a89783fb930..299e83f4495 100644
--- a/docs/installation.rst
+++ b/docs/installation.rst
@@ -2,9 +2,9 @@ Installation
 ============
 
 There are a couple of ways to install Modin. Most users will want to install with
-``pip``, but some users may want to build from the master branch on the `GitHub repo`_.
-The master branch has the most recent patches, but may be less stable than a release
-installed from ``pip``.
+``pip`` or using ``conda`` tool, but some users may want to build from the master branch
+on the `GitHub repo`_. The master branch has the most recent patches, but may be less
+stable than a release installed from ``pip`` or ``conda``.
 
 Installing with pip
 -------------------
@@ -53,6 +53,44 @@ or for different functionalities of Modin. Here is a list of dependency sets for
 
   pip install "modin[dask]" # If you want to use the Dask backend
 
+Installing with conda
+---------------------
+
+Modin releases can be installed using ``Miniconda`` from conda-forge channel. Starting from 0.10.1
+it is possible to install modin with chosen engine(s). Current options are:
+
++---------------------------------+---------------------------+
+| **Package name in conda-forge** | **Engine(s)**             |
++---------------------------------+---------------------------+
+| modin                           | Dask                      |
++---------------------------------+---------------------------+
+| modin-all                       | Dask, Ray, OmniSci_       |
++---------------------------------+---------------------------+
+| modin-dask                      | Dask                      |
++---------------------------------+---------------------------+
+| modin-ray                       | Ray                       |
++---------------------------------+---------------------------+
+| modin-omnisci                   | OmniSci                   |
++---------------------------------+---------------------------+
+
+So for installing Dask and Ray engines into conda environment following command should be used:
+
+.. code-block:: bash
+
+  conda install -c conda-forge modin-ray modin-dask
+
+All set of engines could be available in conda environment by specifying
+
+.. code-block:: bash
+
+  conda install -c conda-forge modin-all
+
+or explicitly
+
+.. code-block:: bash
+
+  conda install -c conda-forge modin-ray modin-dask modin-omnisci
+
 Installing from the GitHub master branch
 ----------------------------------------
 
@@ -112,3 +150,4 @@ Once cloned, ``cd`` into the ``modin`` directory and use ``pip`` to install:
 .. _WSL: https://docs.microsoft.com/en-us/windows/wsl/install-win10
 .. _Ray: http://ray.readthedocs.io
 .. _Dask: https://github.com/dask/dask
+.. _OmniSci: https://www.omnisci.com/platform/omniscidb


Code review comments:
diff_hunk: @@ -53,6 +53,44 @@ or for different functionalities of Modin. Here is a list of dependency sets for
 
   pip install "modin[dask]" # If you want to use the Dask backend
 
+Installing with conda
+---------------------
+
+Modin releases can be installed using ``Miniconda`` from conda-forge channel. Starting from 0.10.1
path: docs/installation.rst
text: @user1:
```suggestion
Modin releases can be installed using ``conda`` from conda-forge channel. Starting from 0.10.1
```
I don't see a point of referencing `miniconda` specifically, that's just a distribution while we're speaking about the tool.