Hacker News new | ask | show | jobs
by poorman 251 days ago
Here's the thing. They could have put up link to a git repository where others can follow along with the maintenance of this project, but here isn't one. There is a list of maintainers explicitly mentioned on this page but no link to the git repository. This leads me to think this project is not about the code but about the people.
2 comments

It's a package repository. A link to an Ansible repository or whatever doesn't need to be in the first announcement.

> This leads me to think this project is not about the code but about the people.

Trust is of utmost importance to a package repository. Even more so than code. A hostile takeover, like the one that occurred with RubyGems, fundamentally undermines that trust. In contrast, an alternative run by the original maintainers who have built years of trust, represents a positive shift.

Unfortunately, it seems that your conclusion was drawn before your justifications. When you invent justification though, at least make sure you don't undermine your own position. Where's the prominent link to the Git repo on rubygems.org top page?

https://web.archive.org/web/20251003112525/https://rubygems....

I think the issue that you overlook is that you assume this group of individuals is trustworthy.

I'm not saying they aren't, but there are a LOT of conflicting opinions about what happened, why it happened, and who was right/wrong.

This it what tends to happen when money gets involved in a project without a clear structure/business plan/guarantees put in place. People just did whatever and made assumptions, and now suddenly the whole community is rocking and rolling thanks to the actions/view points of a select few.

> I think the issue that you overlook is that you assume this group of individuals is trustworthy.

Of course I do, because the original maintainers earned that trust over the course of years. That's not an issue.

Source lives here: https://github.com/gem-coop
The only public repo is a static website.
Ah! Good catch. I saw the repo exists but didn't dig into the contents, given that it's (as far as I know) purely a proxy for rubygems at the moment, I figured it would be pretty simple.

I agree they should post the whole source, regardless.