yuvipanda

Thanks! This is a good start.

Do you have ideas on how you will make the governance of the registry open? Who will make important decisions around policies, and how will they be made? I personally find this to be the core reason I find it hard to use startup-run package registries.

Disclaimer: I work on the hub.

Sorry to hear you found the hub too complex. We're working on making easier-to-use hub setups that fit different use cases. Can you tell us a little more about what your use case was and (optionally) which parts of the hub setup you found too complex?

Thanks!

You can use systemd or docker with JupyterHub, and make it as protected (or not) as you want. We could also write a spawner that spawns full fledged VMs, which would give you 'real' untrusted isolation - would that be something interesting to you?

Don't see anything else around that fits that bill. They also have amazing IRC bridging - I have been using Matrix bridged into Freenode as my primary 'IRC Client' for almost a year now.

Have you considered adding kubernetes support?

Should be able to!

<3

My only question is if it is required that they mention 'I have cramps' explicitly publicly. Not sure if their menstrual cycle is anyone's business. There's also no reason for it to be taboo, but not sure where the balance of 'it is nbd, deal with it!' vs 'I do not really want to broadcast this information to my teammates' is.

We run it at Wikimedia for our Tool Labs setup, and are migrating more things to it over time.

There used to be a team dedicated to making MW Core better / cleaner, but that was lost in a re-org earlier in 2015.