Initial structure for registry.fp.o investigation

This commit contains document structure for registry.fp.o to quay.io migration
investigation.

Signed-off-by: Michal Konecny <mkonecny@redhat.com>

docs/initiatives.rst

@@ -9,6 +9,8 @@ Drafts
 .. toctree::
     :maxdepth: 1
 
+    registry_to_quay/index
+
 Completed review
 ----------------
 .. toctree::
@@ -36,4 +38,4 @@ Implemented
     bodhi/index
     package-automation/index
     communishift/index
-    fmn/index
+    fmn/index

docs/registry_to_quay/fedora_images.rst

@@ -0,0 +1,13 @@
+.. _fedora_images:
+
+Fedora Base/Minimal/CoreOS container images
+===========================================
+
+This document contains information about current workflow used to build and publish these container
+images. It also describes changes needed to make it work with quay.io.
+
+Current workflow
+----------------
+
+Changes for quay.io
+-------------------

docs/registry_to_quay/flatpaks.rst

@@ -0,0 +1,13 @@
+.. _flatpaks:
+
+Fedora Flatpaks
+===============
+
+This document contains information about current workflow used to build and publish Fedora flatpaks.
+It also describes changes needed to make it work with quay.io.
+
+Current workflow
+----------------
+
+Changes for quay.io
+-------------------

docs/registry_to_quay/index.rst

@@ -0,0 +1,65 @@
+Migrate registry.fedoraproject.org to quay.io
+=============================================
+
+Purpose
+-------
+
+This investigation is looking into service `quay.io <https://quay.io/>`_ and how can we utilize
+it for the projects hosted on `registry.fedoraproject.org <https://registry.fedoraproject.org/>`_. It should also resolve if this is work should be initiative.
+
+Resources
+---------
+
+* Fedora Infrastructure ticket: https://pagure.io/fedora-infrastructure/issue/10386
+
+Requirements
+------------
+
+* Multi Arch containers (Already supported on quay.io)
+* OCI images (Already supported on quay.io)
+* Web interface (Quay.io already has web interface)
+* Integrate Quay.io in current workflow
+* Must not affect users of images
+* `candidate-registry <https://candidate-registry.fedoraproject.org/>`_ must be moved as well
+
+Nice to have
+------------
+
+* Staging namespace on quay.io
+
+Risks
+-----
+
+* There is a `pull rate limit <https://docs.quay.io/issues/429.html>`_ per second on IP address on quay.io. This could cause issues in the future, but current load should be easily handled.
+
+Investigation
+-------------
+
+The investigation is separated to multiple parts based on the current artifacts hosted on registry:
+Fedora flatpaks, Fedora container images (base, minimal, coreos) and toolbox images.
+
+.. toctree::
+    :maxdepth: 1
+
+    flatpaks
+    toolbox
+    fedora_images
+
+
+
+Conclusions
+-----------
+
+This is a conclusion for investigation. It should contain output and recommendations.
+
+Proposed Roadmap
+----------------
+
+* Step 1 - Migrate registry.fp.o
+* Step 2 - ???
+* Step 3 - Profit
+
+Estimate of work
+----------------
+
+The estimate for this work.

docs/registry_to_quay/toolbox.rst

@@ -0,0 +1,13 @@
+.. _toolbox:
+
+Fedora Toolbx images
+====================
+
+This document contains information about current workflow used to build and publish these container
+images. It also describes changes needed to make it work with quay.io.
+
+Current workflow
+----------------
+
+Changes for quay.io
+-------------------