Operations | Monitoring | ITSM | DevOps | Cloud

Late last year, the Confluence team introduced the 7.0 platform release for Server and Data Center customers. It was our first platform release since 2016, and it focused on delivering improvements to administration, team productivity and enterprise needs. After a months-long development cycle, we shipped within a week of our goal – not too shabby, if I do say so myself!

In this challenging global environment, we realize many of our customers will work from home for the next several weeks. Thankfully, Logz.io is designed to support distributed teams and work environments, and we wanted to highlight some of the ways you can use the platform both for remote monitoring and to collaborate better with your teams over the course of the COVID-19 pandemic.

Maintaining success in a large open source project is one of the key objectives of Mattermost. We have hundreds of contributors and we want to create a project that could serve as a model in the Go community. Having said that, following idiomatic Go principles is the thing that we care most about while maintaining our code consistency. For this specific task, we utilized go vet and with this blog post, I would like to explain how we pushed the limits of this tool by extending it.

Mattermost 5.21 includes improvements that will help your team work together more effectively. Some of these improvements, including the following ChatOps integration and plugins, were built during our successful open source chatbot hackfest that brought together 2,000 contributors from around the world.

Better communication at work is the answer. Ok, maybe not THE answer… but it’s close. Fact is, it’s almost always step number one when addressing persistent issues that hold you back, as well as what helps you move from good to great. Better communication increases understanding, fosters trust, and stands out as the essential ingredient for getting things done. It’s not a silver bullet, it’s silver buckshot.

We decided to make Mattermost a remote-first company for several reasons. For example, employees don’t have to waste time commuting, we are able to hire from a wider talent pool of self-motivated individuals, and we have coverage in all time zones, which helps us respond to our customers around the world more effectively. And since we’re a remote company building collaboration software, we have plenty of opportunity to dogfood our own product.

Earlier this week, our organization made a big decision. From Monday to Tuesday, Axosoft transitioned from being an in-person company to an entirely remote-based workforce overnight. Our organization’s leadership determined this to be a necessary and preemptive measure in our efforts to minimize effects of the CoronaVirus Pandemic and how it affects our team members. Starting tomorrow, my company, Axosoft, is going all remote until further notice.

If you think of it in terms of Tuckman’s stages of team development, suddenly shifting to remote en masse throws your team into “storming” mode. Confusion and frustration abound, and everything feels twice as hard as it should. (We know because we’ve been there.) Your goal right now is to get back to the “performing” stage and resume your regularly-scheduled level of productivity. Here are five ways to do that.