> First, those are bolt-ons and I don’t actually want them tied to the source code management system. Anecdote: when Richard first proposed the /chat feature i

> First, those are bolt-ons and I don’t actually want them tied to the source code management system. Anecdote: when Richard first proposed the /chat feature in fossil i was highly skeptical about its utility but (as the fossil project's "JS guy") wrote it anyway. Now, almost 3 years later, we've been using chat 24/7 across multiple fossil-hosted projects and can't imagine doing without it. The majority of the sqlite project's coordination happens via fossil's /chat. Yes, it was bolted on, but it's also become indispensable for us as a feature.