On Fri, Oct 24, 2025 at 1:19 PM Jean-Philippe Jung <jjung@redhat.com> wrote:
Hi,
I am seeking help from the TC to raise the urgency of this work across all OpenStack projects and to help me lead an effort to reduce the number of cryptographic modules used in OpenStack (my personal opinion is that there should be no more than five).
Doing this may involve work in each OpenStack Project team; and I can help organize this effort. I'm seeking the following from the TC and/or project teams: Portions of this work will be isolated to specific repositories managed by a project team, while others will involve "cross-project" synchronization. What vehicles can we use to have a "call-to-action" for project teams to get someone to look into their specific projects? How can we go about community wide collaboration?
I've created a document [1] that I assembled from AI analysis of part of the OpenStack code. It gives an overall view of the problem we face.
Thank you for starting this discussion, JP. I've added a topic to the TC's PTG for 1600 UTC on Friday, 31st Oct 2025. I hope you'll be able to share your findings there briefly and invite opinions in-sync. Our vehicle for driving cross project work has been via the Community Goals framework: https://governance.openstack.org/tc/goals/ If we have one or more objectives, this can be proposed as one, and will require a "goal champion" - someone that'll help us gather requirements, and coordinate efforts to complete the goal. Some goals in the past have spawned new groups - either as Pop Up Teams or SIGs (https://governance.openstack.org/tc/reference/comparison-of-official-group-s...).