[tripleo] Proposing Rabi Mishra part of tripleo-core
Hi folks, Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration. Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team. Thanks Rabi for your hard work! -- Emilien Macchi
+1 On Tue, Jul 14, 2020 at 7:39 AM Emilien Macchi <emilien@redhat.com> wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work! -- Emilien Macchi
+1000 I thought he already was core ? used to be? On Tue, Jul 14, 2020 at 4:31 PM Emilien Macchi <emilien@redhat.com> wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work! -- Emilien Macchi
On 7/14/20 3:30 PM, Emilien Macchi wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work!
+1
-- Emilien Macchi
-- Best regards, Bogdan Dobrelya, Irc #bogdando
On Tue, Jul 14, 2020 at 9:11 AM Bogdan Dobrelya <bdobreli@redhat.com> wrote:
On 7/14/20 3:30 PM, Emilien Macchi wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work!
+1
-- Emilien Macchi
Thanks for raising this Emilien!! Thank you to Rabi for your excellent work! +1
-- Best regards, Bogdan Dobrelya, Irc #bogdando
Hi, +1. Thank you Rabi! вт, 14 июл. 2020 г. в 17:53, Wesley Hayutin <whayutin@redhat.com>:
On Tue, Jul 14, 2020 at 9:11 AM Bogdan Dobrelya <bdobreli@redhat.com> wrote:
On 7/14/20 3:30 PM, Emilien Macchi wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work!
+1
-- Emilien Macchi
Thanks for raising this Emilien!! Thank you to Rabi for your excellent work! +1
-- Best regards, Bogdan Dobrelya, Irc #bogdando
-- Sergii Golovatiuk Senior Software Developer Red Hat <https://www.redhat.com/> <https://www.redhat.com/>
Absolutely, +1 On Tue, Jul 14, 2020 at 08:35 Emilien Macchi <emilien@redhat.com> wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work!
-- Emilien Macchi
-- Kevin Carter IRC: Cloudnull
+1 On Tue, Jul 14, 2020 at 10:52:22PM -0500, Carter, Kevin wrote:
Absolutely, +1
On Tue, Jul 14, 2020 at 08:35 Emilien Macchi <emilien@redhat.com> wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work!
-- Emilien Macchi
-- Kevin Carter IRC: Cloudnull
-- Michele Baldessari <michele@acksyn.org> C2A5 9DA3 9961 4FFB E01B D0BC DDD4 DCCB 7515 5C6D
Of course +1! On 7/14/20 3:30 PM, Emilien Macchi wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work! -- Emilien Macchi
-- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/
+1 I thought he was already a core. On Wed, Jul 15, 2020 at 7:05 AM Cédric Jeanneret <cjeanner@redhat.com> wrote:
Of course +1!
On 7/14/20 3:30 PM, Emilien Macchi wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work! -- Emilien Macchi
-- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/
+1 absolutely! On Wed, 15 Jul 2020, 14:07 John Fulton, <johfulto@redhat.com> wrote:
+1 I thought he was already a core.
On Wed, Jul 15, 2020 at 7:05 AM Cédric Jeanneret <cjeanner@redhat.com> wrote:
Of course +1!
On 7/14/20 3:30 PM, Emilien Macchi wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work! -- Emilien Macchi
-- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/
+1 definitely! On Tue, Jul 14, 2020 at 11:03 AM Emilien Macchi <emilien@redhat.com> wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work! -- Emilien Macchi
I added Rabi to the tripleo-core group. Thanks all for your feedback, And again thanks Rabi for your hard work! On Wed, Jul 15, 2020 at 4:17 PM Brent Eagles <beagles@redhat.com> wrote:
+1 definitely!
On Tue, Jul 14, 2020 at 11:03 AM Emilien Macchi <emilien@redhat.com> wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work! -- Emilien Macchi
-- Emilien Macchi
\0/ On Mon, Jul 20, 2020 at 8:24 AM Emilien Macchi <emilien@redhat.com> wrote:
I added Rabi to the tripleo-core group. Thanks all for your feedback,
And again thanks Rabi for your hard work!
On Wed, Jul 15, 2020 at 4:17 PM Brent Eagles <beagles@redhat.com> wrote:
+1 definitely!
On Tue, Jul 14, 2020 at 11:03 AM Emilien Macchi <emilien@redhat.com> wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work! -- Emilien Macchi
-- Emilien Macchi
On Mon, Jul 20, 2020 at 7:58 PM Emilien Macchi <emilien@redhat.com> wrote:
I added Rabi to the tripleo-core group. Thanks all for your feedback,
And again thanks Rabi for your hard work!
Thanks Emilien and others for your generous words and feedback!
On Wed, Jul 15, 2020 at 4:17 PM Brent Eagles <beagles@redhat.com> wrote:
+1 definitely!
On Tue, Jul 14, 2020 at 11:03 AM Emilien Macchi <emilien@redhat.com> wrote:
Hi folks,
Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration.
Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team.
Thanks Rabi for your hard work! -- Emilien Macchi
-- Emilien Macchi
-- Regards, Rabi Mishra
participants (13)
-
Alex Schultz
-
Bogdan Dobrelya
-
Brent Eagles
-
Carter, Kevin
-
Cédric Jeanneret
-
Emilien Macchi
-
Harald Jensas
-
John Fulton
-
Marios Andreou
-
Michele Baldessari
-
Rabi Mishra
-
Sergii Golovatiuk
-
Wesley Hayutin