noeontheend@beehaw.orgtoFree and Open Source Software@beehaw.org•Stop Using Discord for Your Open source Communities | mattcen's mumblings
0·
1 year agoThis is aptly timed for me—I spent some time this weekend trying to decide what chat service to use for a project of mine. I’m just starting to try building the community, so it feels like I should have a chat ready if/when people start showing up.
I didn’t consider Discord because I wanted to stick with free software, for the reasons outlined in this post and other similar ones. In the end, I settled on Zulip, but would be happy to reconsider (so far, the chat is just me talking to myself!) if anyone wants to suggest an alternative or has experience in a similar situation.
This is exactly right. However, something that I’ve found frustrating is that in many projects (at least the ones that I’m interested in), it feels like there’s a secret roadmap that’s not documented anywhere outside of the maintainer’s head(s). You can scour the wiki, watch the IRC channel and mailing lists, and read through the issue discussions, and you still won’t have a good sense of what they want done next or if the change you want to make is incompatible with some big planned rewrite. I know the answer is to just ask—and I’ve done that more and more recently—but that can be a big hurdle if you’re just getting started.
I’m trying to build a community for a project right now, and this is something I’m very aware of. I’m trying to report on what I’m working on and planning in the project chat so that if someone else comes along, hopefully they’ll (a) understand the current status and (b) feel comfortable asking about the overall vision.