The end

[jorritfolmer]

Hey @hkelley, I'm slowly moving away from Splunk and don't have much time, the Splunk infrastructure or license anymore to keep this project going in a meaningful way.

So my proposal would be that you take over:

• I'll update the README here, point to your repo and archive this one.
• I'll update the Splunkbase README and point to your version on Splunkbase when you're ready

What do you think?

[hkelley]

@jorritfolmer , I'm not very well-equipped either (I don't really do Splunk development, I just badly needed the OAuth support for this TA). However, if there is no other caretaker available, then I can at least mind the issues. I don't expect to have time for any updates/feature additions.

I'm also not very Github-savvy, but I think the cleanest way to move a repo is https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository.

What's transferred with a repository?

When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved.

I'm not sure how the Splunkbase part works, but it sounds like you are willing to retain ownership of that. Is there a way to add a delegate there?

[jorritfolmer]

I very much thank you for your involvement and contributions. As neither of us has the bandwidth to further develop this project, it seems fitting to archive the repository at this point.

I'd like to highlight that this addon comes with a super-flexible open source MIT license, which empowers any user to inspect, use, tweak, and even sell it, despite its quirky presence alongside the premium proprietary software called Splunk.