[all][tc] What's happening in Technical Committee: summary 2023 Feb 17: Reading: 5 min

Ghanshyam Mann gmann at ghanshyammann.com
Sat Feb 18 01:18:26 UTC 2023


Hello Everyone,

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

1. TC Meetings:
============

* We had this week's meeting on Feb 15. Most of the meeting discussions are summarized
in this email. The meeting logs are available
@ https://meetings.opendev.org/meetings/tc/2023/tc.2023-02-15-16.00.log.html

* The next TC weekly meeting will be on Feb 22 Wed at 16:00 UTC, Feel free to add the
topic to the agenda[1] by Feb 21.


2. What we completed this week:
=========================
* Guidelines for using the OpenStack/project release version/name in 1. releasenotes 2. Documentation[2]
* Retire repo from the Governance repo - Retire xstatic-font-awesome[3]


3. Activities In progress:
==================
TC Tracker for the 2023.1 cycle
-------------------------------------
* Current cycle working items and their progress are present in the 2023.1 tracker etherpad[4].

Open Reviews
-----------------
* Seven open reviews for ongoing activities[5].

Deprecation process for TripleO
--------------------------------------
You might have seen the ML discussion for TripleO deprecation[6]. TripelO release model is
a little different where they do have stable branches till stable/wallaby and after that, it was
an independent release. But in the independent release model also, stable/zed branch was cut.
With the TripleO deprecation, the team can maintain only till stable/wallaby. This makes the
situation a little difficult where we do not have the best possible way to deprecate/retire stable/zed.
TC discussed it but could not find any suitable options other than maintaining the stable/zed also.
James will be checking this option with TripleO team and updating the ML thread.

Election updates
--------------------
Technical election nomination for the next cycle has been closed[7]. Even though there is no poll
required in PTL as well as in TC elections, the TC campaigning is going on[8] where you can ask
question to the TC candidates.

Defining 2023 upstream investment opportunities
------------------------------------------------------------
Every calendar year, TC defines the upstream investment opportunities where we need help
and the organization can help. I have pushed the patch[9] to define the 2023 calendar year,
which is continuing last year's opportunities. Please let TC know if any of the areas/projects
you think need help and should be added to this list.

Cleanup of PyPI maintainer list for OpenStack Projects
----------------------------------------------------------------
The audit process is going on and a few projects have been completed [10]. There is a discussion
also going on in ML[11]. JayF is working on an email template which can be used to communicate
to additional developers to transfer the ownership to 'openstackci' account and remove them from
the maintainer's list.

The process to find the less active projects early in the cycle:
------------------------------------------------------------------------
No update this week. JayF started the etherpad to collect the data and define the criteria to help
in this process[12].

Project updates
-------------------
* Add Cinder Huawei charm[13]
* Add the woodpecker charm to Openstack charms[14]
* Retire xstatic-font-awesome[15]
* mistral adopting PTL model[16]
* Add xstatic-angular-fileupload as Horizon team deliverables[17]


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[18].
2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [19]
3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel.

[1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions
[2] https://review.opendev.org/c/openstack/governance/+/872769
[3] https://review.opendev.org/c/openstack/governance/+/872837
[4] https://etherpad.opendev.org/p/tc-2023.1-tracker
[5] https://review.opendev.org/q/projects:openstack/governance+status:open
[6] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032083.html
[7] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032240.html
[8] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032241.html
[9] https://review.opendev.org/c/openstack/governance/+/872233
[10] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup
[11] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848.html
[12] https://etherpad.opendev.org/p/project-health-check
[13] https://review.opendev.org/c/openstack/governance/+/867588
[14] https://review.opendev.org/c/openstack/governance/+/869752
[15] https://review.opendev.org/c/openstack/governance/+/872837
[16] https://review.opendev.org/c/openstack/governance/+/873260
[17] https://review.opendev.org/c/openstack/governance/+/873845
[18] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting

-gmann



More information about the openstack-discuss mailing list