Open Stack

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&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 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180726/96ece785/attachment.html>