Note: Boy ADD is fun. I thought I hit send on this days ago…. hey is that a squirrel outside my window?? So this has been an area of interest to me and something I’ve been trying to focus on this past year. I feel as if its a bit different in OpenStack then other open source projects. This is mostly because OpenStack is a series of projects under one governance umbrella. Those individual projects might be connected by different mechanisms. Sometimes they will literally use each other’s APIs but in other cases the same contributors might use both and that is their only connection or even be competing projects. Of course many other projects have similar situations with driver backends but this can be multiple in OpenStack. That being said it’s not an insurmountable challenge. Some things I believe we need to improve on are: - Ease of involvement/contribution. There are a number of projects where the barrier to entry is quite high. We’ve had people from OpenInfra donor organizations speak to the TC about getting patches merged from their organization. Patches which still remain unmerged. - Tooling / Documentation improvements. We’ve discussed this at a previous TC meeting before. Back when OpenStack had its own docs team it was possible to maintain custom themes and other supporting pieces. Today? Old release docs often document search results with a banner at the top which states its an out of date release with a link that takes you to the main docs home page. Many libraries have very minimal information available for them and what they do have is incomplete but gives a sense of completeness. - Core members unwilling to grow the number of core members or consider other models to graduate contributors towards core membership. I’ve heard from multiple projects that they do not have the cycles to review patches or they don’t know how to test them. But when you look at the patch there might be a handful of +1 reviews on it or detailed comments from the author about testing. There’s no way to differentiate a drive by +1 vs an active contributor doing reviews that other core members acknowledge as providing good reviews. Unfortunately much of this is working with the individual projects instead of something the TC can directly address across all projects at once. But I do believe its something the TC should strive to work on with those projects. — Doug
On Aug 26, 2025, at 1:15 AM, Goutham Pacha Ravi <gouthampravi@gmail.com> wrote:
Hello Candidates,
I'd like your view on handling a project team that is essential to the OpenStack ecosystem but is struggling with a lack of active contributors or a sustainable governance?
Thanks, Goutham
On Wed, Aug 20, 2025 at 4:52 PM Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Developers, The TC Election Campaigning Period has now started[1]. During the next couple days, you are all encouraged to ask the candidates questions about their platforms[2], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election.
Candidates, Each of you has posted a platform[2], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise.
[1] https://governance.openstack.org/election/ [2] https://opendev.org/openstack/election/src/branch/master/candidates/2026.1/T...
Ian Y. Choi & Slawek Kaplonski, on behalf of election officials.