This document lists ...
- High level requirements for a community collaboration tool, ranked by importance to the Clojure community.
- mandatory
- expected
- nice to have
- Extant collaboration tools, with pointers towards existing Clojure communities within them, if any.
- A detailed analysis of how each tool satisfies the requirements of the Clojure community.
- Free hugs for everyone
Description: Most popular "modern" collaboration tool for teams. Incumbent home of main Clojurians community.
Where to find it: https://slack.com
Platforms: web, mobile, desktop
Existing Clojure community?: http://clojurians.slack.com (~ XX,000 users)
Description: Gaming oriented collaboration tool, but increasingly adopted as a general purpose collaboration tool.
Where to find it: http://discordapp.com
Existing Clojure community: https://discord.gg/v9QMy9D (~ 200 users registered)
TBD
TBD
How does each tool stack up?
- 👎 Free hugs for everyone
- Nobody has been hugged the entire time I've been here.
TBD
TBD
TBD
Under "Mandatory" I'd like to see moderation and administration concerns, including Code of Conduct (Clojurians Slack has this, as do several Clojure conferences etc) and a way to deal with community abuse (e.g., a team of "admin" members with the privileges needed to remove/ban/manage other community members), as well as "system" stuff like managing/maintaining integrations to, and general configuration of, the chat environment. Slack scores highly on this since it is designed for teams with the concepts of owners and admins.