settingsLogin | Registersettings

[openstack-dev] [election] [TC] TC Candidacy

0 votes

I'd like to announce my candidacy for the TC election.

A bit about me and my involvement with OpenStack: I've been
involved with OpenStack for a long time now in various capacities.
Most recently, I was the PTL for Neutron for the Juno, Kilo and
Liberty cycles. I've been a core reviewer on Neutron since July of
2013. I helped to write the Project Team Guide [1] by participating
in the sprint during it's creation. I founded and continue to lead
the Minnesota OpenStack Meetup [2]. I've spoken at many OpenStack
conferences and other Open Source conferences.

Given the "Big Tent" governance model we now find ourselves under,
my experience in leading Neutron as it adopted the "Neutron Stadium"
is very relevant to the current state of OpenStack. While leading
Neutron, the "Neutron Stadium" allowed many new project teams to
develop and grow. I hope to be able to work with new OpenStack
projects and guide them as they grow into OpenStack projects. I'd
also like to ensure the uniqueness which each projects brings to the
table isn't lost when it becomes an OpenStack project. While I
firmly believe each project must adopt the Four Opens [3] in order
to become an OpenStack project, it's important to not lose the
original spark which was lit to start these projects as they move
into the Big Tent.

If I'm elected, I will continue to dedicate time to work upstream
and help new and old projects. I'll work hard to assist anyone who
requests my help. And I'll continue to strive to do what I can
to ensure OpenStack's future success.

OpenStack has been an amazing community to be involved in. I am
fortunate to have been a part of this community for a long time now,
and should I be elected, I look forward to the chance to help guide
it while serving on the TC for the next two cycles!

Thank you!

--
Kyle Mestery
IRC: mestery

[1] http://docs.openstack.org/project-team-guide/
[2] http://www.meetup.com/Minnesota-OpenStack-Meetup/
[3]
http://docs.openstack.org/project-team-guide/introduction.html#the-four-opens


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Sep 29, 2015 in openstack-dev by Kyle_Mestery (16,960 points)   3 3 7
retagged Feb 4, 2016

6 Responses

0 votes

I am writing to announce my candidacy a position on the TC.

I am not your typical candidate, which is one reason that I am asking for your vote. I have a technical background, with over a decade of software development experience. I have a marketing background, with over a decade of Technology, Product and Brand marketing experience. I have a business development background and have been an entrepreneur. I have been a product manager and a software planner. It's this combination of experiences that I have accumulated during my almost 35 years in the technology industry that I believe will enable me to provide unique value as a member of the TC.

I have been an active member in the community since 2013, working with Community teams to understand market-segment needs and/or barriers to their deployment of OpenStack and bringing that information to the Community in the form of specs, blueprints, prototypes and user stories (Win The Enterprise WG, Enterprise WG, Product WG). These teams have brought resources to develop these capabilities (one example is improving upgrade capabilities through versioned objects implementation) and have been able to close gaps resulting in expanding Enterprise deployments of OpenStack.

I believe that a diverse Community will enable us to develop more innovative software that will meet the needs of global markets. I work with both the Diversity Working Group and the Women of OpenStack to help strengthen the diversity of our Community.

As a TC member, I will work to support our success by utilizing my project/program management experience. Specifically, I will:
1) Tap the collective market knowledge within our Community to identify innovative capabilities that will define the defacto cloud computing platform of the future.
2) Work to bring projects together to define and implement cross-project capabilities and initiatives.
3) Support the development of a multi-release roadmap definition and communication process.

As cross-project coordination needs expand and concepts like big tent stretch our capabilities, I believe that my skill-sets, experiences, and values align well with the emerging needs within our community.

I would appreciate the opportunity to further my contributions to our Community and thank you for your consideration.

Carol Barrett


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Sep 29, 2015 by Barrett,_Carol_L (3,380 points)   2 3
0 votes

Hi!

I would like to continue serving on the TC, if you'll have me.

Although past performance is no guarantee of future profits, I think
it's worth noting that I've been doing this for a while now. I was on
the precursor to the TC, the Project Policy Board. Over the time I've
been the instigator or a key player in several major initiatives, such
as Stackforge, the Project Testing Interface and The Big Tent.

Thing is, that really doesn't matter, because while understanding the
past is important if you want to avoid re-learning the same lessons, we
need to be firmly focused on the future, and to be willing to make
changes as needed to accommodate the reality we find ourselves in.

I think it's time for the TC to take a more active position on technical
design issues.

This past cycle, Sean and Anne wrote up a spec that came from the last
summit around standardization of the keystone catalog data. Doug dove in
to issues around Glance upload. Both are instances where clear technical
leadership and design was needed, and in both instances we understand
that it goes hand in hand with being clear to our deployers and end
users about what it is that we expect via interaction with DefCore.

I want to see more things like that, and I'd like to be involved with
moving the TC another step down the road from being a "policy board" to
being a "technical committee".

On the social side, I'd like to work with people on figuring out how to
expand our capacity for trust across the project. We set up all of our
systems and culture initially to protect against bad-faith and
antagonistic behavior - but we've been doing this long enough now that I
think the assumption of bad and protective behavior is counter
productive. We're never going to get the big issues fixed if we can't
land hard patches.

Finally, I think we need to re-think our mission.

The OpenStack Mission: to produce the ubiquitous Open Source Cloud
Computing platform that will meet the needs of public and private
clouds regardless of size, by being simple to implement and
massively scalable.

That mission is about clouds, and I think it has completely forgotten a
key ingredient - users. Focusing on meeting the needs of the clouds
themselves has gotten us to an amazing place, but in order to take the
next step we have to start putting the consumers of OpenStack Clouds
front and center in our thinking.

Thank you for the trust you've placed in me so far, and I hope I've
lived up to it well enough for you to keep me around.

Monty


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Sep 29, 2015 by Monty_Taylor (22,780 points)   2 5 8
0 votes

+1

I also completely agree on the idea of re-thinking our mission. The key to OpenStack’s future will completely be about the users and supporting them in their effort to use the software at scale.

Philip

On Sep 29, 2015, at 1:54 PM, Monty Taylor mordred@inaugust.com wrote:

Hi!

I would like to continue serving on the TC, if you'll have me.

Although past performance is no guarantee of future profits, I think it's worth noting that I've been doing this for a while now. I was on the precursor to the TC, the Project Policy Board. Over the time I've been the instigator or a key player in several major initiatives, such as Stackforge, the Project Testing Interface and The Big Tent.

Thing is, that really doesn't matter, because while understanding the past is important if you want to avoid re-learning the same lessons, we need to be firmly focused on the future, and to be willing to make changes as needed to accommodate the reality we find ourselves in.

I think it's time for the TC to take a more active position on technical
design issues.

This past cycle, Sean and Anne wrote up a spec that came from the last summit around standardization of the keystone catalog data. Doug dove in to issues around Glance upload. Both are instances where clear technical leadership and design was needed, and in both instances we understand that it goes hand in hand with being clear to our deployers and end users about what it is that we expect via interaction with DefCore.

I want to see more things like that, and I'd like to be involved with moving the TC another step down the road from being a "policy board" to being a "technical committee".

On the social side, I'd like to work with people on figuring out how to expand our capacity for trust across the project. We set up all of our systems and culture initially to protect against bad-faith and antagonistic behavior - but we've been doing this long enough now that I think the assumption of bad and protective behavior is counter productive. We're never going to get the big issues fixed if we can't land hard patches.

Finally, I think we need to re-think our mission.

The OpenStack Mission: to produce the ubiquitous Open Source Cloud
Computing platform that will meet the needs of public and private
clouds regardless of size, by being simple to implement and
massively scalable.

That mission is about clouds, and I think it has completely forgotten a key ingredient - users. Focusing on meeting the needs of the clouds themselves has gotten us to an amazing place, but in order to take the next step we have to start putting the consumers of OpenStack Clouds front and center in our thinking.

Thank you for the trust you've placed in me so far, and I hope I've lived up to it well enough for you to keep me around.

Monty


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Sep 29, 2015 by Philip_Schwartz (360 points)  
0 votes

Greetings,

I'm writing to submit my candidacy for election to the OpenStack
Technical Committee.

By way of introduction, my name is Amrith Kumar, I am the Chief
Technology Officer[1] at Tesora[2], a company focused on
Database-as-a-Service and the OpenStack Trove project.

As OpenStack evolves, so too should the Technical Committee. I believe
that the Technical Committee has a very high representation from the
core (nova, cinder, swift, glance, neutron, ...) projects, and there
needs to be more representation of the other projects in OpenStack
that are not part of this core (trove, sahara, ...). I believe that
the future success of OpenStack depends heavily on the successful
integration of these non-core projects, and the ease with which people
can deploy the core and non-core components of OpenStack.

If elected, I would bring a different perspective to the TC, one that
would broaden the representation the non-core projects on the
Technical Committee.

Here is a quick summary of what I do relative to OpenStack, and why I
believe that you should consider my candidacy for TC

  • active contributor and member of the core review team for Trove,
    and spend all of my time on upstream development activities
    related to OpenStack Trove. I am also a periodic contributor to
    Oslo and the Trove liaison to Oslo

  • authored the book on OpenStack Trove[3] along with Doug Shelley,
    a co-worker and contributor to the Trove project

  • OpenStack evangelism and outreach activities include

      - Frequent participant and speaker at a variety of technical
        events where I have spoken about OpenStack in general, and
        sometimes Trove in particular
    
      - Frequent participant in the Boston OpenStack Meetup,
        presenter at a number of OpenStack Meetups all over the
        country
    
      - Actively promoting an initiative called "OpenStack in the
        Classroom" [4] that I shared on the mailing list several
        months ago. I have had good luck promoting it to a number
        of colleges in the Boston area
    
    • chosen by the OpenStack Foundation to serve as part of a global
      committee of OpenStack experts developing a list of Domains and
      Tasks essential for OpenStack administration professionals.

I believe firmly that the long term success of OpenStack depends on
the ease with which users are able to deploy and bring a cloud into
production. The big tent proposal was a very important step in that
direction but much remains to be done.

It is essential that we make it easier for users to deploy and use
other projects that are not part of the "core", projects like Trove,
Sahara, Magnum, and so on.

A current example of the kind(s) of issues that I believe to exist
relates to the creation of protected 'service resources' that make it
possible for services to provision servers and storage in tenant
context while making it impossible for tenants to manipulate these
resources other than through the service that provisioned them
[5],[6].

This is an example of a specific initiative that I have been working
with members of the community to address.

This is a feature that will have to be provided by the core projects
and the beneficiaries are the non-core projects that request these
'service resources'.

I believe that it is imperative that the Technical Committee take a
leadership role in addressing these kinds of issues, as it did in the
big-tent approach.

The activities of the TC align closely with my own skills and past
experience which include architecting and implementing complex
computer architecture, with flexible and extensible API's and then
working with diverse teams to deliver the software that implements
these. I work very effectively as a facilitator of teams and in
helping groups of people work together.

I believe that I will be able to work with the rest of the team and
drive this kind of activity to successful completion. I am committed
to the success of OpenStack and would like to contribute further as a
member of the Technical Committee.

I look forward to your support in the upcoming election, and I thank
the outgoing members of the TC for their hard work and the solid
foundation that they have laid for future committees.

Here are some more links:

 Official Candidacy: https://review.openstack.org/#/c/229073/
 Review history: https://review.openstack.org/#/q/reviewer:9664,n,z
 Commit history: https://review.openstack.org/#/q/owner:9664,n,z
 Stackalytics: http://stackalytics.com/?user_id=amrith&release=all
 Foundation: http://www.openstack.org/community/members/profile/15733
 Freenode: amrith
 LinkedIn: http://www.linkedin.com/in/amrith

Thank you,

-amrith

[1] http://www.tesora.com/people/amrith-kumar/
[2] http://www.tesora.com/
[3] http://www.apress.com/9781484212226
[4] http://openstack.markmail.org/thread/ukckrielspbrjejp
[5] https://review.openstack.org/#/c/186357/
[6] https://review.openstack.org/#/c/203880/


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Sep 29, 2015 by Amrith_Kumar (10,500 points)   2 4 4
0 votes

Hi all!

I'm announcing my candidacy for a position on the OpenStack Technical
Committee.

On October 1st I will be employed by the OpenStack Foundation as
a Cross-Project Developer Coordinator to help bring focus and support to
cross-project initiatives within the cross-project specs, Def Core, The Product
Working group, etc.

I feel the items below have enabled others across this project to strive for
quality. If you would all have me as a member of the Technical Committee, you
can help me to enable more quality work in OpenStack.

  • I have been working in OpenStack since 2010. I spent a good amount of my time
    working on OpenStack in my free time before being paid full time to work on
    it. It has been an important part of my life, and rewarding to see what we
    have all achieved together.

  • I was PTL for the Cinder project in the Kilo and Liberty releases for two
    cross-project reasons:

    • Third party continuous integration (CI).
    • Stop talking about rolling upgrades, and actually make it happen for
      operators.
  • I led the effort in bringing third party continuous integration to the
    Cinder project for more than 60 different drivers. [1]

    • I removed 25 different storage drivers from Cinder to bring quality to the
      project to ensure what was in the Kilo release would work for operators.
      I did what I believed was right, regardless of whether it would cost me
      re-election for PTL [2].
    • In my conversations with other projects, this has enabled others to
      follow the same effort. Continuing this trend of quality cross-project will
      be my next focus.
  • During my first term of PTL for Cinder, the team, and much respect to Thang
    Pham working on an effort to end the rolling upgrade problem, not just for
    Cinder, but for all projects.

    • First step was making databases independent from services via Oslo
      versioned objects.
    • In Liberty we have a solution coming that helps with RPC versioned messages
      to allow upgrading services independently.
  • I have attempted to help with diversity in our community.

    • Helped lead our community to raise $17,403 for the Ada Initiative [3],
      which was helping address gender-diversity with a focus in open source.
    • For the Vancouver summit, I helped bring in the ally skills workshops from
      the Ada Initiative, so that our community can continue to be a welcoming
      environment [4].
  • Within the Cinder team, I have enabled all to provide good documentation for
    important items in our release notes in Kilo [5] and Liberty [6].

    • Other projects have reached out to me after Kilo feeling motivated for this
      same effort. I've explained in the August 2015 Operators midcycle sprint
      that I will make this a cross-project effort in order to provide better
      communication to our operators and users.
  • I started an OpenStack Dev List summary in the OpenStack Weekly Newsletter
    (What you need to know from the developer's list), in order to enable others
    to keep up with the dev list on important cross-project information. [7][8]

  • I created the Cinder v2 API which has brought consistency in
    request/responses with other OpenStack projects.

    • I documented Cinder v1 and Cinder v2 API's. Later on I created the Cinder
      API reference documentation content. The attempt here was to enable others
      to have somewhere to start, to continue quality documentation with
      continued developments.

Please help me to do more positive work in this project. It would be an
honor to be member of your technical committee.

Thank you,
Mike Perez

Official Candidacy: https://review.openstack.org/#/c/229298/2
Review History: https://review.openstack.org/#/q/reviewer:170,n,z
Commit History: https://review.openstack.org/#/q/owner:170,n,z
Stackalytics: http://stackalytics.com/?user_id=thingee
Foundation: https://www.openstack.org/community/members/profile/4840
IRC Freenode: thingee
Website: http://thing.ee

[1] - http://lists.openstack.org/pipermail/openstack-dev/2015-January/054614.html
[2] - https://review.openstack.org/#/q/status:merged+project:openstack/cinder+branch:master+topic:cinder-driver-removals,n,z
[3] - http://lists.openstack.org/pipermail/openstack-dev/2014-October/047892.html
[4] - http://lists.openstack.org/pipermail/openstack-dev/2015-May/064156.html
[5] - https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Block_Storage_.28Cinder.29
[6] - https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Block_Storage_.28Cinder.29
[7] - http://www.openstack.org/blog/2015/09/openstack-community-weekly-newsletter-sept-12-18/
[8] - http://www.openstack.org/blog/2015/09/openstack-weekly-community-newsletter-sept-19-25/


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Sep 30, 2015 by Mike_Perez (13,120 points)   2 4 6
0 votes

Mike - Congrats on your new position! Looking forward to working with you.
Carol

-----Original Message-----
From: Mike Perez [mailto:thingee@gmail.com]
Sent: Wednesday, September 30, 2015 1:55 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [election][TC] TC Candidacy

Hi all!

I'm announcing my candidacy for a position on the OpenStack Technical Committee.

On October 1st I will be employed by the OpenStack Foundation as a Cross-Project Developer Coordinator to help bring focus and support to cross-project initiatives within the cross-project specs, Def Core, The Product Working group, etc.

I feel the items below have enabled others across this project to strive for quality. If you would all have me as a member of the Technical Committee, you can help me to enable more quality work in OpenStack.

  • I have been working in OpenStack since 2010. I spent a good amount of my time
    working on OpenStack in my free time before being paid full time to work on
    it. It has been an important part of my life, and rewarding to see what we
    have all achieved together.

  • I was PTL for the Cinder project in the Kilo and Liberty releases for two
    cross-project reasons:

    • Third party continuous integration (CI).
    • Stop talking about rolling upgrades, and actually make it happen for
      operators.
  • I led the effort in bringing third party continuous integration to the
    Cinder project for more than 60 different drivers. [1]

    • I removed 25 different storage drivers from Cinder to bring quality to the
      project to ensure what was in the Kilo release would work for operators.
      I did what I believed was right, regardless of whether it would cost me
      re-election for PTL [2].
    • In my conversations with other projects, this has enabled others to
      follow the same effort. Continuing this trend of quality cross-project will
      be my next focus.
  • During my first term of PTL for Cinder, the team, and much respect to Thang
    Pham working on an effort to end the rolling upgrade problem, not just for
    Cinder, but for all projects.

    • First step was making databases independent from services via Oslo
      versioned objects.
    • In Liberty we have a solution coming that helps with RPC versioned messages
      to allow upgrading services independently.
  • I have attempted to help with diversity in our community.

    • Helped lead our community to raise $17,403 for the Ada Initiative [3],
      which was helping address gender-diversity with a focus in open source.
    • For the Vancouver summit, I helped bring in the ally skills workshops from
      the Ada Initiative, so that our community can continue to be a welcoming
      environment [4].
  • Within the Cinder team, I have enabled all to provide good documentation for
    important items in our release notes in Kilo [5] and Liberty [6].

    • Other projects have reached out to me after Kilo feeling motivated for this
      same effort. I've explained in the August 2015 Operators midcycle sprint
      that I will make this a cross-project effort in order to provide better
      communication to our operators and users.
  • I started an OpenStack Dev List summary in the OpenStack Weekly Newsletter
    (What you need to know from the developer's list), in order to enable others
    to keep up with the dev list on important cross-project information. [7][8]

  • I created the Cinder v2 API which has brought consistency in
    request/responses with other OpenStack projects.

    • I documented Cinder v1 and Cinder v2 API's. Later on I created the Cinder
      API reference documentation content. The attempt here was to enable others
      to have somewhere to start, to continue quality documentation with
      continued developments.

Please help me to do more positive work in this project. It would be an honor to be member of your technical committee.

Thank you,
Mike Perez

Official Candidacy: https://review.openstack.org/#/c/229298/2
Review History: https://review.openstack.org/#/q/reviewer:170,n,z
Commit History: https://review.openstack.org/#/q/owner:170,n,z
Stackalytics: http://stackalytics.com/?user_id=thingee
Foundation: https://www.openstack.org/community/members/profile/4840
IRC Freenode: thingee
Website: http://thing.ee

[1] - http://lists.openstack.org/pipermail/openstack-dev/2015-January/054614.html
[2] - https://review.openstack.org/#/q/status:merged+project:openstack/cinder+branch:master+topic:cinder-driver-removals,n,z
[3] - http://lists.openstack.org/pipermail/openstack-dev/2014-October/047892.html
[4] - http://lists.openstack.org/pipermail/openstack-dev/2015-May/064156.html
[5] - https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Block_Storage_.28Cinder.29
[6] - https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Block_Storage_.28Cinder.29
[7] - http://www.openstack.org/blog/2015/09/openstack-community-weekly-newsletter-sept-12-18/
[8] - http://www.openstack.org/blog/2015/09/openstack-weekly-community-newsletter-sept-19-25/


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Sep 30, 2015 by Barrett,_Carol_L (3,380 points)   2 3
...