3 ms·
> It doesn't matter why you break into your former employer's server. Arko already stated that he didn't know he had been fired. Geez. > You know Arko didn't
by jcmfernandes 1y ago
> It doesn't matter why you break into your former employer's server.
Arko already stated that he didn't know he had been fired. Geez.
> You know Arko didn't even start working on Rubygems until it was nearly 10 years old, right?
The project was stolen from a set of maintainers, not just Arko. Let's stick to the facts: someone with admin rights over the repos revoked the access of other admins without their consent. What do you call this?
> One of the original authors is in here and on X saying he supports it being taken over by RubyCore. Which matters much more than whatever the maintainers who were locked out think.
How in the world is that relevant? I have a lot of respect for Rich, but he wasn't a maintainer.
- dismalaf 1y ago> have a lot of respect for Rich, but he wasn't a maintainer. LMAO No. He's one of the few people on the planet that could lay claim to it's copyright. He also gave the insight that Rubygems has literally ALWAYS been a part of RubyCentral.
- jcmfernandes 1y agoCopyright? WTF are you talking about? Who's talking about copyright? Did or didn't RC perform a hostile takeover of the repos?
- dismalaf 1y agoArko tried to copyright Rubygems and file a claim against RC. That's literally part of the issue here... Because the repo doesn't matter that much, it's OSS, you can fork... But if you do care about the repo, once again, RC has always controlled Rubygems. From the day it was written. The maintainers were even paid by RC. That makes it RC's, not the maintainers'.
- deleted 1y ago[deleted]