meander

dgr 2026-03-31T21:01:23.935489Z

Does anybody in this channel still have commit access to the Meander repo? In particular, I ran into this bug the other day. I looks like it has been fixed but Meander hasn’t been released since (no releases for 4+ years, since August 2021). Can anyone speak to the the current and future direction of Meander at this point? https://github.com/noprompt/meander/issues/230

Jimmy Miller 2026-03-31T22:46:37.145609Z

I technically do. But wouldn't feel comfortable doing anything without noprompt. I don't work in clojure anymore and neither does noprompt. Meander is unlikely to see any changes in the future. I could ask him about updating or handing it over to someone or something like that. (He's no longer on slack) But my honest recommendation is a community run fork. I haven't asked him but I highly highly doubt he'd be bothered by it. He likes people using things he created and applying them in new circumstances.

❤️ 2
dgr 2026-04-01T00:34:58.253869Z

Thanks, I appreciate that info. You might want to explore handing it over to clj-commons. I would at least do a final release that wraps up everything that is there now and makes it usable without having to resort to a git SHA in deps.edn. I also did some of the documentation work on Meander back in the day. I have some additional work that was laying dormant in my repo that I’d like to submit as a new PR. If you and Joel are open to questions, I might also contribute further docs for things that aren’t yet surfaced or handled thinly.

➕ 1
Jimmy Miller 2026-04-02T02:12:08.232089Z

It’s definitely not mine to decide what to do with. I gave a talk and wrote some posts. But Joel is the main person. I did less than 1%. Mostly just friends with Joel. We plan on chatting soon and I will bring it up to him. But I'm all honesty I think someone just forking and updating is going to be the lowest friction way. But that again is just a personal opinion.

dgr 2026-04-02T02:30:52.219169Z

Understood.