Adds the API WG repository under the list of repos to be controlled
by the TC. The API WG is a cross project workgroup that aims to
provide guidelines and standards for all openstack projects for
desgon of their REST APIs.
Related project-config change: Iecff31860eb36d124ebcc573d20f2a72dabdc8c4
One of the takeaways from the exercise about kilo priorities was oslo is
not the right home for all cross project discussions. We need a new home
for cross project specs, and since the TC is our governing technical
committee this repo should be under there management.
The specific scope and model for this repo is left up to the TC to
decide. Although I am in favor of using this for specs that are not limited
to a just a few projects (although not every project may hit the issue
the spec is addressing at the same time) and using this as recommended
guidelines. For example having a spec on doing API microversioning would
be useful as several projects hope to implement this and it would be
ashame if they all did it slightly differently. Another example is
logging standards: what debug,info etc should consist of.
Related project-config change: Id9393dfc2c7f1f883a5f20d85f7ecb79e2c52063
The project-config repo is a split of the project configuration
data from the config repo.
Subunit2sql is a new effort to help characterize individual test
failures in a RDBMS.
- Mostly those authors from the Architecture Design Guide book sprint
who had no other commits in Juno. We use a separate book sprint tool
just for book sprints, then bring in to the repo in bulk.
- Egle Sigler gave us the OpenStack Command Line cheat sheet which we added.
- until https://bugs.launchpad.net/openstack-org/+bug/1373101 is resolved with Sebastian, removing him so they can run electorate roll script
Similar to the python-keystoneclient-kerberos auth plugin, the federation
auth plugin for keystoneclient requires external dependencies that should
not be required for all installations of keystoneclient. Therefore this
plugin has been added as a separate repository and package (on pypi).
At its July 2014 meeting, the OpenStack Foundation Board of Directors
heard information about the impact and options to address the
OpenStack Contributor License Agreement. One of the questions raised
was whether the issues being brought forward were simply the opinion
of one member of the Board.
This resolution clarifies that the TC believes that the current CLA is
problematic and the DCO should be considered instead.
There was a typo in repository name - `glance.store` instead of
`glance_store`. To ensure, see repository location at github .
As discussed on our mailing list, I'd like to treat juno co-authors
for Compute ATCs. This is the simplest way to achieve that.
I have been asked to verify the foundation membership status of the
various people proposed in this patch. There is a comment per
person which does that. If the person has a commit _ever_ in an
incubated or graduated repository, then I consider them to be a
foundation member. For those authors where that is not true I have
hand verified their foundation profile id.
I have also been asked to _not_ generate this for other programs,
so I have stopped doing that and gone back to just doing Compute.
Other PTLs can do this for their programs if they desire, using
the script I will propose in a separate change.
Add new ha-guide to Documentation program, this is a split
from the openstack-manuals repository.
See https://review.openstack.org/#/c/121426/ for the config change.
Zaqar is a messaging service which provides support for different
messaging patterns and messaging related semantics. Mentioning `queue`
in the service codename and description misleads people from what the
service goal actually is.
Several things have changed since last the Project Testing Interface
was approved. It seems like a good idea to formally approve the current
state of the world before suggesting new changes.
This text was approved by the PPB way back in OpenStack's history. There
are several things which have changed and have not been recorded in it,
and there is a new change that should be made. For now, this is verbatim
what was voted on in the past. Changes will follow to update to current
Jaromir and Liz have continued to provide significant UX input and
design for features being contributed to Horizon. Several features
reflect their contributions. The project would suffer without their
ongoing contribution and I would like their efforts to be formally
Authentication and authorization is always closely followed by auditing
how the user obtained that authorization and what the user does with
As OpenStack's approach to auditing has matured, it has become clear
that that there is a regular cross-pollination of contributors and
stakeholders between the two projects, making it appropriate to
officially integrate auditing into the Identity program's mission.
As a result, this change also moves the PyCADF library to the Identity
program, which provides OpenStack's auditing data model.