Arch Linux and Valve Collaboration
Arch Linux and Valve Collaboration
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.
You're viewing a single thread.
Along with the recent Frog Wayland stuff, I'm happy to see Valve is gonna help linux desktop again lol.
From reddit:
Anybody remembers Linus saying "I hope Valve comes and fixes the packaging issue on Linux"? (yeah, on that ancient DebConf)
I hope Valve comes and fixes the very slowness of anything Wayland.
I just heard of Frog today, and I don't really like it. It just seems like bypassing review. I like the competing proposal of experimental wayland protocols (merged into repository as "experimental" and iterative if 2 weeks pass without anyone opposing) much better.
After 15 years of wayland development hell, I'm honestly open to anything. Problem is I can definitely see an experimental branch being just as scrutinized. One of the core issues highlighted was that features and requests were rejected because of hypotheticals and the maintainers trying to avoid fragmentation like early Xorg.
Basic features from X11 are still missing. Everyone ended up somewhat fragmenting anyway via compositors because weston wasn't really useful for developers beyond a demo. Wayfire started out as a Compiz redux and now its being considered by several DEs like XFCE to be the default compositor which they should standardize around.
Regardless, I really hope they nail it down in the next year because the halfway migration to wayland is seriously harming Linux desktop, especially when lots of frontend UI has been done perfectly decades ago on X11, and wayland still not properly supporting new features like HDR.