Add Brian Haley (haleyb) candidacy for Neutron PTL
Change-Id: I76cb201cdc173ac89ee7b32e16053c629d646c2f Signed-off-by: Brian Haley <haleyb.dev@gmail.com>
This commit is contained in:
37
candidates/2026.1/Neutron/haleyb.dev@gmail.com
Normal file
37
candidates/2026.1/Neutron/haleyb.dev@gmail.com
Normal file
@@ -0,0 +1,37 @@
|
||||
Hello Openstack Community,
|
||||
|
||||
I am writing to submit my candidacy for the Neutron PTL position
|
||||
during the 2026.1 cycle, continuing in my role from the 2025.2,
|
||||
2025.1, 2024.2 and 2024.1 cycles.
|
||||
|
||||
My priorities as PTL are the same as in previous cycles:
|
||||
|
||||
* Always make sure the stable branches are consumable downstream.
|
||||
With the introduction of unmaintained branches, the community has
|
||||
extended the lifecycle in a new direction. As a member of the
|
||||
downstream community that relies on these branches, I will continue
|
||||
to dedicate part of my time to reviewing backports and keeping them
|
||||
maintained.
|
||||
|
||||
* Continue to make sure Neutron stays ahead of governance timelines,
|
||||
for example, completing eventlet deprecation ahead of schedule.
|
||||
|
||||
* Continue pursuing CI stability.
|
||||
|
||||
* Reduce the bug backlog. Over the past cycle we were able to keep
|
||||
our bug backlog constant through the continued great work of a lot
|
||||
of contributors. Having a reduction, either through verification
|
||||
or bug fixes, continues to be one of my goals.
|
||||
|
||||
* Introduce features for new use cases as they arise. There is a
|
||||
constant submissions of RFEs to the project, and making sure
|
||||
we address these use cases from, sometimes, new users of Openstack
|
||||
can only help us to grow the community.
|
||||
|
||||
* Making sure we are good stewards of gate resources.
|
||||
|
||||
* Always welcome new contributors.
|
||||
|
||||
Thanks for your support.
|
||||
|
||||
-Brian Haley (haleyb, haleyb.dev@gmail.com)
|
Reference in New Issue
Block a user