If you use Sentry, you’re probably familiar with our SDKs. While they aren’t the only reason for Sentry’s success, they do play a very important role, from the first time an error is thrown to the moment you fix the bug. SDKs are often like political figures (editor’s note: there are so many things we resisted saying here) — you don’t notice them if they do a good job. Jokes aside, there are very few expectations for an SDK.

Three years after launching, there are over 1,000 open source projects on GitHub that integrate with Mattermost. Our contributors have also added hundreds of amazing features to Mattermost. We’re reflecting on how we got here—and what we’re doing next to build an even stronger community for our contributors.

For many of our users reacting to downtime data sent from a monitoring system such as StatusCake.com is a 24 hour job, and the process incorporates many staff who will have varying responsibilities, and sometimes work quite different hours. This is particularly true of companies who run “follow-the-sun” with their global dev-ops teams picking up the baton from the last as their time zone starts its working day.