This is the starting point for the "ideas" project.
"ideas" is a repository where everyone can submit their ideas for
global OpenStack changes.
It is the follow up of a discussion in the last summit in Shanghai,
where we discussed the lack of an easy way to browse and search history
of all the (crazy) ideas for OpenStack floated on the mailing lists.
We established (due to recurring topics) that the MLs are not really
appropriate for this searching and revision control.
openstack/openstack is a technical repository that contains
references for other changes in openstack official repositories.
To avoid an unnecessary rename, we should adopt it as a TC repo.
The openstack/arch-wg was used by the Architecture workgroup,
a TC workgroup that ceased operations a couple of years ago.
To avoid an unnecessary rename, we should adopt it as a TC
The openstack/governance-website drives the top index content
for governance.openstack.org, and is driven by the TC chair.
It's a bit of an oversight that it's not listed yet as a TC repo.
The api-wg became the api-sig so this change moves the repo reference
from technical-committee-repos to sigs-repos. In the process the name
of the repo (which changed a few weeks ago) is updated.
The goal-tools repository includes tools for use by goal
champions. Since goals are a TC-driven initiative, it makes sense to
mark the repository as owned by the TC.
Signed-off-by: Doug Hellmann <email@example.com>
This commit fixes all the yamllint issues being reported by the validate
job. Now that we run this job nv in the gate we should clean up the
current output so that we can catch new issues on incoming patches.
The TC has a subgroup working on documentation for project teams
as OpenStack grows to encompass more projects. This is a repo to
host that documentation.
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