Tim Abbott

Agreed, maybe just add a second commit fixing the other issue?

It would be nice to complete the basic documentation first, but I think I agree we don't need to block on that.

I don't think this hubot adapter supports that, but it should be easy to add using the zulip API.

This project isn't ready for distribution yet; we got halfway through extracting the project from zulip/zulip as a resuable component a few months ago, but I don't intend to update...

@rht did that actually cover the whole codebase? I would have thought it's only done for the parts of the codebase that we've moved to the Python 3 type syntax...

I'll see if I can find someone to update this; it shouldn't be a ton of work.

I think probably the right solution to this problem is to just provide a documented path for passing into the integration the path to an SSL certificate it can use...

the Hubot integration uses zulip-node, not the Python API: https://github.com/zulip/zulip-node The Python API has an open PR to add support for specifying a certificate, but the Node API bindings do...

The easiest solution is to just get a free real SSL cert from LetsEncrypt.

The problem is I think that the options feature in `pip` is not super well-implemented. We were able to get that option to work, but not in a `requirements.txt` file....