[all][tc] What's happening in Technical Committee: summary 18th Feb, 21: Reading: 5 min

Ghanshyam Mann gmann at ghanshyammann.com
Fri Feb 18 22:30:37 UTC 2022

Hello Everyone,

Here is this week's summary of the Technical Committee activities.

1. TC Meetings:
* We had this week's meeting on 17th. Most of the meeting discussions are summarized below (Completed
or in-progress activities section). Meeting full logs are available

* Next week's meeting is on 24th Feb Thursday 15:00 UTC, feel free to add the topic on
the agenda[1] by 23rd Feb.

2. What we completed this week:
* Z cycle release name [2]

3. Activities In progress:
TC Tracker for Yoga cycle
* This etherpad includes the Yoga cycle targets/working items for TC[3].
2 out of 9 items are completed.

Open Reviews
* Six open reviews for ongoing activities[4].

Release identification and release name
As Zed is the last release for the current alphabet release name iteration.
TC discussed the future release name ideas. Belmiro has proposed the idea
of adding "<year>.<release count>" number to each release. The proposal is up
for review[5]

Switch Keystone back to PTL model
Keystone team proposed to move Keystone from DPL to PTL model[6] with
Douglas Mendizábal as PTL.

Dropping tags framework
yoctozepto has updated part1 of dropping the tag framework[7] which is ready
for review. Elod us updating the release scripts to remove the tag ref.

Z release cycle Technical Election
The nomination for PTL and TC elections is closed and there is no voting required.
TC Campaigning period is open until 22nd Feb[8]. We will be closing the election on 22nd Feb.
There are total 17 projects that missed the nomination, I have created the etherpad to work
on the leaderless projects[9]. There is already late candidacy for 8 projects and 9 projects still
need leaders. Please add your name if you would like to lead those projects.

TC position on release cadence
No other updates from last week, Dan's proposal is under review[10].

Fixing Zuul config error
Requesting projects with zuul config error to look into those and fix them which should
not take much time[11].

Project updates
* Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [12]

4. How to contact the TC:
If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways:

1. Email: you can send the email with tag [tc] on openstack-discuss ML[13].
2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14]
3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel.

[1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting
[2] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027242.html
[3] https://etherpad.opendev.org/p/tc-yoga-tracker
[4] https://review.opendev.org/q/projects:openstack/governance+status:open
[5] https://review.opendev.org/c/openstack/governance/+/829563
[6] https://review.opendev.org/c/openstack/governance/+/829037
[7] https://review.opendev.org/c/openstack/governance/+/822900
[8] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027311.html
[9] https://etherpad.opendev.org/p/zed-leaderless
[10] https://review.opendev.org/c/openstack/governance/+/828777
[11] https://etherpad.opendev.org/p/zuul-config-error-openstack
[12] https://review.opendev.org/c/openstack/governance/+/798540
[13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting


More information about the openstack-discuss mailing list