• jaybone@lemmy.world
    link
    fedilink
    arrow-up
    29
    arrow-down
    3
    ·
    24 days ago

    It’s like exactly what I said they would do after the original news of the bans from the other day. And I got downvoted for it. Lol

        • Cornelius@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          23 days ago

          Dunno why this is being down voted, obviously they’ll make their own fork and it’ll likely be no different than the regular kernel and they’ll just be constantly rebasing

          • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            22 days ago

            That’s likely what’s going to happen in short to medium term, but it’s quite possible it’ll diverge eventually. We can look at Huawei forking Android as an example here, they kept it largely compatible for a few years, and then started taking things in a new direction that broke compatibility. Between Russia and China alone there’s a huge pool of talented developers who can rival anything developers in the west can do.

    • ReakDuck@lemmy.ml
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      24 days ago

      Especially, because they can chose existing names as there is no Copyright in Russia (afaik, probably a wrong myth but idk)

      • OwlPaste@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        24 days ago

        No there was copyright, it was only relatively enforced between 2000-2015 ish. And then probably only in tourist heavy areas. In the olden days you could find any soft on “black markets” in open stalls

    • OwlPaste@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      1
      ·
      edit-2
      24 days ago

      Will we finally get the “Putinix” distribution that mines cryptocurrency for the regime by default? It will have to be a new coin called “RuOil”

    • tetris11@lemmy.ml
      link
      fedilink
      arrow-up
      12
      arrow-down
      1
      ·
      24 days ago

      At first I thought you meant it’d be a bad fork, but then I realise you meant it’d be a bad fork.

      As long as it’s open source and vetted by the public, I don’t see how it could go bad tbh

        • tetris11@lemmy.ml
          link
          fedilink
          arrow-up
          5
          ·
          23 days ago

          then it wont be linux, but a shittily maintained private copy that will fall out of disuse quickly unless they merge all upstream changes without too much oversight (in which case, why bother?) to keep feature parity

          • Zangoose@lemmy.world
            link
            fedilink
            arrow-up
            3
            arrow-down
            1
            ·
            edit-2
            23 days ago

            You’re not wrong but it’s not like it’s unprecedented. North Korea already does this with Red Star OS. It’s just Linux with a bunch of spyware and government tracking/surveillance on top (edit: it’s also definitely not open source)

    • Dessalines@lemmy.ml
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      23 days ago

      For sure, stuxnet is just the beginning, who knows what the US will subject the world to next.

  • Em Adespoton@lemmy.ca
    link
    fedilink
    arrow-up
    50
    arrow-down
    6
    ·
    25 days ago

    They haven’t been removed from the community though — just the maintainers list. Now they need someone else’s review to commit code to the kernel.

    Personally, I think even maintainers should be required to have that — you can be the committer for pre-reviewed code from others, but not just be able to check anything you want in, no matter your reputation (even if you’re Linus). That way a security breach is less likely to cause havoc.

    • Ephera@lemmy.ml
      link
      fedilink
      arrow-up
      16
      arrow-down
      2
      ·
      25 days ago

      I find that difficult. Aside from code reviews, often times your job as a maintainer is:

      • getting a refactor or code cleanup in while everyone’s asleep
      • shuffling commits around between branches
      • fixing the CI toolchain
      • rolling back or repairing a broken change
      • unfucking the repo
      • fixing a security vulnerability

      A required review slows all of these tasks to a crawl. I do agree that the kernel is important enough that it might be worth the trade-off.
      But at the same, I do not feel like I could do my (non-kernel) maintainer job without direct commit access…

      • Em Adespoton@lemmy.ca
        link
        fedilink
        arrow-up
        6
        ·
        edit-2
        24 days ago

        I feel your pain. I have maintainer roles for a few projects where things could be slowed down by a week or more if I didn’t have direct commit access. And I do use that access to make things run faster and smoother, and am able to step in and just get something fixed up and committed while everyone else is asleep. But. For security critical code paths, I’ve come to realize that much like Debian, sometimes slow and secure IS better, even if it doesn’t feel like it in the moment (like when you’re trying to commit and deploy a critical security patch already being exploited in the wild, and NOBODY is around to do the review, or there’s something upstream that needs to be fixed before your job can go out).