Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-10-15.00.log.html * Next week's meeting is on 17th Feb Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 16th Feb. 2. What we completed this week: ========================= * Reverted the neutron-fwaas deprecation and it is maintained under neutron stadium now[2]. * Removed security-specs from security sig[3]. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 2 out of 9 items are completed. Open Reviews ----------------- * Four open reviews for ongoing activities[5]. Dropping tags framework ------------------------------ yoctozepto has updated the part1 of dropping the tag framework[6] which is ready for review. He will continue working on part2 which is to update the release scripts and openstack navigation sites to remove the tag usage. Z release cycle name ------------------------- TC selection on proposed names is closed and selected names are under trademark checks by foundation, follow the ML[7] for updates. Z release cycle Technical Election --------------------------------------- Nomination for PTL and TC election are in-progress and will be open until 15th Feb[8]. I would like to encourage project leaders to stand for PTL and community members to run for TC. Please add your nomination before deadline[9]. TC position on release cadence ------------------------------------- We had separate call to discuss the next step and TC position on release cadence[10] and as discussed Dan has proposed the new release model as TC resolution[11]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[12]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [13] 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[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/828078 [3] https://review.opendev.org/c/openstack/governance/+/828018 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/openstack/governance/+/822900 [7] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.h... [8] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027117.... [9] https://governance.openstack.org/election/ [10] https://meetpad.opendev.org/OpenStackReleasecadence [11] https://review.opendev.org/c/openstack/governance/+/828777 [12] https://etherpad.opendev.org/p/zuul-config-error-openstack [13] https://review.opendev.org/c/openstack/governance/+/798540 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann