Thanks Michael and team. I am glad to have this opportunity. It's been fun and looking forward for the great progress of the Octavia project.
Thanks. Bharath. On Fri, Apr 8, 2016 at 1:12 PM, Michael Johnson <johnso...@gmail.com> wrote: > Thank you cores. That is a majority core vote in favor, so welcome to > the core reviewer team Bharath! > > Michael > > On Fri, Apr 8, 2016 at 12:26 PM, Bertrand LALLAU > <bertrand.lal...@gmail.com> wrote: > > +1 > > > > On Fri, Apr 8, 2016 at 8:06 PM, Doug Wiegley < > doug...@parksidesoftware.com> > > wrote: > >> > >> +1 > >> > >> > On Apr 4, 2016, at 10:53 AM, Adam Harwell <adam.harw...@rackspace.com > > > >> > wrote: > >> > > >> > +1 > >> > ________________________________________ > >> > From: Brandon Logan <brandon.lo...@rackspace.com> > >> > Sent: Thursday, March 31, 2016 8:04 AM > >> > To: openstack-dev@lists.openstack.org > >> > Subject: Re: [openstack-dev] [lbaas] [octavia] Proposing Bharath > >> > Munirajulu as Octavia Core > >> > > >> > +1 > >> > > >> > On Wed, 2016-03-30 at 13:56 -0700, Michael Johnson wrote: > >> >> I would like to nominate Bharath Munirajulu (bharathm) as a OpenStack > >> >> Octavia core reviewer. > >> >> His contributions [1] are in line with other cores and he has been an > >> >> active member of our community. I have been impressed with the > >> >> insight and quality of his reviews. > >> >> > >> >> Current Octavia cores, please vote by replying to this e-mail. > >> >> > >> >> Michael > >> >> > >> >> > >> >> [1] http://stackalytics.com/report/contribution/octavia/90 > >> >> > >> >> > >> >> > __________________________________________________________________________ > >> >> OpenStack Development Mailing List (not for usage questions) > >> >> Unsubscribe: > >> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > > >> > > >> > > __________________________________________________________________________ > >> > OpenStack Development Mailing List (not for usage questions) > >> > Unsubscribe: > >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > > >> > > >> > > __________________________________________________________________________ > >> > OpenStack Development Mailing List (not for usage questions) > >> > Unsubscribe: > >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > >> > >> > __________________________________________________________________________ > >> OpenStack Development Mailing List (not for usage questions) > >> Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
