Maintainers wanted

[sampointer]

After February 22nd 2018 I will no longer be running this plugin in production myself, instead preferring Kinesis to AWS ES.

Rather than let this code rot and leave those who have invested time without a canonical version I'd instead welcome maintainers to whom commit and publish bits could be granted.

If you're a user of this plugin and would be willing to entertain such a thing please comment below. I'd be very happy to count thumbs-ups as votes of confidence.

Failing that, I'd probably consider 1.7.0 coming out of RC (whenever that might be) an opportune moment to make your own fork.

Should a fork become dominant I'd be happy to hand over the rubygems namespace to the obvious candidate.

[chicofranchico]

I'd love to but I don't know enough ruby to actively maintain it.