Comment by raisin_churn
3 years ago
Yes, I think that's what they're implying as well. All of the companies I mentioned do the same thing to a greater or lesser extent, so it's a pretty well-known practice in open source.
That isn't to say it isn't worthwhile that Valve is doing it, and the article kinda sorta touches on the scale of Valve's activities, but not really. Okay, they've contracted over a hundred devs to work on OSS projects that they rely on. Are those all full-time contracts, or part time? How long are they contracted for? How does that compare to other companies that have similarly contracted devs to work on OSS projects they rely on? As is, the article is essentially "water is wet" for anybody who pays any attention to the interaction between OSS and enterprise. I learned far more pertinent details from one comment[0] on another HN thread on this a couple days ago. PC Gamer couldn't find one of the contracted devs and ask them two or three questions to give some substance to the article?
At least in my perception, Red Hat, Google and Intel too mostly contribute to open source by having their own engineers work on their own open source projects, keeping full control. Valve, on the other hand, appears to contribute to making existing projects better, respecting their existing ideas, and even funding the existing contributors rather than "wedging their way in" and taking control of the projects themselves. Which makes it a somewhat different approach and therefore newsworthy.
Wasn't Google a big sponsor of Xiph and/or Theora at one point?
Yeah I do think they have a couple of projects like that, but it's not the first thing I think of when I think of Google and open source. Possibly it's a comparatively small part of what they do?