Now that we no longer use 'popularity' as a criteria for including
distros in the PTI, there's no need to include a boring disclaimer about
the relative popularity of RHEL vs. CentOS.
Change-Id: I4c566ff4f9d7fa20eb755061af5dae01ac6e8edb
If there are multiple candidates for chair, using CIVS like we do for
other community elections gives us a way to have private ballots.
Change-Id: Ifcf3e208f9a01fb4d3b84d05b6d6b8964df3b4de
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Be a little more explicit about whether the outgoing or incoming chair
is responsible for a block of tasks. Move the liaison assignment task
to the list of tasks after the incoming chair is confirmed.
Change-Id: Ie9f7b5786e73cda2a55c3978b2058dbd39864689
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Combine the links in the list and remove the redundant use of "latest"
on each line.
Change-Id: I44c19d0c6c39e6624c76bfdf8a3e433b5e22983b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Current language did not make it clear enough that it is
part of the TC's role to paint desirable, achievable goals
for our community as a whole, beyond just per-cycle release
goals.
Change-Id: Ib50f4978db8057d05255bbcf144ac5adee0c1fef
We no longer provide governance tags focused on team "fragility" so
the team_fragility.py is fairly irrelevant for us now and its
presence in this repository may be sending the wrong message. It
also relies on Stackalytics which, at the time of writing, is not
open source.
Change-Id: I842e186f113727badfecff78eb37f74c225c1a22
We are looking at removing team details from the openstack.org/software
pages, and linking to the team pages on governance.o.o/tc instead.
Add a link to team activity metrics (as displayed by Stackalytics)
to the team pages, so that people can still find that data if they care
about it.
Change-Id: I8fa5cf7e77174b9ddab2e184e839159afcec2ad4
This patch formally creates a separate Placement project. It started out
as a sub-project of Nova, but the plan all along was to eventually have
it exist on its own.
Change-Id: I53be2614fe19aa27f47a1dd9901a21d691386db6
Ensure that the charter rule that formal-vote items stay open at least
7 days is applied. This change interprets that rule to mean that if
the majority votes in favor of a change within the 7 day period, the 3
day waiting period will include any of the remaining 7 days. So if the
majority is reached on day 1, the patch must stay open 7 days and if
the majority is reached on day 7 the patch must stay open an
additional 3 days.
Change-Id: I48841570ff19b779b2e35de8218a8f56b408df92
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
openstack-dev was still listed, must have been missed somewhere
along the way. This corrects it to openstack-discuss.
Change-Id: I12486244c8507a943ef039443bb36b5f3518dc28
We'll miss you but it's ok, we got you replaced by something cooler.
Depends-On: I96556f82182a6d147e20bfac6debf361309f2038
Change-Id: Ibd4020c0ec347afd372ab54ed139ff2414ba0a87
When the Ubuntu and CentOS were added in the PTI as "supported
distros", SUSE was already one of the most-popular distros [1],
and therefore deserves listing here.
I don't believe the PTI should refer to "popular" term for distros,
as this isn't a popularity contest. Instead, we should allow any
distribution where community effort is provided.
In this case, openSUSE images are present in infra, and SUSE contributors
are using devstack on openSUSE. Next to that, deployment projects like
openstack-ansible or openstack-helm are making use of openSUSE.
Last, but not least, some projects already take into account openSUSE
in their regular work (for example, when the nova team contacts the
distributions at the beginning of the cycle to know their latest
supported libvirt [2]).
I believe all these arguments are enough to warrant the addition of
openSUSE in the list of distributions.
[1]: SUSE was ranked 4th in that survey (with SLES), after RHEL (3rd).
[2]: http://lists.openstack.org/pipermail/openstack-dev/2018-September/135007.html
Change-Id: I1ac3b7477b5d4cb4af75c319b4232d20b4b4b284
This patch aims to add os_mistral to the OpenStack-Ansible
project.
Depends-On: Ic5cab9cfbdc7b396d23d836224e38ffb5e3af3ba
Change-Id: I82d372d7b93e87c41531f6483473ed223b2058f8
According to zaneb on IRC:
"I'm not sure what heat-cfnclient is still used for...
I suspect just testing. It's in the openstack-dev namespace.
If it's never been released I wouldn't start now..."
Change-Id: Ia6981a5a52a4eaec46b9bf398a063ef6f0ab6cd4
Feedback on this section from a couple of different sources reveals that
the current description fails to make clear that the design goals
represent capabilities that we want OpenStack to present to
applications, and aren't necessarily descriptive of the OpenStack
service implementations themselves. Tweak the wording to help readers
interpret the goals in the correct context.
Change-Id: I5e2fe12dca016f0e9039cdf4290060ed51bc10ce
This patch adds two Ansible roles used to manage client software for
Hardware Security Modules (HSMs). These roles are used in TripleO
to install HSM client software on controller nodes to enable the
PKCS#11 backend for Barbican.
Change-Id: I9195626ea987606400f2e68bfe43ab917b4191dd
Depends-On: Ifd7a46da84fb81eeff7ce2e935cc39007dddbf76
