Is it worth contributing non-AWS dockerized clojure collector?

[snowindy]

I unwired Snowplow clojure collector from ElasticBeanStalk, dockerized it and made it ready for usage. Here's link.

I think it may be a good idea to contribute this effort to main repository. Could you please let me know if it's worth trying (maybe there is something similar already) and what can be the process?

[alex]

Hey @snowindy - thanks for sharing! We have an RFC out currently to replace the Clojure Collector:

Replacing the Clojure Collector

This is a Request for Comments (RFC) for replacing Snowplow's Clojure Collector with an alternative event collection approach for the Snowplow batch pipeline. We welcome feedback on all of our RFCs! Please respond with your thoughts and comments in the thread below. Why we created the Clojure Collector We created the Clojure Collector in January 2013 as an alternative to our CloudFront pixel-based collector. The Snowplow community liked the CloudFront Collector for its ease of setup, essent…

Also we are working on a non-AWS version of the Snowplow pipeline using Kafka:

http://snowplowanalytics.com/blog/2016/11/15/snowplow-r85-metamorphosis-released-with-beta-apache-kafka-support/

Based on these, I'm not convinced this is something we would need in snowplow/snowplow, but keen to hear thoughts from the community!