openstack/governance
Code Issues Proposed changes

Merge "Remove remaining 'big tent' references"

Browse Source
This commit is contained in:
Jenkins
2017-07-11 07:54:03 +00:00
committed by Gerrit Code Review
parent 3681af4d98 cd677e60f9
commit 04c9047fe3
4 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
goals/ocata/remove-incubated-oslo-code.rst
View File

@@ -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:
::

2
goals/pike/deploy-api-in-wsgi.rst
View File

@@ -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:

2
reference/tags/stable_follows-policy.rst
View File

@@ -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

8
reference/tags/starter-kit_compute.rst
View File

@@ -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?".