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

[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, 
meeting chair...) then it should not be too much extra work.


PTLs are responsible by default for a lot of things in their projects, 
but all of those things can be delegated to others.


--
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

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

[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 and merged and we would like to change it. 
 
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 :)
 
Best,
Dariusz Krol

  
  
__
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] openstack-dev] [trove] Considering the transfter of the project leadership

[Sean McGinnis]

> >
> > A good news is recently a team from Samsung R 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 tempest plugin. They're
> > also willing and ready to act as the PTL role. The only problem for their
> > nomination may be that none of them have a patched merged into the Trove
> > projects. There're some in the trove-tempest-plugin waiting review, but
> > according to the activities of the project, these patches may need a long
> > time to merge (and we're at Rocky milestone-3, I think we could merge
> > patches in the trove-tempest-plugin, as they're all abouth testing).
> >
> > I also hope and welcome the other current active team members of Trove
> > could nominate themselves, in that way, we could get more discussions about
> > how we think about the direction of Trove.
> >

Great to see another group getting involved!

It's too bad there hasn't been enough time to build up some experience working
upstream and getting at least a few more commits under their belt, but this
sounds like things are heading in the right direction.

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 hopefully be a small time
commitment for you while still easing that transition.

Then hopefully by the T release it would not be an issue at all for someone
else to step up as the new PTL. Or even if things progress well, you could step
down as PTL at some point during the Stein cycle if someone is ready to take
over for you.

Just a suggestion to help ease the process.

Sean


__
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] openstack-dev] [trove] Considering the transfter of the project leadership

[Dariusz Krol]

Hello All,


as a member of Samsung R 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 project. That is why we would like to step up 
and help with development and leadership.

We started our contribution with code reviews and we also submitted our 
first contributions to trove-tempest-plugin. We intend to increase our 
involvement in the community but we understand it need to take some time 
and help from community.


I would like to thank current Trove team for warm welcome, and I'm 
really looking forward to the future collaboration with the community.


Kind regards,

Dariusz Krol

On 07/25/2018 06:18 PM, 赵超 wrote:
> cc to the Trove team members and guys from Samsung R 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 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 patches and reviews fall a lot in this
> cycle comparing Queens.
>
> [1] https://etherpad.openstack.org/p/trove-ptg-rocky
> 
> [2]
> https://etherpad.openstack.org/p/trove-priorities-and-specs-tracking
> 
> [3]
> 
> https://docs.google.com/spreadsheets/d/1Jz6TnmRHnhbg6J_tSBXv-SvYIrG4NLh4nWejupxqdeg/edit#gid=0
> 
> 
>
> And for me, it's a really great chance to play as the PTL role of
> Trove, and I learned a lot during this cycle(from Trove projects
> to the CI infrastrues, and more). However in this cycle, I have
> been with no bandwith to work on the project for months, and the
> situation seems not be better in the forseeable future, so I think
> it's better to transfter the leadership, and look for opportunites
> for more anticipations in the project.
>
> A good news is recently a team from Samsung R 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 tempest plugin. They're also willing and
> ready to act as the PTL role. The only problem for their
> nomination may be that none of them have a patched merged into the
> Trove projects. There're some in the trove-tempest-plugin waiting
> review, but according to the activities of the project, these
> patches may need a long time to merge (and we're at Rocky
> milestone-3, I think we could merge patches in the
> trove-tempest-plugin, as they're all abouth testing).
>
> I also hope and welcome the other current active team members of
> Trove could nominate themselves, in that way, we could get more
> discussions about how we think about the direction of Trove.
>
> I'll stll be here, to help the migration of the integration tests,
> CentOS guest images support, Cluster improvement and all other
> goals we discussed before, and code review.
>
> Thanks.
>
> -- 
> To be free as in freedom.
>
>
>
>
> -- 
> To be free as in freedom.

__
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] openstack-dev] [trove] Considering the transfter of the project leadership

[赵超]

cc to the Trove team members and guys from Samsung R 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 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 patches and
> reviews fall a lot in this cycle comparing Queens.
>
> [1] https://etherpad.openstack.org/p/trove-ptg-rocky
> [2] https://etherpad.openstack.org/p/trove-priorities-and-specs-tracking
> [3] https://docs.google.com/spreadsheets/d/1Jz6TnmRHnhbg6J_tSBXv-
> SvYIrG4NLh4nWejupxqdeg/edit#gid=0
>
> And for me, it's a really great chance to play as the PTL role of Trove,
> and I learned a lot during this cycle(from Trove projects to the CI
> infrastrues, and more). However in this cycle, I have been with no bandwith
> to work on the project for months, and the situation seems not be better in
> the forseeable future, so I think it's better to transfter the leadership,
> and look for opportunites for more anticipations in the project.
>
> A good news is recently a team from Samsung R 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 tempest plugin. They're
> also willing and ready to act as the PTL role. The only problem for their
> nomination may be that none of them have a patched merged into the Trove
> projects. There're some in the trove-tempest-plugin waiting review, but
> according to the activities of the project, these patches may need a long
> time to merge (and we're at Rocky milestone-3, I think we could merge
> patches in the trove-tempest-plugin, as they're all abouth testing).
>
> I also hope and welcome the other current active team members of Trove
> could nominate themselves, in that way, we could get more discussions about
> how we think about the direction of Trove.
>
> I'll stll be here, to help the migration of the integration tests, CentOS
> guest images support, Cluster improvement and all other goals we discussed
> before, and code review.
>
> Thanks.
>
> --
> To be free as in freedom.
>



-- 
To be free as in freedom.
__
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] openstack-dev] [trove] Considering the transfter of the project leadership

[赵超]

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 patches and
reviews fall a lot in this cycle comparing Queens.

[1] https://etherpad.openstack.org/p/trove-ptg-rocky
[2] https://etherpad.openstack.org/p/trove-priorities-and-specs-tracking
[3]
https://docs.google.com/spreadsheets/d/1Jz6TnmRHnhbg6J_tSBXv-SvYIrG4NLh4nWejupxqdeg/edit#gid=0

And for me, it's a really great chance to play as the PTL role of Trove,
and I learned a lot during this cycle(from Trove projects to the CI
infrastrues, and more). However in this cycle, I have been with no bandwith
to work on the project for months, and the situation seems not be better in
the forseeable future, so I think it's better to transfter the leadership,
and look for opportunites for more anticipations in the project.

A good news is recently a team from Samsung R 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 tempest plugin. They're
also willing and ready to act as the PTL role. The only problem for their
nomination may be that none of them have a patched merged into the Trove
projects. There're some in the trove-tempest-plugin waiting review, but
according to the activities of the project, these patches may need a long
time to merge (and we're at Rocky milestone-3, I think we could merge
patches in the trove-tempest-plugin, as they're all abouth testing).

I also hope and welcome the other current active team members of Trove
could nominate themselves, in that way, we could get more discussions about
how we think about the direction of Trove.

I'll stll be here, to help the migration of the integration tests, CentOS
guest images support, Cluster improvement and all other goals we discussed
before, and code review.

Thanks.

-- 
To be free as in freedom.
__
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