Offering to help maintain loom

[jsavyasachi]

Hi @aysylu - opening this as a public note alongside an email I just sent you.

I'm Savy, a Clojure dev (4 years at PayPal, plus a side project reviving Clojure libraries I find useful). loom's the obvious one to care about - it's still the de-facto graph library - but it looks like it hasn't had a maintainer merge since 2021.

Rather than just pile onto the issue tracker, I've already done the work on a fork (https://github.com/jsavyasachi/loom):

• Fixed 8 long-standing correctness bugs, each with a regression test (including a data race in bidirectional BFS and the digraph maximal-cliques bug)
• Landed 4 of the open PRs that were sitting here (Johnson all-cycles Add algorithm for simple cycles in a directed graph #126, simple-paths Added simple-paths function and tests #111, degeneracy-ordering Optimize degeneracy ordering #108, lazy pre-traverse Change loom.alg-generic/pre-traverse to do much less work #120)
• Repaired the ClojureScript build, which had regressed under modern cljs
• Added graph generators (Barabási-Albert, Newman-Watts) and clustering-coefficient

It's all green, and I kept your copyright and the EPL intact.

I'm currently publishing under a longer coordinate (net.clojars.savya/loom), but the fixes really only help people if they land on the canonical loom name. A few ways that could happen, whatever you're most comfortable with:

1. Add me as a maintainer here (or transfer the repo) + add me to the loom Clojars group, or
2. Route it through clj-commons and I maintain it under their umbrella, or
3. I keep publishing under my own name with your blessing.

Genuinely open to other ideas too. No pressure either way - and thanks for loom, it's held up really well.

Savy