Re: [openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-30 Thread 赵超
Dariusz Krol, That's great, thanks. Please submit your nomination asap, the deadline is today(2018-07-31 23:45:00 UTC). For detailed guidance about nomination, please refer to https://governance.openstack.org/election/. I think we need some work on https://review.openstack.org/#/c/586528/2, and w

Re: [openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-30 Thread Dariusz Krol
Hello Zhao Chao, after some internal discussion, I will do the nomination if you decided not to nominate yourself. Thanks for letting know you will be still available in the next release cycle. Regarding commits I would recommend to consider also https://review.openstack.org/#/c/586528/2 .

Re: [openstack-dev] openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-30 Thread Thierry Carrez
Dariusz Krol wrote: [...] On the other hand, I can also understand the lack of time to be a PTL since it requires probably a lot of time to coordinate all the work. Let’s wait for Chao Zhao to give his opinion on the topic :) If the PTL delegates the most time-intensive work (release liaison

Re: [openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-29 Thread 赵超
I found I made a mistake on the subject of this mail, so I corrected it in my last response, hope this won't make any further confusion. On Mon, Jul 30, 2018 at 9:26 AM, 赵超 wrote: > Since the new folks are still so new - if this works for you - I would >> recommend continuing on as the official

Re: [openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-29 Thread 赵超
> > Since the new folks are still so new - if this works for you - I would > recommend continuing on as the official PTL for one more release, but with > the > understanding that you would just be around to answer questions and give > advice > to help the new team get up to speed. That should hopef

Re: [openstack-dev] openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-27 Thread Dariusz Krol
Hi Sean,   This is good point. It would be great to have some help especially to start. We have some experience with contributing to openstack and we are working with gerrit on daily basis so there is no problem with technical aspects. However, it takes some time for changes to be reviewed an

Re: [openstack-dev] openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-26 Thread Sean McGinnis
> > > > A good news is recently a team from Samsung R&D Center in Krakow, Poland > > joined us, they're building a product on OpenStack, have done improvments > > on Trove(internally), and now interested in contributing to the community, > > starting by migrating the intergating tests to the tempes

Re: [openstack-dev] openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-26 Thread Dariusz Krol
Hello All, as a member of Samsung R&D Center in Krakow, I would like to confirm that we are very interested in Trove development. We also notices that Trove project has a small team now and that community around Trove becomes smaller with each release which is a shame since it is a great proj

Re: [openstack-dev] openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-25 Thread 赵超
cc to the Trove team members and guys from Samsung R&D Center in Krakow, Poland privately, so anyone of them who are not reading the ML could also be notified. On Thu, Jul 26, 2018 at 12:09 AM, 赵超 wrote: > Hi All, > > Trove currently has a really small team, and all the active team members > are

[openstack-dev] openstack-dev] [trove] Considering the transfter of the project leadership

2018-07-25 Thread 赵超
Hi All, Trove currently has a really small team, and all the active team members are from China, we had some good discussions during the Rocky online PTG meetings[1], and the goals were arranged and priorited [2][3]. But it's sad that none of us could focus on the project, and the number of patche