This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-01
Channels
- # announcements (5)
- # aws (2)
- # babashka (35)
- # beginners (68)
- # bristol-clojurians (1)
- # calva (14)
- # cider (9)
- # clj-commons (5)
- # clojars (3)
- # clojure (101)
- # clojure-australia (6)
- # clojure-europe (35)
- # clojure-italy (2)
- # clojure-nl (5)
- # clojure-spec (1)
- # clojure-uk (4)
- # clojurescript (70)
- # conjure (3)
- # cursive (7)
- # datomic (36)
- # emacs (11)
- # exercism (1)
- # fulcro (23)
- # helix (2)
- # jobs-discuss (15)
- # lsp (17)
- # malli (8)
- # meander (1)
- # nrepl (60)
- # off-topic (10)
- # pedestal (9)
- # react (8)
- # reagent (53)
- # reveal (10)
- # shadow-cljs (27)
- # spacemacs (4)
- # tools-build (4)
- # tools-deps (4)
- # xtdb (2)
Is the Clojars Repo still the correct place to request verification for a Clojars group? And is the verification still done via DNS TXT record?
@nichols1991 Per Toby's message (above, on September 29th): > Yep, this is not a problem, you just need to verify the clj-commons GH org, which requires creating a repo with a special name. Can you file an issue at https://github.com/clojars/administration/issues to start that process? > Note that verifying org.clj-commons is pretty easy - @danielcompton would just need to create a TXT record, and once a group is verified, any member of the group can deploy to it.
