This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-18
Channels
- # announcements (6)
- # aws (1)
- # babashka (47)
- # beginners (50)
- # calva (65)
- # cider (4)
- # clj-commons (17)
- # clj-kondo (44)
- # clojure (150)
- # clojure-europe (41)
- # clojure-nl (4)
- # clojure-spec (1)
- # clojure-sweden (4)
- # clojure-uk (6)
- # clojurescript (15)
- # clr (1)
- # conjure (1)
- # core-async (7)
- # cursive (5)
- # datomic (12)
- # events (2)
- # fulcro (17)
- # graphql (12)
- # introduce-yourself (1)
- # jackdaw (5)
- # jobs (2)
- # lsp (52)
- # malli (5)
- # meander (3)
- # minecraft (2)
- # missionary (2)
- # off-topic (10)
- # other-languages (9)
- # reitit (9)
- # remote-jobs (1)
- # ring (8)
- # rum (7)
- # shadow-cljs (9)
- # sql (2)
- # tools-deps (20)
- # xtdb (12)
I see that clj-commons has a fork of Zack Tellmans collection-check. Anyone knows why we have a fork and not a transfer of that repo? I’d prefer a transfer, so if anyone doesn’t speak up, I’d go ahead and delete that repo and rather as Zack if he’d be willing to transfer.
It seems we still have a fork of this rather than a transfer @slipset -- I'm adding ORIGINATOR
and .github/CODEOWNERS
everywhere they are missing in clj-commons
so I'm going to assume @kingmob is the owner for this now since they've taken on a lot of Zach's old repos...
I...guess so? The name didn't ring a bell, so I looked it up. It's a test-time dep for potemkin, for one macro. I haven't done anything with it, but sure, add it to the list (unless someone else wants to take it over)
It's really just housekeeping -- no expectations of actual maintenance unless it breaks 🙂
I finally reached out to @U066UJ2KE about this. Thanks for the nudge.
And as I did that, I see that perhaps the best way forward is just to delete this repo on clj-commons? Nothing has been done to it and no artefacts published.
Do any other libraries depend on it?
We'll give Zach a bit longer to respond and if he wants to transfer it, we can delete the fork and then transfer in. Else we might as well keep the fork since most of Zach's other libraries have moved to clj-commons and @kingmob is maintaining them...?
Zach has replied and is fine with the transfer. I was just wondering about the value of having clj-commons maintain it.
I would say it's worth clj-commons maintaining it, if it is used by any of Zach's libraries that clj-commons already maintains?
If none of those libs on clj-commons use it, then maybe it fails the entry criteria of not being sufficiently popular/useful?
Perfect! I see we just approved accepting Riddley as well.
It seems we still have a fork of this rather than a transfer @slipset -- I'm adding ORIGINATOR
and .github/CODEOWNERS
everywhere they are missing in clj-commons
so I'm going to assume @kingmob is the owner for this now since they've taken on a lot of Zach's old repos...