We need a repo into which we can put the project-navigator data. How
about calling it "project-navigator-data"?
Change-Id: I6e15a8b1f433107b84dd6734f68c77d54a9ff793
This reverts commit 5ddcdce53a.
According to wiredfool on the GitHub issue[1], this was an issue
with manylinux wheels as (non-)uploaded to PyPI and should be
fixed now. Let's see.
[1] https://github.com/python-pillow/Pillow/issues/2478
Change-Id: I6ca17860cd73feda5715589adc31f31c506edf31
Add some clarifications on the project addition process,
in particular mention the possibility to ask the TC for
an early read on the adequation of project scope with the
OpenStack mission, and link the process from the projects
team list for easier discovery.
Change-Id: I26aa7e76a71992c93a3e1e284b09d8a56046e8e2
This resolution provides the use case analysis (step 1)
for the addition of Go (aka golang) as a supported
language under the OpenStack governance model based
on the requirements of the Swift object server and its
data consistency engine.
Change-Id: I001e587b7b04491e748f528b84055ec62364654c
Pillow 4.1.0 as released on April 4 is generating import
errors from the badge generation code:
ImportError: The _imagingft C module is not installed
This triggers test/gate failures on the docs job. Blacklist
this version to unblock governance while we figure out where
the issue exactly comes from.
Change-Id: I8ab8e00ddebfce8ed432405eec6a246352b41a47
Create directory structure for Queens goals so that we
can start proposing goals to it. Add placeholder document
so that Sphinx wouldn't complain about an empty directory.
Change-Id: I67665bc65ac2c4b6647bfe221f43141c819378cf
There is one blueprint to satisfy Community Python 3.5 goal
for Pike in I18n team as a planning artifact.
Change-Id: Idff2812c91f54db762e219674266d7011fe34e0e
Keystone has supported Python 3 for some time now. This commit
includes links to Python 3.5 support for OpenStack Identity-related
projects
Change-Id: Ia7c8eaab15bb79c9ca9bf85ec8265d8f9a275848
shade started as a utility library for Infra, but has grown into a
popular and widely-used client library in its own right. However,
even though it's a solidly maintained library and is licensed
appropriately, it is not seen as an OpenStack deliverable.
While there is no rule that says that OpenStack must produce all of the
software it depends on, and in fact, OpenStack itself consumes a vast
amount of dependencies produced elsewhere, the fact that shade is
specifically focused on the OpenStack End User and the OpenStack APIs
makes it seem like it should be an official output of the OpenStack
project.
This is the first instance of moving a project from Infra to OpenStack,
so there are a few weirdnesses - notably shade publishes docs to
docs.openstack.org/infra not docs.openstack.org/developer and the shade
repo is in openstack-infra/shade not openstack/shade. We're not
suggesting changing the git repo due to it being unneccesary disruption.
The docs can be moved though, as it's easy to host a redirect.
Additionally, from shade's inception we've held that shade's existence
is a bug. However, as much fun as that is to say at conferences, perhaps
the time has come to put the negativity of that trope to rest and
instead focus on continuing to empower our users. It'll likely be a few
years yet before we could 'fix' all of the APIs to make shade unneeded
and even then we'll still have old clouds for a few more years that users
will still need to interact with. So as a general multi-cloud aware library
it'll likely be around for some time and should go ahead and be cared
for and fed.
While we're at it, move requestsexception over too. It was written for
and is used by shade, so having it be part of the same deliverable chain
is preferrable.
Change-Id: I7de2937bc18868c1c0c5c4dc2efbe3ede5865494
Signed-off-by: Monty Taylor <mordred@inaugust.com>
Following the discussion at a recent TC meeting[1], add a link
to the new working group list on the wiki, to improve discoverability
of working groups without having to formally bless them one by one.
[1]
http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-03-14-20.01.html
Change-Id: If5bc519361dcdbe9350c32474278ca68c0c050e2
Create a new repo for the CLI for Placement service implemented as
a plugin for OSC.
Blueprint: placement-osc-plugin
Depends-On: I545ae835d2d0fa52198b15ff006de11c319af236
Change-Id: If996025a0bcce7bbc7a7fa9eb187df71dcfad32b
Add the Consistent Testing Interface documentation for Golang.
This represents a hybrid of the existing Python interface and
common usage in the Go community. The idea being to maintain
some of the beneficial attributes of the native language practices
and still be part of OpenStack process.
Change-Id: Ia4e42cc82e6553b3b9e92f6b17c683fb06f4946c
Splitting a project out into its own team causes problems with the
diversity check if the new project is inside of another project. This is
because there is no {project}-group stackalytics container, only a
{{project}} one.
Trap for the 404 error and re-point to {{project}} if {{project}}-group
is not found.
Change-Id: I68b1b7c4d98810f1d710351e4477fb83ef1fad21
The discussion was upstream:
http://lists.openstack.org/pipermail/openstack-dev/2017-January/110033.html
It seems like we've reached a consensus where DIB would be moved to
OpenStack Infra.
Indeed, most TripleO developers don't maintain DIB anymore while the
project is still active.
Also, there is an amount of overlap between the people working on DIB and on
general Infra-oriented tooling, so we're proposing to move DIB under
Infra umbrella.
Note: TripleO team is currently investigating how we can remove
dib-utils. See https://bugs.launchpad.net/tripleo/+bug/1673144
Change-Id: Ibd166de0069a332ed475c168beb5dd66beb9e90b
After a lot of talk within the Gnocchi team, it appeared to us that Gnocchi,
which has been wisely tagged as 'independent' since its inception, has a lot of
potential usage outside of OpenStack directly.
Being part of the big tent helped the project to be built, but it now appears
that it restrains its adoption and contribution from users outside of the
OpenStack realm.
Therefore this patch un-lists Gnocchi from the OpenStack Telemetry project.
Change-Id: I4979e2186e4c3a84a3c205d69a288443c3e7e463
Depends-On: Ie8c58659bc5ae820bda27414e916b41e38a62f46
Adding the details about planning and completion for the QA
projects. Completion is included as well, since there is nothing
to be done on QA projects to achieve this goal.
Change-Id: I0fd68cc0c240d246904ccfa6d624fb69a95dbfed
Monty Taylor