I’m involved in seven at the moment. Four of them are entirely work related, one of them is related to a political group I’m involved with and two of them are just for fun. But what the hell am I talking about?
Over the last 15 years the way people do software development has evolved. Moving away from archaic waterfall based software development methodologies, Agile extolls the importance of a face to face chat over a heavy dependence on documentation. Of course, the internet also means that your software development team may distributed anywhere in the world, so how do you communicate and collaborate effectively with remote colleagues?
One of the earliest examples of online collaboration was through wiki software. A shared, open space on the internet where users (with the right permissions) are allowed to freely edit content on web pages without requiring any HTML skills or having to upload files to a server. These days wiki is highly refined with the likes of Atlassian’s Confluence allowing extremely fine-grained control over content access and real-time notifications when content is updated. However, managing a wiki can soon become a full time job, its adhoc nature quite often resulting in a chaotic mess of information and is, of course, still no replacement for a face to face chat.
But people have been talking on the internet since its beginning with one of the most popular chat mediums in the early days being IRC, Internet Relay Chat. IRC is built on the concept of chat channels, which these days people might prefer to think of as “chat rooms". When you join an IRC server you would join one or more channels, most chat servers allowing users to freely create their own channels. Once you had created your own channel you could control who had access to it, change it’s topic and various other settings. Its protocol is surprisingly simple, based on the exchange of plain text, much like mail exchange protocols like POP3 or IMAP, that anyone with the patience and knowledge could engage with using a simple telnet connection. However, the common user would normally connect to IRC with one of a myriad of applications, the most popular probably being mIRC.
Some of the greatest collaboration around software development has already occurred on IRC, but it’s not a great medium for sharing content and documentation in a way that people can refer to at a later date, the content of chats being fairly transient and file exchanges occurring in a peer to peer fashion. Collaboration efforts over IRC would usually be combined with some kind of wiki. IRC and wikis were inherently public and insecure, so creating community around these technologies would usually involve a company hosting their own wiki and IRC software which would require hardware and people resources to maintain.
It’s pretty clear the folks at Atlassian had a clear vision about how online collaboration could and should work. JIRA has to be the world’s most well know “ticket management” system, allowing people to create tickets (known as issues) in order to track user requirements, user stories, tasks and defects and more. The Atlassian stack is well integrated so once configured you can have updates to JIRA appear on Confluence pages or even in the chat rooms on Atlassian’s own version of IRC known as HipChat. HipChat is like IRC but accessible using Atlassian’s own software or via their website. It also adds file sharing and allows users to share files in the context of a conversation easily while being able to see the historical transcripts of conversations that have happened.
These days it’s really easy for anyone to spin up an instance of an Atlassian stack giving them a wiki, real time chat, and ticket management but there are alternatives out there. Rather than adopting a whole stack groups may only need a small portion of the stack initially so may decide to sign up for just a HipChat or Slack.
Slack is an alternative to HipChat and, sorry Atlassian, I feel it has a superior user experience. In some ways it is even more like IRC that HipChat, but with a user interface that is unobtrusive and a pleasure to use and like HipChat allows contextual file sharing.
Whether you choose HipChat or Slack, or something else, once a team decides they need to add something else to the stack, it’s relatively easy for them to go out to the web and sign up for a wiki, or a task board, or issue management and then integrate it with whatever chat system they’ve decided to use.
However, software development isn’t the only reason to use a HipChat or Slack.
So when groups of people - (ex)colleagues, friends, families, political groups, etc - want a place to collaborate, chat in real time, share files, and so on, tools like HipChat and Slack are a perfect replacement for the Facebook group. They are generally free to use and your content is safe and secure, because the reputation of the companies hosting these tools depends on that.
Thus the Popup Micro Community is born and the death of Facebook by a thousand cuts begins in earnest.