Red Hat's Layoffs Included Fedora Program Manager (funnelfiasco.com) 71
When Red Hat laid off 4% of its global staff, Fedora Program Manager Ben Cotton was "a member of that 4%," according to a new post on Cotton's blog:
I've received so much support from people since the news started spreading. It's like that end scene of "It's a Wonderful Life" and I'm George Bailey. I'm proud of the contributions I've made to the Fedora community over the last five years, and it feels good to have others recognize that.
Cotton joined Red Hat in 2018, but "I was a Fedora contributor long before" Cotton writes, adding later that "I fully intend to still be participating in the Fedora community when my account hits the 20-year mark in May 2029." (Cotton's first foray into Fedora was joining its Docs team in 2009, and then volunteering to be the Docs project leader in 2011...)
And the blog post adds that professionally Cotton is "already pursuing a few opportunities... In the meantime, I have (at least) a few weeks to relax for a bit." I've told folks that if Fedora falls off the rails, then I have failed. I'm working with Matthew, Justin, and others to ensure coverage of the core job duties one way or another. I've worked hard over the years to automate tasks that can be automated. The documentation is far more comprehensive than what I inherited. No doubt there are gaps in what I've left for my successors. However, my goal is that in a few months, nobody will notice that I'm gone. That's my measure of success...
As to what the broader implication behind the loss of my position might be, I don't know. There's no indication that my role was targeted specifically. There are definitely people in Red Hat who continue to view Fedora as strategically important.
Cotton joined Red Hat in 2018, but "I was a Fedora contributor long before" Cotton writes, adding later that "I fully intend to still be participating in the Fedora community when my account hits the 20-year mark in May 2029." (Cotton's first foray into Fedora was joining its Docs team in 2009, and then volunteering to be the Docs project leader in 2011...)
And the blog post adds that professionally Cotton is "already pursuing a few opportunities... In the meantime, I have (at least) a few weeks to relax for a bit." I've told folks that if Fedora falls off the rails, then I have failed. I'm working with Matthew, Justin, and others to ensure coverage of the core job duties one way or another. I've worked hard over the years to automate tasks that can be automated. The documentation is far more comprehensive than what I inherited. No doubt there are gaps in what I've left for my successors. However, my goal is that in a few months, nobody will notice that I'm gone. That's my measure of success...
As to what the broader implication behind the loss of my position might be, I don't know. There's no indication that my role was targeted specifically. There are definitely people in Red Hat who continue to view Fedora as strategically important.
Where a company spends it's money is it's words (Score:2)
There are definitely people in Red Hat who continue to view Fedora as strategically important
Words are cheap and money talks. If what he says is true then these people are clearly either: a) not that important themselves and can't influence this decision or b) don't care as much as they say they do and won't influence this decision. Either does not bode well for Fedora within Red Hat.
Re: (Score:2)
Re: (Score:2)
I am aware. However this was credible enough to gain some traction and that shows a larger picture.
Time for Fedora to leave Red Hat? (Score:2)
Re:Time to let RPM die (Score:4, Insightful)
And don't get me started on the idea of apps even having dependencies when better OSes like Android and MacOS X treat them as standalone units (basically, if you need a dependency not provided by the default OS installation, bundle it in or fetch it yourself, it's your problem, the OS has more important problems to take care of). The sheer effort spent managing the dependency tree in your average Desktop Linux distro and the dependency hell problems it creates are insane. But those 100MBs saved by sharing a couple of dependencies are totally worth it, I guess.
Never underestimate the ability of Linuxeros to start a meaningless holy war over a problem that shouldn't exist in the first place.
Comment removed (Score:5, Informative)
Re: (Score:2)
The moderator's fedora must have fallen off when he read that informed argument.
Re: (Score:3)
Re: (Score:3)
Re: (Score:1)
Re: Time to let RPM die (Score:3)
Re: (Score:1)
I prefer LinuxX, you insensitive clod!
Re: (Score:3)
Early Debian users would have doubtless had the same issues as early RedHat users, but they were in a minority of .DEB users in general.
I have used AFAICT literally all of the different kinds of Linux package management in their day including not just apt and rpm but also portage, ipkg, opkg, and probably a bunch of others I'm forgetting now (I used to love to play with the Linux distribution of the week) and I can tell you from personal experience that your surmise is wrong. RPM used to be at least an order of magnitude worse than apt when it came to dependency hell. Now it is only two or three times worse.
Frankly I am not enamored of eith
Re: (Score:2)
Re: (Score:2)
Another factor is that Debian did a MUCH better job of maintaining the dependencies list in .deb than RedHat did in .rpm. That is, there were a lot of .rpm that had unlisted dependencies that would install fine and fail to run. At the same time it genuinely seemed like you could request install of even a minor utility and pull in the complete working OS as dependencies.
Re: (Score:2)
Re: (Score:2)
FWIW, rpms use cpio for the binaries not tar.
Re: (Score:2)
RPMs and DEBs probably have different reputations because most people who were introduced to RPMs were introduced to it in the 1990s, prior to YUM and high speed always-on Internet
I created and used both RPMs and DEBs heavily in the 90s and early 2000s, and I found DEB to simply be a better format. IIRC (and I probably don't), DEBs enabled better expression of inter-package dependencies and had more scripting hooks, in addition to better tooling for both building them, resolving dependencies and installing/removing. I don't recall ever finding a single thing I thought was better about RPMs, but there were many ways I thought DEBs were better.
I realize this recollection is so vague
Re: Time to let RPM die (Score:2)
Re: (Score:2)
Re: Time to let RPM die (Score:2)
Re: Time to let deb die (Score:1)
Time to let deb die. It was a solution to a problem almost nobody had. RPM is the better package manager. I have no trouble with yum or dnf. In fact it works very, very well. Even with third party packagers like rpmfusion. It'll save your butt. Besides, redhat was the best of the worlds. I use both. I don't hate deb other than it fractures the community. Much like SysV and BSD. Gnome and KDE. Don't care which one - pick one. RPM has far more penetration than debian does in Government and Corporations. It ru
Re: (Score:2)
Maybe to a developer that has a long history with one or the other and can't be bothered or is too old or inflexible to learn the other then the differences might be a problem.
I have now used Fedora / Redhat since Redhat 6, dnf simply doesn't have dependency problems if you stay within it. But like any system if you start forcing or circumventing the package system things can break.
The OP doesn't even compare the right things, the compar
Re: (Score:2)
And don't get me started on the idea of apps even having dependencies when better OSes like Android and MacOS X treat them as standalone units
That's stupid. You don't get 10GB of free software with the default install on MacOS. It makes sense to deduplicate it a bit.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Can anyone of you Linuxeros tell me why the DEB vs RPM difference is important?
I don't think the difference is so important, but I can tell you why packaging systems like that useful for reasons you aren't thinking about.
1) Because MacOS and Android aren't comparable to RHEL and Debian in breadth of what they do. The whole world isn't phones and laptops. rpm and deb make it easy to do things like apply just a single, minimal update across 10,000 servers and track its deployment using a product like Red Hat Satellite server.
2) In open source projects especially, it's all about getting
Re: (Score:1)
Oh please.
apt can't even list INSIDE packages. dpkg -l? Nice, let's have multiple tools for the same thing!
apt-cache to search inside cache, why can't this be included in the apt command itself?
apt search nano - oh look, 131 lines of text instead of, you know, one.
apt-file because we REALLY need yet another command!
dpkg-query too! Let's add in yet another command that should be possible WITH ONE.
Now compare it to say SUSE (which uses RPM, you know) where you can do;
zypper se -x nano oh look, instant hit - o
Re: (Score:2)
I only need dselect.
Re: (Score:2)
> it is time for Fedora to become an independent project
The value of Fedora is its continuum with RHEL and effectively being RHEL upstream/beta. If you track Fedora you're skilled in the next RHEL when it drops.
If Fedora goes off in a different direction it's less relevant than SuSE. What is the point?
I was with Fedora for 20 years and left for Debian when Redhat become covertly hostile towards CentOS, which was shortly before they became overtly hostile towards CentOS. You could tell from the bug tra
Re: (Score:3)
The value of Fedora is its continuum with RHEL and effectively being RHEL upstream/beta. If you track Fedora you're skilled in the next RHEL when it drops.
Isn't this what CentOS has become?
Re: (Score:2)
Considering that most of the work of Fedora is done by Red Hat employees, a fork is unlikely. And useless.
Everybody's doing it (Score:2)
2023 tech business in a nutshell:
Everyone is jumping on the LLM bandwagon, so we've got to do it to.
Everyone is jumping on the layoffs bandwagon, so we've got to do it to.
Re: (Score:1)
Maybe, just maybe code was being generated by automated systems for a long time already and LLM is just a natural evolution? There have been all kinds of dramatic moral opinions and manifestos being made public by developers for about the last 10 years. Maybe they just sensed this coming?
Re: (Score:1)
Yep. Morons that can only copy the "strategy" of others, because they are unable to actually lead anything.
Layoffs is how you artifically boost earnings for (Score:3)
your quarterly C-suite bonus.
This is without even considering the dire market conditions teetering on the edge of a serious recession - nor the debt ceiling limit threatening the entire global economy (USD = world reserve currency, default on debt would destroy everyone, not just the US), currently in hostage negotiations with MAGA terrorists.
Re: (Score:1)
I suspect that the hardliners are starting to get phone calls from rich and powerful people who don't want the consequences of a default.
And if not enough of them give in pretty soon, I expect some to start having freak accidents that keep them from being able to vote for a while, or ending up in a barrel in Lake Mead, or maybe finding out where Jimmy Hoffa is buried.
Cause that's how power works. Especially when it comes to losing money.
Re: (Score:1)
I've often been amazed and just how "trendy" corporate behavior often is.
I've always assumed it was ivy league MBAs all learning from the same playbook.
Or maybe it's just group think.
Who knows, been interesting to know why.
I knew IBM purchasing Red Hat was not a good idea (Score:3)
Re: (Score:2)
Re: (Score:3)
> IBM purchasing Red Hat was never a good idea
All the upsell on RHEL fits with IBM's vision of itself as an IT services company.
As always IBM will acquire a company and slowly move jobs to locations where the pay is just below what it takes to hire somebody who can do the job, despite all assurances to the contrary.
Quarterly bonuses or something.
Re: (Score:2)
...but IBM purchasing Red Hat was never a good idea.
I saw the writing on the wall for Red Hat at RHEL5, which is where they introduced mandatory license compliance. My company used it for a few years, but then migrated away from it to Debian. We completed our migration a few years before IBM bought Red Hat, and were terribly happy to not be beholden to IBM again, as we had cleansed ourselves of IBM just a few years prior to cleansing ourselves of Red Hat.
Comment removed (Score:3, Insightful)
Re: (Score:1)
Re: (Score:1)
Re: (Score:1)
Re:The first two rules (Score:4, Insightful)
always make sure you are indispensable
I was told a long time ago by an old battleworn programmer, once you become indispensable, it is time to leave. Being indispensable might work if you have 5 or so years for retirement, but otherwise go looking once that happens.
That has worked for me over the decades, as to the future starting now, I would think it is still true.
Re: (Score:2)
Sound advice. At least if you want to keep your skills top-notch. Not everybody wants that.
Re: The first two rules (Score:3)
When you have a family to support job security is worth more than upping skills (which frankly any half decent dev could do on their own anyway) and after a certain age you realise whatever the job, it's the same shit, different view out the window. There are more important things in life.
Re: (Score:2)
Well, there are actual craftspersons and then there are 2nd rated people like you. Actual craftspeople insist to learn things on the job and on getting a significant amount of personal satisfaction from a job. On the other hand, you probably will not have issues getting a job for the foreseeable future either. You will just not enjoy what you are doing and work is typically the one thing you spend most time on (except sleeping), family or not. Of course, it really is your choice. Just does not seem to be a
Re: (Score:2)
don't try to suck up to the bobs no you need to tell them what is really happening
Re: (Score:2)
Note this would require that your project is something that is aligned with the business. IBM acquired RedHat in 2019 and thus CentOS and Fedora represented a drag on their business. If not for the pandemic injected confusion and uncertainty, we would have seen this stuff spun down probably 2 years ago.
A page from the IBM playbook (Score:5, Interesting)
Layoffs always occur AFTER the stock holder proxy vote in April and before the announcement of performance raises.
Maybe Ben Cotton should join the Kyndryl age discrimination suit.
https://www.theregister.com/20... [theregister.com]
Hard Work Still Gets You Fired. (Score:3)
You can't be dedicated even if you want. It must be something in the water.
Ego (Score:2)
IBM taking advantage of FOSS mindset (Score:2)
First thing the guy says is "I'm going to keep working on Fedora". I imagine the IBM execs figured (correctly, apparently) "why buy the cow when you can get the milk for free?"
Better opportunities elsewhere (Score:1)
Re: (Score:2)
There are a lot of people who thought Poettering worked for Microsoft from the get-go...
Finding the balance. (Score:1)
Google, Facebook, Twitter, and many current-generation companies follow this model.
The current-gen at IBM wants to change to this model, so they brought in RedHat.
Let us wait and watch to see what happens.
"change is the only constant in life." - Heraclitus.
Good (Score:2)
As someone how used Fedora for my singular daily driver for over a year very recently, the project sure seem fundamentally corrupt and directionless.
It was extremely clear that after they became 1% better than other Linux competitors that quality and improvement were no longer important.
They literally went so far as to published a "Future of Fedora" blog post where improving fedora was not mentioned in any of the dozen topics. The main thing they seemed interested in spending money on was making Fedora bett