Re: [openstack-dev] [all][election] PTL nominations are now closed
> > > > Packaging_Rpm has a late candidate (Dirk Mueller). We always have a few > > teams per cycle that miss the election call, that would fall under that. > > +1 for appointing Dirk as PTL. > > Trove had a volunteer (Dariusz Krol), but that person did not fill the > > requirements for candidates. Given that the previous PTL (Zhao Chao) > > plans to stay around to help onboarding the new contributors, I'd > > support appointing Dariusz. > > I would be fine with this. But I also wonder if it might make sense to move Trove out of governance while they go through this transition so they have more leeway to evolve the project how they need to, with the expectation that if things get to a good and healthy point we can quickly re-accept the project as official. > > I suspect Freezer falls in the same bucket as Packaging_Rpm and we > > should get a candidate there. I would reach out to caoyuan see if they > > would be interested in steeping up. > > > > LOCI is also likely in the same bucket. However, given that it's a > > deployment project, if we can't get anyone to step up and guarantee some > > level of currentness, we should consider removing it from the "official" > > list. > > > > Dragonflow is a bit in the LOCI case. It feels like a miss too, but if > > it's not, given that it's an add-on project that runs within Neutron, I > > would consider removing it from the "official" list if we can't find > > anyone to step up. > > Omer has responded that the deadline was missed and he would like to continue as PTL. I think that is acceptable. (though unfortunate that it was missed) > > For Winstackers and Searchlight, those are low-activity teams (18 and 13 > > commits), which brings the question of PTL workload for feature-complete > > projects. > > Even for feature-complete projects we need to know how to reach the > maintainers, otherwise I feel like we would consider the project > unmaintained, wouldn't we? > I agree with Doug, I think there needs to be someone designated as the contact point for issues with the project. We've seen other "stable" things suddenly go unstable due to library updates or other external factors. I don't think Thierry was suggesting there not be a PTL for these, but for any potential PTL candidates they can know that the demands on their time to fill that role _should_ be pretty light. > > > > Finally, RefStack: I feel like this should be wrapped into an > > Interoperability SIG, since that project team is not producing > > "OpenStack", but helping fostering OpenStack interoperability. Having > > separate groups (Interop WG, RefStack) sounds overkill anyway, and with > > the introduction of SIGs we have been recentering project teams on > > upstream code production. > > > I agree this has gotten to the point where it probably now makes more sense to be owned by a SIG rather than being a full project team. __ 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] [all][election] PTL nominations are now closed
Excerpts from Thierry Carrez's message of 2018-08-02 10:58:53 +0200: > Tony Breeds wrote: > > [...] > > There are 8 projects without candidates, so according to this > > resolution[1], the TC will have to decide how the following > > projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm, > > RefStack, Searchlight, Trove and Winstackers. > > Here is my take on that... > > Packaging_Rpm has a late candidate (Dirk Mueller). We always have a few > teams per cycle that miss the election call, that would fall under that. > > Trove had a volunteer (Dariusz Krol), but that person did not fill the > requirements for candidates. Given that the previous PTL (Zhao Chao) > plans to stay around to help onboarding the new contributors, I'd > support appointing Dariusz. > > I suspect Freezer falls in the same bucket as Packaging_Rpm and we > should get a candidate there. I would reach out to caoyuan see if they > would be interested in steeping up. > > LOCI is also likely in the same bucket. However, given that it's a > deployment project, if we can't get anyone to step up and guarantee some > level of currentness, we should consider removing it from the "official" > list. > > Dragonflow is a bit in the LOCI case. It feels like a miss too, but if > it's not, given that it's an add-on project that runs within Neutron, I > would consider removing it from the "official" list if we can't find > anyone to step up. > > For Winstackers and Searchlight, those are low-activity teams (18 and 13 > commits), which brings the question of PTL workload for feature-complete > projects. Even for feature-complete projects we need to know how to reach the maintainers, otherwise I feel like we would consider the project unmaintained, wouldn't we? > > Finally, RefStack: I feel like this should be wrapped into an > Interoperability SIG, since that project team is not producing > "OpenStack", but helping fostering OpenStack interoperability. Having > separate groups (Interop WG, RefStack) sounds overkill anyway, and with > the introduction of SIGs we have been recentering project teams on > upstream code production. > __ 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] [all][election] PTL nominations are now closed
Excerpts from Omer Anson's message of 2018-08-02 12:56:37 +0300: > Hi, > > I'm sorry for the inconvenience. I completely missed the nomination period. > Is it possible to send in a late nomination for Dragonflow? At this point the TC is going to be looking for a volunteer, so if there is one please let us know. Doug > > Thanks, > Omer Anson. > > On Thu, 2 Aug 2018 at 11:59, Thierry Carrez wrote: > > > Tony Breeds wrote: > > > [...] > > > There are 8 projects without candidates, so according to this > > > resolution[1], the TC will have to decide how the following > > > projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm, > > > RefStack, Searchlight, Trove and Winstackers. > > > > Here is my take on that... > > > > Packaging_Rpm has a late candidate (Dirk Mueller). We always have a few > > teams per cycle that miss the election call, that would fall under that. > > > > Trove had a volunteer (Dariusz Krol), but that person did not fill the > > requirements for candidates. Given that the previous PTL (Zhao Chao) > > plans to stay around to help onboarding the new contributors, I'd > > support appointing Dariusz. > > > > I suspect Freezer falls in the same bucket as Packaging_Rpm and we > > should get a candidate there. I would reach out to caoyuan see if they > > would be interested in steeping up. > > > > LOCI is also likely in the same bucket. However, given that it's a > > deployment project, if we can't get anyone to step up and guarantee some > > level of currentness, we should consider removing it from the "official" > > list. > > > > Dragonflow is a bit in the LOCI case. It feels like a miss too, but if > > it's not, given that it's an add-on project that runs within Neutron, I > > would consider removing it from the "official" list if we can't find > > anyone to step up. > > > > For Winstackers and Searchlight, those are low-activity teams (18 and 13 > > commits), which brings the question of PTL workload for feature-complete > > projects. > > > > Finally, RefStack: I feel like this should be wrapped into an > > Interoperability SIG, since that project team is not producing > > "OpenStack", but helping fostering OpenStack interoperability. Having > > separate groups (Interop WG, RefStack) sounds overkill anyway, and with > > the introduction of SIGs we have been recentering project teams on > > upstream code production. > > > > -- > > Thierry Carrez (ttx) > > > > __ > > 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] [all][election] PTL nominations are now closed
Excerpts from Jeremy Stanley's message of 2018-08-02 13:13:21 +: > On 2018-08-02 10:58:53 +0200 (+0200), Thierry Carrez wrote: > [...] > > Finally, RefStack: I feel like this should be wrapped into an > > Interoperability SIG, since that project team is not producing > > "OpenStack", but helping fostering OpenStack interoperability. > > Having separate groups (Interop WG, RefStack) sounds overkill > > anyway, and with the introduction of SIGs we have been recentering > > project teams on upstream code production. > > That was one of the possibilities I discussed with them during their > meeting a month ago: > > http://eavesdrop.openstack.org/irclogs/%23refstack/%23refstack.2018-07-03.log.html#t2018-07-03T17:05:43 > > Election official hat off and TC Refstack liaison hat on, I think if > Chris Hoge doesn't volunteer to act as PTL this cycle to oversee > shutting down the team and reassigning its deliverables, then we > need to help them fast-track that nowish and not appoint a Stein > cycle PTL. This came up at a joint leadership meeting right after we created SIGs and the Interop WG was reluctant to make any structural changes at the time because they had just gone through a renaming process for the working group. Changing "WG" to "SIG" feels much lighter weight, so maybe we can move ahead with that now. 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] [all][election] PTL nominations are now closed
On 2018-08-02 10:58:53 +0200 (+0200), Thierry Carrez wrote: [...] > Finally, RefStack: I feel like this should be wrapped into an > Interoperability SIG, since that project team is not producing > "OpenStack", but helping fostering OpenStack interoperability. > Having separate groups (Interop WG, RefStack) sounds overkill > anyway, and with the introduction of SIGs we have been recentering > project teams on upstream code production. That was one of the possibilities I discussed with them during their meeting a month ago: http://eavesdrop.openstack.org/irclogs/%23refstack/%23refstack.2018-07-03.log.html#t2018-07-03T17:05:43 Election official hat off and TC Refstack liaison hat on, I think if Chris Hoge doesn't volunteer to act as PTL this cycle to oversee shutting down the team and reassigning its deliverables, then we need to help them fast-track that nowish and not appoint a Stein cycle PTL. -- Jeremy Stanley signature.asc Description: PGP signature __ 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] [all][election] PTL nominations are now closed
Hi, I'm sorry for the inconvenience. I completely missed the nomination period. Is it possible to send in a late nomination for Dragonflow? Thanks, Omer Anson. On Thu, 2 Aug 2018 at 11:59, Thierry Carrez wrote: > Tony Breeds wrote: > > [...] > > There are 8 projects without candidates, so according to this > > resolution[1], the TC will have to decide how the following > > projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm, > > RefStack, Searchlight, Trove and Winstackers. > > Here is my take on that... > > Packaging_Rpm has a late candidate (Dirk Mueller). We always have a few > teams per cycle that miss the election call, that would fall under that. > > Trove had a volunteer (Dariusz Krol), but that person did not fill the > requirements for candidates. Given that the previous PTL (Zhao Chao) > plans to stay around to help onboarding the new contributors, I'd > support appointing Dariusz. > > I suspect Freezer falls in the same bucket as Packaging_Rpm and we > should get a candidate there. I would reach out to caoyuan see if they > would be interested in steeping up. > > LOCI is also likely in the same bucket. However, given that it's a > deployment project, if we can't get anyone to step up and guarantee some > level of currentness, we should consider removing it from the "official" > list. > > Dragonflow is a bit in the LOCI case. It feels like a miss too, but if > it's not, given that it's an add-on project that runs within Neutron, I > would consider removing it from the "official" list if we can't find > anyone to step up. > > For Winstackers and Searchlight, those are low-activity teams (18 and 13 > commits), which brings the question of PTL workload for feature-complete > projects. > > Finally, RefStack: I feel like this should be wrapped into an > Interoperability SIG, since that project team is not producing > "OpenStack", but helping fostering OpenStack interoperability. Having > separate groups (Interop WG, RefStack) sounds overkill anyway, and with > the introduction of SIGs we have been recentering project teams on > upstream code production. > > -- > Thierry Carrez (ttx) > > __ > 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] [all][election] PTL nominations are now closed
Tony Breeds wrote: [...] There are 8 projects without candidates, so according to this resolution[1], the TC will have to decide how the following projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm, RefStack, Searchlight, Trove and Winstackers. Here is my take on that... Packaging_Rpm has a late candidate (Dirk Mueller). We always have a few teams per cycle that miss the election call, that would fall under that. Trove had a volunteer (Dariusz Krol), but that person did not fill the requirements for candidates. Given that the previous PTL (Zhao Chao) plans to stay around to help onboarding the new contributors, I'd support appointing Dariusz. I suspect Freezer falls in the same bucket as Packaging_Rpm and we should get a candidate there. I would reach out to caoyuan see if they would be interested in steeping up. LOCI is also likely in the same bucket. However, given that it's a deployment project, if we can't get anyone to step up and guarantee some level of currentness, we should consider removing it from the "official" list. Dragonflow is a bit in the LOCI case. It feels like a miss too, but if it's not, given that it's an add-on project that runs within Neutron, I would consider removing it from the "official" list if we can't find anyone to step up. For Winstackers and Searchlight, those are low-activity teams (18 and 13 commits), which brings the question of PTL workload for feature-complete projects. Finally, RefStack: I feel like this should be wrapped into an Interoperability SIG, since that project team is not producing "OpenStack", but helping fostering OpenStack interoperability. Having separate groups (Interop WG, RefStack) sounds overkill anyway, and with the introduction of SIGs we have been recentering project teams on upstream code production. -- Thierry Carrez (ttx) __ 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] [all][election] PTL nominations are now closed
Hello all, The PTL Nomination period is now over. The official candidate list is available on the election website[0]. There are 8 projects without candidates, so according to this resolution[1], the TC will have to decide how the following projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm, RefStack, Searchlight, Trove and Winstackers. There are 2 projects that will have elections: Senlin, Tacker. The details for those will be posted shortly after we setup the CIVS system. Thank you, [0] http://governance.openstack.org/election/#stein-ptl-candidates [1] http://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.html Yours Tony. signature.asc Description: PGP signature __ 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
