This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-12
Channels
- # bangalore-clj (4)
- # beginners (40)
- # boot (53)
- # cider (34)
- # cljs-dev (9)
- # cljsrn (11)
- # clojure (113)
- # clojure-boston (5)
- # clojure-dev (9)
- # clojure-dusseldorf (4)
- # clojure-russia (8)
- # clojure-spec (11)
- # clojure-uk (12)
- # clojurescript (88)
- # cloverage (17)
- # conf-proposals (4)
- # core-async (30)
- # cursive (9)
- # datomic (107)
- # euroclojure (5)
- # hoplon (196)
- # luminus (10)
- # off-topic (20)
- # om (24)
- # om-next (1)
- # onyx (80)
- # parinfer (3)
- # pedestal (16)
- # planck (44)
- # proton (8)
- # protorepl (1)
- # re-frame (19)
- # reagent (7)
- # spacemacs (2)
- # untangled (29)
- # yada (25)
> Sorry for playing a certain amount of hardball on this one, but we don't want to massively reshuffle things until we see if this works well. this is certainly relevant
I’d consider asking Tom directly if he’s the person making the decision about whether and when cloverage can be transfered to the github group. If he’s not, ask to involve them in the conversation directly (I expect there’s a certain amount of he-said she-said going on when you ask for specific requirements); possibly via email if they’re more comfortable with a private conv. Maybe give them a day to respond to your last comments though 😛 Also be aware that everyone in LShift is in the UK so the timezones are part of why the discussion takes a while