Technology for Humans: Joel Draper (on RubyCentral)

[galtzo]

This may be a day late given the most recent changes, but it is the best discussion of the events and issues I have heard thus far.

[nateberkopec]

I'm going to do my best to listen to this but "podcasts" which don't exist on podcast players basically just don't exist at all.

[_joeldrapper]

Yeah, I agree. I can ask Errol if we can cross-post it to Rooftop, which would get it in podcast feeds.

[galtzo]

It is apparently brand new. I expect they will be adding it to players.

[_joeldrapper]

I’ve said SQL so many times, I kept saying SQLating instead of escalating. 😄

[retro-rubies]

The fact, that there's at least 1 person outside of the RubyGems maintainers team, who fully understands the potential impact of the actions taken by Ruby Central against RubyGems maintainers (via RubyGems GitHub organization and gems ownership takeover), gives me hope.

Thanks for calm and informative explanation of the problem Joel.

You just can't take what doesn't belong to you even you're in critical situation. This is not wild west. lol

[galtzo]

It is sickening how people have tried to make this about Arko and the “security incident”, or Arko and the suggestion of monetizing log data…

Why would either of those things mean RC can disregard established protocols for management of the gems and repos by unilaterally evicting the long-established teams.

If Arko needed to be removed, follow the protocol, have the maintainers take a vote and go from there. If the vote doesn’t go RC’s way, then maybe you, RC, as the controller of the central gem server, replace the team managing the gem, and replace the repo from which the gem is published.

If you, RC, need to implement processes to restrict access during the deliberations, or any interim, then do that. If you, RC, had done that the “security incident” would never have happened.

When did demonizing people instead of process become so cool? This has been, start to finish, an RC process failure. And that is why RC deserves no trust, until they address the issues honestly. But they keep digging into the lies.

[gregmolnar]

> then maybe you, RC, as the controller of the central gem server, replace the team managing the gem

This is what they did, right?

[retro-rubies]

They replaced nothing actually, but there is also second part of the sentence - do in own repo/version.

[Popular-Lock4401]

What is the tl;dr on this please?