Re: [openstack-dev] [election][tc] Announcing candidacy
On 9/7/2018 12:17 PM, Rico Lin wrote: I'm refering on clear communication channels and go from Use cases to real development tasks (As I try to explain in the last section of my candidacy). Sorry, I totally missed the other details in your candidacy email because they came after your signature. Otherwise I wouldn't have asked. :) And here's some specific initiatives or deliverables sample I got in mind. * From StarlingX, some great improvement for Edge cases are delivered to projects. And there're also communications cross StarlingX and TCs on how to make it integrated with rest OpenStack projects (currently StarlingX still using it's own forks of OpenStack projects). And there're other projects that other organizations contribute to OpenStack or form another communities that depend on OpenStack. * We recently create a new repo `openstack-service-broker` [1]. Use Service Broker (A project from CloudFoundry) expose external resources to applications running in a PaaS. Which is exactly a integration cross CloudFoundry and OpenStack (protentially with K8s too) base on specific scenario. * K8s as one of the most popular case here, I believe we already can see some nice integration cross OpenStack and K8s. Include Manila, Keystone support in K8s, Magnum become one of official deployment tool in K8s community. Also I'm currently working on Integrate Heat AutoScaling to K8s cluster autoscaler as well [2]. * OPNFV integrated with OpenStack as it's cluster provider. Yes this is good detail, thanks Rico. -- Thanks, Matt __ 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] [election][tc] Announcing candidacy
On Fri, Sep 7, 2018 at 9:21 PM Matt Riedemann wrote: > On 9/6/2018 1:49 PM, Rico Lin wrote: > > * Cross-community integrations (K8s, CloudFoundry, Ceph, OPNFV) > > Are there some specific initiatives or deliverables you have in mind > here, or just general open communication channels? It's very hard to > gauge any kind of progress/success on the latter. > I'm refering on clear communication channels and go from Use cases to real development tasks (As I try to explain in the last section of my candidacy). And here's some specific initiatives or deliverables sample I got in mind. * From StarlingX, some great improvement for Edge cases are delivered to projects. And there're also communications cross StarlingX and TCs on how to make it integrated with rest OpenStack projects (currently StarlingX still using it's own forks of OpenStack projects). And there're other projects that other organizations contribute to OpenStack or form another communities that depend on OpenStack. * We recently create a new repo `openstack-service-broker` [1]. Use Service Broker (A project from CloudFoundry) expose external resources to applications running in a PaaS. Which is exactly a integration cross CloudFoundry and OpenStack (protentially with K8s too) base on specific scenario. * K8s as one of the most popular case here, I believe we already can see some nice integration cross OpenStack and K8s. Include Manila, Keystone support in K8s, Magnum become one of official deployment tool in K8s community. Also I'm currently working on Integrate Heat AutoScaling to K8s cluster autoscaler as well [2]. * OPNFV integrated with OpenStack as it's cluster provider. So the goal here IMO is `how can we properly set up cross communication and improve scenarios with use cases or help these scenarios to become deliverable for user?`. SIGs are one of the format that I believe can help to accelerate this goal. As I mentioned in [3] and in goal `Strong the structure of SIGs`. We should consider to allow SIGs to become that platform from use cases and scenario to a trackable development tasks. I know there's nothing block a SIG to do so, but there's also no guideline, structure format, or other resources to make the path easier for SIG. Hope these explains wht the goal is in my mind. [1] https://github.com/openstack/openstack-service-broker [2] https://github.com/kubernetes/autoscaler/pull/1226 [3] http://lists.openstack.org/pipermail/openstack-sigs/2018-August/000453.html __ 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] [election][tc] announcing candidacy
On 9/4/2018 7:30 AM, Doug Hellmann wrote: I am announcing my candidacy for a position on the OpenStack Technical Committee. I started contributing to OpenStack in 2012, not long after joining Dreamhost, and I am currently employed by Red Hat to work on OpenStack with a focus on long-term project concerns. I have served on the Technical Committee for the last five years, including as Chair during the last term. I have also been PTL of the Oslo and Release Management teams at different points in the past. I have spent most of my time in all of those roles over the last few years making incremental improvements in our ability to collaborate while building OpenStack, including initiatives such as leading the current community goal to run CI jobs under Python 3 by default [1]; coordinating last year's documentation migration; and updating our dependency management system to make it easier for projects to run stand-alone. During my time serving as TC Chair, I have tried to update the way the group works with the community. We started by performing a "health check" for all of our project teams [2], as a way to spot potential issues teams are experiencing that we can help with, and to encourage TC members to learn more about teams they may not interact with on a daily basis. We will be reviewing the results at the PTG [3], and continuing to refine that process. I have also had a few opportunities this year to share our governance structure with other communities [4][5]. It's exciting to be able to talk to them about how the ideals and principles that hold our community together can also apply to their projects. The OpenStack community continues to be the most welcoming group I have interacted with in more than 25 years of contributing to open source projects. I look forward to another opportunity to serve the project through the Technical Committee over the coming year. Thank you, Doug Candidacy submission: https://review.openstack.org/599582 Review history: https://review.openstack.org/#/q/reviewer:2472,n,z Commit history: https://review.openstack.org/#/q/owner:2472,n,z Foundation Profile: http://www.openstack.org/community/members/profile/359 Freenode: dhellmann Website: https://doughellmann.com [1] https://governance.openstack.org/tc/goals/stein/python3-first.html [2] https://wiki.openstack.org/wiki/OpenStack_health_tracker [3] https://etherpad.openstack.org/p/tc-stein-ptg [4] https://doughellmann.com/blog/2018/08/21/planting-acorns/ [5] https://www.python.org/dev/peps/pep-8002/ __ 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 I have generally been very cynical of repeat TC members, mostly because I don't know what they actually get done, but this candidacy email is a very nice example of specific issues that you've worked on and I really appreciate you being able to point out the things you've worked on while being on the TC. Thanks for pushing on this stuff Doug. -- Thanks, Matt __ 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] [election][tc] announcing candidacy
On 9/4/2018 7:15 PM, Julia Kreger wrote: The most specific thing that is weighing on my mind is elevating and supporting contributors. While this is not new, I think we as a community need to refocus on it because they are very fibers that make up the fabric of our community and ultimately the electorate. Do you have specific *kinds* of contributors in mind here? Like are you mostly thinking new or part-time contributors, or are you also including long-time maintainers of the project, because let's not forget those are also contributors (usually in a large personal sacrificial way). Do you have specific ideas on how to elevate and support contributors? OR what do you see are the major issues not being addressed? Burn out? Contributor's backing companies not supporting them in some form? Other? -- Thanks, Matt __ 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] [election][tc] Announcing candidacy
On 9/6/2018 1:49 PM, Rico Lin wrote: * Cross-community integrations (K8s, CloudFoundry, Ceph, OPNFV) Are there some specific initiatives or deliverables you have in mind here, or just general open communication channels? It's very hard to gauge any kind of progress/success on the latter. -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [election][tc] Announcing candidacy
Dear all, I'm announcing my candidacy for a position on the OpenStack Technical Committee. I'm Rico Lin. I have been in this community since 2014. And been deeply involved with technical contributions [1], I start from working with heat, which allows me to work on integration and management resources from multiple projects. I have served as Heat PTL for two years. Which allows me to learn better on how we can join users and operators' experiences and requirements and integrated with development workflow and technical decision processes. Here are my major goals with this seat in TC: * Cross-community integrations (K8s, CloudFoundry, Ceph, OPNFV) * Provide guidelines * Strong the structure of SIGs * Application Infra * Cross-cooperation between Users, Operators, and Developers * Diversity I'm already trying to put my goals to actions, still would really hope to join Technical Committee to bring more attention to those domains Thank you for your consideration. Best Regards, Rico Lin IRC: ricolin Twitter: @ricolintw https://www.openstack.org/community/members/profile/33346/rico-lin http://stackalytics.com/?release=all_id=rico-lin=person-day Here I put some explanations for my goals: - Cross-community integrations (K8s, CloudFoundry, Ceph, OPNFV): This is a long-term goal for our community, but would really like to see this getting more scenario for use cases, and a more clear target for development. As we talk about Edge, AI, etc. It's essential to bring real use cases into this integration( like StarlingX bring some requirements cross-projects to real use cases). On the other hand, K8s-SIG, Self-healing sig, FEMDC SIG are all some nice place for this kind of interacting and integrating to happen. - Provide guidelines: There is one WIP guideline from First Contact SIG I particular interesting on. The `Guidelines for Organisations Contributing to OpenStack` [4]. This is something I believe is quite important for showing how can organizations interacting with OpenStack community correctly. I try to work on the same goal from event to event as well (give presentations like [5]). There are some other guidelines that need to update/renew as well (most of us, who already reading ML and work in the community for long, might no longer require to read guidelines, but remember, whoever try to join now a day, still require an up-to-date guideline to give them hints). - Strong the structure of SIGs: As I show in above two goals, SIGs plays some important roles. I do like to trigger discussions on how can we strengthen the structure of SIGs. Make them more efficient and become someplace for users and ops can directly interact with developers. For real use cases like an Edge computing use case issue, or self-healing service issues. I can't think of a better place than FEMDC SIG and Self-healing SIG to record and target these issues. We might be able to allow Opts to feedback issues on SIG's StoryBoard and ask project teams to connect and review with it. There might be multiple ways to do this. So would really like to trigger this discussion. - Application Infra: We've updated our resolution with [3] and saying we care about what applications needs on top of OpenStack. As for jobs from few projects are taking the role and thinking about what application needs, we should provide help with setting up community goals, making resolutions, or define what are top priority applications (can be a short-term definition) we need to focus on and taking action items/guidelines and finding weaknesses, so others from the community can follow (if they agree with the goals, but got no idea on what they can help, IMO this will be a good stuff). - Cross-cooperation between Users, Operators, and Developers: We have been losing some communication cross Users, Operators, and Developers. And it's never a good thing when users can share use cases, ops shares experiences, developers shares code, but they won't make it to one another not if a user provides developers by them self. In this case, works like StoryBoard should be in our first priority. We need a more solid way to bring user feedback to developers, so we can actually learn what's working or not for each feature. And maybe it's considerable, to strengthen the communication between TCs and UCs (User Committee). We take some steps (like merge PTG and Ops-meetup) to this goal, but I believe we can make the interacting more active. - Diversity: The math is easy. [2] shows we got around one-third of users from Asia (with 75% of users in China). Also IIRC, around the same percentage of developers. But we got 0 in TC. The actual works are hard. We need forwards our technical guideline to developers in Asia and provide chances to get more feedback from them, so we can provide better technical resolutions which should be able to tight developers all together. Which I think I'm a good candidate for this. [1]
Re: [openstack-dev] [election][tc] announcing candidacy
That is an excellent question John! The most specific thing that is weighing on my mind is elevating and supporting contributors. While this is not new, I think we as a community need to refocus on it because they are very fibers that make up the fabric of our community and ultimately the electorate. I also feel that we focus a bit too much on what is new without having the data to really back it up. With so many project teams and working groups, it is going to take time for the TC to really digest and attempt to draw any actionable direction from the health assessment that has been underway over the past few months. -Julia On Tue, Sep 4, 2018 at 2:07 PM John Dickinson wrote: > > > > On 4 Sep 2018, at 12:16, Julia Kreger wrote: > > > Greetings Stackers! > > > > I hereby announce my candidacy for a position on the OpenStack > > Technical > > Committee. > > > > In many respects I consider myself a maverick, except reality is > > sometimes > > entirely different than my own self perception, upon reflection. > > I find self reflection and introspection to be powerful tools, along > > with > > passion and desire for the common good. That desire for the common > > good > > is the driving force behind my involvement in OpenStack, which I hope > > to > > see as a vibrant and thriving community for years to come. > > > > Have things changed? Yes, I think they are ever evolving. I think we > > can only > > take the logical paths that we see before us at the time. Does this > > mean > > we will make mistakes? Absolutely, but mistakes are also opportunities > > to learn and evolve as time goes on; which perhaps is an unspoken > > backbone > > of our community. The key is that we must not fear change but embrace > > it. > > > > Changing our community for the better is a process we can only take > > one step at a time, and we must recognize our strength > > is in our diversity. As we move forward, as we evolve, we need to keep > > in > > mind our goals and overall vision. In a sense, these things vary > > across all > > projects, but our central community vision and goal helps provide > > direction. > > > > As we continue our journey, I believe we need to lift up new > > contributors, > > incorporate new thoughts, and new ideas. Embracing change while > > keeping our > > basic course so new contributors can better find and integrate with > > our > > community as we continue forward. We need to listen and take that as > > feedback to better understand other perspectives, for it is not only > > our singular personal perspective which helps give us direction, > > but the community as a whole. > > > > For those who do not know me well my name is Julia Ashley Kreger. > > Often > > I can be found on IRC as TheJulia, in numerous OpenStack related > > channels. > > I have had the pleasure of serving the community this past year on the > > Technical Committee. I have also served the ironic community quite a > > bit > > during my time in the OpenStack community, which began during the Juno > > cycle. > > > > I am the current Project Team Lead for the Ironic team. I began > > serving in that capacity starting with the Rocky cycle. Prior, > > I served as the team's release liaison. You might have seen me as one > > of those crazy people advocating for standalone usage. Prior lives > > included deploying and operating complex systems, but that is enough > > about me. > > > > Ultimately I believe I bring a different perspective to the TC and it > > is for > > this, and my many strong beliefs and experiences, I feel I am well > > suited > > > > to serve the community for another year on the Technical Committee. > > > > Thank you for your consideration, > > > > Julia > > > > freenode: TheJulia > > Twitter: @ashinclouds > > https://www.openstack.org/community/members/profile/19088/julia-kreger > > http://stackalytics.com/?release=all_id=juliaashleykreger > > > > __ > > 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 > > Julia, > > Do you have any specific examples of new ideas you are wanting to > propose or advocate for, should you be re-elected? > > --John > > > > __ > 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] [election][tc] announcing candidacy
On 4 Sep 2018, at 12:16, Julia Kreger wrote: Greetings Stackers! I hereby announce my candidacy for a position on the OpenStack Technical Committee. In many respects I consider myself a maverick, except reality is sometimes entirely different than my own self perception, upon reflection. I find self reflection and introspection to be powerful tools, along with passion and desire for the common good. That desire for the common good is the driving force behind my involvement in OpenStack, which I hope to see as a vibrant and thriving community for years to come. Have things changed? Yes, I think they are ever evolving. I think we can only take the logical paths that we see before us at the time. Does this mean we will make mistakes? Absolutely, but mistakes are also opportunities to learn and evolve as time goes on; which perhaps is an unspoken backbone of our community. The key is that we must not fear change but embrace it. Changing our community for the better is a process we can only take one step at a time, and we must recognize our strength is in our diversity. As we move forward, as we evolve, we need to keep in mind our goals and overall vision. In a sense, these things vary across all projects, but our central community vision and goal helps provide direction. As we continue our journey, I believe we need to lift up new contributors, incorporate new thoughts, and new ideas. Embracing change while keeping our basic course so new contributors can better find and integrate with our community as we continue forward. We need to listen and take that as feedback to better understand other perspectives, for it is not only our singular personal perspective which helps give us direction, but the community as a whole. For those who do not know me well my name is Julia Ashley Kreger. Often I can be found on IRC as TheJulia, in numerous OpenStack related channels. I have had the pleasure of serving the community this past year on the Technical Committee. I have also served the ironic community quite a bit during my time in the OpenStack community, which began during the Juno cycle. I am the current Project Team Lead for the Ironic team. I began serving in that capacity starting with the Rocky cycle. Prior, I served as the team's release liaison. You might have seen me as one of those crazy people advocating for standalone usage. Prior lives included deploying and operating complex systems, but that is enough about me. Ultimately I believe I bring a different perspective to the TC and it is for this, and my many strong beliefs and experiences, I feel I am well suited to serve the community for another year on the Technical Committee. Thank you for your consideration, Julia freenode: TheJulia Twitter: @ashinclouds https://www.openstack.org/community/members/profile/19088/julia-kreger http://stackalytics.com/?release=all_id=juliaashleykreger __ 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 Julia, Do you have any specific examples of new ideas you are wanting to propose or advocate for, should you be re-elected? --John __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [election][tc] announcing candidacy
Greetings Stackers! I hereby announce my candidacy for a position on the OpenStack Technical Committee. In many respects I consider myself a maverick, except reality is sometimes entirely different than my own self perception, upon reflection. I find self reflection and introspection to be powerful tools, along with passion and desire for the common good. That desire for the common good is the driving force behind my involvement in OpenStack, which I hope to see as a vibrant and thriving community for years to come. Have things changed? Yes, I think they are ever evolving. I think we can only take the logical paths that we see before us at the time. Does this mean we will make mistakes? Absolutely, but mistakes are also opportunities to learn and evolve as time goes on; which perhaps is an unspoken backbone of our community. The key is that we must not fear change but embrace it. Changing our community for the better is a process we can only take one step at a time, and we must recognize our strength is in our diversity. As we move forward, as we evolve, we need to keep in mind our goals and overall vision. In a sense, these things vary across all projects, but our central community vision and goal helps provide direction. As we continue our journey, I believe we need to lift up new contributors, incorporate new thoughts, and new ideas. Embracing change while keeping our basic course so new contributors can better find and integrate with our community as we continue forward. We need to listen and take that as feedback to better understand other perspectives, for it is not only our singular personal perspective which helps give us direction, but the community as a whole. For those who do not know me well my name is Julia Ashley Kreger. Often I can be found on IRC as TheJulia, in numerous OpenStack related channels. I have had the pleasure of serving the community this past year on the Technical Committee. I have also served the ironic community quite a bit during my time in the OpenStack community, which began during the Juno cycle. I am the current Project Team Lead for the Ironic team. I began serving in that capacity starting with the Rocky cycle. Prior, I served as the team's release liaison. You might have seen me as one of those crazy people advocating for standalone usage. Prior lives included deploying and operating complex systems, but that is enough about me. Ultimately I believe I bring a different perspective to the TC and it is for this, and my many strong beliefs and experiences, I feel I am well suited to serve the community for another year on the Technical Committee. Thank you for your consideration, Julia freenode: TheJulia Twitter: @ashinclouds https://www.openstack.org/community/members/profile/19088/julia-kreger http://stackalytics.com/?release=all_id=juliaashleykreger __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [election][tc] announcing candidacy
I am announcing my candidacy for a position on the OpenStack Technical Committee. I started contributing to OpenStack in 2012, not long after joining Dreamhost, and I am currently employed by Red Hat to work on OpenStack with a focus on long-term project concerns. I have served on the Technical Committee for the last five years, including as Chair during the last term. I have also been PTL of the Oslo and Release Management teams at different points in the past. I have spent most of my time in all of those roles over the last few years making incremental improvements in our ability to collaborate while building OpenStack, including initiatives such as leading the current community goal to run CI jobs under Python 3 by default [1]; coordinating last year's documentation migration; and updating our dependency management system to make it easier for projects to run stand-alone. During my time serving as TC Chair, I have tried to update the way the group works with the community. We started by performing a "health check" for all of our project teams [2], as a way to spot potential issues teams are experiencing that we can help with, and to encourage TC members to learn more about teams they may not interact with on a daily basis. We will be reviewing the results at the PTG [3], and continuing to refine that process. I have also had a few opportunities this year to share our governance structure with other communities [4][5]. It's exciting to be able to talk to them about how the ideals and principles that hold our community together can also apply to their projects. The OpenStack community continues to be the most welcoming group I have interacted with in more than 25 years of contributing to open source projects. I look forward to another opportunity to serve the project through the Technical Committee over the coming year. Thank you, Doug Candidacy submission: https://review.openstack.org/599582 Review history: https://review.openstack.org/#/q/reviewer:2472,n,z Commit history: https://review.openstack.org/#/q/owner:2472,n,z Foundation Profile: http://www.openstack.org/community/members/profile/359 Freenode: dhellmann Website: https://doughellmann.com [1] https://governance.openstack.org/tc/goals/stein/python3-first.html [2] https://wiki.openstack.org/wiki/OpenStack_health_tracker [3] https://etherpad.openstack.org/p/tc-stein-ptg [4] https://doughellmann.com/blog/2018/08/21/planting-acorns/ [5] https://www.python.org/dev/peps/pep-8002/ __ 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
