Official statement regarding recent Greg’ commit 6e90b675cf942e from Serge Semin

Hello Linux-kernel community,

I am sure you have already heard the news caused by the recent Greg’ commit 6e90b675cf942e (“MAINTAINERS: Remove some entries due to various compliance requirements.”). As you may have noticed the change concerned some of the Ru-related developers removal from the list of the official kernel maintainers, including me.

The community members rightly noted that the quite short commit log contained very vague terms with no explicit change justification. No matter how hard I tried to get more details about the reason, alas the senior maintainer I was discussing the matter with haven’t given an explanation to what compliance requirements that was. I won’t cite the exact emails text since it was a private messaging, but the key words are “sanctions”, “sorry”, “nothing I can do”, “talk to your (company) lawyer”… I can’t say for all the guys affected by the change, but my work for the community has been purely volunteer for more than a year now (and less than half of it had been payable before that). For that reason I have no any (company) lawyer to talk to, and honestly after the way the patch has been merged in I don’t really want to now. Silently, behind everyone’s back, bypassing the standard patch-review process, with no affected developers/subsystem notified - it’s indeed the worse way to do what has been done. No gratitude, no credits to the developers for all these years of the devoted work for the community. No matter the reason of the situation but haven’t we deserved more than that? Adding to the GREDITS file at least, no?..

I can’t believe the kernel senior maintainers didn’t consider that the patch wouldn’t go unnoticed, and the situation might get out of control with unpredictable results for the community, if not straight away then in the middle or long term perspective. I am sure there have been plenty ways to solve the problem less harmfully, but they decided to take the easiest path. Alas what’s done is done. A bifurcation point slightly initiated a year ago has just been fully implemented. The reason of the situation is obviously in the political ground which in this case surely shatters a basement the community has been built on in the first place. If so then God knows what might be next (who else might be sanctioned…), but the implemented move clearly sends a bad signal to the Linux community new comers, to the already working volunteers and hobbyists like me.

Thus even if it was still possible for me to send patches or perform some reviews, after what has been done my motivation to do that as a volunteer has simply vanished. (I might be doing a commercial upstreaming in future though). But before saying goodbye I’d like to express my gratitude to all the community members I have been lucky to work with during all these years.

  • 0x4E4F@infosec.pubOP
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    5
    ·
    edit-2
    1 month ago

    because the santion load is just going to increase and more countries will be included.

    Not to mention more stupid shit, like not being able to visit the US if your wife is Russian, cuz… you know, you might be a spy.

    If they are just doing this because of a political fad and partaking “the current thing” then they are just voluntarily digging their own and the linux foundation’s grave.

    My 2 cents. Nobody is asking them to do anything… yet… and they probably never will, but… they’re scared shitless and they would rather comply, even for things no one is asking of them yet and is dubious whether or not they’re even covered by the sanctions, than show some backbone.

    • prole@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      5
      arrow-down
      6
      ·
      edit-2
      30 days ago

      Here’s an idea: don’t invade sovereign nations unprovoked.

      (Can’t wait for the inevitable “whatabout America?!” reply. Yes, America is shit too and we deserved to be punished for Iraq… Unfortunately there wasn’t really any international authority that could do it)

      • 0x4E4F@infosec.pubOP
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        29 days ago

        Here’s an idea: don’t invade sovereign nations unprovoked.

        That is a great idea! Unfortunately, not everyone has a say in that, especially mere mortals… you know, people like devs.

        Unfortunately there wasn’t really any international authority that could do it

        There is, the UN, but they silent, as always… at least regarding the US. We all know why…

        • Auli@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          29 days ago

          Sure but they are working for sanctioned companies. Which from comments in thread are part of the Russian war machine. They do have that choice.

          • mihor
            link
            fedilink
            arrow-up
            4
            arrow-down
            1
            ·
            29 days ago

            ‘Russian war machine’ - is this perhaps similar to the ‘US Military-Industrial Complex’ that happily delivers bombs to IDF so they can slaughter women and children? It never bothered the peace-loving Linus enough to restrict military use of his kernel…

          • 0x4E4F@infosec.pubOP
            link
            fedilink
            English
            arrow-up
            2
            ·
            28 days ago

            Let’s say that this company pays the best $$$ and that you really need money for… whatever… now, let’s reverse the roles and this person is working for a company that has contracts with the US military during the time of the invasion of Iraq.

            See my point… there would have been nothing wrong with that, but all of sudden, it’s a problem if Russians do it 🤨…