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

Ghanshyam Mann gmann at ghanshyammann.com
Fri Feb 10 23:12:57 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 8. 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-08-16.00.log.html

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


2. What we completed this week:
=========================
* Defined 2023.2 cycle testing runtime[2]
I have pushed the job template change which needs to wait until 2023.1 release[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
-----------------
* Six open reviews for ongoing activities[5].

OpenInfra Board + OpenStack Syncup Call
--------------------------------------------------
We continued the sync-up call with Board members on Feb 8[6]. We continued the discussion
from the previous meeting on below two topics:

1. Renovate translation SIG i18
Brian gave the updates on this and weblate license is purchased. There is a discussion going
on about hosting the service. Another thing pending on this is to find the maintainer to help
in weblate hosting and translation work. Brian will discuss it with Ian and Seongsoo about it. 

2. Less Diversity (of organization contributing to OpenStack)
This was continued to know if there is any actual progress to solve this problem. We always
discuss spreading the word about benefits to the community and hope more companies
will come forward for help. We are still facing less diversity from organizations involved
in upstream activities. 
Many projects are/will face a single company maintaining them and will end up on retirement
if that company changes their plan. TripelO is a recent example of it. Proposal was to 

Guidelines for using the OpenStack/project release version/name in 1. releasenotes 2. Documentation
-------------------------------------------------------------------------------------------------------------------------
As discussed in the last vPTG, there was some confusion about using the OpenStack release name
or version and project version in release notes and documentation. Slawek proposed guidelines
about it[7] which is up fore review.

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[8] to define the 2023 calendar year
which is nothing but 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 [9]. There is a discussion
also going on in ML[10]. 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[11].

Project updates
-------------------
* Add Cinder Huawei charm[12]
* Add the woodpecker charm to Openstack charms[13]
* Retire xstatic-font-awesome[14]
* mistral adopting PTL model[15]



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[16].
2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [17]
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/+/872232
[3] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/873051
[4] https://etherpad.opendev.org/p/tc-2023.1-tracker
[5] https://review.opendev.org/q/projects:openstack/governance+status:open
[6] https://etherpad.opendev.org/p/2023-02-board-openstack-sync
[7] https://review.opendev.org/c/openstack/governance/+/872769
[8] https://review.opendev.org/c/openstack/governance/+/872233
[9] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup
[10] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848.html
[11] https://etherpad.opendev.org/p/project-health-check
[12] https://review.opendev.org/c/openstack/governance/+/867588
[13] https://review.opendev.org/c/openstack/governance/+/869752
[14] https://review.opendev.org/c/openstack/governance/+/872837
[15] https://review.opendev.org/c/openstack/governance/+/873260
[16] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting

-gmann




More information about the openstack-discuss mailing list