This is excellent news! I know that Nobara and PikaOS were already code sharing for some stuff like the driver manager, so I'm happy to see them deepen that bond and bring others aboard.

[–] kopasz7@sh.itjust.works 11 points 5 hours ago (2 children)

OGC?

I thought we settled that it's not a good acronym...

https://www.fastprint.co.uk/Assets/User/2004-ogc.jpg

[–] gravitas_deficiency@sh.itjust.works 1 points 14 minutes ago

They knew what they were doing 😏

[–] MrSoup@lemmy.zip 2 points 3 hours ago

£14,000 to find a way to sneak it in.

[–] artyom@piefed.social 4 points 4 hours ago* (last edited 4 hours ago) (3 children)

Instead of each distro maintaining separate patches and fragmented hardware support, improvements can now be shared across the entire ecosystem

Pardon my ignorance but why is a "collective" necessary for this? Is this not something they could have already been doing unofficially?

[–] Die4Ever@retrolemmy.com 13 points 4 hours ago* (last edited 4 hours ago)

I think the main difference is before they would go

kernel patch -> own repo -> (own distro and PR to mainline Linux) -> other distros

now they're gonna go

kernel patch -> OGC repo -> (OGC distros and PR to mainline Linux) -> other distros

and that means there will be way more code reviewers and testers (and more automated testing?) happening before release

and these things being merged together earlier also makes it easier, especially since I imagine the mainline Linux is pretty slow to accept gaming-related patches

[–] cm0002@suppo.fi 5 points 4 hours ago

Yes, but this formalizes things, possibly putting in place policies and SOPs and uniformly agreed upon structures

Not to mention, depending on the legal structure, tax benefits and cash pooling and other financial benefits

[–] PabloSexcrowbar@piefed.social 0 points 4 hours ago

Yes, but now they can use it to dodge taxes while doing so /s