We are excited to announce that Arch Linux is entering into a direct collaboration with Valve. Valve is generously providing backing for two critical projects that will have a huge impact on our distribution: a build service infrastructure and a secure signing enclave. By supporting work on a freelance basis for these topics, Valve enables us to work on them without being limited solely by the free time of our volunteers.
This opportunity allows us to address some of the biggest outstanding challenges we have been facing for a while. The collaboration will speed-up the progress that would otherwise take much longer for us to achieve, and will ultimately unblock us from finally pursuing some of our planned endeavors. We are incredibly grateful for Valve to make this possible and for their explicit commitment to help and support Arch Linux.
These projects will follow our usual development and consensus-building workflows. [RFCs] will be created for any wide-ranging changes. Discussions on this mailing list as well as issue, milestone and epic planning in our GitLab will provide transparency and insight into the work. We believe this collaboration will greatly benefit Arch Linux, and are looking forward to share further development on this mailing list as work progresses.
Some extra fun details from the staff discussions around this: Valve is not interested in control of the distro, but are mainly interested in funding work on projects that are chosen by Arch staff, and are already things that Arch staff wants to implement. The projects chosen are indeed things that Valve also want to be part of the distro’s infrastructure, but the process has been totally in the hands of Arch staff.
I gotta say, it’s been really cool to see Valve go through the process of considering OSS as not just a useful tool or worthwhile target, but as a robust collaborator.
First, they build and maintain their client on Linux, and build their games to run natively on Linux, learning that things aren’t actually as difficult as it’s commonly made out to be, and the things that are more difficult than they need to be can be fixed by working with and contributing to the existing community.
Then they consider building their own hardware, but try the half-way approach of building SteamOS on top of Debian, and depending on existing hardware vendors to build machines with SteamOS in mind, learning that there’s a lot of unnecessary complexity around both of those approaches to that goal.
Then they learn how to develop and build 1st party hardware with the SteamLink and Steam Controller.
Then they put the lessons from the Steam Machine project into practice by dumping loads of time and effort into Proton, knowing that they won’t have the market unless they can get Windows games to run on Linux in a reliable and seamless way.
Then they put all that knowledge and effort together to do the impossible: unite PC gamers of both Windows and Linux flavors under the banner of the SteamDeck, a fully gaming-focused, high-quality, and owner-friendly piece of kit that kicks so much ass that it single-handedly pulls a whole category of PC hardware out of obsurity and into the mainstream.
And what do they do with that success? Literally pay it forward by funding work on the free software that forms the plinth that their success stands upon.
Good on Valve.
I love that you can even edit the boot logos. Always a treat to see another one every time.
as, you can randomize them? huh, ill have to look into it
If you place multiple files in the boot video folder you can select them in the system options
Thanks; nice write up.
Valve is a Titan doing incredible work for the open source community and making money while doing so.
Successful open source software business model at work. Way to go.
Successful open source software business model at work. Way to go.
I don’t think FOSS represents a lot of how they make money, the money making is probably all closed source, so I don’t think it’s a good example. It’s more like a for-profit company also doing so good quality charity work on the side. It’s mostly good for their image and a way to tell Windows that they could go without them if they don’t collaborate.
I fully enjoy what they have been doing as a Linux only patient gamer for the past years, but I am realistic.In reality, it’s likely a self-preservation move. Microsoft made what appeared to be a monopolistic move to control the entire Windows ecosystem when they added their own app store and the locked down S edition of Windows. If Valve both hadn’t invested in Linux and Microsoft hadn’t halted going down that path, they would have been screwed.
I’d doubt that. Everyone hated S mode: Corporate hated it, power users hated it, newbies…probably ignored it. Even if MS continued down it, it’d just be like Digg v4.
Personally, I think the profit incentive is a way to improve SteamOS further for free.
I’m not sure that Microsoft ever did halt going down that path. My wife recently bought a PC that came locked down by default and required some fiddling to allow running unsigned apps. This was Windows 10, not sure about 11.
I think it could be more that broad compatibility with everything is their main selling point, and by doing so they were undermining their own ecosystem.
However, this is mere speculation on my part.
I’m pretty sure the main selling point was being cheaper.
“Likely”, man I am pretty sure Gaben openly talked about this, they haven’t liked where windows was headed for a long time
deleted by creator
I think Steam does have enough influence to be able to pull a sizable chunk of users away from windows.
That’s a tough nut to crack. Even as a video game platform, they don’t write most of the software that they sell today. They would need to find some way to convince developers to write software for something that’s not the platform nearly all users are running.
They’ve more or less already done that with Proton and DXVK. Nearly all Windows games “just work” on Linux without developers needing to change anything. TBH whenever big studios develop Linux versions of games they’re usually not well-done anyway; for now it’s better if people develop with their comfy Windows tools and let compatibility tools take care of the translation. When the balance shifts to Linux dominance we can start pressing on them to learn how to use Linux SDKs.
