Maintainership: offering to help, and a question about the project's future

Hi @daybrush — and hello to anyone who landed here from #1128 or #1137.

Context

The Moveable ecosystem has been quiet for a while:

Repo	Last commit on master
moveable	2023-12-03
selecto	2023-12-03
gesto	2023-12-01
keycon	2024-07-29

Meanwhile the library still has ~10.7k stars, and react-moveable is doing around 412k npm downloads a week. There are two open threads asking whether the project is still alive — #1128 (Aug 2024) and #1137 (Nov 2024). Between them eight people have commented, the most recent one nine days ago, and neither thread has an answer yet.

This isn't a complaint. Maintainer time is finite, and it's clear that @daybrush's focus has moved to egjs. This issue is simply an offer, made in public so that it's on the record.

What I'm offering

I've been using react-moveable in production for the past year, in a canvas editor. Along the way I built the layer that Moveable deliberately leaves out: persistent groups.

Moveable's groups are runtime selections (a targets array) rather than entities you can serialize, store and reload. Every team building a real editor ends up rebuilding the same two things:

• group / ungroup with rotation-aware conversion between a child's absolute position and its position relative to the group center
• recursive group resize, dispatched to children by type — font-size for text, inner crop offsets for media, viewport dimensions for SVG

Both of these are running in production today, and I'd like to contribute them upstream — along with helping triage the 448 open issues.

What I'm asking

@daybrush — two questions, and either answer is fine:

1. Are you still merging PRs? If yes, I'll start sending them. Nothing else is needed from you.
2. If you'd rather step back, would you consider adding maintainers with GitHub write access and npm publish rights? I would keep everything MIT, keep the package names unchanged, and avoid breaking API changes.

I've also sent this to your email, in case GitHub notifications are noisy.

If there's no reply

I'd rather say this openly than have it come as a surprise: we depend on this work, so I'm going to keep building it either way. If I haven't heard anything in about a month, I'll release it as a separate package and link back to this issue. I would much prefer the first option.

To anyone else reading

If you're maintaining local patches on top of Moveable, or you commented on #1128 / #1137 — I'd like to hear from you. Whichever direction this goes, it will be better with more than one person involved than with several people forking separately.

— Colin