slack gitlab_所以是的，我们尝试了Slack ...，我们对此深感遗憾

slack gitlab

by freeCodeCamp

通过freeCodeCamp

所以是的，我们尝试了Slack ...，我们对此深感遗憾 (So Yeah We Tried Slack… and We Deeply Regretted It)

Back in April, all was well with our community of busy adults learning to code. We were communicating using Gitter.im, a GitHub based chatroom system. And yet every day, someone would ask me “Why aren’t your campers using Slack?”

早在四月，我们忙碌的成年人学习编码的社区就一切顺利。 我们正在使用基于GitHub的聊天室系统Gitter.im进行通信。 但是每天都有人问我：“为什么你的露营者不使用Slack？”

I’d considered Slack back in October before even starting Free Code Camp, so I was well aware of its limitations. But gradually, my cool kid friends persuaded me.

早在十月份开始免费代码训练营之前，我就考虑过Slack，所以我很清楚它的局限性。 但是渐渐地，我很酷的孩子朋友们说服了我。

First we messed around with Slack’s API and found an undocumented workaround for their cumbersome email invite system, so we’d be able to automatically add campers to our Slack. Then Harvard’s CS50 class, one of the most popular online courses, started using it. I thought, “OK — if it’s good enough for Harvard, it’s probably safe for us to switch.”

首先，我们弄乱了Slack的API，并为他们繁琐的电子邮件邀请系统找到了一个未记录的解决方法，因此我们能够将露营者自动添加到我们的Slack中。 然后，哈佛大学的CS50课程(最受欢迎的在线课程之一)开始使用它。 我以为，“好吧-如果对哈佛大学来说足够好了，那对我们来说可能是安全的。”

Though their free tier warns that you only get 10,000 messages of searchable archive, and 5 integrations, they clearly state that “there is no limit on how many people you can add to your team on Slack.” So we assumed we wouldn’t need to worry about outgrowing their service. But trusting Slack’s marketing would prove to be a huge mistake.

尽管他们的免费会员警告您只能获得10,000条可搜索的存档消息和5个集成，但他们明确指出“在Slack上可以添加多少人没有限制。” 因此，我们假设我们不必担心服务的增长。 但是，相信Slack的营销将是一个巨大的错误。

屈服于同伴压力 (Bowing to Peer Pressure)

Our campers were happy. We were finally using the premier collaboration tool! Our campers lauded Slack’s hotkeys and mobile experience. They were delighted by Slack’s plaid patterns and warm visual design.

我们的营员很高兴。 我们终于使用了一流的协作工具！ 我们的露营者称赞Slack的热键和移动体验。 他们对Slack的格子图案和温暖的视觉设计感到满意。

Our other core contributors sighed in relief. Our campers were among the cool kids.

我们的其他核心贡献者松了一口气。 我们的露营者属于酷孩子。

裂缝开始显现 (The cracks start to show)

Anxiety set in as I saw how quickly we reached Slack’s limits. Messages like this one appeared everywhere, in full view of our campers:

当我看到我们很快达到Slack的极限时，焦虑就开始了。 在我们的营员的视野中，这样的信息随处可见：

Slack’s cheapest plan was $5 per user, per month. That’s $5 x 12 months x 8,462 campers = $507,720 per year, just for our current campers. Until we paid, Slack would aggressively archive messages, sometimes only minutes after they were sent.

Slack最便宜的计划是每位用户每月5美元。 那就是$ 5 x 12个月x 8,462露营者=每年$ 507,720，仅适用于我们目前的露营者。 在我们付款之前，Slack会积极地归档邮件，有时仅在发送后几分钟。

Slack’s support team told us that if we wanted this message to go away, we would need to create an integration that exported the messages, then deleted them. We were fine with this, and grateful that this was an option, so we started work on it.

Slack的支持团队告诉我们，如果我们希望此消息消失，我们将需要创建一个导出消息的集成，然后将其删除。 我们对此表示满意，并很感激这是一个选择，因此我们开始对此进行研究。

A few weeks later, we hit around 5,000 campers in our Slack, and Slack’s desktop apps became sluggish. Then their mobile apps became literally unusable. Then one morning I did a single @everyone mention, and Slack sent out 50 duplicate notification emails to every single camper over the next 3 hours.

几周后，我们在Slack中击中了大约5​​,000名露营者，Slack的桌面应用程序变得呆滞。 然后他们的移动应用程序实际上变得不可用。 然后一个早晨，我提到了一个@所有人，Slack在接下来的3小时内向每个露营者发送了50封重复的通知电子邮件。

And still, we blithely shepherded 300 to 500 new campers into our Slack every day, hopeful that this messaging company, now worth $2.8 billion, would hire more engineers to flog their infrastructure into shape. We also held our breaths as we waited for Slacks’ teased support for large open source communities like ours.

而且，我们每天仍将300至500个新的露营者放进Slack，希望这家如今市值28亿美元的消息传递公司将雇用更多的工程师来改造他们的基础架构。 在等待Slacks对像我们这样的大型开源社区的支持时，我们也屏住了呼吸。

最后一根稻草 (The last straw)

I woke up this morning to a mountain of tweets and emails from new campers saying they weren’t receiving our automatically sent Slack invites. Not exactly what you want to happen three days after your open source community is featured in Wired Magazine.

今天早上，我醒来时收到大量来自新露营者的推文和电子邮件，说他们没有收到我们自动发送的Slack邀请。 在Wired Magazine上公开开源社区三天后，您想做的事情并不完全是。

Slack’s support team was enthusiastic about helping, and kept saying the email notifications had gone out.

Slack的支持团队热心于帮助，并一直说电子邮件通知已消失。

In my desperation, I tried to manually send out the invites. That’s when I was confronted with an ominous message: “You have reached the maximum number of users”.

无奈之下，我试图手动发出邀请。 那时，我面临着一个不祥的消息：“您已经达到最大用户数”。

My heart sank. Our contributors had sunk so many hours into building Slack features. We’d endorsed Slack to thousands of people on our Twitch.tv streams, and even mentioned it in interviews with the media. We were heavily dependent on their service.

我的心沉没了。 我们的贡献者花了很多小时来构建Slack功能。 我们已经在Twitch.tv信息流中向成千上万的人认可了Slack，甚至在接受媒体采访时都提到了Slack。 我们严重依赖他们的服务。

In a cold sweat, I started googling. There was literally nothing on web saying anything about Slack having a maximum number of users — only marketing material saying that free tier organizations could have as many users as we wanted. Apparently, we were the first community to ever hit Slack’s undisclosed limit.

一阵冷汗，我开始谷歌搜索。 在网络上，几乎没有任何关于Slack拥有最大用户数的信息–只有市场营销资料表明，免费层组织可以拥有我们想要的尽可能多的用户。 显然，我们是第一个达到Slack未公开限制的社区。

I opened yet another support ticket and phoned our core contributors for an emergency Saturday night meeting to discuss our options.

我又开了一张支持票，并打电话给我们的核心贡献者，参加周六晚上的紧急会议，讨论我们的选择。

Shortly afterward, Slack Support sent me this email:

之后不久，Slack支持人员给我发送了此电子邮件：

Well, that was that. No way were we going to spread our community across a bunch of disparate Slack instances. The entire point of a chat room app is convenient real time conversation. Trying to remember which Slack you had to go to to talk with a specific camper would be a logistical nightmare. Just sending an email would be way faster than this.

恩，就是那样。 我们绝不会在众多不同的Slack实例中分散我们的社区。 聊天室应用程序的重点是方便的实时对话。 试图记住您必须与特定露营者交谈的哪个Slack，这将是后勤上的噩梦。 仅发送电子邮件会比这快得多。

浪子回来了 (The prodigal son returns)

Even though it was 1 a.m. London time, someone from Gitter’s team quickly responded to my desperate tweet, reassuring me that Gitter had no hidden maximum room size. They assured me that things “should be fine”.

即使是伦敦时间凌晨1点，吉特团队的人也Swift回应了我的绝望推文，使我确信吉特没有隐藏的最大房间大小。 他们向我保证，事情“应该没事”。

It’s worth pointing out that Gitter is a small team. Crunchbase doesn’t show them as having any funding at all. And yet they are slowly winning a battle with competitors like Atlassian’s Hipchat, Basecamp, and Slack, at least for housing large open source communities.

值得指出的是，吉特是一个小团队。 Crunchbase根本没有显示他们有任何资金。 但是，他们正在慢慢赢得与Atlassian的Hipchat，Basecamp和Slack等竞争对手的战斗，至少是在容纳大型开源社区方面。

I tried Gitter’s iOS app. It was much faster than before, and included new features like tab completion on @mentions.

我尝试了Gitter的iOS应用。 它比以前快得多，并且包括了新功能，例如@mentions上的制表符补全。

Another thing I noticed is that Gitter now allows you the option of hiding your email address, something Slack has yet to implement despite popular demand and the relative ease with which this could be implemented. This was a privacy issue that we’d had to explicitly warn our campers of, but will no longer have to worry about.

我注意到的另一件事是，Gitter现在允许您选择隐藏您的电子邮件地址， 尽管受到广泛需求并且相对容易实施， 但 Slack尚未实现。 这是一个隐私问题，我们不得不明确警告露营者，但不再需要担心。

A moment ago, I even received this email from one of Gitter’s founders:

不久前，我什至收到了一位Gitter创始人的电子邮件：

Gitter, like us, has embraced the power of Node.js. They are hardening their infrastructure so they can support growing open-source communities like ours. They are a scrappy startup with responsive support team (their founders). The warmth of their response made me feel embarrassed that I had bowed to peer pressure and ever left them.

像我们一样，吉特(Gitter)接受了Node.js的强大功能。 他们正在加强基础架构，以便可以支持像我们这样的不断增长的开源社区。 他们是一家具有响应能力的支持团队(其创始人)的零碎创业公司。 他们的热情洋溢让我感到尴尬，因为我屈服于同龄人的压力并离开了他们。

In retrospect we clearly should have tried to work closer with them on our issues.

回想起来，我们显然应该在我们的问题上与他们紧密合作。

It was very strange moving back to our old Gitter chatroom. It was like a scene from The Walking Dead. Half finished conversations. Thousands of accounts standing idle.

回到我们旧的Gitter聊天室是很奇怪的。 就像《行尸走肉》中的一幕。 对话完成了一半。 数千个帐户处于闲置状态。

But it feels good to be back. We’re going to dust this place off and get back to helping people learn to code and land coding jobs.

但是回来很高兴。 我们将清理这个地方，然后回到帮助人们学习编码和土地编码工作的位置。

翻译自: https://www.freecodecamp.org/news/so-yeah-we-tried-slack-and-we-deeply-regretted-it-391bcc714c81/

slack gitlab