Nowadays, Technical Writing SIG is lacking maintainer and the
current Chair Stephen Finucane would not be able to continue
leading this SIG.
In TC weekly meetings and PTG[1], we decided to merge this
SIG responsibility in TC and a few repos which are related
to upstream institute training will be moved to First Contact
SIG.
One repo 'training-labs' is left for now, which will be called
for the maintainer, and if there is no one, we can retire it.
We are not even sure who is using it. Upstream training and CoA
do not use this repo.
[1] https://etherpad.opendev.org/p/tc-yoga-ptghttp://lists.openstack.org/pipermail/openstack-discuss/2021-October/025554.html
Needed-By: https://review.opendev.org/c/openstack/governance-sigs/+/815868
Change-Id: Ie745e91e6a0edb8adf6ce5b36dbef22a338d8ca5
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.
Depends-On: https://review.opendev.org/#/c/701530
Change-Id: I8aea45dbd4b52dfedd31965764aa2cf0673f6c3f
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.
Change-Id: I1abbbd71bfde755d6cd4e4fdaccb8a1d44afbfaa
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
repo.
Change-Id: Ibeec53fb1a2841027b921e087c9cdb9ad64a5f2b
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.
Change-Id: I5673e1b61ce4f622aff910169c1c568b786a8343
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.
Change-Id: Id947ad72b1ffeb9d1b0065dd1964be19fa557a81
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.
Change-Id: If916d30b4e343cbb3b40d46af06edc684e83db2f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We need a repo into which we can put the project-navigator data. How
about calling it "project-navigator-data"?
Change-Id: I6e15a8b1f433107b84dd6734f68c77d54a9ff793
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.
Change-Id: Iac9cd534d177f975ce524fa7a945887dd0fa1806
This is like the api-wg, but a dedicated repository for doing the
service types authority.
Depends-On: I75f7066dca7b26204fa7a0196fd019c1b33aa3a3
Change-Id: I1a28446fc3279b69f05f8089d30b05b6e8d14801
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.
Change-Id: Ib4f9934ca6d0946ca3f633f95c9336227bd6de28
Depends-On: I46292749d645f5f8e99c4f52c975c79bb446c6db
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
Change-Id: I8c708bcb4ba9a818b6aecdd51e65619c66bb69e1
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
Change-Id: I498a304057043a54370b132f2153a4c65840639c
Since the TC isn't a program, create a new YAML file listing which
repositories are owned by the TC.
Change-Id: I142ac8ff7ba6b1d4c8f6a7bfeef68b1739f23f6c
Ghanshyam Mann