Refresh of the team diversity tags for Sept, 2017:
* designate is no longer diverse-affiliation, due to core reviews
depending too much on one person
* glance now has diverse-affiliation, thanks to contributions from
Red Hat, Huawei, Rackspace, NTT, Verizon, Intel, Fiberhome...
* heat is no longer diverse-affiliation, with 56% of commits coming
from Red Hat
* mistral is no longer diverse-affiliation, with Nokia accounting
for 57% of core reviews and Nokia + Red Hat accounting for 85%
of core reviews
* murano now has diverse-affiliation, thanks to balanced involvement
of ZTE Corporation, AT&T and several others
* rally now has diverse-affiliation, thanks to contributions from
Mirantis, Huawei, GoDaddy, Fujitsu and ZTE Corporation
* swift is no longer diverse-affiliation, with 52% of commits and 60%
of core reviews coming from SwiftStack
* trove is no longer diverse-affiliation, with core reviews currently
being a one-person job
* vitrage is no longer single-vendor, thanks to increased involvement
of ZTE Corporation
Change-Id: I9c61fb6d09a51adbe0a3b4bf2098ec1c98ea33e1
So, this is an idea I've been poking around for a bit. TBH, I ran this
idea through some folks last year but it didn't seem to be the right
moment for it. During the last elections, Matt asked[0] a question about
inclusiveness in the TC, which resulted in myself[1] and ttx[2]
proposing this idea.
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-April/115227.html
[1] http://lists.openstack.org/pipermail/openstack-dev/2017-April/115255.html
[2] http://lists.openstack.org/pipermail/openstack-dev/2017-April/115313.html
Now, down to business. From a practical perspective, most of the
discussions we have at a TC level happen (or should happen) on gerrit
and the mailing list. Lately, most of our meetings have been mostly
useful to rubber stamp things that we've voted on already on gerrit.
This is not to say that meetings are useless and that we don't have any
interesting discussions during these meetings. We do, in fact, have some
more heated discussions during our meetings from time to time but they
are not as freequent as they used to be.
So, instead of having a blocked hour, every week, for the TC meeting,
I'd like to propose we drop the meetings entirely and, instead,
encourage discussion in #openstack-dev. Here's are some things I think
this would give us:
- Possibility for arranging more focused discussions with stackholders
on hours that work best. The smaller the group, the easier it is to
pick a time.
- More open and transparent discussions as it'll force everyone to
discuss things using gerrit and the mailing list instead of waiting
for meetings to happen.
- It'll be easier for folks to stay up-to-date with the on-going
discussions as we'll be reducing one channel of communication and
focus on the other 2 we're already using.
- It'll be easier for folks (especially non-native English speakers) to
participate in the discussions as it'll allow them to take their time
to do it.
Co-Authored: John Garbutt <john.garbutt@rackspace.com>
Change-Id: If70bb95da3216aad7632983f1955d06de1c50521
Change Ie8eb49023e7ec1a847070d4626a63b62e5bb9f36 retired oslo-incubator,
let's reflect this here as well.
Change-Id: Ibd341438d2aa917d1d82b6cebc563d9b33016361
With the reorg on docs.o.o, the projects publish to new places, adjust
all URLs.
Also, use https everywhere.
Change-Id: I28422350e3e37fb4a9b3905e9ed36e3f98fe0c58
This resolution is to allow teams to host meetings in their own
channels. It's the result of the latest thread[0] on the topic and the
recent migration to office-hours that some teams are going through.
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
Change-Id: I631e2597bf818c5e4b2f813da14764d2cb55d0ce
Create new repository for solum tempest plugin to fulfill
Queens Goal "Split Tempest Plugins into Separate Repos/Projects".
Change-Id: Id010d5822f9d8557ef06edc849c4224830d91d8a
Depends-On: I2e127401480c77a5873aaa907d674a1eb7f05109
Nobody self-nominated in time to become the Storlets PTL for the
Queens cycle, therefore the TC must appoint someone or disband
the project team.
The Pike PTL, Eran Rom, has moved to another organization and
can no longer dedicate time to Storlets. Kato Tsuyuzaki has been
the leading contributor for Storlets in the Pike cycle. He is
willing and able to fill the PTL position for the Queens cycle.
Change-Id: I4f1d0277ed34a94965e72a038aff6c84a14a0de8
The current language puts undue pressure on election officials to
immediately notify the TC in the event of a leaderless project, while
also not providing a maximum timeframe for notification, which may leave
a project leaderless for some time in exceptional circumstances.
The replacement language places a clear bound on the notification period,
allowing election officials to take care with their reporting, and the
technical committee to have information in a timeframe that allows a new
PTL to be selected to start with their peers.
Change-Id: Id82afaf24b6fd8f8db90df635debc38a04627791
Murano completed this work toward the end of the Pike-2 milestone.
Included in this patch:
* Link to the final patch in the chain that marks the completion of
this work.
* Associated published documentation.
Change-Id: Ibfafc4b37298a4761f93e05f14a37842b0d3daa5
Create new repository for watcher's tempest plugin to fulfill
Queens Goal "Split Tempest Plugins into Separate Repos/Projects".
Depends-On: I0f227f3b6317b44e2299b3ccbd26e29679f401e9
Change-Id: I4acb68a5f46f1d12b1e74d2203ff61357460eab7