Add interop and endusers to OpenStack Mission
This resolution suggests the adoption of a slightly different wording for the OpenStack Mission, to include interoperability and end users needs. Change-Id: I9fca919dad85a79af8ae0f94f46bdd3fb2026197
This commit is contained in:
parent
8e5fe36561
commit
6bbdddfd77
29
resolutions/20160106-mission-amendment.rst
Normal file
29
resolutions/20160106-mission-amendment.rst
Normal file
@ -0,0 +1,29 @@
|
|||||||
|
========================================
|
||||||
|
2016-01-06 OpenStack Mission amendment
|
||||||
|
========================================
|
||||||
|
|
||||||
|
The OpenStack Mission is a critical statement which defines what the
|
||||||
|
OpenStack project is about and the goals we, as a community, aspire to reach.
|
||||||
|
As such, modifying it requires buy-in from all sides of the project
|
||||||
|
governance.
|
||||||
|
|
||||||
|
As of today, the OpenStack Mission is the following::
|
||||||
|
|
||||||
|
to produce the ubiquitous Open Source Cloud Computing platform that will
|
||||||
|
meet the needs of public and private clouds regardless of size, by being
|
||||||
|
simple to implement and massively scalable.
|
||||||
|
|
||||||
|
It appears that the current statement fails to mention two critical elements:
|
||||||
|
promoting interoperability and serving end users. Those two themes are already
|
||||||
|
recognized as key goals of the OpenStack Community, but yet they are missing
|
||||||
|
from our mission statement.
|
||||||
|
|
||||||
|
Therefore, the Technical Committee suggests that we make a small change to
|
||||||
|
the OpenStack Mission statement to include those two elements. It suggests
|
||||||
|
the adoption of the following wording::
|
||||||
|
|
||||||
|
to produce the ubiquitous Open Source Cloud Computing platform that enables
|
||||||
|
building interoperable public and private clouds regardless of size, by being
|
||||||
|
simple to implement and massively scalable while serving the cloud users'
|
||||||
|
needs.
|
||||||
|
|
@ -5,6 +5,15 @@
|
|||||||
When a motion does not result in a change in a reference doc, it can
|
When a motion does not result in a change in a reference doc, it can
|
||||||
be expressed as a resolution.
|
be expressed as a resolution.
|
||||||
|
|
||||||
|
2016
|
||||||
|
====
|
||||||
|
|
||||||
|
.. toctree::
|
||||||
|
:maxdepth: 1
|
||||||
|
:glob:
|
||||||
|
|
||||||
|
2016*
|
||||||
|
|
||||||
2015
|
2015
|
||||||
====
|
====
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user