[nova][elections][ptl] Application for the PTL role
Hello, I would like to run for the PTL election for Nova and Placement. I am fortunate to be employed by Red Hat to work on this project, and I have been doing so for about three years. This means I am quite familiar with the project's processes and codebase, though I wouldn’t call myself an expert. To be honest, I initially thought of becoming a core member before running for this election. However, knowing that Sylvain wants to step down, and after discussing it with him and other members of the community, I realized that becoming PTL, while challenging, is a viable path and a great opportunity. I know this role will push me out of my comfort zone and require me to work on areas where I have less experience. But I believe that sometimes, growth comes from facing new challenges. So, I took a deep breath and decided to write this message. Regarding the future of the project, my goal is not to revolutionize anything. I believe I will need some time to find my footing, and I will do my best to continue in the direction that Sylvain has set. It won’t always be easy, but I trust in the kindness of those involved in this project to support me. I also rely on Sylvain’s mentoring, as he proposed during his candidacy, to ensure a smooth transition. One aspect I intend to be particularly mindful of is supporting contributors in getting their code merged. Having recently merged a major feature (virtiofs) that I carried for a long time, I know how difficult and demanding the process can be—it requires a lot of resilience. That’s why I'll pay attention to making this process smoother and support contributors as effectively as I can. Thanks, René
Hey Rene, just a question around your comment: On 2/6/25 5:45 AM, René Ribaud wrote:
One aspect I intend to be particularly mindful of is supporting contributors in getting their code merged.
Do you have any specific ideas on activating on this idea and getting more review bandwidth? Thanks, Jay Faulkner
Hi Jay, Unfortunately, there is no magic here. Extending the review bandwidth doesn’t seem possible at the moment. However, I see something we should focus on: If a feature misses the release freeze, it still has a "fresh" review. To avoid losing context and focus, we should aim to keep the momentum and try to prioritize it so that it gets merged as early as possible in the next cycle. We should also try to review well ahead of the release freeze to prevent last-minute changes that might cause a feature to slip again. The key is to minimize feature rollovers from cycle to cycle as much as possible, as it can be really demotivating and lead to a loss of self-confidence. At least, that’s how it felt for me. Of course, I understand that there are plenty of valid reasons why this happens, and unfortunately, it will happen again. Le jeu. 6 févr. 2025 à 19:33, Jay Faulkner <jay@gr-oss.io> a écrit :
Hey Rene, just a question around your comment: On 2/6/25 5:45 AM, René Ribaud wrote:
One aspect I intend to be particularly mindful of is supporting contributors in getting their code merged.
Do you have any specific ideas on activating on this idea and getting more review bandwidth?
Thanks,
Jay Faulkner
On 2025-02-07 18:00:35 +0100 (+0100), René Ribaud wrote: [...]
Unfortunately, there is no magic here. Extending the review bandwidth doesn’t seem possible at the moment.
However, I see something we should focus on: If a feature misses the release freeze, it still has a "fresh" review. To avoid losing context and focus, we should aim to keep the momentum and try to prioritize it so that it gets merged as early as possible in the next cycle.
We should also try to review well ahead of the release freeze to prevent last-minute changes that might cause a feature to slip again.
The key is to minimize feature rollovers from cycle to cycle as much as possible, as it can be really demotivating and lead to a loss of self-confidence. At least, that’s how it felt for me.
Of course, I understand that there are plenty of valid reasons why this happens, and unfortunately, it will happen again.
These are all great suggestions! I applaud your desire to dig into options for improving the contributor experience, and also suggest you consider getting involved in the ongoing Bridging the Gap effort. See this earlier thread for links to resources and ideas for where we could use some additional help moving things forward: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... -- Jeremy Stanley
Thanks, Jeremy. I have read the link you provided and would be happy to share feedback in a future *Bridging the Gap* session, if there is one. As a relatively new contributor, I believe I can share some pain points from my experience or things I wish I had known earlier. Best regards. René (Uggla) Le ven. 7 févr. 2025 à 18:53, Jeremy Stanley <fungi@yuggoth.org> a écrit :
Unfortunately, there is no magic here. Extending the review bandwidth doesn’t seem possible at the moment.
However, I see something we should focus on: If a feature misses the release freeze, it still has a "fresh" review. To avoid losing context and focus, we should aim to keep the momentum and
On 2025-02-07 18:00:35 +0100 (+0100), René Ribaud wrote: [...] try
to prioritize it so that it gets merged as early as possible in the next cycle.
We should also try to review well ahead of the release freeze to prevent last-minute changes that might cause a feature to slip again.
The key is to minimize feature rollovers from cycle to cycle as much as possible, as it can be really demotivating and lead to a loss of self-confidence. At least, that’s how it felt for me.
Of course, I understand that there are plenty of valid reasons why this happens, and unfortunately, it will happen again.
These are all great suggestions! I applaud your desire to dig into options for improving the contributor experience, and also suggest you consider getting involved in the ongoing Bridging the Gap effort. See this earlier thread for links to resources and ideas for where we could use some additional help moving things forward:
https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack....
-- Jeremy Stanley
On Thu, Feb 6, 2025 at 5:45 AM René Ribaud <rene.ribaud@gmail.com> wrote:
Hello,
I would like to run for the PTL election for Nova and Placement. I am fortunate to be employed by Red Hat to work on this project, and I have been doing so for about three years. This means I am quite familiar with the project's processes and codebase, though I wouldn’t call myself an expert.
To be honest, I initially thought of becoming a core member before running for this election. However, knowing that Sylvain wants to step down, and after discussing it with him and other members of the community, I realized that becoming PTL, while challenging, is a viable path and a great opportunity.
I know this role will push me out of my comfort zone and require me to work on areas where I have less experience. But I believe that sometimes, growth comes from facing new challenges. So, I took a deep breath and decided to write this message.
Regarding the future of the project, my goal is not to revolutionize anything. I believe I will need some time to find my footing, and I will do my best to continue in the direction that Sylvain has set. It won’t always be easy, but I trust in the kindness of those involved in this project to support me. I also rely on Sylvain’s mentoring, as he proposed during his candidacy, to ensure a smooth transition.
One aspect I intend to be particularly mindful of is supporting contributors in getting their code merged. Having recently merged a major feature (virtiofs) that I carried for a long time, I know how difficult and demanding the process can be—it requires a lot of resilience. That’s why I'll pay attention to making this process smoother and support contributors as effectively as I can.
I can connect with many things you've written here, René! It makes me super happy to see you step up and nominate yourself. The sustainability of our community relies on volunteers taking on the hard job of leadership. It's very encouraging to the entire community when folks nominate themselves for the first time! All the best for the election, and thank you! Huge thanks also to the mentors that make this possible!
Thanks, René
Hi René, Merci, thank you for stepping forward! Cheers, Kees __ Kees Meijs BICT Nefos Cloud & IT <https://nefos.nl/contact> Nefos IT bv Burgemeester Mollaan 34a 5582 CK Waalre - NL kvk 66494931 +31 (0)88 2088 188 <tel:+31882088188> nefos.nl <https://nefos.nl/contact> The information contained in this message is intended for the addressee only and may contain classified information. If you are not the addressee, please delete this message and notify the sender; you should not copy or distribute this message or disclose its contents to anyone. Any views or opinions expressed in this message are those of the individual(s) and not necessarily of the organization. No reliance may be placed on this message without written confirmation from an authorised representative of its contents. No guarantee is implied that this message or any attachment is virus free or has not been intercepted and amended. General terms and conditions ("The NLdigital Terms") apply to all our products and services. On 06-02-2025 14:45, René Ribaud wrote:
Hello,
I would like to run for the PTL election for Nova and Placement. I am fortunate to be employed by Red Hat to work on this project, and I have been doing so for about three years. This means I am quite familiar with the project's processes and codebase, though I wouldn’t call myself an expert.
To be honest, I initially thought of becoming a core member before running for this election. However, knowing that Sylvain wants to step down, and after discussing it with him and other members of the community, I realized that becoming PTL, while challenging, is a viable path and a great opportunity.
I know this role will push me out of my comfort zone and require me to work on areas where I have less experience. But I believe that sometimes, growth comes from facing new challenges. So, I took a deep breath and decided to write this message.
Regarding the future of the project, my goal is not to revolutionize anything. I believe I will need some time to find my footing, and I will do my best to continue in the direction that Sylvain has set. It won’t always be easy, but I trust in the kindness of those involved in this project to support me. I also rely on Sylvain’s mentoring, as he proposed during his candidacy, to ensure a smooth transition.
One aspect I intend to be particularly mindful of is supporting contributors in getting their code merged. Having recently merged a major feature (virtiofs) that I carried for a long time, I know how difficult and demanding the process can be—it requires a lot of resilience. That’s why I'll pay attention to making this process smoother and support contributors as effectively as I can.
Thanks, René
participants (5)
-
Goutham Pacha Ravi
-
Jay Faulkner
-
Jeremy Stanley
-
Kees Meijs | Nefos
-
René Ribaud