Re: [openstack-dev] [neutron] Changes to the core team

2015-01-23 Thread Mark McClain

 On Jan 22, 2015, at 12:21 PM, Kyle Mestery mest...@mestery.com wrote:
 
 On Thu, Jan 15, 2015 at 4:31 PM, Kyle Mestery mest...@mestery.com 
 mailto:mest...@mestery.com wrote:
 The last time we looked at core reviewer stats was in December [1]. In 
 looking at the current stats, I'm going to propose some changes to the core 
 team. Reviews are the most important part of being a core reviewer, so we 
 need to ensure cores are doing reviews. The stats for the 90 day period [2] 
 indicate some changes are needed for core reviewers who are no longer 
 reviewing on pace with the other core reviewers.
 
 First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has been 
 a core reviewer for a long time, and his past contributions are very much 
 thanked by the entire OpenStack Neutron team. If Sumit jumps back in with 
 thoughtful reviews in the future, we can look at getting him back as a 
 Neutron core reviewer. But for now, his stats indicate he's not reviewing at 
 a level consistent with the rest of the Neutron core reviewers.
 
 As part of the change, I'd like to propose Doug Wiegley as a new Neutron core 
 reviewer. Doug has been actively reviewing code across not only all the 
 Neutron projects, but also other projects such as infra. His help and work in 
 the services split in December were the reason we were so successful in 
 making that happen. Doug has also been instrumental in the Neutron LBaaS V2 
 rollout, as well as helping to merge code in the other neutron service 
 repositories.
 
 I'd also like to take this time to remind everyone that reviewing code is a 
 responsibility, in Neutron the same as other projects. And core reviewers are 
 especially beholden to this responsibility. I'd also like to point out that 
 +1/-1 reviews are very useful, and I encourage everyone to continue reviewing 
 code even if you are not a core reviewer.
 
 Existing neutron cores, please vote +1/-1 for the addition of Doug to the 
 core team.
 
 It's been a week, and Doug has received plenty of support. Welcome to the 
 Neutron Core Review team Doug!
 

Welcome Doug!

mark


__
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] [neutron] Changes to the core team

2015-01-22 Thread Gary Kotton
+1

On 1/22/15, 2:18 AM, Akihiro Motoki amot...@gmail.com wrote:

+1 for Doug

2015-01-20 13:59 GMT+09:00 Aaron Rosen aaronoro...@gmail.com:
 +1

 On Fri, Jan 16, 2015 at 12:03 PM, Carl Baldwin c...@ecbaldwin.net
wrote:

 +1

 On Thu, Jan 15, 2015 at 3:31 PM, Kyle Mestery mest...@mestery.com
wrote:
  The last time we looked at core reviewer stats was in December [1].
In
  looking at the current stats, I'm going to propose some changes to
the
  core
  team. Reviews are the most important part of being a core reviewer,
so
  we
  need to ensure cores are doing reviews. The stats for the 90 day
period
  [2]
  indicate some changes are needed for core reviewers who are no longer
  reviewing on pace with the other core reviewers.
 
  First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit
has
  been
  a core reviewer for a long time, and his past contributions are very
  much
  thanked by the entire OpenStack Neutron team. If Sumit jumps back in
  with
  thoughtful reviews in the future, we can look at getting him back as
a
  Neutron core reviewer. But for now, his stats indicate he's not
  reviewing at
  a level consistent with the rest of the Neutron core reviewers.
 
  As part of the change, I'd like to propose Doug Wiegley as a new
Neutron
  core reviewer. Doug has been actively reviewing code across not only
all
  the
  Neutron projects, but also other projects such as infra. His help and
  work
  in the services split in December were the reason we were so
successful
  in
  making that happen. Doug has also been instrumental in the Neutron
LBaaS
  V2
  rollout, as well as helping to merge code in the other neutron
service
  repositories.
 
  I'd also like to take this time to remind everyone that reviewing
code
  is a
  responsibility, in Neutron the same as other projects. And core
  reviewers
  are especially beholden to this responsibility. I'd also like to
point
  out
  that +1/-1 reviews are very useful, and I encourage everyone to
continue
  reviewing code even if you are not a core reviewer.
 
  Existing neutron cores, please vote +1/-1 for the addition of Doug to
  the
  core team.
 
  Thanks!
  Kyle
 
  [1]
 
  
http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.
html
  [2] 
https://urldefense.proofpoint.com/v2/url?u=http-3A__russellbryant.net_op
enstack-2Dstats_neutron-2Dreviewers-2D90.txtd=AwICAgc=Sqcl0Ez6M0X8aeM6
7LKIiDJAXVeAw-YihVMNtXt-uEsr=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyN
cm=wnB98q7iZ33MRx4YfBbDiqXhNykzwMe8k-kvd6hF_wss=5UaM_DNnTPV9ccACNgWx0n
vfNRPXZcjxWjQqIlAtgYse=
 
 
  

__
  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




-- 
Akihiro Motoki amot...@gmail.com

__
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] [neutron] Changes to the core team

2015-01-22 Thread Brandon Logan
Congratulations Doug!

On Thu, 2015-01-22 at 11:21 -0600, Kyle Mestery wrote:
 On Thu, Jan 15, 2015 at 4:31 PM, Kyle Mestery mest...@mestery.com
 wrote:
 The last time we looked at core reviewer stats was in December
 [1]. In looking at the current stats, I'm going to propose
 some changes to the core team. Reviews are the most important
 part of being a core reviewer, so we need to ensure cores are
 doing reviews. The stats for the 90 day period [2] indicate
 some changes are needed for core reviewers who are no longer
 reviewing on pace with the other core reviewers.
 
 
 First of all, I'm removing Sumit Naiksatam from neutron-core.
 Sumit has been a core reviewer for a long time, and his past
 contributions are very much thanked by the entire OpenStack
 Neutron team. If Sumit jumps back in with thoughtful reviews
 in the future, we can look at getting him back as a Neutron
 core reviewer. But for now, his stats indicate he's not
 reviewing at a level consistent with the rest of the Neutron
 core reviewers.
 
 
 As part of the change, I'd like to propose Doug Wiegley as a
 new Neutron core reviewer. Doug has been actively reviewing
 code across not only all the Neutron projects, but also other
 projects such as infra. His help and work in the services
 split in December were the reason we were so successful in
 making that happen. Doug has also been instrumental in the
 Neutron LBaaS V2 rollout, as well as helping to merge code in
 the other neutron service repositories.
 
 I'd also like to take this time to remind everyone that
 reviewing code is a responsibility, in Neutron the same as
 other projects. And core reviewers are especially beholden to
 this responsibility. I'd also like to point out that +1/-1
 reviews are very useful, and I encourage everyone to continue
 reviewing code even if you are not a core reviewer.
 
 Existing neutron cores, please vote +1/-1 for the addition of
 Doug to the core team.
 
 
 It's been a week, and Doug has received plenty of support. Welcome to
 the Neutron Core Review team Doug!
 
 Kyle
  
 
 Thanks!
 Kyle
 
 [1]
 
 http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
 [2]
 http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt
 
 
 
 __
 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] [neutron] Changes to the core team

2015-01-22 Thread Kyle Mestery
On Thu, Jan 15, 2015 at 4:31 PM, Kyle Mestery mest...@mestery.com wrote:

 The last time we looked at core reviewer stats was in December [1]. In
 looking at the current stats, I'm going to propose some changes to the core
 team. Reviews are the most important part of being a core reviewer, so we
 need to ensure cores are doing reviews. The stats for the 90 day period [2]
 indicate some changes are needed for core reviewers who are no longer
 reviewing on pace with the other core reviewers.

 First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has
 been a core reviewer for a long time, and his past contributions are very
 much thanked by the entire OpenStack Neutron team. If Sumit jumps back in
 with thoughtful reviews in the future, we can look at getting him back as a
 Neutron core reviewer. But for now, his stats indicate he's not reviewing
 at a level consistent with the rest of the Neutron core reviewers.

 As part of the change, I'd like to propose Doug Wiegley as a new Neutron
 core reviewer. Doug has been actively reviewing code across not only all
 the Neutron projects, but also other projects such as infra. His help and
 work in the services split in December were the reason we were so
 successful in making that happen. Doug has also been instrumental in the
 Neutron LBaaS V2 rollout, as well as helping to merge code in the other
 neutron service repositories.

 I'd also like to take this time to remind everyone that reviewing code is
 a responsibility, in Neutron the same as other projects. And core reviewers
 are especially beholden to this responsibility. I'd also like to point out
 that +1/-1 reviews are very useful, and I encourage everyone to continue
 reviewing code even if you are not a core reviewer.

 Existing neutron cores, please vote +1/-1 for the addition of Doug to the
 core team.

 It's been a week, and Doug has received plenty of support. Welcome to the
Neutron Core Review team Doug!

Kyle


 Thanks!
 Kyle

 [1]
 http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
 [2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt

__
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] [neutron] Changes to the core team

2015-01-21 Thread Akihiro Motoki
+1 for Doug

2015-01-20 13:59 GMT+09:00 Aaron Rosen aaronoro...@gmail.com:
 +1

 On Fri, Jan 16, 2015 at 12:03 PM, Carl Baldwin c...@ecbaldwin.net wrote:

 +1

 On Thu, Jan 15, 2015 at 3:31 PM, Kyle Mestery mest...@mestery.com wrote:
  The last time we looked at core reviewer stats was in December [1]. In
  looking at the current stats, I'm going to propose some changes to the
  core
  team. Reviews are the most important part of being a core reviewer, so
  we
  need to ensure cores are doing reviews. The stats for the 90 day period
  [2]
  indicate some changes are needed for core reviewers who are no longer
  reviewing on pace with the other core reviewers.
 
  First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has
  been
  a core reviewer for a long time, and his past contributions are very
  much
  thanked by the entire OpenStack Neutron team. If Sumit jumps back in
  with
  thoughtful reviews in the future, we can look at getting him back as a
  Neutron core reviewer. But for now, his stats indicate he's not
  reviewing at
  a level consistent with the rest of the Neutron core reviewers.
 
  As part of the change, I'd like to propose Doug Wiegley as a new Neutron
  core reviewer. Doug has been actively reviewing code across not only all
  the
  Neutron projects, but also other projects such as infra. His help and
  work
  in the services split in December were the reason we were so successful
  in
  making that happen. Doug has also been instrumental in the Neutron LBaaS
  V2
  rollout, as well as helping to merge code in the other neutron service
  repositories.
 
  I'd also like to take this time to remind everyone that reviewing code
  is a
  responsibility, in Neutron the same as other projects. And core
  reviewers
  are especially beholden to this responsibility. I'd also like to point
  out
  that +1/-1 reviews are very useful, and I encourage everyone to continue
  reviewing code even if you are not a core reviewer.
 
  Existing neutron cores, please vote +1/-1 for the addition of Doug to
  the
  core team.
 
  Thanks!
  Kyle
 
  [1]
 
  http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
  [2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt
 
 
  __
  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




-- 
Akihiro Motoki amot...@gmail.com

__
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] [neutron] Changes to the core team

2015-01-19 Thread Aaron Rosen
+1

On Fri, Jan 16, 2015 at 12:03 PM, Carl Baldwin c...@ecbaldwin.net wrote:

 +1

 On Thu, Jan 15, 2015 at 3:31 PM, Kyle Mestery mest...@mestery.com wrote:
  The last time we looked at core reviewer stats was in December [1]. In
  looking at the current stats, I'm going to propose some changes to the
 core
  team. Reviews are the most important part of being a core reviewer, so we
  need to ensure cores are doing reviews. The stats for the 90 day period
 [2]
  indicate some changes are needed for core reviewers who are no longer
  reviewing on pace with the other core reviewers.
 
  First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has
 been
  a core reviewer for a long time, and his past contributions are very much
  thanked by the entire OpenStack Neutron team. If Sumit jumps back in with
  thoughtful reviews in the future, we can look at getting him back as a
  Neutron core reviewer. But for now, his stats indicate he's not
 reviewing at
  a level consistent with the rest of the Neutron core reviewers.
 
  As part of the change, I'd like to propose Doug Wiegley as a new Neutron
  core reviewer. Doug has been actively reviewing code across not only all
 the
  Neutron projects, but also other projects such as infra. His help and
 work
  in the services split in December were the reason we were so successful
 in
  making that happen. Doug has also been instrumental in the Neutron LBaaS
 V2
  rollout, as well as helping to merge code in the other neutron service
  repositories.
 
  I'd also like to take this time to remind everyone that reviewing code
 is a
  responsibility, in Neutron the same as other projects. And core reviewers
  are especially beholden to this responsibility. I'd also like to point
 out
  that +1/-1 reviews are very useful, and I encourage everyone to continue
  reviewing code even if you are not a core reviewer.
 
  Existing neutron cores, please vote +1/-1 for the addition of Doug to the
  core team.
 
  Thanks!
  Kyle
 
  [1]
 
 http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
  [2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt
 
 
 __
  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] [neutron] Changes to the core team

2015-01-19 Thread Joshua Zhang
+1

On Tue, Jan 20, 2015 at 12:59 PM, Aaron Rosen aaronoro...@gmail.com wrote:

 +1

 On Fri, Jan 16, 2015 at 12:03 PM, Carl Baldwin c...@ecbaldwin.net wrote:

 +1

 On Thu, Jan 15, 2015 at 3:31 PM, Kyle Mestery mest...@mestery.com
 wrote:
  The last time we looked at core reviewer stats was in December [1]. In
  looking at the current stats, I'm going to propose some changes to the
 core
  team. Reviews are the most important part of being a core reviewer, so
 we
  need to ensure cores are doing reviews. The stats for the 90 day period
 [2]
  indicate some changes are needed for core reviewers who are no longer
  reviewing on pace with the other core reviewers.
 
  First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has
 been
  a core reviewer for a long time, and his past contributions are very
 much
  thanked by the entire OpenStack Neutron team. If Sumit jumps back in
 with
  thoughtful reviews in the future, we can look at getting him back as a
  Neutron core reviewer. But for now, his stats indicate he's not
 reviewing at
  a level consistent with the rest of the Neutron core reviewers.
 
  As part of the change, I'd like to propose Doug Wiegley as a new Neutron
  core reviewer. Doug has been actively reviewing code across not only
 all the
  Neutron projects, but also other projects such as infra. His help and
 work
  in the services split in December were the reason we were so successful
 in
  making that happen. Doug has also been instrumental in the Neutron
 LBaaS V2
  rollout, as well as helping to merge code in the other neutron service
  repositories.
 
  I'd also like to take this time to remind everyone that reviewing code
 is a
  responsibility, in Neutron the same as other projects. And core
 reviewers
  are especially beholden to this responsibility. I'd also like to point
 out
  that +1/-1 reviews are very useful, and I encourage everyone to continue
  reviewing code even if you are not a core reviewer.
 
  Existing neutron cores, please vote +1/-1 for the addition of Doug to
 the
  core team.
 
  Thanks!
  Kyle
 
  [1]
 
 http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
  [2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt
 
 
 __
  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




-- 
Best Regards
Zhang Hua(张华)
Software Engineer | Canonical
IRC:  zhhuabj
__
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] [neutron] Changes to the core team

2015-01-16 Thread Oleg Bondarev
+1 for Doug, he does a great job!

Thanks,
Oleg

On Fri, Jan 16, 2015 at 9:59 AM, Salvatore Orlando sorla...@nicira.com
wrote:

 I agree with the proposed changes.

 I would also like to take a chance to thank Sumit for the effort he has
 put in this project over several years - he has been in the core team since
 the project's inception and has been a witness of all its developments -
 both the good and the bad ones!

 Salvatore

 On 16 January 2015 at 04:38, Henry Gessau ges...@cisco.com wrote:

 On Thu, Jan 15, 2015, Kyle Mestery mest...@mestery.com wrote:
  As part of the change, I'd like to propose Doug Wiegley as a new
 Neutron core
  reviewer. Doug has been actively reviewing code across not only all the
  Neutron projects, but also other projects such as infra. His help and
 work in
  the services split in December were the reason we were so successful in
 making
  that happen. Doug has also been instrumental in the Neutron LBaaS V2
 rollout,
  as well as helping to merge code in the other neutron service
 repositories.

 +1 for Doug.


 __
 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] [neutron] Changes to the core team

2015-01-16 Thread Tina TSOU
Dear all,

+1 for Doug.


Thank you,
Tina

On Jan 16, 2015, at 4:07 PM, Oleg Bondarev 
obonda...@mirantis.commailto:obonda...@mirantis.com wrote:

+1 for Doug, he does a great job!

Thanks,
Oleg

On Fri, Jan 16, 2015 at 9:59 AM, Salvatore Orlando 
sorla...@nicira.commailto:sorla...@nicira.com wrote:
I agree with the proposed changes.

I would also like to take a chance to thank Sumit for the effort he has put in 
this project over several years - he has been in the core team since the 
project's inception and has been a witness of all its developments - both the 
good and the bad ones!

Salvatore

On 16 January 2015 at 04:38, Henry Gessau 
ges...@cisco.commailto:ges...@cisco.com wrote:
On Thu, Jan 15, 2015, Kyle Mestery 
mest...@mestery.commailto:mest...@mestery.com wrote:
 As part of the change, I'd like to propose Doug Wiegley as a new Neutron core
 reviewer. Doug has been actively reviewing code across not only all the
 Neutron projects, but also other projects such as infra. His help and work in
 the services split in December were the reason we were so successful in making
 that happen. Doug has also been instrumental in the Neutron LBaaS V2 rollout,
 as well as helping to merge code in the other neutron service repositories.

+1 for Doug.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://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:unsubscribehttp://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] [neutron] Changes to the core team

2015-01-16 Thread Carl Baldwin
+1

On Thu, Jan 15, 2015 at 3:31 PM, Kyle Mestery mest...@mestery.com wrote:
 The last time we looked at core reviewer stats was in December [1]. In
 looking at the current stats, I'm going to propose some changes to the core
 team. Reviews are the most important part of being a core reviewer, so we
 need to ensure cores are doing reviews. The stats for the 90 day period [2]
 indicate some changes are needed for core reviewers who are no longer
 reviewing on pace with the other core reviewers.

 First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has been
 a core reviewer for a long time, and his past contributions are very much
 thanked by the entire OpenStack Neutron team. If Sumit jumps back in with
 thoughtful reviews in the future, we can look at getting him back as a
 Neutron core reviewer. But for now, his stats indicate he's not reviewing at
 a level consistent with the rest of the Neutron core reviewers.

 As part of the change, I'd like to propose Doug Wiegley as a new Neutron
 core reviewer. Doug has been actively reviewing code across not only all the
 Neutron projects, but also other projects such as infra. His help and work
 in the services split in December were the reason we were so successful in
 making that happen. Doug has also been instrumental in the Neutron LBaaS V2
 rollout, as well as helping to merge code in the other neutron service
 repositories.

 I'd also like to take this time to remind everyone that reviewing code is a
 responsibility, in Neutron the same as other projects. And core reviewers
 are especially beholden to this responsibility. I'd also like to point out
 that +1/-1 reviews are very useful, and I encourage everyone to continue
 reviewing code even if you are not a core reviewer.

 Existing neutron cores, please vote +1/-1 for the addition of Doug to the
 core team.

 Thanks!
 Kyle

 [1]
 http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
 [2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt

 __
 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] [neutron] Changes to the core team

2015-01-15 Thread Anita Kuno
On 01/16/2015 11:31 AM, Kyle Mestery wrote:
 The last time we looked at core reviewer stats was in December [1]. In
 looking at the current stats, I'm going to propose some changes to the core
 team. Reviews are the most important part of being a core reviewer, so we
 need to ensure cores are doing reviews. The stats for the 90 day period [2]
 indicate some changes are needed for core reviewers who are no longer
 reviewing on pace with the other core reviewers.
 
 First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has
 been a core reviewer for a long time, and his past contributions are very
 much thanked by the entire OpenStack Neutron team. If Sumit jumps back in
 with thoughtful reviews in the future, we can look at getting him back as a
 Neutron core reviewer. But for now, his stats indicate he's not reviewing
 at a level consistent with the rest of the Neutron core reviewers.
 
 As part of the change, I'd like to propose Doug Wiegley as a new Neutron
 core reviewer. Doug has been actively reviewing code across not only all
 the Neutron projects, but also other projects such as infra. His help and
 work in the services split in December were the reason we were so
 successful in making that happen. Doug has also been instrumental in the
 Neutron LBaaS V2 rollout, as well as helping to merge code in the other
 neutron service repositories.
I don't have a vote here but I would like to echo Kyle's summary of the
value of Doug's work with infra with the services split effort. It
wouldn't have happened without Doug's patience, persistence and leadership.

Thanks,
Anita.
 
 I'd also like to take this time to remind everyone that reviewing code is a
 responsibility, in Neutron the same as other projects. And core reviewers
 are especially beholden to this responsibility. I'd also like to point out
 that +1/-1 reviews are very useful, and I encourage everyone to continue
 reviewing code even if you are not a core reviewer.
 
 Existing neutron cores, please vote +1/-1 for the addition of Doug to the
 core team.
 
 Thanks!
 Kyle
 
 [1]
 http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
 [2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt
 
 
 
 __
 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] [neutron] Changes to the core team

2015-01-15 Thread Kevin Benton
+1, without Doug's help fixing everything, the services split probably
wouldn't have happened.

On Thu, Jan 15, 2015 at 2:31 PM, Kyle Mestery mest...@mestery.com wrote:

 The last time we looked at core reviewer stats was in December [1]. In
 looking at the current stats, I'm going to propose some changes to the core
 team. Reviews are the most important part of being a core reviewer, so we
 need to ensure cores are doing reviews. The stats for the 90 day period [2]
 indicate some changes are needed for core reviewers who are no longer
 reviewing on pace with the other core reviewers.

 First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has
 been a core reviewer for a long time, and his past contributions are very
 much thanked by the entire OpenStack Neutron team. If Sumit jumps back in
 with thoughtful reviews in the future, we can look at getting him back as a
 Neutron core reviewer. But for now, his stats indicate he's not reviewing
 at a level consistent with the rest of the Neutron core reviewers.

 As part of the change, I'd like to propose Doug Wiegley as a new Neutron
 core reviewer. Doug has been actively reviewing code across not only all
 the Neutron projects, but also other projects such as infra. His help and
 work in the services split in December were the reason we were so
 successful in making that happen. Doug has also been instrumental in the
 Neutron LBaaS V2 rollout, as well as helping to merge code in the other
 neutron service repositories.

 I'd also like to take this time to remind everyone that reviewing code is
 a responsibility, in Neutron the same as other projects. And core reviewers
 are especially beholden to this responsibility. I'd also like to point out
 that +1/-1 reviews are very useful, and I encourage everyone to continue
 reviewing code even if you are not a core reviewer.

 Existing neutron cores, please vote +1/-1 for the addition of Doug to the
 core team.

 Thanks!
 Kyle

 [1]
 http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
 [2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt

 __
 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




-- 
Kevin Benton
__
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] [neutron] Changes to the core team

2015-01-15 Thread Maru Newby
+1 to Doug’s addition.  He’s been a workhorse in moving lbaas and the services 
split forward and his being able to finally merge code in the main repo should 
be a boon to our merge velocity.

Many thanks to Sumit for his long-serving dedication as a core reviewer.  I 
hope to see him return to the fold soon!


Maru

 On Jan 15, 2015, at 2:31 PM, Kyle Mestery mest...@mestery.com wrote:
 
 The last time we looked at core reviewer stats was in December [1]. In 
 looking at the current stats, I'm going to propose some changes to the core 
 team. Reviews are the most important part of being a core reviewer, so we 
 need to ensure cores are doing reviews. The stats for the 90 day period [2] 
 indicate some changes are needed for core reviewers who are no longer 
 reviewing on pace with the other core reviewers.
 
 First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has been 
 a core reviewer for a long time, and his past contributions are very much 
 thanked by the entire OpenStack Neutron team. If Sumit jumps back in with 
 thoughtful reviews in the future, we can look at getting him back as a 
 Neutron core reviewer. But for now, his stats indicate he's not reviewing at 
 a level consistent with the rest of the Neutron core reviewers.
 
 As part of the change, I'd like to propose Doug Wiegley as a new Neutron core 
 reviewer. Doug has been actively reviewing code across not only all the 
 Neutron projects, but also other projects such as infra. His help and work in 
 the services split in December were the reason we were so successful in 
 making that happen. Doug has also been instrumental in the Neutron LBaaS V2 
 rollout, as well as helping to merge code in the other neutron service 
 repositories.
 
 I'd also like to take this time to remind everyone that reviewing code is a 
 responsibility, in Neutron the same as other projects. And core reviewers are 
 especially beholden to this responsibility. I'd also like to point out that 
 +1/-1 reviews are very useful, and I encourage everyone to continue reviewing 
 code even if you are not a core reviewer.
 
 Existing neutron cores, please vote +1/-1 for the addition of Doug to the 
 core team.
 
 Thanks!
 Kyle
 
 [1] 
 http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
 [2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt
 __
 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] [neutron] Changes to the core team

2015-01-15 Thread Edgar Magana
+1 For adding Doug as Core in Neutron!

I have seen his work on the services part and he is a great member of the 
OpenStack community!

Edgar

From: Kyle Mestery mest...@mestery.commailto:mest...@mestery.com
Reply-To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday, January 15, 2015 at 2:31 PM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] Changes to the core team

The last time we looked at core reviewer stats was in December [1]. In looking 
at the current stats, I'm going to propose some changes to the core team. 
Reviews are the most important part of being a core reviewer, so we need to 
ensure cores are doing reviews. The stats for the 90 day period [2] indicate 
some changes are needed for core reviewers who are no longer reviewing on pace 
with the other core reviewers.

First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has been a 
core reviewer for a long time, and his past contributions are very much thanked 
by the entire OpenStack Neutron team. If Sumit jumps back in with thoughtful 
reviews in the future, we can look at getting him back as a Neutron core 
reviewer. But for now, his stats indicate he's not reviewing at a level 
consistent with the rest of the Neutron core reviewers.

As part of the change, I'd like to propose Doug Wiegley as a new Neutron core 
reviewer. Doug has been actively reviewing code across not only all the Neutron 
projects, but also other projects such as infra. His help and work in the 
services split in December were the reason we were so successful in making that 
happen. Doug has also been instrumental in the Neutron LBaaS V2 rollout, as 
well as helping to merge code in the other neutron service repositories.

I'd also like to take this time to remind everyone that reviewing code is a 
responsibility, in Neutron the same as other projects. And core reviewers are 
especially beholden to this responsibility. I'd also like to point out that 
+1/-1 reviews are very useful, and I encourage everyone to continue reviewing 
code even if you are not a core reviewer.

Existing neutron cores, please vote +1/-1 for the addition of Doug to the core 
team.

Thanks!
Kyle

[1] http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
[2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt
__
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] [neutron] Changes to the core team

2015-01-15 Thread Henry Gessau
On Thu, Jan 15, 2015, Kyle Mestery mest...@mestery.com wrote:
 As part of the change, I'd like to propose Doug Wiegley as a new Neutron core
 reviewer. Doug has been actively reviewing code across not only all the
 Neutron projects, but also other projects such as infra. His help and work in
 the services split in December were the reason we were so successful in making
 that happen. Doug has also been instrumental in the Neutron LBaaS V2 rollout,
 as well as helping to merge code in the other neutron service repositories.

+1 for Doug.


__
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] [neutron] Changes to the core team

2015-01-15 Thread Salvatore Orlando
I agree with the proposed changes.

I would also like to take a chance to thank Sumit for the effort he has put
in this project over several years - he has been in the core team since the
project's inception and has been a witness of all its developments - both
the good and the bad ones!

Salvatore

On 16 January 2015 at 04:38, Henry Gessau ges...@cisco.com wrote:

 On Thu, Jan 15, 2015, Kyle Mestery mest...@mestery.com wrote:
  As part of the change, I'd like to propose Doug Wiegley as a new Neutron
 core
  reviewer. Doug has been actively reviewing code across not only all the
  Neutron projects, but also other projects such as infra. His help and
 work in
  the services split in December were the reason we were so successful in
 making
  that happen. Doug has also been instrumental in the Neutron LBaaS V2
 rollout,
  as well as helping to merge code in the other neutron service
 repositories.

 +1 for Doug.


 __
 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] [neutron] Changes to the core team

2015-01-15 Thread Armando M.
+1

On 15 January 2015 at 14:46, Edgar Magana edgar.mag...@workday.com wrote:

  +1 For adding Doug as Core in Neutron!

  I have seen his work on the services part and he is a great member of
 the OpenStack community!

  Edgar

   From: Kyle Mestery mest...@mestery.com
 Reply-To: OpenStack Development Mailing List (not for usage questions) 
 openstack-dev@lists.openstack.org
 Date: Thursday, January 15, 2015 at 2:31 PM
 To: OpenStack Development Mailing List (not for usage questions) 
 openstack-dev@lists.openstack.org
 Subject: [openstack-dev] [neutron] Changes to the core team

The last time we looked at core reviewer stats was in December [1]. In
 looking at the current stats, I'm going to propose some changes to the core
 team. Reviews are the most important part of being a core reviewer, so we
 need to ensure cores are doing reviews. The stats for the 90 day period [2]
 indicate some changes are needed for core reviewers who are no longer
 reviewing on pace with the other core reviewers.

  First of all, I'm removing Sumit Naiksatam from neutron-core. Sumit has
 been a core reviewer for a long time, and his past contributions are very
 much thanked by the entire OpenStack Neutron team. If Sumit jumps back in
 with thoughtful reviews in the future, we can look at getting him back as a
 Neutron core reviewer. But for now, his stats indicate he's not reviewing
 at a level consistent with the rest of the Neutron core reviewers.

  As part of the change, I'd like to propose Doug Wiegley as a new Neutron
 core reviewer. Doug has been actively reviewing code across not only all
 the Neutron projects, but also other projects such as infra. His help and
 work in the services split in December were the reason we were so
 successful in making that happen. Doug has also been instrumental in the
 Neutron LBaaS V2 rollout, as well as helping to merge code in the other
 neutron service repositories.

 I'd also like to take this time to remind everyone that reviewing code is
 a responsibility, in Neutron the same as other projects. And core reviewers
 are especially beholden to this responsibility. I'd also like to point out
 that +1/-1 reviews are very useful, and I encourage everyone to continue
 reviewing code even if you are not a core reviewer.

 Existing neutron cores, please vote +1/-1 for the addition of Doug to the
 core team.

 Thanks!
 Kyle

 [1]
 http://lists.openstack.org/pipermail/openstack-dev/2014-December/051986.html
 [2] http://russellbryant.net/openstack-stats/neutron-reviewers-90.txt

 __
 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] [neutron] Changes to the core team

2014-12-08 Thread Kyle Mestery
On Tue, Dec 2, 2014 at 9:59 AM, Kyle Mestery mest...@mestery.com wrote:

 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.

 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.

 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.

 Enough time has passed now, and Kevin and Henry have received enough +1
votes. So I'd like to welcome them to the core team!

Thanks,
Kyle


 Thanks!
 Kyle

 [1] http://stackalytics.com/report/contribution/neutron-group/180

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-08 Thread Paul Michali (pcm)
Way to go Kevin and Henry!



PCM (Paul Michali)

MAIL …..…. p...@cisco.com
IRC ……..… pc_m (irc.freenode.com)
TW ………... @pmichali
GPG Key … 4525ECC253E31A83
Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83




On Dec 8, 2014, at 11:02 AM, Kyle Mestery mest...@mestery.com wrote:

 On Tue, Dec 2, 2014 at 9:59 AM, Kyle Mestery mest...@mestery.com wrote:
 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.
 
 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.
 
 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.
 
 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.
 
 Enough time has passed now, and Kevin and Henry have received enough +1 
 votes. So I'd like to welcome them to the core team!
 
 Thanks,
 Kyle
  
 Thanks!
 Kyle
 
 [1] http://stackalytics.com/report/contribution/neutron-group/180
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-08 Thread trinath.soman...@freescale.com
Congratulation Kevin and Henry ☺

--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048

From: Kyle Mestery [mailto:mest...@mestery.com]
Sent: Monday, December 08, 2014 11:32 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] Changes to the core team

On Tue, Dec 2, 2014 at 9:59 AM, Kyle Mestery 
mest...@mestery.commailto:mest...@mestery.com wrote:
Now that we're in the thick of working hard on Kilo deliverables, I'd
like to make some changes to the neutron core team. Reviews are the
most important part of being a core reviewer, so we need to ensure
cores are doing reviews. The stats for the 180 day period [1] indicate
some changes are needed for cores who are no longer reviewing.

First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
neutron-core. Bob and Nachi have been core members for a while now.
They have contributed to Neutron over the years in reviews, code and
leading sub-teams. I'd like to thank them for all that they have done
over the years. I'd also like to propose that should they start
reviewing more going forward the core team looks to fast track them
back into neutron-core. But for now, their review stats place them
below the rest of the team for 180 days.

As part of the changes, I'd also like to propose two new members to
neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
been very active in reviews, meetings, and code for a while now. Henry
lead the DB team which fixed Neutron DB migrations during Juno. Kevin
has been actively working across all of Neutron, he's done some great
work on security fixes and stability fixes in particular. Their
comments in reviews are insightful and they have helped to onboard new
reviewers and taken the time to work with people on their patches.

Existing neutron cores, please vote +1/-1 for the addition of Henry
and Kevin to the core team.
Enough time has passed now, and Kevin and Henry have received enough +1 votes. 
So I'd like to welcome them to the core team!

Thanks,
Kyle

Thanks!
Kyle

[1] http://stackalytics.com/report/contribution/neutron-group/180

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-08 Thread Gariganti, Sudhakar Babu
Congrats Kevin and Henry ☺.

From: Kyle Mestery [mailto:mest...@mestery.com]
Sent: Monday, December 08, 2014 11:32 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] Changes to the core team

On Tue, Dec 2, 2014 at 9:59 AM, Kyle Mestery 
mest...@mestery.commailto:mest...@mestery.com wrote:
Now that we're in the thick of working hard on Kilo deliverables, I'd
like to make some changes to the neutron core team. Reviews are the
most important part of being a core reviewer, so we need to ensure
cores are doing reviews. The stats for the 180 day period [1] indicate
some changes are needed for cores who are no longer reviewing.

First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
neutron-core. Bob and Nachi have been core members for a while now.
They have contributed to Neutron over the years in reviews, code and
leading sub-teams. I'd like to thank them for all that they have done
over the years. I'd also like to propose that should they start
reviewing more going forward the core team looks to fast track them
back into neutron-core. But for now, their review stats place them
below the rest of the team for 180 days.

As part of the changes, I'd also like to propose two new members to
neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
been very active in reviews, meetings, and code for a while now. Henry
lead the DB team which fixed Neutron DB migrations during Juno. Kevin
has been actively working across all of Neutron, he's done some great
work on security fixes and stability fixes in particular. Their
comments in reviews are insightful and they have helped to onboard new
reviewers and taken the time to work with people on their patches.

Existing neutron cores, please vote +1/-1 for the addition of Henry
and Kevin to the core team.
Enough time has passed now, and Kevin and Henry have received enough +1 votes. 
So I'd like to welcome them to the core team!

Thanks,
Kyle

Thanks!
Kyle

[1] http://stackalytics.com/report/contribution/neutron-group/180

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-04 Thread Mathieu Rohon
On Thu, Dec 4, 2014 at 8:38 AM, Sumit Naiksatam
sumitnaiksa...@gmail.com wrote:
 On Wed, Dec 3, 2014 at 9:07 PM, Adam Young ayo...@redhat.com wrote:
 On 12/03/2014 06:24 PM, Sukhdev Kapur wrote:

 Congratulations Henry and Kevin. It has always been pleasure working with
 you guys.


 If I may express my opinion, Bob's contribution to ML2 has been quite
 substantial. The kind of stability ML2 has achieved makes a statement of his
 dedication to this work. I have worked very closely with Bob on several
 issues and co-chaired ML2-Subteam with him and have developed tremendous
 respect for his dedication.
 Reading his email reply makes me believe he wants to continue to contribute
 as core developer. Therefore, I would like to take an opportunity to appeal
 to the core team to consider granting him his wish - i.e. vote -1 on his
 removal.

 If I might venture an outside voice in support of Bob:  you don't want to
 chase away the continuity.  Yes, sometimes the day job makes us focus on
 things other than upstream work for a while, but I would say that you should
 err on the side of keeping someone that is otherwise still engaged.
 Especially when that core has been as fundamental on a project as I know Bob
 to have been on Quantumer Neutron.

 I would definitely echo the above sentiments; Bob has continually made
 valuable design contributions to ML2 and Neutron that go beyond the
 review count metric. Kindly consider keeping him as a part of the core
 team.

Working with bob in the ML2 sub team was a real pleasure. He is
providing a good technical and community leadership.
Its reviews are really valuable, since he always reviews a patch in
the context of the overall project and other work in progress.
This takes more time.

 That said, a big +1 to both, Henry and Kevin, as additions to the core
 team! Welcome!!

 Thanks,
 ~Sumit.







 regards..
 -Sukhdev






 On Wed, Dec 3, 2014 at 11:48 AM, Edgar Magana edgar.mag...@workday.com
 wrote:

 I give +2 to Henry and Kevin. So, Congratulations Folks!
 I have been working with both of them and great quality reviews are always
 coming out from them.

 Many thanks to Nachi and Bob for their hard work!

 Edgar

 On 12/2/14, 7:59 AM, Kyle Mestery mest...@mestery.com wrote:

 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.
 
 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.
 
 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.
 
 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.
 
 Thanks!
 Kyle
 
 [1] http://stackalytics.com/report/contribution/neutron-group/180
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-04 Thread Anita Kuno
On 12/04/2014 05:21 AM, Mathieu Rohon wrote:
 On Thu, Dec 4, 2014 at 8:38 AM, Sumit Naiksatam
 sumitnaiksa...@gmail.com wrote:
 On Wed, Dec 3, 2014 at 9:07 PM, Adam Young ayo...@redhat.com wrote:
 On 12/03/2014 06:24 PM, Sukhdev Kapur wrote:

 Congratulations Henry and Kevin. It has always been pleasure working with
 you guys.


 If I may express my opinion, Bob's contribution to ML2 has been quite
 substantial. The kind of stability ML2 has achieved makes a statement of his
 dedication to this work. I have worked very closely with Bob on several
 issues and co-chaired ML2-Subteam with him and have developed tremendous
 respect for his dedication.
 Reading his email reply makes me believe he wants to continue to contribute
 as core developer. Therefore, I would like to take an opportunity to appeal
 to the core team to consider granting him his wish - i.e. vote -1 on his
 removal.

 If I might venture an outside voice in support of Bob:  you don't want to
 chase away the continuity.  Yes, sometimes the day job makes us focus on
 things other than upstream work for a while, but I would say that you should
 err on the side of keeping someone that is otherwise still engaged.
 Especially when that core has been as fundamental on a project as I know Bob
 to have been on Quantumer Neutron.

 I would definitely echo the above sentiments; Bob has continually made
 valuable design contributions to ML2 and Neutron that go beyond the
 review count metric. Kindly consider keeping him as a part of the core
 team.
 
 Working with bob in the ML2 sub team was a real pleasure. He is
 providing a good technical and community leadership.
 Its reviews are really valuable, since he always reviews a patch in
 the context of the overall project and other work in progress.
 This takes more time.
 
 That said, a big +1 to both, Henry and Kevin, as additions to the core
 team! Welcome!!

 Thanks,
 ~Sumit.







 regards..
 -Sukhdev






 On Wed, Dec 3, 2014 at 11:48 AM, Edgar Magana edgar.mag...@workday.com
 wrote:

 I give +2 to Henry and Kevin. So, Congratulations Folks!
 I have been working with both of them and great quality reviews are always
 coming out from them.

 Many thanks to Nachi and Bob for their hard work!

 Edgar

 On 12/2/14, 7:59 AM, Kyle Mestery mest...@mestery.com wrote:

 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.

 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.

 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.

 Thanks!
 Kyle

 [1] http://stackalytics.com/report/contribution/neutron-group/180

I think we move into very dangerous territory if we are equating a core
review Gerrit permission (it is just a Gerrit permission, if it is
perceived as anything other than that that is a perception we have
created ourselves) with value as an OpenStack contributor.

I work with and value many OpenStack contributors daily who do not have
a core review Gerrit permission. I do not advocate for any decision that
even indirectly conveys the message that I value their contribution any
differently then any other contributor simply based on Gerrit permissions.

As to who in Neutron should or should not have certain Gerrit
permissions is not for me to say, as I do not have the perspective
(other than third party things) to have an opinion.

Thank you,
Anita.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-04 Thread Stefano Maffulli
On 12/04/2014 09:24 AM, Anita Kuno wrote:
 I think we move into very dangerous territory if we are equating a core
 review Gerrit permission (it is just a Gerrit permission, if it is
 perceived as anything other than that that is a perception we have
 created ourselves) with value as an OpenStack contributor.

+2 to what Anita is saying.

We're talking about a tick box in gerrit and it's mostly a burden, an
obligation.

It's also a box that has been proven multiple times to be
bi-directional: sometimes people get to go work on other things, or get
called back in active duty, and reassigned as code janitors.

I haven't read anything but great comments and thank you notes for Bob
and Nati. They're both great developers and have taken good care of
Neutron's code. Once they're ready to get dirty again, it'll take only a
couple of weeks doing reviews to be picked.

Now, if you (and, more importantly, your employer) thinks that being
core reviewer is a honor and your bonus depends on it, contact me
offline to discuss this further.

Regards,
Stef

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-04 Thread Adam Young

On 12/04/2014 01:44 PM, Stefano Maffulli wrote:

On 12/04/2014 09:24 AM, Anita Kuno wrote:

I think we move into very dangerous territory if we are equating a core
review Gerrit permission (it is just a Gerrit permission, if it is
perceived as anything other than that that is a perception we have
created ourselves) with value as an OpenStack contributor.

Forget the +2.  I would want Bob to have -2 capability on Neutron.

A -1 can be reset with just a new review.  A -2  is the real power of 
core.  The power to say this is wrong, and you need to address it 
before it moves on.


And I say that as someone who has been on the receiving end of multiple 
-2s...





+2 to what Anita is saying.

We're talking about a tick box in gerrit and it's mostly a burden, an
obligation.

It's also a box that has been proven multiple times to be
bi-directional: sometimes people get to go work on other things, or get
called back in active duty, and reassigned as code janitors.

I haven't read anything but great comments and thank you notes for Bob
and Nati. They're both great developers and have taken good care of
Neutron's code. Once they're ready to get dirty again, it'll take only a
couple of weeks doing reviews to be picked.

Now, if you (and, more importantly, your employer) thinks that being
core reviewer is a honor and your bonus depends on it, contact me
offline to discuss this further.

Regards,
Stef

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-04 Thread Jeremy Stanley
On 2014-12-03 23:24:41 + (+), Sukhdev Kapur wrote:
[...]
 If I may express my opinion, Bob's contribution to ML2 has been
 quite substantial. The kind of stability ML2 has achieved makes a
 statement of his dedication to this work. I have worked very
 closely with Bob on several issues and co-chaired ML2-Subteam with
 him and have developed tremendous respect for his dedication.

He is a remarkable contributor to the project--of that I have no
doubt.

 Reading his email reply makes me believe he wants to continue to
 contribute as core developer.

And here, I believe, is the source of the confusion: core
developer isn't a specific role in OpenStack projects. We have all
sorts of contributions including not only software development but
also documentation, translation, infrastructure management, quality
assurance, et cetera, et cetera... _and_ code review.

 Therefore, I would like to take an opportunity to appeal to the
 core team to consider granting him his wish - i.e. vote -1 on his
 removal.

The proposal was to remove him from the list of Neutron core
*reviewers* (the people tasked with wading through the endless
volumes of code contributed by developers day after day). This says
nothing of his remarkable ongoing contributions to the project,
except merely that he hasn't had a lot of time to review other
people's code contributions for a while now. It's not a stigma, it's
simply a reflection of which kinds of contributions he focuses on
making.
-- 
Jeremy Stanley

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-03 Thread Oleg Bondarev
+1! Congrats, Henry and Kevin!

On Tue, Dec 2, 2014 at 6:59 PM, Kyle Mestery mest...@mestery.com wrote:

 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.

 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.

 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.

 Thanks!
 Kyle

 [1] http://stackalytics.com/report/contribution/neutron-group/180

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-03 Thread Miguel Ángel Ajo
Congratulations to Henry and Kevin, very well deserved!,
keep up the good work! :)


Miguel Ángel Ajo


On Wednesday, 3 de December de 2014 at 09:44, Oleg Bondarev wrote:

 +1! Congrats, Henry and Kevin!
  
 On Tue, Dec 2, 2014 at 6:59 PM, Kyle Mestery mest...@mestery.com 
 (mailto:mest...@mestery.com) wrote:
  Now that we're in the thick of working hard on Kilo deliverables, I'd
  like to make some changes to the neutron core team. Reviews are the
  most important part of being a core reviewer, so we need to ensure
  cores are doing reviews. The stats for the 180 day period [1] indicate
  some changes are needed for cores who are no longer reviewing.
   
  First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
  neutron-core. Bob and Nachi have been core members for a while now.
  They have contributed to Neutron over the years in reviews, code and
  leading sub-teams. I'd like to thank them for all that they have done
  over the years. I'd also like to propose that should they start
  reviewing more going forward the core team looks to fast track them
  back into neutron-core. But for now, their review stats place them
  below the rest of the team for 180 days.
   
  As part of the changes, I'd also like to propose two new members to
  neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
  been very active in reviews, meetings, and code for a while now. Henry
  lead the DB team which fixed Neutron DB migrations during Juno. Kevin
  has been actively working across all of Neutron, he's done some great
  work on security fixes and stability fixes in particular. Their
  comments in reviews are insightful and they have helped to onboard new
  reviewers and taken the time to work with people on their patches.
   
  Existing neutron cores, please vote +1/-1 for the addition of Henry
  and Kevin to the core team.
   
  Thanks!
  Kyle
   
  [1] http://stackalytics.com/report/contribution/neutron-group/180
   
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org (mailto:OpenStack-dev@lists.openstack.org)
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
  
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org (mailto:OpenStack-dev@lists.openstack.org)
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
  
  


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-03 Thread Mathieu Rohon
Hi all,

It seems that a process with a survey for neutron core
election/removal was about to take place [1]. Has it been applied for
this proposal?
This proposal has been hardly discussed during neutron meetings
[2][3]. Many cores agree that the number of reviews shouldn't be the
only metrics. And this statement is reflected in the Survey Questions.
So I'm surprised to see such a proposal based on stackalitics figures.

[1]https://etherpad.openstack.org/p/neutron-peer-review
[2]http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-10-13-21.02.log.html
[3]http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-10-21-14.00.log.html

On Wed, Dec 3, 2014 at 9:44 AM, Oleg Bondarev obonda...@mirantis.com wrote:
 +1! Congrats, Henry and Kevin!

 On Tue, Dec 2, 2014 at 6:59 PM, Kyle Mestery mest...@mestery.com wrote:

 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.

 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.

 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.

 Thanks!
 Kyle

 [1] http://stackalytics.com/report/contribution/neutron-group/180

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-03 Thread Kyle Mestery
Mathieu:

The peer review proposal was NOT about removing core reviewers, that
is very clear in the proposal. The peer review proposal was about
deciding as a team what it means to be a core reviewer, and ensuring
core reviewers are doing that. I still plan to do try out the peer
review process in the coming weeks. But even with that process,
reviews are the main thing a core reviewer must be doing. If you're
not doing reviews upstream, especially for long stretches, you're not
really a core reviewer.

Thanks,
Kyle

On Wed, Dec 3, 2014 at 4:41 AM, Mathieu Rohon mathieu.ro...@gmail.com wrote:
 Hi all,

 It seems that a process with a survey for neutron core
 election/removal was about to take place [1]. Has it been applied for
 this proposal?
 This proposal has been hardly discussed during neutron meetings
 [2][3]. Many cores agree that the number of reviews shouldn't be the
 only metrics. And this statement is reflected in the Survey Questions.
 So I'm surprised to see such a proposal based on stackalitics figures.

 [1]https://etherpad.openstack.org/p/neutron-peer-review
 [2]http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-10-13-21.02.log.html
 [3]http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-10-21-14.00.log.html

 On Wed, Dec 3, 2014 at 9:44 AM, Oleg Bondarev obonda...@mirantis.com wrote:
 +1! Congrats, Henry and Kevin!

 On Tue, Dec 2, 2014 at 6:59 PM, Kyle Mestery mest...@mestery.com wrote:

 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.

 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.

 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.

 Thanks!
 Kyle

 [1] http://stackalytics.com/report/contribution/neutron-group/180

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-03 Thread Akihiro Motoki
+1 for Kevin and Henry. Thanks for your continuous efforts so far and
it would be great additions to our community.

I also would like to say great thanks to Bob and Nachi.
It would be really nice if we see their activities in reviews soon.
We already understand your contributions and skills, so
I believe you all can be back cores even though what is the conclusion
(as nova team usually does).

Thanks,
Akihiro



On Wed, Dec 3, 2014 at 12:59 AM, Kyle Mestery mest...@mestery.com wrote:
 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.

 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.

 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.

 Thanks!
 Kyle

 [1] http://stackalytics.com/report/contribution/neutron-group/180

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Akihiro Motoki amot...@gmail.com

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-03 Thread Edgar Magana
I give +2 to Henry and Kevin. So, Congratulations Folks!
I have been working with both of them and great quality reviews are always
coming out from them.

Many thanks to Nachi and Bob for their hard work!

Edgar

On 12/2/14, 7:59 AM, Kyle Mestery mest...@mestery.com wrote:

Now that we're in the thick of working hard on Kilo deliverables, I'd
like to make some changes to the neutron core team. Reviews are the
most important part of being a core reviewer, so we need to ensure
cores are doing reviews. The stats for the 180 day period [1] indicate
some changes are needed for cores who are no longer reviewing.

First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
neutron-core. Bob and Nachi have been core members for a while now.
They have contributed to Neutron over the years in reviews, code and
leading sub-teams. I'd like to thank them for all that they have done
over the years. I'd also like to propose that should they start
reviewing more going forward the core team looks to fast track them
back into neutron-core. But for now, their review stats place them
below the rest of the team for 180 days.

As part of the changes, I'd also like to propose two new members to
neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
been very active in reviews, meetings, and code for a while now. Henry
lead the DB team which fixed Neutron DB migrations during Juno. Kevin
has been actively working across all of Neutron, he's done some great
work on security fixes and stability fixes in particular. Their
comments in reviews are insightful and they have helped to onboard new
reviewers and taken the time to work with people on their patches.

Existing neutron cores, please vote +1/-1 for the addition of Henry
and Kevin to the core team.

Thanks!
Kyle

[1] http://stackalytics.com/report/contribution/neutron-group/180

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-03 Thread Sukhdev Kapur
Congratulations Henry and Kevin. It has always been pleasure working with
you guys.


If I may express my opinion, Bob's contribution to ML2 has been quite
substantial. The kind of stability ML2 has achieved makes a statement of
his dedication to this work. I have worked very closely with Bob on several
issues and co-chaired ML2-Subteam with him and have developed tremendous
respect for his dedication.
Reading his email reply makes me believe he wants to continue to contribute
as core developer. Therefore, I would like to take an opportunity to appeal
to the core team to consider granting him his wish - i.e. vote -1 on his
removal.

regards..
-Sukhdev






On Wed, Dec 3, 2014 at 11:48 AM, Edgar Magana edgar.mag...@workday.com
wrote:

 I give +2 to Henry and Kevin. So, Congratulations Folks!
 I have been working with both of them and great quality reviews are always
 coming out from them.

 Many thanks to Nachi and Bob for their hard work!

 Edgar

 On 12/2/14, 7:59 AM, Kyle Mestery mest...@mestery.com wrote:

 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.
 
 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.
 
 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.
 
 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.
 
 Thanks!
 Kyle
 
 [1] http://stackalytics.com/report/contribution/neutron-group/180
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-03 Thread Adam Young

On 12/03/2014 06:24 PM, Sukhdev Kapur wrote:
Congratulations Henry and Kevin. It has always been pleasure working 
with you guys.



If I may express my opinion, Bob's contribution to ML2 has been quite 
substantial. The kind of stability ML2 has achieved makes a statement 
of his dedication to this work. I have worked very closely with Bob on 
several issues and co-chaired ML2-Subteam with him and have developed 
tremendous respect for his dedication.
Reading his email reply makes me believe he wants to continue to 
contribute as core developer. Therefore, I would like to take an 
opportunity to appeal to the core team to consider granting him his 
wish - i.e. vote -1 on his removal.
If I might venture an outside voice in support of Bob:  you don't want 
to chase away the continuity.  Yes, sometimes the day job makes us focus 
on things other than upstream work for a while, but I would say that you 
should err on the side of keeping someone that is otherwise still 
engaged.  Especially when that core has been as fundamental on a project 
as I know Bob to have been on Quantumer Neutron.







regards..
-Sukhdev






On Wed, Dec 3, 2014 at 11:48 AM, Edgar Magana 
edgar.mag...@workday.com mailto:edgar.mag...@workday.com wrote:


I give +2 to Henry and Kevin. So, Congratulations Folks!
I have been working with both of them and great quality reviews
are always
coming out from them.

Many thanks to Nachi and Bob for their hard work!

Edgar

On 12/2/14, 7:59 AM, Kyle Mestery mest...@mestery.com
mailto:mest...@mestery.com wrote:

Now that we're in the thick of working hard on Kilo deliverables, I'd
like to make some changes to the neutron core team. Reviews are the
most important part of being a core reviewer, so we need to ensure
cores are doing reviews. The stats for the 180 day period [1]
indicate
some changes are needed for cores who are no longer reviewing.

First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
neutron-core. Bob and Nachi have been core members for a while now.
They have contributed to Neutron over the years in reviews, code and
leading sub-teams. I'd like to thank them for all that they have done
over the years. I'd also like to propose that should they start
reviewing more going forward the core team looks to fast track them
back into neutron-core. But for now, their review stats place them
below the rest of the team for 180 days.

As part of the changes, I'd also like to propose two new members to
neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin
have
been very active in reviews, meetings, and code for a while now.
Henry
lead the DB team which fixed Neutron DB migrations during Juno. Kevin
has been actively working across all of Neutron, he's done some great
work on security fixes and stability fixes in particular. Their
comments in reviews are insightful and they have helped to
onboard new
reviewers and taken the time to work with people on their patches.

Existing neutron cores, please vote +1/-1 for the addition of Henry
and Kevin to the core team.

Thanks!
Kyle

[1] http://stackalytics.com/report/contribution/neutron-group/180

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
mailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
mailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-03 Thread Sumit Naiksatam
On Wed, Dec 3, 2014 at 9:07 PM, Adam Young ayo...@redhat.com wrote:
 On 12/03/2014 06:24 PM, Sukhdev Kapur wrote:

 Congratulations Henry and Kevin. It has always been pleasure working with
 you guys.


 If I may express my opinion, Bob's contribution to ML2 has been quite
 substantial. The kind of stability ML2 has achieved makes a statement of his
 dedication to this work. I have worked very closely with Bob on several
 issues and co-chaired ML2-Subteam with him and have developed tremendous
 respect for his dedication.
 Reading his email reply makes me believe he wants to continue to contribute
 as core developer. Therefore, I would like to take an opportunity to appeal
 to the core team to consider granting him his wish - i.e. vote -1 on his
 removal.

 If I might venture an outside voice in support of Bob:  you don't want to
 chase away the continuity.  Yes, sometimes the day job makes us focus on
 things other than upstream work for a while, but I would say that you should
 err on the side of keeping someone that is otherwise still engaged.
 Especially when that core has been as fundamental on a project as I know Bob
 to have been on Quantumer Neutron.

I would definitely echo the above sentiments; Bob has continually made
valuable design contributions to ML2 and Neutron that go beyond the
review count metric. Kindly consider keeping him as a part of the core
team.

That said, a big +1 to both, Henry and Kevin, as additions to the core
team! Welcome!!

Thanks,
~Sumit.







 regards..
 -Sukhdev






 On Wed, Dec 3, 2014 at 11:48 AM, Edgar Magana edgar.mag...@workday.com
 wrote:

 I give +2 to Henry and Kevin. So, Congratulations Folks!
 I have been working with both of them and great quality reviews are always
 coming out from them.

 Many thanks to Nachi and Bob for their hard work!

 Edgar

 On 12/2/14, 7:59 AM, Kyle Mestery mest...@mestery.com wrote:

 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.
 
 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.
 
 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.
 
 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.
 
 Thanks!
 Kyle
 
 [1] http://stackalytics.com/report/contribution/neutron-group/180
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-02 Thread Mark McClain

 On Dec 2, 2014, at 10:59 AM, Kyle Mestery mest...@mestery.com wrote:
 
 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

Thanks to Bob and Nachi for all of their hard work during the early cycles of 
Quantum/Neutron.

 
 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.
 
 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.
 

+1 to Henry and Kevin.  They’ve both been great contributors the last few 
cycles and would make great cores.

mark
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-02 Thread Salvatore Orlando
I am happy with the proposed change in the core team.

Many thanks to the outgoing members and a warm welcome to hell (err core
team) to Henry and Kevin!

Salvatore
Il 02/dic/2014 17:20 Mark McClain m...@mcclain.xyz ha scritto:


  On Dec 2, 2014, at 10:59 AM, Kyle Mestery mest...@mestery.com wrote:
 
  First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
  neutron-core. Bob and Nachi have been core members for a while now.
  They have contributed to Neutron over the years in reviews, code and
  leading sub-teams. I'd like to thank them for all that they have done
  over the years. I'd also like to propose that should they start
  reviewing more going forward the core team looks to fast track them
  back into neutron-core. But for now, their review stats place them
  below the rest of the team for 180 days.

 Thanks to Bob and Nachi for all of their hard work during the early cycles
 of Quantum/Neutron.

 
  As part of the changes, I'd also like to propose two new members to
  neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
  been very active in reviews, meetings, and code for a while now. Henry
  lead the DB team which fixed Neutron DB migrations during Juno. Kevin
  has been actively working across all of Neutron, he's done some great
  work on security fixes and stability fixes in particular. Their
  comments in reviews are insightful and they have helped to onboard new
  reviewers and taken the time to work with people on their patches.
 
  Existing neutron cores, please vote +1/-1 for the addition of Henry
  and Kevin to the core team.
 

 +1 to Henry and Kevin.  They’ve both been great contributors the last few
 cycles and would make great cores.

 mark
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-02 Thread Armando M.
Congrats to Henry and Kevin, +1!
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-02 Thread Robert Kukura
Assuming I still have a vote, I vote +1 for adding Henry and Kevin, both 
of whom I am confident will do a great job as core reviewer.


I'd ask people to consider voting against dropping me from core (and I 
vote -1 on that if I get a vote). During Juno, my plan was to balance my 
time between neutron core work and implementing GBP as part of neutron. 
Unfortunately, that did not go as planned, and the Juno GBP work has 
continued outside neutron, requiring most of my attention, and leaving 
little time for neutron work. I've felt that it would be irresponsible 
to do drive-by reviews in neutron while this is the case, so had pretty 
much stopped doing neutron reviews until the point when I could devote 
enough attention to follow through on the patches that I review.  But 
I've continued to participate in other ways, including co-leading the 
ML2 sub team. The Juno GBP work is just about complete, and I have 
agreement from my management to make neutron work my top priority for 
the remainder of Kilo. So, as core or not, I expect to be ramping my 
neutron reviewing back up very quickly, and plan to be in SLC next week 
for the mid cycle meetup. If you agree that my contributions as a core 
reviewer have been worthwhile over the long term, and trust that I will 
do as I say and make core reviews my top priority for the remainder of 
Kilo, I ask that you vote -1 on dropping me. If I am not dropped and my 
stats don't improve significantly in the next 30 days, I'll happily 
resign from core.


Regarding dropping Nachi, I will pass, as I've not been paying enough 
attention to the reviews to judge his recent level of contribution.


-Bob

On 12/2/14 10:59 AM, Kyle Mestery wrote:

Now that we're in the thick of working hard on Kilo deliverables, I'd
like to make some changes to the neutron core team. Reviews are the
most important part of being a core reviewer, so we need to ensure
cores are doing reviews. The stats for the 180 day period [1] indicate
some changes are needed for cores who are no longer reviewing.

First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
neutron-core. Bob and Nachi have been core members for a while now.
They have contributed to Neutron over the years in reviews, code and
leading sub-teams. I'd like to thank them for all that they have done
over the years. I'd also like to propose that should they start
reviewing more going forward the core team looks to fast track them
back into neutron-core. But for now, their review stats place them
below the rest of the team for 180 days.

As part of the changes, I'd also like to propose two new members to
neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
been very active in reviews, meetings, and code for a while now. Henry
lead the DB team which fixed Neutron DB migrations during Juno. Kevin
has been actively working across all of Neutron, he's done some great
work on security fixes and stability fixes in particular. Their
comments in reviews are insightful and they have helped to onboard new
reviewers and taken the time to work with people on their patches.

Existing neutron cores, please vote +1/-1 for the addition of Henry
and Kevin to the core team.

Thanks!
Kyle

[1] http://stackalytics.com/report/contribution/neutron-group/180

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-02 Thread Carl Baldwin
+1 from me for all the changes.  I appreciate the work from all four
of these excellent contributors.  I'm happy to welcome Henry and Kevin
as new core reviewers.  I also look forward to continuing to work with
Nachi and Bob as important members of the community.

Carl

On Tue, Dec 2, 2014 at 8:59 AM, Kyle Mestery mest...@mestery.com wrote:
 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.

 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.

 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.

 Thanks!
 Kyle

 [1] http://stackalytics.com/report/contribution/neutron-group/180

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-02 Thread Nati Ueno
Hi folks

Congrats! Henry and Kevin.
I'll keep contributing the community, but Thank you for working with
me as core team :)

Best
Nachi

2014-12-03 2:05 GMT+09:00 Carl Baldwin c...@ecbaldwin.net:
 +1 from me for all the changes.  I appreciate the work from all four
 of these excellent contributors.  I'm happy to welcome Henry and Kevin
 as new core reviewers.  I also look forward to continuing to work with
 Nachi and Bob as important members of the community.

 Carl

 On Tue, Dec 2, 2014 at 8:59 AM, Kyle Mestery mest...@mestery.com wrote:
 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.

 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.

 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.

 Thanks!
 Kyle

 [1] http://stackalytics.com/report/contribution/neutron-group/180

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Nachi Ueno
email:nati.u...@gmail.com
twitter:http://twitter.com/nati

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-02 Thread Aaron Rosen
+1 for Kevin and Henry!

On Tue, Dec 2, 2014 at 10:40 AM, Nati Ueno nati.u...@gmail.com wrote:

 Hi folks

 Congrats! Henry and Kevin.
 I'll keep contributing the community, but Thank you for working with
 me as core team :)

 Best
 Nachi

 2014-12-03 2:05 GMT+09:00 Carl Baldwin c...@ecbaldwin.net:
  +1 from me for all the changes.  I appreciate the work from all four
  of these excellent contributors.  I'm happy to welcome Henry and Kevin
  as new core reviewers.  I also look forward to continuing to work with
  Nachi and Bob as important members of the community.
 
  Carl
 
  On Tue, Dec 2, 2014 at 8:59 AM, Kyle Mestery mest...@mestery.com
 wrote:
  Now that we're in the thick of working hard on Kilo deliverables, I'd
  like to make some changes to the neutron core team. Reviews are the
  most important part of being a core reviewer, so we need to ensure
  cores are doing reviews. The stats for the 180 day period [1] indicate
  some changes are needed for cores who are no longer reviewing.
 
  First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
  neutron-core. Bob and Nachi have been core members for a while now.
  They have contributed to Neutron over the years in reviews, code and
  leading sub-teams. I'd like to thank them for all that they have done
  over the years. I'd also like to propose that should they start
  reviewing more going forward the core team looks to fast track them
  back into neutron-core. But for now, their review stats place them
  below the rest of the team for 180 days.
 
  As part of the changes, I'd also like to propose two new members to
  neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
  been very active in reviews, meetings, and code for a while now. Henry
  lead the DB team which fixed Neutron DB migrations during Juno. Kevin
  has been actively working across all of Neutron, he's done some great
  work on security fixes and stability fixes in particular. Their
  comments in reviews are insightful and they have helped to onboard new
  reviewers and taken the time to work with people on their patches.
 
  Existing neutron cores, please vote +1/-1 for the addition of Henry
  and Kevin to the core team.
 
  Thanks!
  Kyle
 
  [1] http://stackalytics.com/report/contribution/neutron-group/180
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 --
 Nachi Ueno
 email:nati.u...@gmail.com
 twitter:http://twitter.com/nati

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] Changes to the core team

2014-12-02 Thread Gary Kotton
+1 for both. Long overdue!

From: Aaron Rosen aaronoro...@gmail.commailto:aaronoro...@gmail.com
Reply-To: OpenStack List 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Wednesday, December 3, 2014 at 4:13 AM
To: OpenStack List 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron] Changes to the core team

+1 for Kevin and Henry!

On Tue, Dec 2, 2014 at 10:40 AM, Nati Ueno 
nati.u...@gmail.commailto:nati.u...@gmail.com wrote:
Hi folks

Congrats! Henry and Kevin.
I'll keep contributing the community, but Thank you for working with
me as core team :)

Best
Nachi

2014-12-03 2:05 GMT+09:00 Carl Baldwin 
c...@ecbaldwin.netmailto:c...@ecbaldwin.net:
 +1 from me for all the changes.  I appreciate the work from all four
 of these excellent contributors.  I'm happy to welcome Henry and Kevin
 as new core reviewers.  I also look forward to continuing to work with
 Nachi and Bob as important members of the community.

 Carl

 On Tue, Dec 2, 2014 at 8:59 AM, Kyle Mestery 
 mest...@mestery.commailto:mest...@mestery.com wrote:
 Now that we're in the thick of working hard on Kilo deliverables, I'd
 like to make some changes to the neutron core team. Reviews are the
 most important part of being a core reviewer, so we need to ensure
 cores are doing reviews. The stats for the 180 day period [1] indicate
 some changes are needed for cores who are no longer reviewing.

 First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from
 neutron-core. Bob and Nachi have been core members for a while now.
 They have contributed to Neutron over the years in reviews, code and
 leading sub-teams. I'd like to thank them for all that they have done
 over the years. I'd also like to propose that should they start
 reviewing more going forward the core team looks to fast track them
 back into neutron-core. But for now, their review stats place them
 below the rest of the team for 180 days.

 As part of the changes, I'd also like to propose two new members to
 neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have
 been very active in reviews, meetings, and code for a while now. Henry
 lead the DB team which fixed Neutron DB migrations during Juno. Kevin
 has been actively working across all of Neutron, he's done some great
 work on security fixes and stability fixes in particular. Their
 comments in reviews are insightful and they have helped to onboard new
 reviewers and taken the time to work with people on their patches.

 Existing neutron cores, please vote +1/-1 for the addition of Henry
 and Kevin to the core team.

 Thanks!
 Kyle

 [1] 
 http://stackalytics.com/report/contribution/neutron-group/180https://urldefense.proofpoint.com/v2/url?u=http-3A__stackalytics.com_report_contribution_neutron-2Dgroup_180d=AAMFaQc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNcm=wwXEfqogDKsBxx77lGdC6Svp6cK-un0VngT8lZCbv3ws=l3HU22Yx4ArL_aeQbF3CU7vnwJoAha2yk2dBVmfVNKoe=

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Nachi Ueno
email:nati.u...@gmail.commailto:email%3anati.u...@gmail.com
twitter:http://twitter.com/natihttps://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_natid=AAMFaQc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNcm=wwXEfqogDKsBxx77lGdC6Svp6cK-un0VngT8lZCbv3ws=MZbEJRJVGIrgDO3jYcYNJmzAYIN5JWvktt53O42LRaYe=

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev