This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-08
Channels
- # announcements (42)
- # aws (2)
- # babashka (69)
- # beginners (38)
- # calva (18)
- # cider (39)
- # circleci (1)
- # clj-commons (10)
- # cljs-dev (2)
- # clojure (36)
- # clojure-australia (14)
- # clojure-europe (25)
- # clojure-gamedev (40)
- # clojure-losangeles (4)
- # clojure-nl (5)
- # clojure-sweden (1)
- # clojure-uk (5)
- # clojurescript (133)
- # core-logic (24)
- # cursive (7)
- # datalevin (4)
- # datascript (3)
- # figwheel-main (1)
- # fulcro (45)
- # honeysql (1)
- # integrant (43)
- # introduce-yourself (1)
- # jobs (4)
- # leiningen (3)
- # lsp (32)
- # nextjournal (9)
- # pathom (18)
- # polylith (21)
- # portal (65)
- # re-frame (6)
- # releases (1)
- # remote-jobs (1)
- # reveal (12)
- # rewrite-clj (1)
- # sci (84)
- # tools-deps (22)
> @deactivateduser10790 has requested approval for a third-party application to access "CLJ Commons" organization resources via the GitHub API: > > "CLA assistant" from CLA assistant
Let's hold off on that for now and find out a bit more
@deactivateduser10790 is on this slack
Hey everyone! Sorry - I didn’t even realise we had a channel! 😉
And yeah sorry about that ping from CLA Assistant. I’m evaluating it for use with some of my projects (including some hosted as part of clj-commons
) and the first thing it did was ask me to login with GitHub. I saw a “request access for these orgs” type list, but glossed over it (I’m in quite a few orgs, apart from clj-commons
). Only after logging in did I see it had sent some kind of access request to the org admins.
(and was slightly mortified as a result…)
But it does raise an interesting question in my mind for you: what is clj-commons
’ policy on CLAs (if any)?
(oh and CLA = “Contributor License Agreement”, just in case anyone isn’t familiar with that acronym)