This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-28
Channels
- # admin-announcements (4)
- # beginners (11)
- # boot (148)
- # cider (74)
- # cljs-dev (31)
- # cljsrn (30)
- # clojure (55)
- # clojure-berlin (15)
- # clojure-greece (1)
- # clojure-japan (18)
- # clojure-poland (35)
- # clojure-russia (72)
- # clojure-spec (35)
- # clojure-uk (34)
- # clojurescript (134)
- # cursive (26)
- # datomic (42)
- # dirac (7)
- # editors-rus (1)
- # emacs (17)
- # hoplon (29)
- # jobs-rus (3)
- # juxt (1)
- # luminus (11)
- # off-topic (9)
- # om (66)
- # onyx (49)
- # pedestal (1)
- # perun (19)
- # proton (13)
- # protorepl (5)
- # re-frame (31)
- # reagent (13)
- # ring (2)
- # spacemacs (1)
- # specter (40)
- # spirituality-ethics (2)
- # test-check (41)
- # untangled (7)
- # yada (17)
Also consider using a non-personal group, this way when adding a contributor you don't have to give them access to your entire array of closes projects @richiardiandrea
@martinklepsch: I see your good point and, together with the other idea of having a boot-contrib
lib, shall I create an account called boot-contrib
where I put boot-cljs-devtools
?
@richiardiandrea: I actually thought of a single boot-contrib
project — really for simple stuff like boot-cat
, boot-gzip
, ...
boot-cljs-devtools
seems perfectly fine as an isolated project
but for things like concatenating files a full project seems overkill
yes, but we could have boot-contrib/boot-contrib
in that group right? and boot-contrib/boot-cljs-devtools
, some sort of umbrella group (maybe boot-contrib
is a bit of a misleading name)
there is already an umbrella project which is boot-clj
actually