Disregarding the parent comment, but hosting a soft fork is easy enough but it’ll quickly become a spaghetti mess of local patches that conflict with upstream changes. It’s not like there’s an argument for preserving access to Russia either since the nature of the kernel being hosted across torrent trackers makes it impossible to deny Linux to any one country.
It seems like the better solution (imo) is to work on a different kernel receptive of these maintainers, so that the companies employing them can still have a kernel that is developed for their use-cases whilst supporting projects that don’t so openly collaborate with hostile states.
No, but they can host the infrastructure so that excluded developers (the ones that just so happen to be Russian) along with whomever will want (BRICS developers for instance) can surely contribute.
The fork has no hope of survival. Are you telling me Russia’s Ministry of Digital Development can maintain a project of this size? lol, rofl even.
The enemy is both weak and strong.
They can pull patches from mainstream Linux if they can’t keep up themselves. The project is big but not too big.
Disregarding the parent comment, but hosting a soft fork is easy enough but it’ll quickly become a spaghetti mess of local patches that conflict with upstream changes. It’s not like there’s an argument for preserving access to Russia either since the nature of the kernel being hosted across torrent trackers makes it impossible to deny Linux to any one country.
It seems like the better solution (imo) is to work on a different kernel receptive of these maintainers, so that the companies employing them can still have a kernel that is developed for their use-cases whilst supporting projects that don’t so openly collaborate with hostile states.
Geopolitical propaganda spotted. Reporting…
No, but they can host the infrastructure so that excluded developers (the ones that just so happen to be Russian) along with whomever will want (BRICS developers for instance) can surely contribute.