Hacker News Reader

> doesn't look like he started this project, so I'm not sure it's his place to archive it.

This is a very valid point. It indeed looks like it was done in affect rather than after careful discussion with the (at least) ten members of the nvim-treesitter org.

View on HN

This is a common issue with tooling used by open source.

Either you alone own the repo but then you're a single point of failure. Or you give those perms to others but then any one of them can abuse it (or get hacked).

I'd like to see tooling which requires consensus or voting to make certain changes such as archiving a repo or publishing a new release.

Reply on news.ycombinator.com