This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-18
Channels
- # announcements (11)
- # architecture (1)
- # aws (2)
- # beginners (101)
- # calva (3)
- # clj-kondo (2)
- # cljdoc (1)
- # cljs-dev (20)
- # clojure (92)
- # clojure-dev (34)
- # clojure-france (1)
- # clojure-italy (2)
- # clojure-spec (13)
- # clojure-uk (3)
- # clojurescript (28)
- # cursive (7)
- # data-science (58)
- # datomic (18)
- # docs (1)
- # fulcro (11)
- # graphql (3)
- # hoplon (25)
- # klipse (3)
- # leiningen (4)
- # nrepl (3)
- # off-topic (57)
- # pedestal (1)
- # portland-or (1)
- # precept (1)
- # reagent (5)
- # reitit (2)
- # rewrite-clj (4)
- # ring (1)
- # shadow-cljs (97)
- # sql (90)
- # tools-deps (2)
I just published interactive docs for supdate
: https://vvvvalvalval.github.io/supdate/
Holy lambda has just been released. https://github.com/FieryCod/holy-lambda Tiny integration between the AWS Lambda and the Clojure which allows you to run your lambdas either on Java Official AWS Lambda or on the Custom Native one built into the library.
FYI, migration of jira users, projects, and issues is now complete at https://clojure.atlassian.net
you can link to specific issues at links like https://clojure.atlassian.net/browse/CLJ-2504
redirects will be set up from old urls to new, but for the moment, still need access to the old system
if you have ever edited an issue in the old jira system, you should have an account tied to the email address set up in the old system (you can log in there to check what that was if needed). you can use that email and go through the forgot password process to establish a password for access. processes will be changing around filing issues (won't need an account) and gaining access. more to come on that.
if you see anything weird, ping me
I guess I should say for any discussion - let's take it to #clojure-dev
Yetibot talk from Clojure/north is up! https://yetibot.com/blog/2019-05-18-yetis-at-clojure-north