LearnTeachCode / code-coffee-compendium

Curated resource compendium, created for/by the LearnTeachCode community
https://learnteachcode.org/code-coffee-compendium/home/
MIT License
36 stars 24 forks source link

Please add the discord? #64

Closed asalwaysimani closed 4 years ago

asalwaysimani commented 4 years ago

https://discord.gg/PKrAxvy

LearningNerd commented 4 years ago

Hi @MargaretCatter! I posted a message on the Discord to discuss this with you all, but posting here too to keep this conversation transparent to all our organizers.

My only concern is that having two async chat communities could cause some confusion / splintering for the Learn Teach Code community as a whole. But I'd like your thoughts on this! Here's how I'm currently looking at it:

Pros of adding an official LTC Discord:

Cons:

Some background on our Slack:

Anyhow, I'd love to hear from more people to bring up points that I hadn't considered above. I think this is a good time to discuss how to make the most of all these online platforms available to us since we're meeting 100% virtually for a while.

(cc: @capsulecorplab @sugarsyntax @jbazalar @cynful @TristanDamron @KChorseraddish @armaneous and of course anyone from our community is welcome to post here!)

armaneous commented 4 years ago

Chiming in here so that the conversation is public.

I anticipate that a migration to another platform will incur ~90% of user loss; only ~400 will make the jump. Slack does have irregular periods of activity and I'd estimate there are only about 200 or so that are monthly active users in public channels. I don't know if those are the same as ones active in private channels and direct messages. Also, unless the Slack is shut down altogether, it's likely that a portion of users will continue to use it despite an announced migration. Perhaps that's acceptable?

Personally, I'd really rather not be tied to yet another company. Discord is repositioning itself to more directly compete with Slack, probably because its valuation has raised some eyebrows, but I worry about its business model changing. We could wind up in the same situation we're in with Slack's limitations on free teams. Mattermost seems interesting because of that, but we incur operational overhead and a small monthly fee. Not too worried about the latter, but I don't think I can sustainably commit to the former long-term.

If we're not talking about a migration, there is definitely a fracturing of the community that'll happen by maintaining more than one platform. And that's aside from the operational overhead mentioned already with moderation and guiding new members towards which community is right for them.

I'm not saying the Slack is the best, either. I just think we should be very careful with the decision we make and have a thorough, inclusive plan.

capsulecorplab commented 4 years ago

I personally don't mind having both Slack and Discord. To use a space exploration metaphor, we're not migrating, we're merely colonizing another of planet (platform). Slack can remain as the front facing community forum, which perhaps caters itself to a more professional/networking and newcomer friendly atmosphere, where as the Discord can serve more special interest topics, e.g., infosec, game dev, technical writing, etc. It's also worth mentioning Discord (at the moment) has unlimited message storage, so you don't lose messages unlike Slack's free tier.