Gist: “Evidently, starting next month, all external code contributions to AOSP will require approval from two Google reviewers before they can be submitted.”

  • smileyhead@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    28
    ·
    1 year ago

    Before anyone raises their pitchforks: Google already has to accept changes made to Android, like any project ever created. The change is only that there now has to be two people instead of one.

    Yes, Android is moving in bad direction in user freedom perspective, but please don’t react hostile to every single news about Android, because then you show community caring about this stuff as being crazy.

    • Polar
      link
      fedilink
      English
      arrow-up
      28
      ·
      1 year ago

      You’re honestly turning this into a weird negative thing? Better security by having two people review the code vs just one is a bad thing to you?

      Alright.

      • On@kbin.social
        link
        fedilink
        arrow-up
        3
        arrow-down
        3
        ·
        1 year ago

        what about this? https://kbin.social/m/[email protected]/t/467656/To-improve-security-Google-s-making-it-slightly-harder-to-contribute#entry-comment-2442599

        Google is not making Android for users, but itself as its advertising platform. Ever wonder why custom ROMs and even other manufacturers have a permission to block internet access for specific apps in their Android forks but Google does not? hmm… Alright

        Google isn’t looking out for anyone but itself. These kind of restrictions and excuses are exactly what Apple calls “security”.

        • Kayn@dormi.zone
          link
          fedilink
          English
          arrow-up
          12
          ·
          1 year ago

          Yes, Google sucks, but what does this have to do with requiring additional approvals for code contributions?

          What is Google going to restrict now with 2 required approval, which they couldn’t with 1?

    • ExtremeDullard@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      You are free to fork AOSP and maintain your own fork if you have the resources.

      Unfortunately not many people / organizations do or have the stomach to commit to doing that, and that’s how Google is able to maintain a tight grip on what is supposed to be an open source project.

      • sv1sjp@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        1 year ago

        Well…lets pretend that with SafetyNet they don’t enforce people to stay away from Foss android. I mean, yes, I am running DivestOS, but a lot of APS are not working because they need Google Play Services. Some other they don’t even want you to have an unlocked bootloader. Most of Android devices do not support relocking your bootloader…