openstack/governance
Code Issues Proposed changes

Propose an update to the OpenStack mission statement.

Browse Source 
This patch is a follow-up to our previous resolution suggesting an
update to the OpenStack mission statement.  The OpenStack Foundation
Board of Directors had feedback and requested it be discussed further on
the foundation mailing list.  This version reflects the outcome of that
discussion.

Change-Id: I16a649872414099b394ec1543fb6e73e7de72151
This commit is contained in:
Russell Bryant 2016-02-17 13:41:44 -05:00
parent a690a0efc9
commit bbf89e0aea
1 changed files with 35 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
resolutions/20160217-mission-amendment.rst Normal file
View File

@ -0,0 +1,35 @@
========================================
2016-02-17 OpenStack Mission amendment
========================================
.. note::
This is an update to :doc:`20160106-mission-amendment` in response to
feedback from the OpenStack Foundation Board of Directors and the following
`discussion on the foundation mailing list
<http://lists.openstack.org/pipermail/foundation/2016-February/002263.html>`_.
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 a ubiquitous Open Source Cloud Computing platform that is
easy to use, simple to implement, interoperable between deployments,
works well at all scales, and meets the needs of users and operators of
both public and private clouds.