[all][tc] What's happening in Technical Committee: summary 28th Jan, 21: Reading: 5 min
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-01-27-15.00.log.html
* Next week's meeting is on 3rd Feb Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 2nd Feb.
2. What we completed this week: ========================= * "FIPS compatibility and compliance" community-wide goal proposal is merged[2] * Renamed Skyline repo to openstack/ namespace[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 ----------------- * 3 open reviews for ongoing activities[5].
Renaming all `master` branches on all repos to `main` --------------------------------------------------------------- lourot brought this topic and we discussed if we want to do that. Key point here is how much effort it will take to do for all the existing repo in term of make it working in CI/integration testing tooling/other scripts or not. And we should do it for new repo only. All these are unknown as of now. As first step, lourot will try the project-config importing of dummy project with 'main' branch from GitHub. Based on that, we will discuss it further.
Z release cycle name ------------------------- Name nomination is closed, election for proposed names are in-progress. Follow the ML thread for updates[6].
Z release cycle Technical Election --------------------------------------- Election schedule is under review [7], please review and add your feedback.
Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[8].
OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[9] and Rico will inform you about the next meeting details.
TC position on release cadence ------------------------------------- Dan started the skip level upgrade in grenade and made its working for stable/wallaby to master[10]. TC is planning to meet and discuss the release cadence on 3rd Feb 16 UTC.
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] https://governance.openstack.org/tc/goals/proposed/fips.html [3] https://review.opendev.org/c/openstack/governance/+/826243 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.h... [7] https://review.opendev.org/c/openstack/election/+/825017 [8] https://review.opendev.org/c/openstack/governance/+/822900 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245.... [10] https://review.opendev.org/c/openstack/grenade/+/826101 [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
-gmann
participants (1)
-
Ghanshyam Mann