[openstack-dev] [oslo] PTL candidacy
You can find my statement at https://review.openstack.org/#/c/587096/1/candidates/stein/Oslo/openstack%2540nemebean.com That's certainly not an exhaustive list of what I plan to do next cycle, but given the size of our team I thought my time was better spent doing those things than writing a flowery campaign speech that nobody would ever read. ;-) -Ben __ 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] [oslo] PTL candidacy
Ben Nemec wrote: > I am submitting my candidacy for Oslo PTL. Thanks Ben for stepping up ! -- Thierry __ 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] [oslo] PTL candidacy
Thanks for stepping up to take the role, Ben looking forward to making oslo better with your lead . 2018-02-03 2:43 GMT+08:00 Ben Nemec : > Hi, > > I am submitting my candidacy for Oslo PTL. > > I have been an Oslo core since 2014 and although my involvement in the > project > has at times been limited by other responsibilities, I have always kept up > on > what is going on in Oslo. > > For the Rocky cycle my primary goals would be: > > * Continue to maintain the stability and quality of the existing Oslo code. > > * Help drive the oslo.config improvements that are underway. > > * Encourage new and existing contributors to ensure the long-term health of > the project. > > I am, of course, always open to suggestions on other areas of focus for > Oslo. > > Thanks. > > -Ben > > __ > 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 > -- ChangBo Guo(gcb) Community Director @EasyStack __ 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] [oslo] PTL candidacy
Hi, I am submitting my candidacy for Oslo PTL. I have been an Oslo core since 2014 and although my involvement in the project has at times been limited by other responsibilities, I have always kept up on what is going on in Oslo. For the Rocky cycle my primary goals would be: * Continue to maintain the stability and quality of the existing Oslo code. * Help drive the oslo.config improvements that are underway. * Encourage new and existing contributors to ensure the long-term health of the project. I am, of course, always open to suggestions on other areas of focus for Oslo. Thanks. -Ben __ 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] [oslo] PTL candidacy
Howdy folks, I'd like to run again (before passing the baton) for the PTL of Oslo, I would like to help out as much as I am able and continue pushing and making Oslo be the best it can be during the Ocata release. I have probably not done as best as I could during this Newton cycle (due to various job movements and such) but I am hoping to help out and improve and guide folks during this next cycle. Thanks for considering myself (and a shout out to the rest of the Oslo folks and contributors who keep on chugging forward with the supporting foundation of many many projects, inside and outside OpenStack). P.S. Election repo review @ https://review.openstack.org/371979 -Josh __ 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] [oslo] PTL Candidacy
Hi there oslo folks, I'm submitting myself as candidate for oslo-ptl for the (fig) newton cycle. Most of you (that can vote) probably already know me and know what I work on and what I contribute to. For those that don't this link probably is a good explanation/list of that (or just find me and ask): https://news.ycombinator.com/user?id=harlowja I'm usually on the oslo and state-management channel(s) (although the past few weeks have been a little different, for personal and/or professional reasons) but I think I would be a good cheerful and jolly candidate for the newton cycle. I'm sure it would be a useful learning experience for myself and the others involved and I feel that I know enough (not all) about how oslo works (code, people, and process wise) that I can be a useful PTL for at least six months. Some things I'd like to work on (with others help) for newton: * Advocacy, we have a lot of libraries in oslo, and I believe that others do not know all about them or what they can offer, so I think we (as a group) need to advocate and educate others better in good usage patterns and others. * Tutorials, similar to education but it'd be nice to have some simple(ish) tutorials that consuming projects can follow and read over (perhaps similar to taskflow examples) so that others can know good practices and patterns to follow when using the various oslo libraries. * Achieving more activity with consuming projects; similar to advocacy, but this would be focusing more on helping other projects use oslo libraries effectively, and how to request (or even complain about lacking) functionality in those libraries so that oslo folks can help make those features (or complaints) a solved problem. * There is a-lot of technical experience that various oslo folks have; it'd be nice to figure out how to use this more effectively so that projects that would benefit from said experience can (perhaps even in ways that are not code/libraries). * (and more!) Your votes (and/or commentary and/or questions) are welcome, Thanks for the time! Candidate review @ https://review.openstack.org/292643 -Joshua Harlow __ 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] [oslo] PTL candidacy
Hi, It's been a great privilege to be the Oslo PTL for Liberty and getting to know and learn a whole lot of things. I hope i have helped move the Oslo project along its path in the process. Things we should be proud about include the fact that oslo-incubator is almost empty. We have a whole bunch of new libraries both general purpose outside of OpenStack and those who are specific to openstack. We as a team, have greatly stabilized core libraries like oslo.db and oslo.messaging etc as well. We have grown both the oslo core team and the cores for individual oslo projects to inject new blood into the project. Another aspect we really pushed hard is to make sure we did a lot of testing before we released code to reduce the chances of breaking projects as well as making sure that we stuck to a schedule of releases every week to release things early. For Mitaka, i would like to focus on Documentation. This has been a sore spot for a while and folks have to end up reading code quickly when things fail. I'd also like the team to finally get rid of the remnants in the oslo-incubator and spearhead adoption of the oslo libraries in various projects. Shadowing Doug in the previous cycle helped me along the way in liberty, so i'd love to show and help hand over the duties to the next ptl for the N release. Happy to do this even if there is a new PTL for the Mitaka release. As mentioned in the oslo meeting today, it would be great to have a VOTE and thanks for Joshua (and anyone else who may throw their hat) for making it a race :) Looking forward to new oslo libraries, more drivers for existing libraries and working together to make the OpenStack ecosystem more vibrant and welcoming to everyone. Thanks, Dims -- Davanum Srinivas :: https://twitter.com/dims __ 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] [oslo] PTL candidacy
Howdy folks, I'd like to propose myself for oslo PTL for the mitaka cycle, For those that don't know me I've been involved in openstack for ~4 years, Have worked at yahoo! for ~7 years, ~4 of the last years have been getting openstack adopted in yahoo! (where it is now used by everyone, and is a common word/name/project all employees know about, quite a change from when ~three other engineers and myself started investigating it ~4 years ago). It has been quite the journey (for myself, others and yahoo! in general) and I've been pretty active in oslo for ~2 years so I thought it might be a good time to try to run and see how I can help in a PTL role (this also ensures nobody else in oslo-core burns out). I contribute to many projects (inside and outside of openstack): - http://stackalytics.com/report/users/harlowja Created/maintain/co-maintain/contributor/core to the following: (not directly openstack, generally useful to all) - https://kazoo.readthedocs.org - https://redis-py.readthedocs.org - https://cloudinit.readthedocs.org - https://fasteners.readthedocs.org - https://pymemcache.readthedocs.org - https://pypi.python.org/pypi/zake - https://pypi.python.org/pypi/doc8 - https://pypi.python.org/pypi/retrying (mainly created for usage by openstack, but not limited to) - https://anvil.readthedocs.org - http://docs.openstack.org/developer/futurist/ - http://docs.openstack.org/developer/automaton/ - http://docs.openstack.org/developer/debtcollector/ - http://docs.openstack.org/developer/taskflow/ - http://docs.openstack.org/developer/tooz/ (created for usage by openstack) - oslo.messaging - oslo.utils - oslo.serialization - oslo.service - (all the other 'oslo.*' libraries) (and more...) I feel I can help bring a unique viewpoint to oslo and openstack in general; one of increasing exposure and general usefulness of oslo libraries outside of openstack; fostering community inside and outside and continuing to make oslo and openstack the best it can be. Some of the things that I would like to focus on (not inclusive of all the things): - Increasing outreach to consuming projects so that they can benefit from the oslo libraries, code and knowledge (and patterns) that have been built up by these libraries; perhaps some kind of bi-weekly blog about oslo? - Improving our outreach to others in the wider world (even ones not in the big tent); the python community is a big world and it'd be great to make sure we do our part there as well. - Asking the hard questions. - Being jolly. Thanks for considering me, Any questions/comments/feedback, please let me know and I'll do my best to answer them :-) -Joshua Harlow __ 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] [oslo] PTL Candidacy
confirmed On 23/09/14 01:54 PM, Doug Hellmann wrote: > I am running for PTL for Oslo for the Kilo release cycle. > > I have served 2 terms now, and my tl;dr platform for Kilo is, “More of the > same!” > > I have already posted the retrospective the team put together for Juno [1], > so I won’t go over those items in depth here. From my perspective, the team > is working well together and made excellent progress with our goals for Juno. > We’ve ironed out a lot of the kinks in the graduation process, and with those > adjustments I think Kilo will go just as smoothly as Juno has, if not more. > > My first priority for us is to finish the work on the libraries we graduated > in Juno, including adoption, removing incubated code, adding documentation, > and any of the other tasks we identify that we need to do before we can say > we are “done”. I would like to focus on this for K1. > > We started oslo.log and oslo.concurrency late in the cycle, so we have more > work to do there than for some of the other libraries. I really count those > as Kilo graduations, even though we did get them started in Juno. I think we > can finish these for K1 as well. > > Dims has already started working on the analysis for which modules are ready > to come out next, and we should finish that relatively soon to give us time > to plan things out for the summit. My impression is we have 3-4 more > libraries ready to move out of the incubator for K2-K3. At that point, I > think we will have handled most of the code that is ready for graduation. We > will need to look at anything that remains, to decide how to handle it for > the L release cycle. > > Graduation work was the focus of our attention for Juno, and I would give it > a high priority during Kilo as well. However, we also need to bring bug > triage and fixes back to the forefront, to make sure we take advantage of the > new libraries to release fixes quickly to all of OpenStack, without waiting > for projects to sync changes. > > I hope these goals seem reasonable to everyone, and I look forward to working > with all of you again this cycle. > > Doug > > > [1] > http://lists.openstack.org/pipermail/openstack-dev/2014-September/046757.html > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [oslo] PTL Candidacy
I am running for PTL for Oslo for the Kilo release cycle. I have served 2 terms now, and my tl;dr platform for Kilo is, “More of the same!” I have already posted the retrospective the team put together for Juno [1], so I won’t go over those items in depth here. From my perspective, the team is working well together and made excellent progress with our goals for Juno. We’ve ironed out a lot of the kinks in the graduation process, and with those adjustments I think Kilo will go just as smoothly as Juno has, if not more. My first priority for us is to finish the work on the libraries we graduated in Juno, including adoption, removing incubated code, adding documentation, and any of the other tasks we identify that we need to do before we can say we are “done”. I would like to focus on this for K1. We started oslo.log and oslo.concurrency late in the cycle, so we have more work to do there than for some of the other libraries. I really count those as Kilo graduations, even though we did get them started in Juno. I think we can finish these for K1 as well. Dims has already started working on the analysis for which modules are ready to come out next, and we should finish that relatively soon to give us time to plan things out for the summit. My impression is we have 3-4 more libraries ready to move out of the incubator for K2-K3. At that point, I think we will have handled most of the code that is ready for graduation. We will need to look at anything that remains, to decide how to handle it for the L release cycle. Graduation work was the focus of our attention for Juno, and I would give it a high priority during Kilo as well. However, we also need to bring bug triage and fixes back to the forefront, to make sure we take advantage of the new libraries to release fixes quickly to all of OpenStack, without waiting for projects to sync changes. I hope these goals seem reasonable to everyone, and I look forward to working with all of you again this cycle. Doug [1] http://lists.openstack.org/pipermail/openstack-dev/2014-September/046757.html ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Oslo PTL Candidacy
confirmed On 03/31/2014 05:37 PM, Doug Hellmann wrote: > I am running for a second term as PTL for the OpenStack Common Libraries > (Oslo) project. > > I have been programming in Python professionally for over 15 years, in a > variety of application areas. I am currently a Senior Developer at > DreamHost, on our DreamCompute OpenStack-based public cloud project. > > I started working on OpenStack just before the Folsom summit. I am a core > reviewer and one of the founding members of the Ceilometer project, and a > core reviewer for the requirements and unified command line interface > projects. I am also on the stable release maintenance team and am part of > the team working on the Python 3 transition. I have contributed to many of > the OpenStack projects through code and reviews. > > I joined the Oslo team at the Folsom summit, and served as PTL during the > Icehouse release cycle. > > Although overall I think Icehouse went well for Oslo when checked against > our internal goals, we have heard from developers in other projects who are > frustrated. Syncing fixes has become increasingly difficult, and some > breaking changes were merged in the existing libraries and not caught until > those libraries were released. The sync issue is a symptom of two > underlying problems. Our rapid growth as a community has made it difficult > to keep up with the number of new projects pulling changes from the > incubator, making it harder for us to keep everyone up to date. Oslo's goal > of providing a "collaboration space" has also been lost somewhat, and > instead the program has started to be treated more as a team producing > tools to be consumed by other projects. We have been working hard to adapt > Oslo to the changing needs of the community, but to truly fix these issues > we need to bring back the original collaborative intent of the program. > > During Icehouse we have worked with the infra team to develop the processes > to release more of the incubated code as standalone libraries [1], and to > set up the additional testing that will be needed to prevent the issues we > had with libraries during Icehouse. I anticipate having a few final changes > land soon after the Icehouse feature freeze lifts to clear the way for our > Juno plans [2]. As we move more stable code out of the incubator and into > libraries, it will mean fewer sync merges and better testing of Oslo code > in devstack and unit test gate jobs. After these initial low level > libraries are released, we will be able to release more incubated modules > in future cycles. > > To return Oslo to being a collaborative project, I plan to adopt and > formalize Joe Gordon's suggestion of having designated liaisons to > coordinate changes from Oslo code with each project [3]. There are just too > many other projects for the small Oslo team to be intimately familiar with, > and contribute to, all of them directly. The liaisons will be responsible > for helping merge changes into their project to move to the libraries being > released. We will also need the liaisons to help us identify API > incompatibilities between what is in the proposed library and the way > projects are using the incubated modules now. > > In the days leading up to RC1, we have had several different items brought > to our attention as critical blocking issues that had been going on for > many weeks. None of these took what I would call a lot of time or effort to > fix or work around, but because we were not aware of the issues or their > impact, frustration built up in the teams affected by the issues. I hope > that having designated liaisons will help us establish communication > channels to identify, prioritize, and resolve these sorts of issues earlier. > > My commit history: > https://review.openstack.org/#/q/owner:doug.hellmann%2540dreamhost.com,n,z > > My review history: > https://review.openstack.org/#/q/reviewer:doug.hellmann%2540dreamhost.com,n,z > > I'm looking forward to continuing to work with everyone, > Doug > > > [1] https://wiki.openstack.org/wiki/Oslo/CreatingANewLibrary > [2] https://wiki.openstack.org/wiki/Oslo/JunoGraduationPlans > [3] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Oslo PTL Candidacy
I am running for a second term as PTL for the OpenStack Common Libraries (Oslo) project. I have been programming in Python professionally for over 15 years, in a variety of application areas. I am currently a Senior Developer at DreamHost, on our DreamCompute OpenStack-based public cloud project. I started working on OpenStack just before the Folsom summit. I am a core reviewer and one of the founding members of the Ceilometer project, and a core reviewer for the requirements and unified command line interface projects. I am also on the stable release maintenance team and am part of the team working on the Python 3 transition. I have contributed to many of the OpenStack projects through code and reviews. I joined the Oslo team at the Folsom summit, and served as PTL during the Icehouse release cycle. Although overall I think Icehouse went well for Oslo when checked against our internal goals, we have heard from developers in other projects who are frustrated. Syncing fixes has become increasingly difficult, and some breaking changes were merged in the existing libraries and not caught until those libraries were released. The sync issue is a symptom of two underlying problems. Our rapid growth as a community has made it difficult to keep up with the number of new projects pulling changes from the incubator, making it harder for us to keep everyone up to date. Oslo's goal of providing a "collaboration space" has also been lost somewhat, and instead the program has started to be treated more as a team producing tools to be consumed by other projects. We have been working hard to adapt Oslo to the changing needs of the community, but to truly fix these issues we need to bring back the original collaborative intent of the program. During Icehouse we have worked with the infra team to develop the processes to release more of the incubated code as standalone libraries [1], and to set up the additional testing that will be needed to prevent the issues we had with libraries during Icehouse. I anticipate having a few final changes land soon after the Icehouse feature freeze lifts to clear the way for our Juno plans [2]. As we move more stable code out of the incubator and into libraries, it will mean fewer sync merges and better testing of Oslo code in devstack and unit test gate jobs. After these initial low level libraries are released, we will be able to release more incubated modules in future cycles. To return Oslo to being a collaborative project, I plan to adopt and formalize Joe Gordon's suggestion of having designated liaisons to coordinate changes from Oslo code with each project [3]. There are just too many other projects for the small Oslo team to be intimately familiar with, and contribute to, all of them directly. The liaisons will be responsible for helping merge changes into their project to move to the libraries being released. We will also need the liaisons to help us identify API incompatibilities between what is in the proposed library and the way projects are using the incubated modules now. In the days leading up to RC1, we have had several different items brought to our attention as critical blocking issues that had been going on for many weeks. None of these took what I would call a lot of time or effort to fix or work around, but because we were not aware of the issues or their impact, frustration built up in the teams affected by the issues. I hope that having designated liaisons will help us establish communication channels to identify, prioritize, and resolve these sorts of issues earlier. My commit history: https://review.openstack.org/#/q/owner:doug.hellmann%2540dreamhost.com,n,z My review history: https://review.openstack.org/#/q/reviewer:doug.hellmann%2540dreamhost.com,n,z I'm looking forward to continuing to work with everyone, Doug [1] https://wiki.openstack.org/wiki/Oslo/CreatingANewLibrary [2] https://wiki.openstack.org/wiki/Oslo/JunoGraduationPlans [3] https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Oslo] PTL Candidacy
On Sat, 2013-09-21 at 09:16 -0400, Doug Hellmann wrote: > I am running for PTL for the OpenStack Common Libraries (Oslo) project. Excellent! Doug has been a superb contributor to Oslo and I've particularly appreciated his keen eye for Python API design. I've no doubt that Doug would make a wonderful PTL for Oslo. Thanks, Mark. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Oslo] PTL Candidacy
I am running for PTL for the OpenStack Common Libraries (Oslo) project. I have been programming in Python professionally for 15 years, in a variety of application areas. I am a member of the Python Software Foundation, have been on the PyCon Program Committee, and was Editor in Chief of Python Magazine. I am currently a Senior Developer at DreamHost, and the dev lead for our DreamCompute OpenStack-based public cloud project. I started working on OpenStack just before the Folsom summit. I am a core reviewer and one of the founding members of the Ceilometer project, and a core reviewer for the requirements and unified command line interface projects. I am also on the stable release maintenance team for grizzly and am part of the team working on the Python 3 transition. I have contributed to many of the OpenStack projects through code and reviews. I joined the Oslo team at the Folsom summit, not long after starting to work on OpenStack. During the havana cycle, I contributed to Oslo in several ways. I was active in the design of the new oslo.messaging library, which will eventually replace openstack.common.rpc. I worked to deprecate openstack.common.wsgi in favor of Pecan/WSME, with the goal of making it easier to create new API services. I started updating the way projects load plugins using stevedore. I also created the oslo.sphinx library to hold our documentation theme and tools, and contributed to our new packaging library (pbr). Pecan and WSME are both now stackforge projects, so it is easier for us to contribute to and maintain them. During Icehouse, I plan to move stevedore, cliff, and sphinxcontrib-pecanwsme onto stackforge for the same reason. My philosophy for Oslo is similar to Mark's, although I may lean more in the direction of creating loosley-coupled libraries that are usable outside of OpenStack as much as possible (e.g., cliff and stevedore). We depend on a lot of other developers, and I would like for us to be releasing code in a way that other projects can use it, where it makes sense for us to do so. The Oslo team is making excellent progress moving code out of the oslo-incubator repository to separate libraries, but we still have a lot of work to do. My goal for Icehouse is to have oslo.messaging adopted by two or more integrated projects and continue to graduate more code from the incubator. oslo.messaging just missed being adopted by nova and ceilometer during havana, so it makes sense for us to finish that work after the feature freeze is lifted. During the summit we should discuss which parts of the incubated code are ready to move into separate libraries, and set our priorities based on stability and utility. My commit history: https://review.openstack.org/#/q/owner:doug.hellmann%2540dreamhost.com,n,z My review history: https://review.openstack.org/#/q/reviewer:doug.hellmann%2540dreamhost.com,n,z I'm looking forward to continuing to work with everyone,Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
