Nice one! I really enjoyed the title, and also the idea to make an effort to actively support lurkers.

I was wondering if you find Lurking especially impactful in the Open Source context, or in InnerSource as well?

Also did you have either of these in mind when writing the blog posts? I wasn't clear about that from the post as it talks both about "communities" as well as "teams".

Thanks for sharing!

We have used the GitHub Sponsors program here, to support this open source project: https://help.github.com/en/github/supporting-the-open-source...

GitHub is also working on what they call "Corporate Sponsorship", which should make this even easier in the future: https://github.blog/2019-06-12-faq-with-the-github-sponsors-...

Interesting, which configuration management system do you use?

Chef and hating it.

I just checked with the Jim, the author of the blog post, and module (we both work for Meltwater).

He confirmed "You only need one instance per account, we have always been fine with just one".

I will let him fill in further details here but I figured you would be interested in a short update on this.

Yes exactly, SSH access is also one of the reasons for building the module, that is mentioned in the blog post.

> Access: When troubleshooting, we save time not having to look up the instance’s internal IP address for SSH access.

Great to hear! Please let us know how the testing goes!

I am biased, as I am working for the same company, but I really appreciate the level of detail that we are sharing here about how we are approaching the query load balancing challenges in Elasticsearch.

What exactly is an ACH deposit btw? (sorry, German reader here)

Can one only send money with an ACH deposit or also pull money from an account?

hey seb, ACH = automated clearing house[1]. It's the US network for moving funds between two bank accounts. ACH is a push & pull system, but our API only supports push.

[1] http://en.wikipedia.org/wiki/Automated_Clearing_House