openstack/governance
Code Issues Proposed changes
9e77ed6816
governance/resolutions/20160217-mission-amendment.rst
James E. Blair 0d232dba24 Preserve superseded resolutions 
Rather than directly amending a previously-passed resolution, the TC
has decided the change should be a new resolution.

For the stackforge resolution, this commit adds the text of the
updated resolution as a new resolution with some introductory
explanatory text noting what the update is and the reason for it.
It also reverts the text of the original resolution to that which
was originally passed and adds a new section at the bottom of the
original resolution which indicates it is amended by a subsequent
resolution and links to it.

The superseded resolutions are placed in a specific folder for
clarity. The same process was applied to the Mission statement
resolution.

Change-Id: I446d0797554311b199fce999a7469dbf4e3a2d30
2016-06-16 16:52:34 +02:00

1.6 KiB
Raw Blame History

2016-02-17 OpenStack Mission amendment

Note

This is an update to 20160106_mission_amendment in response to feedback from the OpenStack Foundation Board of Directors and the following discussion on the foundation mailing list.

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.