The future development of this plugin

[kubotat]

Hi,

Thanks for developing such a great plugin!
I'm a member of @fluent-plugins-nursery team who try to maintain Fluentd plugins widely used in the community and keep them updated.
https://github.com/fluent-plugins-nursery/contact

It seems that fluent-plugin-splunk-hec will reach End of Support on January 1, 2024. Since many users are still relying on this plugin, we want to adopt this plugin as well.

So the question is: is it possible to transfer the ownership of this project to fluent-plugins-nursery after January 1, 2024?
If you can, we'd continue developing this work as part of our program to sustain the ecosystem.

We are looking forward to hearing back from you!

[terry-citrix]

I'll second the request. It would be great if the fluent-nursery team took over this project (by giving ownership of the repo to them)!

[nate-duke]

If anybody that works for Splunk/Cisco is still around, please consider giving this repo to the community to maintain.

Thank you.

[shazib-summar]

+1 this is a widely adopted and used plugin. Please dont let it die

[sebv7]

+1 can only emphasize that. Appreciate it if this could be handed over to the community.

[tavlima]

Hey, @kubotat, any traction here? From what is described in the latest version of the README, it seems a PR changing the CODEOWNERS would be needed.

[jeanpSMJ]

Hello @kubotat @tavlima @sebv7 @shazib-summar @nate-duke @terry-citrix and anyone who is interested in this topic.

I'm part of @splunk / Cisco Product Organization.
I was given the responsibility to act on this repo and its respective image.

This image/code is currently part of a plan to act on its future, along with other images such as:

---

/splunk/k8s-metrics
/splunk/k8s-metrics-aggr
/splunk/kube-objects
/splunk/splunk-sdk-travis-ci
/splunk/jupyterhub-istio-proxy

---

The current plan is to remove the images unless there's anyone interested in maintaining and transferring ownership.

Thankfully, I came across this open issue before we could potentially disturb any of the dependencies on this image you all have.

Please reply to this thread so we can jointly coordinate your interest on this image /splunk/fluentd-hec or any of the other images from the list provided above so we can start internal discussions at Splunk to coordinate what could be the best path to follow with us community.

[sebv7]

moved to fluentbit, so not of interest for me anymore

[terry-citrix]

Hi @jeanpSMJ , we still use /splunk/fluentd-hec in order for our K8S services to send logs to Splunk... basically for it stated purpose. We are in the process of moving to fluentbit, but are not ready to completely switch over yet. We can't volunteer to maintain it unfortunately, but will still need this for another 4-5 months or so.
FYI @vasilis-keramidas

[kubotat]

Hi @jeanpSMJ, Thanks for getting back!

We, Fluentd Plugin Nursery Team, are interested in maintaining this plugin.
Would you be willing to transfer not only /splunk/fluentd-hec but also git repository and Ruby Gem?
If you agree, we would like to proceed with the following steps:

• Original author agrees to transfer their project.
• Admins invite the original author to fluent-plugins-nursery.
• Original author transfers repository to fluent-plugins-nursery. (How to transfer your repository)
• Original author adds a new maintainer as a Gem owner. (How to add a new maintainer to your Gem)

You can find detailed steps here.

Looking forward to hearing your feedback.