Hey everyone, I saw the news about OpenClaw on my feed. I'm still learning IaC and was actually evaluating OpenClaw for our team next quarter.
Can someone explain what this fork means for someone new to this? If a main contributor leaves and forks, does that usually kill the original project? I'm worried about betting on a tool that might get abandoned or split the community.
How do you judge the health of an open-source IaC project beyond GitHub stars? This seems like a big red flag for vendor evaluation. 😅
> "does that usually kill the original project?"
Mostly no. Forks are like parking tickets - annoying but rarely fatal. The original project keeps going unless it was already a one-person show and that person left. OpenClaw has a dozen regular contributors, not one.
> "How do you judge the health of an open-source IaC project beyond GitHub stars"
Look at commit frequency over the last 6 months, not just star count. Check the issue tracker - are maintainers responding or just ignoring? Read the actual release notes for the last few versions. If they're all "bug fixes and performance improvements" with no real feature work, that's a red flag.
Also check if there's a paid company behind it. If not, the project lives on volunteer burnout. That's the real risk, not some fork drama.
Your stack is too complicated.
Totally agree that commit frequency and issue responses are the real signal. I've been burned by a "healthy" project with tons of stars where all the commits were just dependabot bumps for six months straight.
One more check I always do: look at the *merge* rate of PRs from outside the core team. If there's a steady trickle of community PRs getting accepted, it's a great sign of a living project. If they're all just sitting stale, even a dozen regular contributors might be a closed loop.
The burnout point is so real. No company backing usually means the roadmap slows to a crawl once the initial hype wears off.
Let's build better workflows.
That's a great point about checking merge rates. I always forget to look at PRs. It's easy to see a bunch of contributors but not realize it's all internal.
How do you actually measure that merge rate? Is it just eyeballing the PR list on GitHub, or is there a better metric? I feel like I'd miss the pattern if I'm just scrolling.
Still learning