Remove remaining 'big tent' references
The words 'Big tent' have proven to be confusing to people. Their initial meaning was that project teams can join OpenStack if they are "one of us" (as defined by sharing our mission and our principles). However, misinformed people (or people who maliciously choose to be misinformed) took it to mean that there is an absence of rules, and anything and anyone can call themselves an OpenStack project. While most references to the 'big tent' were replaced over time (with references to the 'project structure reform of 2014', or 'official projects' depending on what the words were actually used for), some mentions still remained. This commit cleans them up. “It's a beautiful thing, the destruction of words.” ― George Orwell, 1984 Change-Id: I249ee50e1651997d4248b32a6e30d0737192f119
This commit is contained in:
parent
d5f9dd2375
commit
cd677e60f9
|
@ -7,7 +7,7 @@
|
|||
The Oslo team has moved all previously incubated code from the
|
||||
``openstack/oslo-incubator`` repository into separate library
|
||||
repositories and released those libraries to the Python Package
|
||||
Index. Many of our big tent project teams are still using the old,
|
||||
Index. Many of our official project teams are still using the old,
|
||||
unsupported, incubated versions of the code. The Oslo team has been
|
||||
working to remove that incubated code from projects, and the time has
|
||||
come to finish that work.
|
||||
|
@ -51,7 +51,7 @@ http://specs.openstack.org/openstack/oslo-specs/
|
|||
Current State / Anticipated Impact
|
||||
==================================
|
||||
|
||||
On 5 Aug 2016 a review of git repositories owned by big tent project
|
||||
On 5 Aug 2016 a review of git repositories owned by official projects
|
||||
showed:
|
||||
|
||||
::
|
||||
|
|
|
@ -64,7 +64,7 @@ Reference documentation for the existing WSGI deployments:
|
|||
Current State / Anticipated Impact
|
||||
==================================
|
||||
|
||||
On 12 Jan 2017 a review of git repositories owned by big tent project
|
||||
On 12 Jan 2017 a review of git repositories owned by official projects
|
||||
showed the projects that don't support their control-plane API services deployed
|
||||
via WSGI:
|
||||
|
||||
|
|
|
@ -24,7 +24,7 @@ Application to current deliverables
|
|||
Rationale
|
||||
=========
|
||||
|
||||
In the big tent, all project teams can create stable branches, with the
|
||||
All OpenStack project teams can create stable branches, with the
|
||||
name of their choice. However, some of those branches do not follow the
|
||||
`Stable branch policy`_: some approve backports that modify the behavior
|
||||
of the software, some backport new features, some do not actively backport
|
||||
|
|
|
@ -71,10 +71,10 @@ Starter Kit implies this is not the end point, but just a beginning.
|
|||
Why is this needed?
|
||||
-------------------
|
||||
|
||||
The big tent has been great for expanding the scope and features that
|
||||
are part of OpenStack. However that has scared and confused many
|
||||
members of our community who used the integrated release as their
|
||||
starting point, and see that now going away. Smaller Operators,
|
||||
The 'big tent' project structure reform of 2014 has been great for expanding
|
||||
the scope and features that are part of OpenStack. However that has scared and
|
||||
confused many members of our community who used the integrated release as
|
||||
their starting point, and see that now going away. Smaller Operators,
|
||||
Trainers, Hobbyists all have been asking the question, "where do I
|
||||
start?".
|
||||
|
||||
|
|
Loading…
Reference in New Issue