On 09/12/2015 01:14 PM, Armando M. wrote:

On 12 September 2015 at 18:38, Gary Kotton <gkot...@vmware.com
<mailto:gkot...@vmware.com>> wrote:

    Thanks! You did a great job. Looking back you made some very tough and
    healthy decisions. Neutron has a new lease on life!
    It is tradition that the exiting PTL buy drinks for the community :)

Ok, none of these kind words make you change your mind? This project needs you!

I can only add kind words myself, thanks for all the hard work over the past three cycles Kyle!

-Brian


    From: "mest...@mestery.com <mailto:mest...@mestery.com>"
    <mest...@mestery.com <mailto:mest...@mestery.com>>
    Reply-To: OpenStack List <openstack-dev@lists.openstack.org
    <mailto:openstack-dev@lists.openstack.org>>
    Date: Saturday, September 12, 2015 at 12:12 AM
    To: OpenStack List <openstack-dev@lists.openstack.org
    <mailto:openstack-dev@lists.openstack.org>>
    Subject: [openstack-dev] [neutron] PTL Non-Candidacy

    I'm writing to let everyone know that I do not plan to run for Neutron PTL
    for a fourth cycle. Being a PTL is a rewarding but difficult job, as Morgan
    recently put it in his non-candidacy email [1]. But it goes further than
    that for me. As Flavio put it in his post about "Being a PTL" [2], it's a
    full time job. In the case of Neutron, it's more than a full time job, it's
    literally an always on job.

    I've tried really hard over my three cycles as PTL to build a stronger web
    of trust so the project can grow, and I feel that's been accomplished. We
    have a strong bench of future PTLs and leaders ready to go, I'm excited to
    watch them lead and help them in anyway I can.

    As was said by Zane in a recent email [3], while Heat may have pioneered the
    concept of rotating PTL duties with each cycle, I'd like to highly encourage
    Neutron and other projects to do the same. Having a deep bench of leaders
    supporting each other is important for the future of all projects.

    See you all in Tokyo!
    Kyle

    [1]
    
http://lists.openstack.org/pipermail/openstack-dev/2015-September/074157.html
    [1]
    
http://lists.openstack.org/pipermail/openstack-dev/2015-September/073986.html
    [2]
    
http://lists.openstack.org/pipermail/openstack-dev/2015-September/074242.html

    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
    <http://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

Reply via email to