A vision

During the rocky PTG, we discussed the vision
for ironic. We learned to use the same words.
We reached the same page.

As a result, the week felt very productive.

And so, we should actually write some of this down.

Accordingly the patch proposes a draft vision, as well
as sets the context of the discussions in an attept to
have a point or document that we can refer back to at
a later point in time.

The contents are based off of the Rocky ironic PTG vision
etherpad[1].

[1]: https://etherpad.openstack.org/p/ironic-rocky-ptg-vision

Change-Id: Ie7208cc5aeade96409b658041b9edb4976512ad7

doc/source/contributor/index.rst

@@ -16,6 +16,7 @@ project.
   Priorities <https://specs.openstack.org/openstack/ironic-specs/#priorities>
   Specifications <https://specs.openstack.org/openstack/ironic-specs/>
   Frequently Asked Questions <faq>
+  Contributor Vision <vision>
 
 The following pages describe the architecture of the Bare Metal service
 and may be helpful to anyone working on or with the service, but are written

doc/source/contributor/vision.rst

@@ -0,0 +1,71 @@
+.. _vision:
+
+==================
+Contributor Vision
+==================
+
+Background
+==========
+During the Rocky Project Teams Gathering, The contributors in the room at that
+time took a few minutes to write out out each contributor's vision of where
+they see ironic in five years time.
+
+After everyone had a chance to spend a few minutes writing, we went around the
+room and gave every contributor the chance to read their vision and allow other
+contributors to ask questions to better understand what each individual
+contributor wrote. While we were doing that, we also took time to capture
+the common themes.
+
+This entire exercise did result in some laughs and a common set of words,
+and truly helped to ensure that the entire team proceeded to use the same
+"words" to describe various aspects as the sessions progressed during
+the week. We also agreed that we should write a shared vision, to have
+something to reference and remind us of where we want to go as a community.
+
+Rocky Vision
+============
+
+Common Themes
+-------------
+Below is an entirely unscientific summary of common themes that arose
+during the discussion among fourteen contributors.
+
+* Contributors picked a time between 2020, and 2023.
+* 4 Contributors foresee ironic being the leading Open Source baremetal
+  deployment technology
+* 2 Contributors foresee ironic reaching feature parity with Nova.
+* 2 Contributors foresee users moving all workloads "to the cloud"
+* 1 Contributor foresees Kubernetes and Container integration being the
+  major focus of Bare Metal as a Service further down the road.
+* 2 Contributors foresee greater composible hardware being more common.
+* 1 Contributor foresees ironic growing into or supporting CMDBs.
+* 2 Contributors foresee that features are more micro-service oriented.
+* 2 Contributors foresee that ironic supported all of the possible
+  baremetal management needs
+* 1 Contributor foresees standalone use being more common.
+* 2 Contributors foresee the ironic's developer community growing
+* 2 Contributors foresee that auto-discovery will be more common.
+* 2 Contributors foresee ironic being used for devices beyond servers,
+  such as lightbulbs, IOT, etc.
+
+Vision Statement
+----------------
+
+The year is 2022. We're meeting planning the Z release of Ironic.
+We stopped to reflect upon the last few years of Ironic's growth,
+how we had come such a long way to become the defacto open source
+baremetal deployment technology. How we had grown our use cases,
+and support for consumers such as containers, and users who wished
+to managed specialized fleets of composed machines.
+
+New contributors and their different use cases have brought us closer
+to parity with virtual machines. Everyday we're gaining word of more
+operators adopting the ironic community's CMDB integration to leverage
+hardware discovery. We've heard of operators deploying racks upon racks
+of new hardware by just connecting the power and network cables,
+and from there the operators have discovered time to write the world's
+greatest operator novel with the time saved in commissioning new racks
+of hardware.
+
+Time has brought us closer and taught us to be more collaborative across
+the community, and we look forward to our next release together.