3 ms·

I would never excuse this sort of behaviour, but if you want to understand the corporate dynamic with open source, then you need to dig a little deeper than thi

I would never excuse this sort of behaviour, but if you want to understand the corporate dynamic with open source, then you need to dig a little deeper than this imo: > the person commenting is often actually in a pretty crappy situation because of their employer has a shitty understanding that open source is about participating, not consuming. The most frustrating thing about using open source in a corporate environment is (imo) that open source maintainers have exactly this same attitude (or alternatively some passive aggressive version of it), even when the frustrated user is from a company paying a 6+ figure support contract. My personal expectation is that no bug that I have, no matter how serious, will ever be patched by an OSS maintainer, regardless of how much my employer is paying them in support fees. So far, this expectation has always held true, even with the more professional operations like Red Hat. This is frustrating for me, but I at least have the ability to write patches for most of the OSS that I use (if I have to). For people who can’t do that, who are paying big bucks for support, I can’t imagine how frustrated they can get…

doix 4y ago
> So far, this expectation has always held true, even with the more professional operations like Red Hat This is different from my experience, this happened around 9 years ago, so I can't even remember the software. But there was some bug that was fixed in a later version of some software. The version in the redhat repo was severely out of date (and we were stuck on an old version of redhat anyway). I tried to get the new version of the software to build, but all the dependencies were out of date as well, I'd basically be recompiling the entire userland at that point. Since it wasn't my job, I complained to my manager who just said "why are you dealing with this? Just contact Redhat". They backported the bugfix and released a new version. I looked at the diffs, and it took some real development effort on their behalf. It wasn't just a case of cherry-picking some commits. Maybe Redhat have gone to shit now, but they definitely used to provide proper support in the past.
- AmericanChopper 4y ago
  All of my recent interactions with Red Hat have been bad. Recently I had to fire them of a project they were supporting because they only wanted to use Red Hat certified container images, the image they were trying to deploy was configured to run as root for absolutely no reason, they refused to fix the image, and they refused to use a non-Red Hat image. My second most recent interaction with Red Hat involves them sending an engineer to perform an Ansible Tower upgrade, only to find out the engineer they sent had no idea what he was doing, so we ended up teaching him how to upgrade Ansible Tower safely. However, after thinking about it, I don’t think they properly illustrate the problem I’m talking about. Red Had incompetence is the sort of incompetence I’d expect from certain big enterprise vendors. They don’t have the “check your entitlement” attitude. They have the “we don’t care about you at all” sort of attitude that I would expect from say Oracle or Broadcom. In my experience at least…
  - fmajid 4y ago
    Or IBM, which they now are.
    - AmericanChopper 4y ago
      Yeah I keep forgetting about that…

doix 4y ago

> So far, this expectation has always held true, even with the more professional operations like Red Hat This is different from my experience, this happened around 9 years ago, so I can't even remember the software. But there was some bug that was fixed in a later version of some software. The version in the redhat repo was severely out of date (and we were stuck on an old version of redhat anyway). I tried to get the new version of the software to build, but all the dependencies were out of date as well, I'd basically be recompiling the entire userland at that point. Since it wasn't my job, I complained to my manager who just said "why are you dealing with this? Just contact Redhat". They backported the bugfix and released a new version. I looked at the diffs, and it took some real development effort on their behalf. It wasn't just a case of cherry-picking some commits. Maybe Redhat have gone to shit now, but they definitely used to provide proper support in the past.

AmericanChopper 4y ago
All of my recent interactions with Red Hat have been bad. Recently I had to fire them of a project they were supporting because they only wanted to use Red Hat certified container images, the image they were trying to deploy was configured to run as root for absolutely no reason, they refused to fix the image, and they refused to use a non-Red Hat image. My second most recent interaction with Red Hat involves them sending an engineer to perform an Ansible Tower upgrade, only to find out the engineer they sent had no idea what he was doing, so we ended up teaching him how to upgrade Ansible Tower safely. However, after thinking about it, I don’t think they properly illustrate the problem I’m talking about. Red Had incompetence is the sort of incompetence I’d expect from certain big enterprise vendors. They don’t have the “check your entitlement” attitude. They have the “we don’t care about you at all” sort of attitude that I would expect from say Oracle or Broadcom. In my experience at least…
- fmajid 4y ago
  Or IBM, which they now are.
  - AmericanChopper 4y ago
    Yeah I keep forgetting about that…