This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-18
Channels
- # announcements (8)
- # aws (5)
- # babashka (69)
- # beginners (37)
- # calva (222)
- # cider (10)
- # clj-commons (8)
- # clj-kondo (69)
- # cljdoc (5)
- # clojure (62)
- # clojure-dev (23)
- # clojure-europe (37)
- # clojure-italy (2)
- # clojure-nl (6)
- # clojure-sg (6)
- # clojure-uk (5)
- # clojurescript (25)
- # clojureverse-ops (12)
- # conjure (1)
- # cursive (1)
- # fulcro (9)
- # gorilla (1)
- # graalvm (6)
- # graphql (1)
- # gratitude (1)
- # honeysql (7)
- # introduce-yourself (4)
- # jobs (1)
- # kaocha (9)
- # keyboards (4)
- # leiningen (8)
- # lsp (21)
- # malli (9)
- # music (3)
- # nextjournal (17)
- # nrepl (6)
- # off-topic (10)
- # pathom (12)
- # portal (25)
- # reagent (8)
- # releases (1)
- # specter (1)
- # xtdb (1)
Apologies if I've missed this somewhere, but is there an easy way to tell if a clj-commons project is still being maintained by the group? I ask in the context of looking to pick a new metrics publishing lib, have used https://github.com/clj-commons/iapetos in the past, and just wanted to check if the lack of a commit this year was because things are relatively stable, or an indication of lack of maintenance.
@mrkiouak This file: https://github.com/clj-commons/iapetos/blob/master/.github/CODEOWNERS should indicate who is the current maintainer or maintainers
One of the problems that can theoretically occur is that a maintainer doesn't respond to issues and clj-commons as an org isn't really aware of this. @slipset any thoughts on how to deal with this?
Seems like that’s what have happened. here. I guess letting us know here is one option, as @mrkiouak did.
We use iapetos
at work, and I guess I consider it stable, so I wouldn’t be too worried about the lack of commits. I’d be more worried (and that’s on me) that there are some new issues and a PR that should’a been handled