In terms of future commitments: the largest thing we have identified as a blocker for launching additional community services (such as Lemmy or kbin, for example) is the lack of a single sign-on infrastructure for Treehouse.

We discussed SSO options for a while, such as LDAP/Kerberos and Keycloak.

We concluded that there was not really any pre-existing solution that was developed on a stack that we felt confident maintaining (for example: we are not going to deploy Active Directory because we do not have the resources to manage a Windows machine, and Keycloak is a giant pile of barely-maintained Java), so we are considering writing our own light-weight OIDC/SAML single sign-on solution.

Although there is interest in deploying a Lemmy or kbin instance for discussion boards, this will roll out before we deploy a Lemmy or kbin instance. This also allows Lemmy and kbin to mature a little more before we pick and deploy one of them.