There was a thread on `r/programming` a while ago ...
# general
b
There was a thread on
r/programming
a while ago on Slack vs Forums, linking to a blog post: https://www.reddit.com/r/programming/comments/qpz8jz/you_should_use_forums_rather_than_slackdiscord_to/ https://www.mooreds.com/wordpress/archives/3451 The blog post suggest forums are better because (filtering to the first two, the other points IMO are less important): • Slack Free plan has limited history, so information is lossy • Google can't index Slack chats However, Reddit comments do highlight that Slack is free and easy and forums don't have an equivalent "free-and-easy" drop-in. I wonder how much support could be lifted from the devs here if Google was able to index the answers y'all provide to questions 🤔 (Obviously there's no silver bullet, and Slack is great for a ton of things. Just food for thought. Maybe there's a slack Q&A bot with fancy AI stuff? Who knows)
1
💯 1
b
+💯. As Pants' devrel lead, I'd love for the community support to be indexable by search engines. Not only so that more people can find the literal text content, but also so people can readily observe for themselves the community's culture of kindness, thoroughness, responsiveness, transparency, and commitment. Of course, there are pros and cons to switching to a publicly indexed forum or else we would have already done it. Folks, let's discuss. What are your thoughts?
h
We've discussed this in the past, there are definitely pros and cons to all options. Switching up is a major undertaking, so we keep punting on it, but there is a bullet to be bitten at some point... maybe now or soon
l
That's probably being considered - but if anything would love to have Github Discussions for that matter - would make it centralized with code and easy to access / contribute to
b
Funny you should mention. I've been interested in that as well. Things like being able to move issues and questions around seamlessly to the right place, and being able to mark questions as answered, etc are intriguing. https://docs.github.com/en/discussions Have you been using it for your team @loud-stone-83419?
l
We have been using it for some of the inner sourcing community we are trying to build
we have both slack and that - it is hard to know when to use which one
b
One thing that GH Discussions lacks is DMs. That's a significant portion of the slack's overall activity.
1
f
Forums seem like they could be good overall. I’m not sure if it is easy to replicate the “agressivly” friendly pattern you have going here: I clicked on the link just to check what information was posted, one of the maintainers reached out to see if I had any questions, that led to me asking said question rather than just continuing to hunt on my own, and discovering that this is a really useful resource in a way I might not have otherwise
b
That's great to hear! Your experience is definitely the one we aim for, and hopefully is replicable elsewhere. But for sure it's essential that no change of platform undermine the aggressively friendly pattern 😉 we've built up here.
Another option is readme.com's own discussion forums. Pants docs are hosted on readme, so this would mean that discussions would not only be indexable by google et al but also indexed by our own docs search. https://docs.readme.com/docs/submit-a-question Though no private messaging. @hundreds-father-404 @happy-kitchen-89482 it looks like you briefly tested readme discussions. Thoughts?
h
I very much don't want to give up DMs. For example, I've had cool conversations with people about where we live for example that would be probably spammy for everyone to see. Same with coordinating pair programming Readme discussions were fine. A little harder to debug things imo because it's not as instantaneous
b
Yeah, I agree DMs are really valuable. I can't see losing them either. Why wasn't readme instantaneous? Is there a notifications lag?
There's also the hybrid option: essentially mirroring the Slack to an indexable public location. If we did that, I'd want the public one to be read-only so that keeping up with support doesn't get harder. We could config slackbot to notify newcomers about the mirror at the outset (heck, it's how many newcomers would discover the community in the first place) and then give a periodic (quarterly?) reminder. For users, it would mean that they could easily share support discussions with colleagues because there'd be a public permalink instead of having to join the slack first themselves.
👍 1
h
No delay, I mean that forums and GitHub issues are generally a slower medium than chat
b
That intangible sense of immediacy.
Gotcha.
For the hybrid option, channel descriptions could also include a "Mirrored to https://pantsbuild.org/support/general"
Zulip is FLOSS, free for open source projects https://zulip.com/for/open-source/, supports DMing, and can be used either as a Slack replacement https://zulip.com/features/ or as a read-only mirror https://clojureverse.org/t/ann-searchable-slack-archive/3777 That first url brings up another benefit: being able to link to from GH issues to permalinks of prior discussions. I like that this would give us the option of staying in Slack while gaining the benefits of indexability then having the option to switch over fairly seamlessly at some point in the future if and when we're ready. Also Zulip is Python, which ❤️ .
f
I think mirroring makes sense. I like the idea of indexability, but forums remove the immediacy of chat-based communication. Also using a forum feels like throwback to the 00s-era internet, and not in a good way.
3
b