Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-04-04 Thread Vikram Hosakote (vhosakot) 
Thanks a lot for the opportunity Steve, the kolla core team, and the kolla 
community! :)

Regards,
Vikram Hosakote
IRC: vhosakot

From: "Steven Dake (stdake)" <std...@cisco.com<mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Monday, April 4, 2016 at 4:31 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

The vote is unanimous in favor of Vikram joining the core reviewer team.  I 
have made the appropriate permission changes in gerrit.

Welcome to the core reviewer team Vikram!

Regards
-steve

From: Steven Dake <std...@cisco.com<mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, March 29, 2016 at 9:07 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

Hey folks,

Consider this proposal a +1 in favor of Vikram joining the core reviewer team.  
His reviews are outstanding.  If he doesn't have anything useful to add to a 
review, he doesn't pile on the review with more -1s which are slightly 
disheartening to people.  Vikram has started a trend amongst the core reviewers 
of actually diagnosing gate failures in peoples patches as opposed to saying 
gate failed please fix.  He does this diagnosis in nearly every review I see, 
and if he is stumped  he says so.  His 30 days review stats place him in pole 
position and his 90 day review stats place him in second position.  Of critical 
notice is that Vikram is ever-present on IRC which in my professional 
experience is the #1 indicator of how well a core reviewer will perform long 
term.   Besides IRC and review requirements, we also have code requirements for 
core reviewers.  Vikram has implemented only 10 patches so far, butI feel he 
could amp this up if he had feature work to do.  At the moment we are in a 
holding pattern on master development because we need to fix Mitaka bugs.  That 
said Vikram is actively working on diagnosing root causes of people's bugs in 
the IRC channel pretty much 12-18 hours a day so we can ship Mitaka in a 
working bug-free state.

Our core team consists of 11 people.  Vikram requires at minimum 6 +1 votes, 
with no veto -2 votes within a 7 day voting window to end on April 7th.  If 
there is a veto vote prior to April 7th I will close voting.  If there is a 
unanimous vote prior to April 7th, I will make appropriate changes in gerrit.

Regards
-steve

[1] http://stackalytics.com/report/contribution/kolla-group/30
[2] http://stackalytics.com/report/contribution/kolla-group/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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-04-04 Thread Steven Dake (stdake) 
The vote is unanimous in favor of Vikram joining the core reviewer team.  I 
have made the appropriate permission changes in gerrit.

Welcome to the core reviewer team Vikram!

Regards
-steve

From: Steven Dake <std...@cisco.com<mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, March 29, 2016 at 9:07 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

Hey folks,

Consider this proposal a +1 in favor of Vikram joining the core reviewer team.  
His reviews are outstanding.  If he doesn't have anything useful to add to a 
review, he doesn't pile on the review with more -1s which are slightly 
disheartening to people.  Vikram has started a trend amongst the core reviewers 
of actually diagnosing gate failures in peoples patches as opposed to saying 
gate failed please fix.  He does this diagnosis in nearly every review I see, 
and if he is stumped  he says so.  His 30 days review stats place him in pole 
position and his 90 day review stats place him in second position.  Of critical 
notice is that Vikram is ever-present on IRC which in my professional 
experience is the #1 indicator of how well a core reviewer will perform long 
term.   Besides IRC and review requirements, we also have code requirements for 
core reviewers.  Vikram has implemented only 10 patches so far, butI feel he 
could amp this up if he had feature work to do.  At the moment we are in a 
holding pattern on master development because we need to fix Mitaka bugs.  That 
said Vikram is actively working on diagnosing root causes of people's bugs in 
the IRC channel pretty much 12-18 hours a day so we can ship Mitaka in a 
working bug-free state.

Our core team consists of 11 people.  Vikram requires at minimum 6 +1 votes, 
with no veto -2 votes within a 7 day voting window to end on April 7th.  If 
there is a veto vote prior to April 7th I will close voting.  If there is a 
unanimous vote prior to April 7th, I will make appropriate changes in gerrit.

Regards
-steve

[1] http://stackalytics.com/report/contribution/kolla-group/30
[2] http://stackalytics.com/report/contribution/kolla-group/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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-04-04 Thread Martin André 
+1
Nice work Vikram.

On Thu, Mar 31, 2016 at 4:04 PM, Jeff Peeler  wrote:

> +1
>
> On Tue, Mar 29, 2016 at 12:07 PM, Steven Dake (stdake) 
> wrote:
> > Hey folks,
> >
> > Consider this proposal a +1 in favor of Vikram joining the core reviewer
> > team.  His reviews are outstanding.  If he doesn’t have anything useful
> to
> > add to a review, he doesn't pile on the review with more –1s which are
> > slightly disheartening to people.  Vikram has started a trend amongst the
> > core reviewers of actually diagnosing gate failures in peoples patches as
> > opposed to saying gate failed please fix.  He does this diagnosis in
> nearly
> > every review I see, and if he is stumped  he says so.  His 30 days review
> > stats place him in pole position and his 90 day review stats place him in
> > second position.  Of critical notice is that Vikram is ever-present on
> IRC
> > which in my professional experience is the #1 indicator of how well a
> core
> > reviewer will perform long term.   Besides IRC and review requirements,
> we
> > also have code requirements for core reviewers.  Vikram has implemented
> only
> > 10 patches so far, butI feel he could amp this up if he had feature work
> to
> > do.  At the moment we are in a holding pattern on master development
> because
> > we need to fix Mitaka bugs.  That said Vikram is actively working on
> > diagnosing root causes of people's bugs in the IRC channel pretty much
> 12-18
> > hours a day so we can ship Mitaka in a working bug-free state.
> >
> > Our core team consists of 11 people.  Vikram requires at minimum 6 +1
> votes,
> > with no veto –2 votes within a 7 day voting window to end on April 7th.
> If
> > there is a veto vote prior to April 7th I will close voting.  If there
> is a
> > unanimous vote prior to April 7th, I will make appropriate changes in
> > gerrit.
> >
> > Regards
> > -steve
> >
> > [1] http://stackalytics.com/report/contribution/kolla-group/30
> > [2] http://stackalytics.com/report/contribution/kolla-group/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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-31 Thread Jeff Peeler 
+1

On Tue, Mar 29, 2016 at 12:07 PM, Steven Dake (stdake)  wrote:
> Hey folks,
>
> Consider this proposal a +1 in favor of Vikram joining the core reviewer
> team.  His reviews are outstanding.  If he doesn’t have anything useful to
> add to a review, he doesn't pile on the review with more –1s which are
> slightly disheartening to people.  Vikram has started a trend amongst the
> core reviewers of actually diagnosing gate failures in peoples patches as
> opposed to saying gate failed please fix.  He does this diagnosis in nearly
> every review I see, and if he is stumped  he says so.  His 30 days review
> stats place him in pole position and his 90 day review stats place him in
> second position.  Of critical notice is that Vikram is ever-present on IRC
> which in my professional experience is the #1 indicator of how well a core
> reviewer will perform long term.   Besides IRC and review requirements, we
> also have code requirements for core reviewers.  Vikram has implemented only
> 10 patches so far, butI feel he could amp this up if he had feature work to
> do.  At the moment we are in a holding pattern on master development because
> we need to fix Mitaka bugs.  That said Vikram is actively working on
> diagnosing root causes of people's bugs in the IRC channel pretty much 12-18
> hours a day so we can ship Mitaka in a working bug-free state.
>
> Our core team consists of 11 people.  Vikram requires at minimum 6 +1 votes,
> with no veto –2 votes within a 7 day voting window to end on April 7th.  If
> there is a veto vote prior to April 7th I will close voting.  If there is a
> unanimous vote prior to April 7th, I will make appropriate changes in
> gerrit.
>
> Regards
> -steve
>
> [1] http://stackalytics.com/report/contribution/kolla-group/30
> [2] http://stackalytics.com/report/contribution/kolla-group/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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-30 Thread Kwasniewska, Alicja 

+1


-Original Message-
From: Michal Rostecki [mailto:michal.roste...@gmail.com] 
Sent: Wednesday, March 30, 2016 7:18 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

+1

__
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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-29 Thread Michal Rostecki 

+1

__
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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-29 Thread MD. Nadeem 
+1 
No doubt he is good at review and also helpful to guide newbies joining kolla.

-Original Message-
From: Swapnil Kulkarni [mailto:m...@coolsvap.net] 
Sent: Wednesday, March 30, 2016 9:14 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

On Tue, Mar 29, 2016 at 9:37 PM, Steven Dake (stdake) <std...@cisco.com> wrote:
> Hey folks,
>
> Consider this proposal a +1 in favor of Vikram joining the core 
> reviewer team.  His reviews are outstanding.  If he doesn’t have 
> anything useful to add to a review, he doesn't pile on the review with 
> more –1s which are slightly disheartening to people.  Vikram has 
> started a trend amongst the core reviewers of actually diagnosing gate 
> failures in peoples patches as opposed to saying gate failed please 
> fix.  He does this diagnosis in nearly every review I see, and if he 
> is stumped  he says so.  His 30 days review stats place him in pole 
> position and his 90 day review stats place him in second position.  Of 
> critical notice is that Vikram is ever-present on IRC which in my 
> professional experience is the #1 indicator of how well a core
> reviewer will perform long term.   Besides IRC and review requirements, we
> also have code requirements for core reviewers.  Vikram has 
> implemented only
> 10 patches so far, butI feel he could amp this up if he had feature 
> work to do.  At the moment we are in a holding pattern on master 
> development because we need to fix Mitaka bugs.  That said Vikram is 
> actively working on diagnosing root causes of people's bugs in the IRC 
> channel pretty much 12-18 hours a day so we can ship Mitaka in a working 
> bug-free state.
>
> Our core team consists of 11 people.  Vikram requires at minimum 6 +1 
> votes, with no veto –2 votes within a 7 day voting window to end on 
> April 7th.  If there is a veto vote prior to April 7th I will close 
> voting.  If there is a unanimous vote prior to April 7th, I will make 
> appropriate changes in gerrit.
>
> Regards
> -steve
>
> [1] http://stackalytics.com/report/contribution/kolla-group/30
> [2] http://stackalytics.com/report/contribution/kolla-group/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
>

Big +1.

__
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



DISCLAIMER:
---
The contents of this e-mail and any attachment(s) are confidential and
intended
for the named recipient(s) only. 
It shall not attach any liability on the originator or NEC or its
affiliates. Any views or opinions presented in 
this email are solely those of the author and may not necessarily reflect the
opinions of NEC or its affiliates. 
Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of 
this message without the prior written consent of the author of this e-mail is
strictly prohibited. If you have 
received this email in error please delete it and notify the sender
immediately. .
---
__
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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-29 Thread Swapnil Kulkarni 
On Tue, Mar 29, 2016 at 9:37 PM, Steven Dake (stdake)  wrote:
> Hey folks,
>
> Consider this proposal a +1 in favor of Vikram joining the core reviewer
> team.  His reviews are outstanding.  If he doesn’t have anything useful to
> add to a review, he doesn't pile on the review with more –1s which are
> slightly disheartening to people.  Vikram has started a trend amongst the
> core reviewers of actually diagnosing gate failures in peoples patches as
> opposed to saying gate failed please fix.  He does this diagnosis in nearly
> every review I see, and if he is stumped  he says so.  His 30 days review
> stats place him in pole position and his 90 day review stats place him in
> second position.  Of critical notice is that Vikram is ever-present on IRC
> which in my professional experience is the #1 indicator of how well a core
> reviewer will perform long term.   Besides IRC and review requirements, we
> also have code requirements for core reviewers.  Vikram has implemented only
> 10 patches so far, butI feel he could amp this up if he had feature work to
> do.  At the moment we are in a holding pattern on master development because
> we need to fix Mitaka bugs.  That said Vikram is actively working on
> diagnosing root causes of people's bugs in the IRC channel pretty much 12-18
> hours a day so we can ship Mitaka in a working bug-free state.
>
> Our core team consists of 11 people.  Vikram requires at minimum 6 +1 votes,
> with no veto –2 votes within a 7 day voting window to end on April 7th.  If
> there is a veto vote prior to April 7th I will close voting.  If there is a
> unanimous vote prior to April 7th, I will make appropriate changes in
> gerrit.
>
> Regards
> -steve
>
> [1] http://stackalytics.com/report/contribution/kolla-group/30
> [2] http://stackalytics.com/report/contribution/kolla-group/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
>

Big +1.

__
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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-29 Thread Jeffrey Zhang 
+1

On Wed, Mar 30, 2016 at 8:25 AM, Angus Salkeld <asalk...@mirantis.com>
wrote:

> +1
>
>
> On Wed, Mar 30, 2016 at 6:45 AM Michał Jastrzębski <inc...@gmail.com>
> wrote:
>
>> +1
>>
>> On 29 March 2016 at 11:39, Ryan Hallisey <rhall...@redhat.com> wrote:
>> > +1
>> >
>> > - Original Message -
>> > From: "Paul Bourke" <paul.bou...@oracle.com>
>> > To: openstack-dev@lists.openstack.org
>> > Sent: Tuesday, March 29, 2016 12:10:38 PM
>> > Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot
>> for Core Reviewer
>> >
>> > +1
>> >
>> > On 29/03/16 17:07, Steven Dake (stdake) wrote:
>> >> Hey folks,
>> >>
>> >> Consider this proposal a +1 in favor of Vikram joining the core
>> reviewer
>> >> team.  His reviews are outstanding.  If he doesn’t have anything useful
>> >> to add to a review, he doesn't pile on the review with more –1s which
>> >> are slightly disheartening to people.  Vikram has started a trend
>> >> amongst the core reviewers of actually diagnosing gate failures in
>> >> peoples patches as opposed to saying gate failed please fix.  He does
>> >> this diagnosis in nearly every review I see, and if he is stumped  he
>> >> says so.  His 30 days review stats place him in pole position and his
>> 90
>> >> day review stats place him in second position.  Of critical notice is
>> >> that Vikram is ever-present on IRC which in my professional experience
>> >> is the #1 indicator of how well a core reviewer will perform long term.
>> >>Besides IRC and review requirements, we also have code requirements
>> >> for core reviewers.  Vikram has implemented only 10 patches so far,
>> butI
>> >> feel he could amp this up if he had feature work to do.  At the moment
>> >> we are in a holding pattern on master development because we need to
>> fix
>> >> Mitaka bugs.  That said Vikram is actively working on diagnosing root
>> >> causes of people's bugs in the IRC channel pretty much 12-18 hours a
>> day
>> >> so we can ship Mitaka in a working bug-free state.
>> >>
>> >> Our core team consists of 11 people.  Vikram requires at minimum 6 +1
>> >> votes, with no veto –2 votes within a 7 day voting window to end on
>> >> April 7th.  If there is a veto vote prior to April 7th I will close
>> >> voting.  If there is a unanimous vote prior to April 7th, I will make
>> >> appropriate changes in gerrit.
>> >>
>> >> Regards
>> >> -steve
>> >>
>> >> [1] http://stackalytics.com/report/contribution/kolla-group/30
>> >> [2] http://stackalytics.com/report/contribution/kolla-group/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
>
>


-- 
Jeffrey Zhang
Blog: http://xcodest.me
__
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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-29 Thread Angus Salkeld 
+1

On Wed, Mar 30, 2016 at 6:45 AM Michał Jastrzębski <inc...@gmail.com> wrote:

> +1
>
> On 29 March 2016 at 11:39, Ryan Hallisey <rhall...@redhat.com> wrote:
> > +1
> >
> > - Original Message -
> > From: "Paul Bourke" <paul.bou...@oracle.com>
> > To: openstack-dev@lists.openstack.org
> > Sent: Tuesday, March 29, 2016 12:10:38 PM
> > Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for
> Core Reviewer
> >
> > +1
> >
> > On 29/03/16 17:07, Steven Dake (stdake) wrote:
> >> Hey folks,
> >>
> >> Consider this proposal a +1 in favor of Vikram joining the core reviewer
> >> team.  His reviews are outstanding.  If he doesn’t have anything useful
> >> to add to a review, he doesn't pile on the review with more –1s which
> >> are slightly disheartening to people.  Vikram has started a trend
> >> amongst the core reviewers of actually diagnosing gate failures in
> >> peoples patches as opposed to saying gate failed please fix.  He does
> >> this diagnosis in nearly every review I see, and if he is stumped  he
> >> says so.  His 30 days review stats place him in pole position and his 90
> >> day review stats place him in second position.  Of critical notice is
> >> that Vikram is ever-present on IRC which in my professional experience
> >> is the #1 indicator of how well a core reviewer will perform long term.
> >>Besides IRC and review requirements, we also have code requirements
> >> for core reviewers.  Vikram has implemented only 10 patches so far, butI
> >> feel he could amp this up if he had feature work to do.  At the moment
> >> we are in a holding pattern on master development because we need to fix
> >> Mitaka bugs.  That said Vikram is actively working on diagnosing root
> >> causes of people's bugs in the IRC channel pretty much 12-18 hours a day
> >> so we can ship Mitaka in a working bug-free state.
> >>
> >> Our core team consists of 11 people.  Vikram requires at minimum 6 +1
> >> votes, with no veto –2 votes within a 7 day voting window to end on
> >> April 7th.  If there is a veto vote prior to April 7th I will close
> >> voting.  If there is a unanimous vote prior to April 7th, I will make
> >> appropriate changes in gerrit.
> >>
> >> Regards
> >> -steve
> >>
> >> [1] http://stackalytics.com/report/contribution/kolla-group/30
> >> [2] http://stackalytics.com/report/contribution/kolla-group/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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-29 Thread Michał Jastrzębski 
+1

On 29 March 2016 at 11:39, Ryan Hallisey <rhall...@redhat.com> wrote:
> +1
>
> - Original Message -
> From: "Paul Bourke" <paul.bou...@oracle.com>
> To: openstack-dev@lists.openstack.org
> Sent: Tuesday, March 29, 2016 12:10:38 PM
> Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
> Reviewer
>
> +1
>
> On 29/03/16 17:07, Steven Dake (stdake) wrote:
>> Hey folks,
>>
>> Consider this proposal a +1 in favor of Vikram joining the core reviewer
>> team.  His reviews are outstanding.  If he doesn’t have anything useful
>> to add to a review, he doesn't pile on the review with more –1s which
>> are slightly disheartening to people.  Vikram has started a trend
>> amongst the core reviewers of actually diagnosing gate failures in
>> peoples patches as opposed to saying gate failed please fix.  He does
>> this diagnosis in nearly every review I see, and if he is stumped  he
>> says so.  His 30 days review stats place him in pole position and his 90
>> day review stats place him in second position.  Of critical notice is
>> that Vikram is ever-present on IRC which in my professional experience
>> is the #1 indicator of how well a core reviewer will perform long term.
>>Besides IRC and review requirements, we also have code requirements
>> for core reviewers.  Vikram has implemented only 10 patches so far, butI
>> feel he could amp this up if he had feature work to do.  At the moment
>> we are in a holding pattern on master development because we need to fix
>> Mitaka bugs.  That said Vikram is actively working on diagnosing root
>> causes of people's bugs in the IRC channel pretty much 12-18 hours a day
>> so we can ship Mitaka in a working bug-free state.
>>
>> Our core team consists of 11 people.  Vikram requires at minimum 6 +1
>> votes, with no veto –2 votes within a 7 day voting window to end on
>> April 7th.  If there is a veto vote prior to April 7th I will close
>> voting.  If there is a unanimous vote prior to April 7th, I will make
>> appropriate changes in gerrit.
>>
>> Regards
>> -steve
>>
>> [1] http://stackalytics.com/report/contribution/kolla-group/30
>> [2] http://stackalytics.com/report/contribution/kolla-group/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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-29 Thread Ryan Hallisey 
+1

- Original Message -
From: "Paul Bourke" <paul.bou...@oracle.com>
To: openstack-dev@lists.openstack.org
Sent: Tuesday, March 29, 2016 12:10:38 PM
Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

+1

On 29/03/16 17:07, Steven Dake (stdake) wrote:
> Hey folks,
>
> Consider this proposal a +1 in favor of Vikram joining the core reviewer
> team.  His reviews are outstanding.  If he doesn’t have anything useful
> to add to a review, he doesn't pile on the review with more –1s which
> are slightly disheartening to people.  Vikram has started a trend
> amongst the core reviewers of actually diagnosing gate failures in
> peoples patches as opposed to saying gate failed please fix.  He does
> this diagnosis in nearly every review I see, and if he is stumped  he
> says so.  His 30 days review stats place him in pole position and his 90
> day review stats place him in second position.  Of critical notice is
> that Vikram is ever-present on IRC which in my professional experience
> is the #1 indicator of how well a core reviewer will perform long term.
>Besides IRC and review requirements, we also have code requirements
> for core reviewers.  Vikram has implemented only 10 patches so far, butI
> feel he could amp this up if he had feature work to do.  At the moment
> we are in a holding pattern on master development because we need to fix
> Mitaka bugs.  That said Vikram is actively working on diagnosing root
> causes of people's bugs in the IRC channel pretty much 12-18 hours a day
> so we can ship Mitaka in a working bug-free state.
>
> Our core team consists of 11 people.  Vikram requires at minimum 6 +1
> votes, with no veto –2 votes within a 7 day voting window to end on
> April 7th.  If there is a veto vote prior to April 7th I will close
> voting.  If there is a unanimous vote prior to April 7th, I will make
> appropriate changes in gerrit.
>
> Regards
> -steve
>
> [1] http://stackalytics.com/report/contribution/kolla-group/30
> [2] http://stackalytics.com/report/contribution/kolla-group/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

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-29 Thread Paul Bourke 

+1

On 29/03/16 17:07, Steven Dake (stdake) wrote:

Hey folks,

Consider this proposal a +1 in favor of Vikram joining the core reviewer
team.  His reviews are outstanding.  If he doesn’t have anything useful
to add to a review, he doesn't pile on the review with more –1s which
are slightly disheartening to people.  Vikram has started a trend
amongst the core reviewers of actually diagnosing gate failures in
peoples patches as opposed to saying gate failed please fix.  He does
this diagnosis in nearly every review I see, and if he is stumped  he
says so.  His 30 days review stats place him in pole position and his 90
day review stats place him in second position.  Of critical notice is
that Vikram is ever-present on IRC which in my professional experience
is the #1 indicator of how well a core reviewer will perform long term.
   Besides IRC and review requirements, we also have code requirements
for core reviewers.  Vikram has implemented only 10 patches so far, butI
feel he could amp this up if he had feature work to do.  At the moment
we are in a holding pattern on master development because we need to fix
Mitaka bugs.  That said Vikram is actively working on diagnosing root
causes of people's bugs in the IRC channel pretty much 12-18 hours a day
so we can ship Mitaka in a working bug-free state.

Our core team consists of 11 people.  Vikram requires at minimum 6 +1
votes, with no veto –2 votes within a 7 day voting window to end on
April 7th.  If there is a veto vote prior to April 7th I will close
voting.  If there is a unanimous vote prior to April 7th, I will make
appropriate changes in gerrit.

Regards
-steve

[1] http://stackalytics.com/report/contribution/kolla-group/30
[2] http://stackalytics.com/report/contribution/kolla-group/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-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

2016-03-29 Thread Steven Dake (stdake) 
Hey folks,

Consider this proposal a +1 in favor of Vikram joining the core reviewer team.  
His reviews are outstanding.  If he doesn't have anything useful to add to a 
review, he doesn't pile on the review with more -1s which are slightly 
disheartening to people.  Vikram has started a trend amongst the core reviewers 
of actually diagnosing gate failures in peoples patches as opposed to saying 
gate failed please fix.  He does this diagnosis in nearly every review I see, 
and if he is stumped  he says so.  His 30 days review stats place him in pole 
position and his 90 day review stats place him in second position.  Of critical 
notice is that Vikram is ever-present on IRC which in my professional 
experience is the #1 indicator of how well a core reviewer will perform long 
term.   Besides IRC and review requirements, we also have code requirements for 
core reviewers.  Vikram has implemented only 10 patches so far, butI feel he 
could amp this up if he had feature work to do.  At the moment we are in a 
holding pattern on master development because we need to fix Mitaka bugs.  That 
said Vikram is actively working on diagnosing root causes of people's bugs in 
the IRC channel pretty much 12-18 hours a day so we can ship Mitaka in a 
working bug-free state.

Our core team consists of 11 people.  Vikram requires at minimum 6 +1 votes, 
with no veto -2 votes within a 7 day voting window to end on April 7th.  If 
there is a veto vote prior to April 7th I will close voting.  If there is a 
unanimous vote prior to April 7th, I will make appropriate changes in gerrit.

Regards
-steve

[1] http://stackalytics.com/report/contribution/kolla-group/30
[2] http://stackalytics.com/report/contribution/kolla-group/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