I am happy to help out with Gnocchi too. I have experience with the code base and wrote an influxdb backend for gnocchi but it was around the time it got split off from openstack and it never made it in.  (we use an updated patch in production)
I canâ??t think of much needed in the way of extra features for our use case but I would be able to help out on maintenance and also CI issues.
> On 20 Dec 2019, at 11:27 am, Lingxian Kong <anlin.kong at gmail.com> wrote:
> I'd prefer we fork Gnocchi to opendev/gerrit so the developers could
> have the same experiences with other openstack projects. Before people
> fixing any bugs or developing any features, the first task is to set up
> the CI and publish docs in openstack website.
> I can offer some help as well.
> Best regards,
> Lingxian Kong
> Catalyst Cloud
> On Fri, Dec 20, 2019 at 3:06 AM Thierry Carrez <thierry at openstack.org <mailto:thierry at openstack.org>> wrote:
> Tobias Urdin wrote:
> > I can volounteer to spend time on Ceilomter and Gnocchi while I have
> > some mimimal knowledge on Ceilomter
> > and pretty much none on the Gnocchi codebase I would like to see the
> > project continued.
> > Another thing would be if Gnocchi should be moved back or if I should
> > somehow get in contact with the former
> > Gnocchi maintainers and see if we can get access to GitHub?
> If the goal is to maintain Gnocchi as-is for the narrow OpenStack use
> case, my preference would be to fork / move it back to opendev, under a
> gnocchi namespace. That would ensure a clean cut from the unmaintained
> "gnocchi for all the things" project on GitHub, and reset expectations.
> If the goal is to take over Gnocchi and support all other use cases,
> then maybe taking it over on GitHub might be easier to ensure continuity.
> Thierry Carrez (ttx)
-------------- next part --------------
An HTML attachment was scrubbed...