This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-28
Channels
- # beginners (79)
- # boot (24)
- # cider (5)
- # clara (5)
- # cljs-experience (5)
- # clojure (126)
- # clojure-greece (5)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-russia (1)
- # clojure-spec (21)
- # clojure-uk (31)
- # clojurescript (151)
- # community-development (20)
- # cursive (25)
- # datomic (24)
- # flambo (1)
- # fulcro (312)
- # graphql (10)
- # hoplon (20)
- # juxt (2)
- # keechma (6)
- # leiningen (7)
- # luminus (4)
- # om (4)
- # onyx (7)
- # parinfer (24)
- # protorepl (1)
- # re-frame (7)
- # reagent (13)
- # shadow-cljs (19)
- # spacemacs (14)
- # specter (14)
- # uncomplicate (22)
- # unrepl (1)
56% is lost anyways then, how much of the 44% is worth logging, that's a very good point @seancorfield I had not considered...maybe then the good thing would be not to change platform but to integrate Slack with some sort of Q&A engine
my current colleagues have developed a bot for marking conversations and paste them as issue/pr comments
not all the conversations are useful of course and admins/Q&A maintainers could mark the good ones only
We also have http://clojureverse.org/, which can be the recipient of the Q&A
I don't think we have any spare integration slots on the free plan for new bots, but keep the admins posted and we'll see what we can do.
i might make it chrome extension written in clj/cljs so anyone can use it if he deems situation Q&A worthy
@lepistane well, step by step, keep me posted on the repos not sure I have too much time, but I'll try my best...I can also peek at the current implementation we have here