The static file format that we've held for a while fails to scale
at some point, as run out of ways to split data. This patch
converts it all into a YAML file.
Change-Id: I4264c663d82077940873e2d3a1564b4e232daa9e
Show who has voted or not on each change, in case someone needs to be
pinged.
Change-Id: I67c3566b3e7c22419dbc60bb585ef20b8a6d499b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We have the data to know who the release PTL is, so we can look it
up. We don't have a name for the VMT or stable SIG, so we have to
continue to hard-code those.
Change-Id: Ia87fd65f25f709d49fd6bad365e4c1607f878d8f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
I would like to nominate myself to serve as the chair of the TC
for the upcoming session.
First of all, I'd like to thank Doug for his service as the chair
for the past few periods of time. He has been instrumental in
helping our TC, provided a lot of leadership and guidance and
he was very instrumental in helping me understand this role by
helping him as vice-chair.
We have a lot to work on as a team and I would like to explore
more and new options to communicate more often and follow-up on
our projects within the TC. As time goes by, the role of the TC
to validate new projects seems to have decreased, and it seems
that the community would like a more "hands-on" involvement with
actionable 'artifacts' that come out of the TC.
That's not to say that we haven't built any of that over the past
few months, we've come up with a lot of very important documents
to help define a lot of things, but I'd like us to focus on working
with our teams to help push OpenStack with our community in the
best and most succcesful path possible.
We have a community of long term contirbutors that we trust to know
the best decision to take, however, there is still a lot of doubt
from our new-comers and perhaps a lot of questions on "how should
we deal with this?" -- as a technical committee, we need to be there
for our developers to help steer them in the best direction.
With the changes within the OSF, it's also more important than ever
to be aware of what is happening on the foundation level on how it
affects us, as well as working with other foundation-level projects
to find value that benefits all of us (which we already do, in the
case of Zuul).
Thank you for your consideration.
Change-Id: I92c867c7237295bc6fea731b656d5d2c69e01926
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
