Hello Jay, Thanks for the questions. So my day job involves leading a team that is focused on a number of OpenStack components. We are focused on staying current with releases so the push from me is to do everything upstream. My activities with upstream vary from code contributions, code reviews, helping with cloud infra issues. For a long time I worked with versions that were too old of interest to upstream so I have not been visible. My interest in the TC is around some of the proposed goals and working to advance those. I want to work on how we can have more operators be contributors. I am also interested in exploring where we can make some improvements in giving existing maintainers more cycles back to do what they do best, maintain code. As far as time goes, as an engineer that’s moved to leading other engineers it’s been hard to stop coding but I know that I can be a force multiplier by working with a team. So I would shift more time into TC related work. Thanks. -- Doug
On Aug 29, 2024, at 1:19 PM, Jay Faulkner <jay@gr-oss.io> wrote:
Hello all,
First of all, I'm incredibly happy that the community has stepped up and provided us the opportunity to avoid any issues at all around company affiliations this cycle. Thank you to all the new folks who have run for the TC and helped with this.
My two questions are simple:
How much of your workweek is spent focused on upstream OpenStack? How much of that time will be available to use for TC-related activities?
Thanks, Jay Faulkner