4 ms·
They do mention in the write-up that, "We also held our breaths as we waited for Slacks' teased support for large open source communities like ours." and show t
by metasean 11y ago
They do mention in the write-up that, "We also held our breaths as we waited for Slacks' teased support for large open source communities like ours." and show the FAQ addressing their use case - https://www.evernote.com/l/AHQa0WlJiC9IRZyu8Us7Xm3xOAD31_cX8RAB/image.png https://www.evernote.com/l/AHQa0WlJiC9IRZyu8Us7Xm3xOAD31_cX8...
- detaro 11y agoWhere did Slack tease support for open source communities with thousands of members? Because seeing that FAQ makes me think "oh, hey, cool, potentially cheaper plans for open source teams", not "move a GIANT group over in anticipation". I agree though, Slack probably could have communicated that a bit better, at least if they contacted Slack beforehand. Even if the answer had been "We actually have no clue what happens if you try to join 10k people.", the problems certainly sound like that's the case.
- andmarios 11y agoThe screenshot you quote is about open source projects, not communities. If I understand correctly, even a large project like the Linux kernel has only a few hundred active developers at a time and the rest are one-time small-patch contributors. It would be interesting though to know how many students used slack for Harvard's online CS50 and how it worked for them.
- rylee 11y agoWhy would you jump ship for something that hasn't even arrived yet?