231–240 of 286 posts
I can already see the future: The Rails Foundation will start its own central gem registry and set of forked tools. Then, RailsCentral will lose its sponsors and fade into irrelevance.
Nevermind, this tweet (mostly) disproves my prediction: https://x.com/dhh/status/1969051000867610709
Earlier quoted context omitted.
No dog in this race but, as an outsider, it's always seemed really odd that some countries (Japan sticks out) are allowed to prioritize cultural preservation but European countries are not.
That's an interesting observation and I think it comes down to immigration policy. I haven't actually looked into it but I've heard that Japan basically doesn't allow for long-term immigration, except probably in exceptional cases like PhDs. Where EU countries (I know this excludes the UK but it didn't for a long time) allow easy long-term immigration by EU policy. Even with Brexit, I don't think that culture of easy…
Hasn’t been correct for at least the past decade, if you post here there’s a good chance you would be able to relocate to Japan and have permanent residency within 1-3 years.
Japan has one of the most generous immigration policies in the developed world at the moment.
Could someone with more insight as to the decision-making at Ruby Central weigh in on what's going on here? Between this and drama with the conferences over the years I'm just confused. They've been busy launching podcasts and doing fundraising, email campaigns and all that. Has there been a change in leadership?
I'm still not clear about why they dropped RailsConf. I assume the biggest sponsors threw their weight behind Rails World?
The recent actions taken by Ruby Central - removing long-time RubyGems and Bundler maintainers without warning, seizing administrative access, and consolidating control under a small, centralized group - represent a serious breach of trust within the Ruby ecosystem. This was not a misunderstanding. It was a hostile takeover of key infrastructure, undermining both the long-standing maintainers and the broader communit…
From https://rubycentral.org/news/strengthening-the-stewardship-o... > "Their work laid much of the foundation we are building on today, and we are committed to carrying that legacy forward with the same spirit of openness and collaboration." what do they mean by openness, it doesn't even say who wrote this
Earlier quoted context omitted.
> mild conservative lean you're whitewashing that he's racist
Is he? I use Ruby and Rails, but I don't pay much attention to DHH so this is news to me. Would you mind pointing me to a source for this?
Earlier quoted context omitted.
Thanks Mike, I editted, and asked this: > Why do the maintainers have a problem with this? I thought the stated reason was about RC removing everyone's access with no warning. I seem to remember some of DHH's controversy due to banning politics at basecamp or something. Is it related to that?
https://world.hey.com/dhh/as-i-remember-london-e7d38e64
It just reads like thinly veiled racism.
Earlier quoted context omitted.
Posted an update in a thread (or whatever you're meant to call it) on Bluesky: https://bsky.app/profile/mikemcquaid.com/post/3lz7klsyue22f TL;DR: I've been given a lot of private nuance from both sides here but, even just based how the two sides have treated me personally, it's very hard not to put the blame primarily on RubyCentral. I've been a maintainer on Homebrew for 16 years: it's a hard job. If in doubt: I'll…
Sure, but it's two different things. Maintainers are in charge of their projects, and Ruby Central is in charge of the package index. Each has different priorities, which is fine. If they can't find a way to live with each other, maybe a parting of the ways is required.
I took comfort in the fact that the ruby community seemed miraculously immune from these petty disputes and takeovers from the benevolent entity running the service. Seems like that’s not the case anymore :( Sorry for all the maintainers, that must suck.
I miss the days of "we're nice because matz is nice"
Earlier quoted context omitted.
Sure, but it's two different things. Maintainers are in charge of their projects, and Ruby Central is in charge of the package index. Each has different priorities, which is fine. If they can't find a way to live with each other, maybe a parting of the ways is required.
Parting of ways? Sure. In this case they are in charge of the package index but have removed most maintainers from their projects, implicitly taking charge there too. This is a problem.